From: santosh.shilimkar@oracle.com
To: Grygorii Strashko <grygorii.strashko@ti.com>,
Dave Gerlach <d-gerlach@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Tero Kristo <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Lokesh Vutla <lokeshvutla@ti.com>
Cc: Sekhar Nori <nsekhar@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/5] soc: ti: add k3 platforms chipid module driver
Date: Fri, 1 May 2020 14:25:17 -0700 [thread overview]
Message-ID: <8fa7126c-3a26-442c-b239-9969d65d4a19@oracle.com> (raw)
In-Reply-To: <23b3b069-426e-a113-a8bf-816b30f10490@ti.com>
On 5/1/20 1:55 PM, Grygorii Strashko wrote:
> Hi Santosh, Tero
>
> On 23/04/2020 21:05, Grygorii Strashko wrote:
>> Hi All,
>>
>> This series introduces TI K3 Multicore SoC platforms chipid module driver
>> which provides identification support of the TI K3 SoCs (family,
>> revision)
>> and register this information with the SoC bus. It is available under
>> /sys/devices/soc0/ for user space, and can be checked, where needed,
>> in Kernel using soc_device_match().
>> It is also required for introducing support for new revisions of
>> K3 AM65x/J721E SoCs.
>>
>> Example J721E:
>> # cat /sys/devices/soc0/{machine,family,revision}
>> Texas Instruments K3 J721E SoC
>> J721E
>> SR1.0
>>
>> Example AM65x:
>> # cat /sys/devices/soc0/{machine,family,revision}
>> Texas Instruments AM654 Base Board
>> AM65X
>> SR1.0
>>
>> Grygorii Strashko (5):
>> dt-bindings: soc: ti: add binding for k3 platforms chipid module
>> soc: ti: add k3 platforms chipid module driver
>> arm64: arch_k3: enable chipid driver
>> arm64: dts: ti: k3-am65-wakeup: add k3 platforms chipid module node
>> arm64: dts: ti: k3-j721e-mcu-wakeup: add k3 platforms chipid module
>> node
>>
>> .../bindings/soc/ti/k3-socinfo.yaml | 40 ++++++
>> arch/arm64/Kconfig.platforms | 1 +
>> arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 5 +
>> .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 5 +
>> drivers/soc/ti/Kconfig | 10 ++
>> drivers/soc/ti/Makefile | 1 +
>> drivers/soc/ti/k3-socinfo.c | 135 ++++++++++++++++++
>> 7 files changed, 197 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/soc/ti/k3-socinfo.yaml
>> create mode 100644 drivers/soc/ti/k3-socinfo.c
>>
>
> Any more comments? I'm going resend it.
>
If you have acks from DT maintainers, then I suggest you to split this
series and post platform and drivers patches separately.
Regards,
Santosh
prev parent reply other threads:[~2020-05-01 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 18:05 [PATCH 0/5] soc: ti: add k3 platforms chipid module driver Grygorii Strashko
2020-04-23 18:05 ` [PATCH 1/5] dt-bindings: soc: ti: add binding for k3 platforms chipid module Grygorii Strashko
2020-05-04 9:38 ` Grygorii Strashko
2020-04-23 18:05 ` [PATCH 2/5] soc: ti: add k3 platforms chipid module driver Grygorii Strashko
2020-04-24 4:36 ` Lokesh Vutla
2020-04-23 18:05 ` [PATCH 3/5] arm64: arch_k3: enable chipid driver Grygorii Strashko
2020-04-23 18:05 ` [PATCH 4/5] arm64: dts: ti: k3-am65-wakeup: add k3 platforms chipid module node Grygorii Strashko
2020-04-23 18:05 ` [PATCH 5/5] arm64: dts: ti: k3-j721e-mcu-wakeup: " Grygorii Strashko
2020-05-01 20:55 ` [PATCH 0/5] soc: ti: add k3 platforms chipid module driver Grygorii Strashko
2020-05-01 21:25 ` santosh.shilimkar [this message]
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=8fa7126c-3a26-442c-b239-9969d65d4a19@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=catalin.marinas@arm.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.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).