Re: [PATCH v3] Add new `export-symbols` node
Ayush Singh <[email protected]>
| Newsgroups | org.kernel.vger.devicetree-spec,org.kernel.vger.linux-devicetree |
|---|---|
| Message-ID | <[email protected]> |
On 4/11/25 23:09, Andrew Davis wrote: > On 4/11/25 3:00 AM, Ayush Singh wrote: >> `export-symbols` is designed to be a local replacement of global >> `__symbols__` allowing nodes to define aliases to nodes in a tree, which >> will take precedence over the aliases defined in the global >> `__symbols__`. >> >> Having a way to allow node local aliases helps in usecases such as >> connectors and addon-boards, by allowing decoupling of >> overlays/devicetree nodes of addon-board from the base connector. >> >> Reviewed-by: Herve Codina <[email protected]> >> Reviewed-by: Luca Ceresoli <[email protected]> >> Signed-off-by: Ayush Singh <[email protected]> >> --- >> This patch series follows the initial RFC [9] sent a few weeks ago. I >> will be reiterating the RFC here for anyone who might be seeing this the >> first time, since there was not much feedback in that thread. >> > > I think this is a useful tool in the effort to build a complete > addon-board > solution. But I'm still missing how it all fits together, do you have > a real > working overlay making use of this somewhere I could take a look at? > Maybe > an overlay for one of the addon-boards you list below (one of the > BeagleCapes > for instance). > > Andrew Well, I do not have a completely working for MikroBUS right now, but I think Herve Codina and Luca Ceresolli should have some working overlays for their addon-board setups, so maybe they can link those here. I have mostly been working on devicetree side of things to make it more general devicetree thing rather just a Linux thing (Zephyr also needs MikroBUS support). Additionally, I have been trying to get the support in base fdtoverlay, so that static use-cases are also covered. I will try posting a MikroBUS patch based on the kernel export-symbols support patches [0] soon to maybe provide a better picture regarding how all the pieces fit together. The spec patch series was supposed to be for getting initial feedback regarding this particular direction, but I guess to get real feedback, I need some more concrete prototypes. Best Regards, Ayush Singh [0]: https://lore.kernel.org/all/[email protected]/