Message ID | 20200512123449.16517-1-grygorii.strashko@ti.com (mailing list archive) |
---|---|
Headers | show |
Series | soc: ti: add k3 platforms chipid module driver | expand |
Hi Santosh, On 12/05/2020 15:34, 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 v4: > - convert to platform_driver as suggested by Arnd Bergmann <arnd@arndb.de> > > Changes in v3: > - add handling of kasprintf() fail > > 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> > > v3: https://lkml.org/lkml/2020/5/8/357 > v2: https://lkml.org/lkml/2020/5/5/1193 > 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 > > .../bindings/soc/ti/k3-socinfo.yaml | 40 +++++ > drivers/soc/ti/Kconfig | 10 ++ > drivers/soc/ti/Makefile | 1 + > drivers/soc/ti/k3-socinfo.c | 152 ++++++++++++++++++ > 4 files changed, 203 insertions(+) > create mode 100644 Documentation/devicetree/bindings/soc/ti/k3-socinfo.yaml > create mode 100644 drivers/soc/ti/k3-socinfo.c > Any chances you can pick this up?
On Fri, May 29, 2020 at 8:22 PM Grygorii Strashko <grygorii.strashko@ti.com> wrote: > On 12/05/2020 15:34, Grygorii Strashko wrote: > > .../bindings/soc/ti/k3-socinfo.yaml | 40 +++++ > > drivers/soc/ti/Kconfig | 10 ++ > > drivers/soc/ti/Makefile | 1 + > > drivers/soc/ti/k3-socinfo.c | 152 ++++++++++++++++++ > > 4 files changed, 203 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/soc/ti/k3-socinfo.yaml > > create mode 100644 drivers/soc/ti/k3-socinfo.c > > > > Any chances you can pick this up? I merged a version of this driver from Santosh's pull request into the arm/drviers tree yesterday. Is there something missing? Arnd
On 5/29/20 11:34 AM, Arnd Bergmann wrote: > On Fri, May 29, 2020 at 8:22 PM Grygorii Strashko > <grygorii.strashko@ti.com> wrote: >> On 12/05/2020 15:34, Grygorii Strashko wrote: > >>> .../bindings/soc/ti/k3-socinfo.yaml | 40 +++++ >>> drivers/soc/ti/Kconfig | 10 ++ >>> drivers/soc/ti/Makefile | 1 + >>> drivers/soc/ti/k3-socinfo.c | 152 ++++++++++++++++++ >>> 4 files changed, 203 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/soc/ti/k3-socinfo.yaml >>> create mode 100644 drivers/soc/ti/k3-socinfo.c >>> >> >> Any chances you can pick this up? > > I merged a version of this driver from Santosh's pull request into the > arm/drviers tree yesterday. > > Is there something missing? > Nope. I was going to reply on the thread but missed it. Regards, Santosh
On 29/05/2020 22:19, santosh.shilimkar@oracle.com wrote: > On 5/29/20 11:34 AM, Arnd Bergmann wrote: >> On Fri, May 29, 2020 at 8:22 PM Grygorii Strashko >> <grygorii.strashko@ti.com> wrote: >>> On 12/05/2020 15:34, Grygorii Strashko wrote: >> >>>> .../bindings/soc/ti/k3-socinfo.yaml | 40 +++++ >>>> drivers/soc/ti/Kconfig | 10 ++ >>>> drivers/soc/ti/Makefile | 1 + >>>> drivers/soc/ti/k3-socinfo.c | 152 ++++++++++++++++++ >>>> 4 files changed, 203 insertions(+) >>>> create mode 100644 Documentation/devicetree/bindings/soc/ti/k3-socinfo.yaml >>>> create mode 100644 drivers/soc/ti/k3-socinfo.c >>>> >>> >>> Any chances you can pick this up? >> >> I merged a version of this driver from Santosh's pull request into the >> arm/drviers tree yesterday. >> >> Is there something missing? >> > Nope. I was going to reply on the thread but missed it. Oh. Thanks. I've missed that it was already picked up. Thanks again.