From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, harb@amperecomputing.com,
Sudeep Holla <sudeep.holla@arm.com>,
Will Deacon <will@kernel.org>
Subject: [PATCH 0/2] base: soc: Add JEP106 manufacturer's identification code
Date: Fri, 22 May 2020 13:49:49 +0100 [thread overview]
Message-ID: <20200522124951.35776-1-sudeep.holla@arm.com> (raw)
Hi,
While attempting to add custom sysfs attributes for SMCCC ARCH_SOC_ID
Arnd suggested to make it generic. Here is my first attempt.
The original thread/discussion can be found here[1]
Regards,
Sudeep
[1] https://lore.kernel.org/r/CAK8P3a3dV0B26XE3oFQGTFf8EWV0AHoLudNtpSSB_t+pCfkOkQ@mail.gmail.com/
Sudeep Holla (2):
base: soc: Add JEDEC JEP106 manufacturer's identification code attribute
firmware: smccc: Add ARCH_SOC_ID support
Documentation/ABI/testing/sysfs-devices-soc | 31 ++++++
drivers/base/soc.c | 12 +++
drivers/firmware/smccc/Kconfig | 9 ++
drivers/firmware/smccc/Makefile | 1 +
drivers/firmware/smccc/soc_id.c | 113 ++++++++++++++++++++
include/linux/arm-smccc.h | 5 +
include/linux/sys_soc.h | 1 +
7 files changed, 172 insertions(+)
create mode 100644 drivers/firmware/smccc/soc_id.c
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-05-22 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 12:49 Sudeep Holla [this message]
2020-05-22 12:49 ` [PATCH 1/2] base: soc: Add JEDEC JEP106 manufacturer's identification code attribute Sudeep Holla
2020-05-22 12:49 ` [PATCH 2/2] firmware: smccc: Add ARCH_SOC_ID support Sudeep Holla
2020-05-22 14:46 ` Arnd Bergmann
2020-05-22 16:54 ` Sudeep Holla
2020-05-22 17:13 ` Sudeep Holla
2020-05-22 18:41 ` Arnd Bergmann
2020-05-23 17:27 ` Sudeep Holla
2020-05-23 19:40 ` Arnd Bergmann
2020-05-28 13:05 ` Jose Marinho
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=20200522124951.35776-1-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=harb@amperecomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).