From: santosh.shilimkar@oracle.com
To: Grygorii Strashko <grygorii.strashko@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>,
devicetree@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>, Dave Gerlach <d-gerlach@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Tero Kristo <t-kristo@ti.com>,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2 0/2] soc: ti: add k3 platforms chipid module driver
Date: Tue, 5 May 2020 16:21:17 -0700 [thread overview]
Message-ID: <c091ac42-ac28-477c-90a9-4bbe790d42f7@oracle.com> (raw)
In-Reply-To: <20200505193417.2112-1-grygorii.strashko@ti.com>
On 5/5/20 12:34 PM, 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
>
> Changes in v2:
> - pr_debug() replaced with pr_info() to show SoC info on init
> - minor format change
> - split series on driver and platform changes
> - add Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
>
> v1: https://lwn.net/Articles/818577/
>
> Grygorii Strashko (2):
> dt-bindings: soc: ti: add binding for k3 platforms chipid module
> soc: ti: add k3 platforms chipid module driver
>
Need ack from DT maintainers on bindings.
Regards,
Santosh
next prev parent reply other threads:[~2020-05-05 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 19:34 Grygorii Strashko
2020-05-05 19:34 ` [PATCH v2 1/2] dt-bindings: soc: ti: add binding for k3 platforms chipid module Grygorii Strashko
2020-05-06 19:21 ` Grygorii Strashko
2020-05-05 19:34 ` [PATCH v2 2/2] soc: ti: add k3 platforms chipid module driver Grygorii Strashko
2020-05-07 11:46 ` Tero Kristo
2020-05-05 23:21 ` santosh.shilimkar [this message]
2020-05-07 11:47 ` [PATCH v2 0/2] " Tero Kristo
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=c091ac42-ac28-477c-90a9-4bbe790d42f7@oracle.com \
--to=santosh.shilimkar@oracle.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 \
/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
all inboxes | Powered by JetHome®