However, we should carefully read the notice (*) in the manufacturer's
datasheet. For example, some interfaces may not be used in a connector. Or the
carrier board has power limitations for the module and we should limit this
during initialization. But this is the problem of people who will be adding the
code for these boards :) They need to take these specifics into account when
initializing the board.

I had the idea to re-use the devicetree alias mechanism to support
carriers with different modules. The modules would declare aliases
with the names from the COMe standard and the carriers would be able
to pick them up and add devices below these interfaces. This would
automatically catch incompatibilities because of the optional/alter-
native interfaces COMe allows (sconfig wouldn't be able to link them).

I guess it would be most useful for evaluation carriers, but probably
not much beyond. And as I never write complete support for them, I
didn't put any effort into it yet.

View Change

To view, visit change 42609. To unsubscribe, or for help writing mail filters, visit settings.