From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: Andrew Davis <afd@ti.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Markus Schneider-Pargmann <msp@baylibre.com>
Subject: [PATCH 0/4] soc: ti: k3-socinfo: Add support for nvmem cells
Date: Tue, 6 Feb 2024 15:37:07 +0100 [thread overview]
Message-ID: <20240206143711.2410135-1-msp@baylibre.com> (raw)
Hi,
am62 has a number of efuse fields that are situated in the device range
of the current chipid device node. As other devices require these
information as well, I am trying to establish a new nvmem layout for the
information available in this register range.
In this series the conflicting chipid driver is updated to support
nvmem-cells and the chipid node gets the register range removed and
replaced with nvmem cells on am62.
In a follow-up series the opp table will be updated.
Best,
Markus
Markus Schneider-Pargmann (4):
nvmem: core: Read into buffers larger than data
dt-bindings: hwinfo: ti,k3-socinfo: Add nvmem-cells
soc: ti: k3-socinfo: Add support for nvmem cells
arm64: dts: ti: k3-am62-wakeup: Add chip efuse nodes
.../bindings/hwinfo/ti,k3-socinfo.yaml | 23 ++++++-
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 36 +++++++++-
drivers/nvmem/core.c | 6 +-
drivers/soc/ti/k3-socinfo.c | 67 +++++++++++++------
4 files changed, 107 insertions(+), 25 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-06 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:37 Markus Schneider-Pargmann [this message]
2024-02-06 14:37 ` [PATCH 1/4] nvmem: core: Read into buffers larger than data Markus Schneider-Pargmann
2024-02-06 22:07 ` Srinivas Kandagatla
2024-02-06 14:37 ` [PATCH 2/4] dt-bindings: hwinfo: ti,k3-socinfo: Add nvmem-cells Markus Schneider-Pargmann
2024-02-06 18:23 ` Rob Herring
2024-02-06 18:43 ` Rob Herring
2024-02-14 9:31 ` Markus Schneider-Pargmann
2024-02-17 14:25 ` Krzysztof Kozlowski
2024-03-04 10:36 ` Markus Schneider-Pargmann
2024-03-05 7:43 ` Krzysztof Kozlowski
2024-03-05 11:17 ` Markus Schneider-Pargmann
2024-03-05 14:11 ` Krzysztof Kozlowski
2024-03-05 14:42 ` Andrew Davis
2024-03-05 17:01 ` Krzysztof Kozlowski
2024-03-05 17:41 ` Andrew Davis
2024-03-18 16:10 ` Markus Schneider-Pargmann
2024-02-07 7:58 ` Krzysztof Kozlowski
2024-02-06 14:37 ` [PATCH 3/4] soc: ti: k3-socinfo: Add support for nvmem cells Markus Schneider-Pargmann
2024-02-06 14:37 ` [PATCH 4/4] arm64: dts: ti: k3-am62-wakeup: Add chip efuse nodes Markus Schneider-Pargmann
2024-02-06 17:48 ` Andrew Davis
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=20240206143711.2410135-1-msp@baylibre.com \
--to=msp@baylibre.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@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®