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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 8 Oct 2019 17:43:46 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Stephen Boyd <swboyd@...omium.org>
Cc:     Murali Nalajala <mnalajal@...eaurora.org>, rafael@...nel.org,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        bjorn.andersson@...aro.org
Subject: Re: [PATCH v2] base: soc: Handle custom soc information sysfs entries

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@...eaurora.org>
> > ---
> 
> Reviewed-by: Stephen Boyd <swboyd@...omium.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.

thanks,

greg k-h