All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
	Murali Nalajala <mnalajal@codeaurora.org>,
	rafael@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] base: soc: Handle custom soc information sysfs entries
Date: Tue, 8 Oct 2019 11:06:31 -0700	[thread overview]
Message-ID: <20191008180631.GI63675@minitux> (raw)
In-Reply-To: <20191008154346.GA2881455@kroah.com>

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

  parent reply	other threads:[~2019-10-08 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 20:37 [PATCH v2] base: soc: Handle custom soc information sysfs entries Murali Nalajala
2019-10-08 15:33 ` Stephen Boyd
2019-10-08 15:43   ` Greg KH
2019-10-08 17:10     ` mnalajal
2019-10-08 17:17       ` Greg KH
2019-10-08 18:06     ` Bjorn Andersson [this message]
2019-10-08 18:06 ` Bjorn Andersson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191008180631.GI63675@minitux \
    --to=bjorn.andersson@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mnalajal@codeaurora.org \
    --cc=rafael@kernel.org \
    --cc=swboyd@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.