From: Greg KH <gregkh@linuxfoundation.org>
To: mnalajal@codeaurora.org
Cc: rafael@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, bjorn.andersson@linaro.org
Subject: Re: [PATCH] base: soc: Handle custom soc information sysfs entries
Date: Thu, 3 Oct 2019 20:28:32 +0200 [thread overview]
Message-ID: <20191003182832.GA3579521@kroah.com> (raw)
In-Reply-To: <dd126bd256feb2e32f38409b2a7ba5cc@codeaurora.org>
On Thu, Oct 03, 2019 at 11:17:39AM -0700, mnalajal@codeaurora.org wrote:
> On 2019-10-03 00:05, Greg KH wrote:
> > On Wed, Oct 02, 2019 at 05:06:14PM -0700, Murali Nalajala wrote:
> > > 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>
> > > ---
> > > drivers/base/soc.c | 26 ++++++++++++++++++--------
> > > include/linux/sys_soc.h | 1 +
> > > 2 files changed, 19 insertions(+), 8 deletions(-)
> >
> > Can you change a soc driver to use this? I don't think that this patch
> > works because:
> >
> > >
> > > diff --git a/drivers/base/soc.c b/drivers/base/soc.c
> > > index 7c0c5ca..ec70a58 100644
> > > --- a/drivers/base/soc.c
> > > +++ b/drivers/base/soc.c
> > > @@ -15,6 +15,8 @@
> > > #include <linux/err.h>
> > > #include <linux/glob.h>
> > >
> > > +#define NUM_ATTR_GROUPS 3
> > > +
> > > static DEFINE_IDA(soc_ida);
> > >
> > > static ssize_t soc_info_get(struct device *dev,
> > > @@ -104,11 +106,6 @@ static ssize_t soc_info_get(struct device *dev,
> > > .is_visible = soc_attribute_mode,
> > > };
> > >
> > > -static const struct attribute_group *soc_attr_groups[] = {
> > > - &soc_attr_group,
> > > - NULL,
> > > -};
> > > -
> > > static void soc_release(struct device *dev)
> > > {
> > > struct soc_device *soc_dev = container_of(dev, struct soc_device,
> > > dev);
> > > @@ -121,6 +118,7 @@ static void soc_release(struct device *dev)
> > > struct soc_device *soc_device_register(struct soc_device_attribute
> > > *soc_dev_attr)
> > > {
> > > struct soc_device *soc_dev;
> > > + const struct attribute_group **soc_attr_groups = NULL;
> > > int ret;
> > >
> > > if (!soc_bus_type.p) {
> > > @@ -136,10 +134,20 @@ struct soc_device *soc_device_register(struct
> > > soc_device_attribute *soc_dev_attr
> > > goto out1;
> > > }
> > >
> > > + soc_attr_groups = kzalloc(sizeof(*soc_attr_groups) *
> > > + NUM_ATTR_GROUPS, GFP_KERNEL);
> > > + if (!soc_attr_groups) {
> > > + ret = -ENOMEM;
> > > + goto out2;
> > > + }
> > > + soc_attr_groups[0] = &soc_attr_group;
> > > + soc_attr_groups[1] = soc_dev_attr->custom_attr_group;
> > > + soc_attr_groups[2] = NULL;
> >
> > You set this, but never do anything with it that I can see. What am I
> > missing?
> no, since i am using the "soc_attr_groups" name as it here you do not see
> the assignment below.
> It is something like this soc_dev->dev.groups = soc_attr_groups;
Ah, I see that now. Tricky :)
nice work,
greg k-h
next prev parent reply other threads:[~2019-10-03 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 0:06 [PATCH] base: soc: Handle custom soc information sysfs entries Murali Nalajala
2019-10-03 7:05 ` Greg KH
2019-10-03 18:17 ` mnalajal
2019-10-03 18:28 ` Greg KH [this message]
2019-10-03 7:06 ` Greg KH
2019-10-03 18:23 ` mnalajal
2019-10-03 18:33 ` Greg KH
2019-10-03 21:11 ` mnalajal
2019-10-03 21:36 ` Bjorn Andersson
2019-10-03 23:22 ` Stephen Boyd
2019-10-03 23:44 ` mnalajal
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=20191003182832.GA3579521@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnalajal@codeaurora.org \
--cc=rafael@kernel.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.