On Tue, Dec 14, 2021 at 02:58:55PM +0200, Andy Shevchenko wrote: > When creating MFD platform devices the firmware node is left unset. > This, in particular, prevents GPIO library to use it for different > purposes. Propagate firmware node from the parent device and let > GPIO library do the right thing. > I came across the same thing this week. By populating the of_compatible field of the mfd_cell, the child device will have the appropriate firmware node populated. Unfortunately that currently means that I'll have to put every device type in the MFD instead of in an of_match_table in the child driver itself. Figuring that out is one of the next things on my list.
