Commits on Mar 17, 2024

1. Add descriptors used in mikroBUS manifest …

   mikroBUS addon boards allow using same mikroBUS connector for a wide
   range of peripherals. It is also possible for the addon board not to use
   all the pins in mikroBUS socket (marked by NC or Not Connected). This
   would require the need to create an almost new overlays for each
   permutation of the hardware.
   
   To overcome this, a manifest format based on Greybus manifest
   specification was created which allows describing mikroBUS addon boards.
   The reason for choosing greybus manifest for the identifier is that so far
   we discussed only about physical mikroBUS ports on the board, but we can
   also have mikroBUS ports on a remote microcontroller appearing on host
   over greybus (beagleconnect) and there a device tree overlay solution does
   not work as the standard identifier mechanism.
   
   New mikroBUS addon boards also sometimes contain a 1-wire EEPROM with
   the mikroBUS manifest, thus enabling plug and play support.
   
   There is ongoing work to get mikroBUS deriver merged in mainline linux
   kernel that used mikroBUS manifest for dynamic device identification.
   
   Link: https://www.mikroe.com/clickid ClickID
   Link:
   https://docs.beagleboard.org/latest/projects/beagleconnect/index.html
   beagleconnect
   
   Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>

   

   Ayush1325 committed Mar 17, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for f656a5f
   • Browse repository at this point

   Copy the full SHA

   f656a5f View commit details

   Browse the repository at this point in the history