just curious, do you have a specific use-case in mind for this?

Ah, plenty ;) There has a pattern evolved (I've seen mostly in soc/
intel/common/) where chip specific code is often coupled with
generic drivers just to provide configuration information from the
devicetree. It adds lots of odd boilerplate. What finally made me
write this was `soc/intel/common/blocks/graphics/` where I wanted
to consolidate existing and add more panel configuration. Eventually,
that driver would be standalone then without any soc hooks. The
same probably applies to many more drivers.

There's another, potential long-term idea. I would like to have an
ABI for drivers. For instance, a binary module that could be placed
in CBFS just like an option ROM, that can override `struct device_
operations` functions. That might need more fine-grained configu-
ration too.

View Change

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