Re: [PATCH v2] base: soc: Handle custom soc information sysfs entries

Bjorn Andersson
2019-10-08T18:06:36Z

On Tue 08 Oct 08:43 PDT 2019, Greg KH wrote:

> On Tue, Oct 08, 2019 at 08:33:11AM -0700, Stephen Boyd wrote:
> > Quoting Murali Nalajala (2019-10-07 13:37:42)
> > > Soc framework exposed sysfs entries are not sufficient for some
> > > of the h/w platforms. Currently there is no interface where soc
> > > drivers can expose further information about their SoCs via soc
> > > framework. This change address this limitation where clients can
> > > pass their custom entries as attribute group and soc framework
> > > would expose them as sysfs properties.
> > >
> > > Signed-off-by: Murali Nalajala <mnalajal@codeaurora.org>
> > > ---
> >
> > Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> >
>
> Nice, can we convert the existing soc drivers to use this interface
> instead of the "export the device pointer" mess that they currently
> have? That way we can drop that function entirely.
>

Unfortunately we can't just drop it, because it's used on some SoCs as
the parent of all platform_devices.

But we can definitely get rid of all that uses it to create sysfs files.

Regards,
Bjorn