[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220703183449.12917-1-krzysztof.kozlowski@linaro.org>
Date: Sun, 3 Jul 2022 20:34:47 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Geert Uytterhoeven <geert+renesas@...der.be>,
Magnus Damm <magnus.damm@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Nishanth Menon <nm@...com>,
Vignesh Raghavendra <vigneshr@...com>,
Tero Kristo <kristo@...nel.org>,
linux-renesas-soc@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: [PATCH v2 0/2] dt-bindings: hwinfo: group devices and add s5pv210-chipid
Hi,
As suggested by Rob [1], I organized a bit bindings for SoC devices having
similar purpose - chip identification.
These sometimes are put under nvmem directory, although in that case the
purpose is usually broader than just chipid.
Best regards,
Krzysztof
Krzysztof Kozlowski (2):
dt-bindings: hwinfo: group Chip ID-like devices
dt-bindings: hwinfo: samsung,s5pv210-chipid: add S5PV210 ChipID
.../{soc/renesas => hwinfo}/renesas,prr.yaml | 2 +-
.../samsung,exynos-chipid.yaml} | 2 +-
.../hwinfo/samsung,s5pv210-chipid.yaml | 30 +++++++++++++++++++
.../ti,k3-socinfo.yaml} | 2 +-
MAINTAINERS | 3 ++
5 files changed, 36 insertions(+), 3 deletions(-)
rename Documentation/devicetree/bindings/{soc/renesas => hwinfo}/renesas,prr.yaml (92%)
rename Documentation/devicetree/bindings/{soc/samsung/exynos-chipid.yaml => hwinfo/samsung,exynos-chipid.yaml} (92%)
create mode 100644 Documentation/devicetree/bindings/hwinfo/samsung,s5pv210-chipid.yaml
rename Documentation/devicetree/bindings/{soc/ti/k3-socinfo.yaml => hwinfo/ti,k3-socinfo.yaml} (92%)
--
2.34.1
Powered by blists - more mailing lists