On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: [...] > > In your case the platform code that adds the lookup may be identical to > > the code that registers the struct reset_controller_dev, but that > > doesn't have to be the case. I'm not sure how that is supposed to work > > for the phy framework (I see no platform code adding phy lookups, only > > drivers). > > > In our use case, we would be adding the lookup in the driver rather than > in the platform code, which is why I am suggesting doing it like the phy > framework.
Shouldn't it be the job of the platform code to describe the connections between reset controller and peripheral module reset inputs? regards Philipp
