← Thread:Talk:BeagleBoard/Mikrobus Support/Phases/reply
Could you please clarify if my understanding of the approach is in the right direction?
mikroBUS bus driver with gbsim
Modify Greybus to include Mikrobus under GB Bridged Phy similar to other PHY bus like I2C,SPI . So when a manifest under this category is loaded, then all the greybus interfaces(virtual interfaces for each perpiheral on the mikroBUS: I2C,SPI,GPIO,...) are created and then the corresponding new_device(or similar) call in the mikrobus bus driver is made with the platform data for the device fetched from the manifest to instantiate the device on the bus(greybus created mikrobus), the bus driver then completes the platform data structure for the device and call the device driver to instantiate the device on the bus(virtual greybus). gbsim takes care of the transport(greybus mikrobus<->physical mikrobus).
Instantiate the driver on PocketBeagle+TechLab using whatever device tree entries you need to define it. Define the bus, not any of the devices.
I have one more doubt(maybe dumb), in this case the Mikrobus Driver doesn't do the transport(greybus<->physical) right? So why does it require information about the actual physical Mikrobus? Is it Possible(feasible) to include the transport in the driver itself? Like this:
- In a suitable device tree entry we define the transport, say 'phy' (where the mikrobus port is on the same device as where kernel greybus is running) then we route out the individual greybus interfaces(SPI/I2C/..) separately to the physical peripheral(SPI/I2C/UART) specified in device tree.
mikroBUS bus driver with I2C EEPROM holding manifest
In this case, the Mikrobus Bus Driver should fetch the manifest blob from an I2C EEPROM(similar to approach done by Bone Cape Manager) and then pass it to greybus(?), so the greybus mikrobus creation and device instantiation happens in the previous manner itself.
Use the Greybus code to parse the manifest, but do not require gbsim to get the data.
In this case who performs the transport?
You do not have permission to edit this page, for the following reasons:
- The action you have requested is limited to users in the group: Users.
- You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.
You can view and copy the source of this page.
mikroBUS bus driver with gbsim
Is 'match' not needed in this case? Could there be a 'match' function that ends up calling the 'match' function for the I2C/SPI/UART busses? How would it determine which buses it needs?
As per my understanding match function is required?Which eventually calls the match function of the individual I2C/SPI/UART buses, I was thinking that the manifest has different Cports in it , so we can structure it like this: say for a click that uses I2C and GPIO resources :
; I2C protocol on CPort 1 [cport-descriptor 1] bundle = 1 protocol = 0x03 property = ...
; GPIO protocol on CPort 2 [cport-descriptor 2] bundle = 2 protocol = 0x02 property = ...
The property field under each Cport specifies the Extra Platform Data, is this feasible? In this case we can get the required information from the manifest itself.
Why would the device tree define the transport? So many confusing terms!!!
This was a misunderstanding, I was thinking of the bus driver's relation with greybus, The bus driver has no direct relation with greybus right? It is just an independent bus driver, mainly for handling of defining the extra platform data while instantiating the click devices(works similar to Cape Bus difference being the data will be fetched from manifest blob, reusing the greybus manifest parsing logic), in the later phase this bus can be added to greybus Phy.
I wonder if it would help if I did a device tree example for instantiating a mikroBUS bus. What do you think? I might add that to the main page as a draft.
This would be really helpful