From: mnalajal@codeaurora.org
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
rafael@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, bjorn.andersson@linaro.org
Subject: Re: [PATCH v2] base: soc: Handle custom soc information sysfs entries
Date: Tue, 08 Oct 2019 10:10:08 -0700 [thread overview]
Message-ID: <463ec0b5a3f1946df0ed2771ba741545@codeaurora.org> (raw)
In-Reply-To: <20191008154346.GA2881455@kroah.com>
On 2019-10-08 08:43, 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.
>
Thank you for the reviews.
In the current linux tree i can find these driver instances who is using
"soc_device_to_device" for populating their sysfs entries.
drivers/soc/ux500/ux500-soc-id.c: parent =
soc_device_to_device(soc_dev);
drivers/soc/tegra/fuse/fuse-tegra.c: return
soc_device_to_device(dev);
drivers/soc/amlogic/meson-gx-socinfo.c: dev =
soc_device_to_device(soc_dev);
drivers/soc/amlogic/meson-mx-socinfo.c:
dev_info(soc_device_to_device(soc_dev), "Amlogic %s %s detected\n",
drivers/soc/imx/soc-imx8.c: ret =
device_create_file(soc_device_to_device(soc_dev),
drivers/soc/imx/soc-imx-scu.c: ret =
device_create_file(soc_device_to_device(soc_dev),
drivers/soc/versatile/soc-realview.c:
device_create_file(soc_device_to_device(soc_dev), &realview_manf_attr);
drivers/soc/versatile/soc-realview.c:
device_create_file(soc_device_to_device(soc_dev), &realview_board_attr);
drivers/soc/versatile/soc-realview.c:
device_create_file(soc_device_to_device(soc_dev), &realview_arch_attr);
drivers/soc/versatile/soc-realview.c:
device_create_file(soc_device_to_device(soc_dev), &realview_build_attr);
drivers/soc/versatile/soc-integrator.c: dev =
soc_device_to_device(soc_dev);
These drivers can use the current proposed approach to expose their
sysfs entries.
Will try to address these and submit. But i can't able to test these
changes because i do not have these h/w's
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2019-10-08 17:10 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 [this message]
2019-10-08 17:17 ` Greg KH
2019-10-08 18:06 ` Bjorn Andersson
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=463ec0b5a3f1946df0ed2771ba741545@codeaurora.org \
--to=mnalajal@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox