From: <patrick.delaunay@foss.st.com>
To: 'Marek Vasut' <marex@denx.de>, <linux-arm-kernel@lists.infradead.org>
Cc: Alexandre TORGUE - foss <alexandre.torgue@foss.st.com>,
'Conor Dooley' <conor+dt@kernel.org>,
'Krzysztof Kozlowski' <krzysztof.kozlowski+dt@linaro.org>,
'Maxime Coquelin' <mcoquelin.stm32@gmail.com>,
'Rob Herring' <robh+dt@kernel.org>,
'Srinivas Kandagatla' <srinivas.kandagatla@linaro.org>,
<devicetree@vger.kernel.org>, <kernel@dh-electronics.com>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: RE: [PATCH v2 3/3] ARM: dts: stm32: Add nvmem-syscon node to TAMP to expose boot count on DHSOM
Date: Fri, 26 May 2023 17:28:51 +0200 [thread overview]
Message-ID: <02ca01d98fe6$ca371d80$5ea55880$@foss.st.com> (raw)
In-Reply-To: <20230517152513.27922-3-marex@denx.de>
Hi Marek,
> From: Marek Vasut <marex@denx.de>
> Sent: Wednesday, May 17, 2023 5:25 PM
> Subject: [PATCH v2 3/3] ARM: dts: stm32: Add nvmem-syscon node to TAMP to
> expose boot count on DHSOM
>
> Add nvmem-syscon subnode to expose TAMP_BKPxR register 19 to user space.
> This register contains U-Boot boot counter, by exposing it to user space the user
> space can reset the boot counter.
>
> Read access example:
> "
> $ hexdump -vC /sys/bus/nvmem/devices/5c00a000.tamp\:nvmem0/nvmem
> 00000000 0c 00 c4 b0
> "
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Cc: devicetree@vger.kernel.org
> Cc: kernel@dh-electronics.com
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-stm32@st-md-mailman.stormreply.com
> ---
> V2: No change
> ---
> arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi | 11 +++++++++++
> arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi | 11 +++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> b/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> index 74735552f4803..b2557bb718f52 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> @@ -537,6 +537,17 @@ &sdmmc3 {
> status = "okay";
> };
>
> +&tamp {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + /* Boot counter */
> + nvmem {
> + compatible = "nvmem-syscon";
> + reg = <0x14c 0x4>;
> + };
> +};
> +
> &uart4 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart4_pins_a>;
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> b/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> index bba19f21e5277..864960387e634 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> @@ -269,3 +269,14 @@ &rng1 {
> &rtc {
> status = "okay";
> };
> +
> +&tamp {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + /* Boot counter */
> + nvmem {
According binding you need to add "@<reg>" => nvmem@14c
And you export only TAMP_BKP19R directly in a nvmem region ?
> + compatible = "nvmem-syscon";
> + reg = <0x14c 0x4>;
> + };
> +};
the boot counter could be a nvem cell so you could expose other backup registers
For example :
&tamp {
#address-cells = <1>;
#size-cells = <1>;
nvmem@14c {
compatible = "nvmem-syscon";
reg = <0x14c 0x4>;
/* Data cells */
boot_counter: boot-counter@14c {
reg = <0x14c 0x4>;
};
};
};
Even if you export more backup register the cell will be correctly described in DT
and could be accessible directly with sysfs without managed offset in userland
with https://lore.kernel.org/lkml/202305240724.z3McDuYM-lkp@intel.com/T/
Or previous serie https://lore.kernel.org/lkml/20211220064730.28806-1-zajec5@gmail.com/
for example to export all the free register:
Reference: https://wiki.st.com/stm32mpu/wiki/STM32MP15_backup_registers
the cell " boot-counter" will be always available for users.
&tamp {
#address-cells = <1>;
#size-cells = <1>;
/* backup register: 10 to 21 */
nvmem@0x128 {
compatible = "nvmem-syscon";
reg = <0x128 0x44>;
/* Data cells */
boot_counter: boot-counter@14c {
reg = <0x14c 0x4>;
};
boot_mode: boot-mode@150 {
reg = <0x150 0x4>;
};
....
};
};
Patrick
> --
> 2.39.2
ST Restricted
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: <patrick.delaunay@foss.st.com>
To: 'Marek Vasut' <marex@denx.de>, <linux-arm-kernel@lists.infradead.org>
Cc: Alexandre TORGUE - foss <alexandre.torgue@foss.st.com>,
'Conor Dooley' <conor+dt@kernel.org>,
'Krzysztof Kozlowski' <krzysztof.kozlowski+dt@linaro.org>,
'Maxime Coquelin' <mcoquelin.stm32@gmail.com>,
'Rob Herring' <robh+dt@kernel.org>,
'Srinivas Kandagatla' <srinivas.kandagatla@linaro.org>,
<devicetree@vger.kernel.org>, <kernel@dh-electronics.com>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: RE: [PATCH v2 3/3] ARM: dts: stm32: Add nvmem-syscon node to TAMP to expose boot count on DHSOM
Date: Fri, 26 May 2023 17:28:51 +0200 [thread overview]
Message-ID: <02ca01d98fe6$ca371d80$5ea55880$@foss.st.com> (raw)
In-Reply-To: <20230517152513.27922-3-marex@denx.de>
Hi Marek,
> From: Marek Vasut <marex@denx.de>
> Sent: Wednesday, May 17, 2023 5:25 PM
> Subject: [PATCH v2 3/3] ARM: dts: stm32: Add nvmem-syscon node to TAMP to
> expose boot count on DHSOM
>
> Add nvmem-syscon subnode to expose TAMP_BKPxR register 19 to user space.
> This register contains U-Boot boot counter, by exposing it to user space the user
> space can reset the boot counter.
>
> Read access example:
> "
> $ hexdump -vC /sys/bus/nvmem/devices/5c00a000.tamp\:nvmem0/nvmem
> 00000000 0c 00 c4 b0
> "
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Cc: devicetree@vger.kernel.org
> Cc: kernel@dh-electronics.com
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-stm32@st-md-mailman.stormreply.com
> ---
> V2: No change
> ---
> arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi | 11 +++++++++++
> arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi | 11 +++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> b/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> index 74735552f4803..b2557bb718f52 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> @@ -537,6 +537,17 @@ &sdmmc3 {
> status = "okay";
> };
>
> +&tamp {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + /* Boot counter */
> + nvmem {
> + compatible = "nvmem-syscon";
> + reg = <0x14c 0x4>;
> + };
> +};
> +
> &uart4 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart4_pins_a>;
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> b/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> index bba19f21e5277..864960387e634 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> @@ -269,3 +269,14 @@ &rng1 {
> &rtc {
> status = "okay";
> };
> +
> +&tamp {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + /* Boot counter */
> + nvmem {
According binding you need to add "@<reg>" => nvmem@14c
And you export only TAMP_BKP19R directly in a nvmem region ?
> + compatible = "nvmem-syscon";
> + reg = <0x14c 0x4>;
> + };
> +};
the boot counter could be a nvem cell so you could expose other backup registers
For example :
&tamp {
#address-cells = <1>;
#size-cells = <1>;
nvmem@14c {
compatible = "nvmem-syscon";
reg = <0x14c 0x4>;
/* Data cells */
boot_counter: boot-counter@14c {
reg = <0x14c 0x4>;
};
};
};
Even if you export more backup register the cell will be correctly described in DT
and could be accessible directly with sysfs without managed offset in userland
with https://lore.kernel.org/lkml/202305240724.z3McDuYM-lkp@intel.com/T/
Or previous serie https://lore.kernel.org/lkml/20211220064730.28806-1-zajec5@gmail.com/
for example to export all the free register:
Reference: https://wiki.st.com/stm32mpu/wiki/STM32MP15_backup_registers
the cell " boot-counter" will be always available for users.
&tamp {
#address-cells = <1>;
#size-cells = <1>;
/* backup register: 10 to 21 */
nvmem@0x128 {
compatible = "nvmem-syscon";
reg = <0x128 0x44>;
/* Data cells */
boot_counter: boot-counter@14c {
reg = <0x14c 0x4>;
};
boot_mode: boot-mode@150 {
reg = <0x150 0x4>;
};
....
};
};
Patrick
> --
> 2.39.2
ST Restricted
next prev parent reply other threads:[~2023-05-26 15:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 15:25 [PATCH v2 1/3] dt-bindings: nvmem: syscon: Add syscon backed nvmem bindings Marek Vasut
2023-05-17 15:25 ` Marek Vasut
2023-05-17 15:25 ` [PATCH v2 2/3] nvmem: syscon: Add syscon backed nvmem driver Marek Vasut
2023-05-17 15:25 ` Marek Vasut
2023-05-18 14:22 ` Krzysztof Kozlowski
2023-05-18 14:22 ` Krzysztof Kozlowski
2023-05-24 3:30 ` Marek Vasut
2023-05-24 3:30 ` Marek Vasut
2023-05-17 15:25 ` [PATCH v2 3/3] ARM: dts: stm32: Add nvmem-syscon node to TAMP to expose boot count on DHSOM Marek Vasut
2023-05-17 15:25 ` Marek Vasut
2023-05-26 14:32 ` Alexandre TORGUE
2023-05-26 14:32 ` Alexandre TORGUE
2023-05-26 15:28 ` patrick.delaunay [this message]
2023-05-26 15:28 ` patrick.delaunay
2023-05-31 23:09 ` Marek Vasut
2023-05-31 23:09 ` Marek Vasut
2023-06-01 15:15 ` Patrick DELAUNAY
2023-06-01 15:15 ` Patrick DELAUNAY
2023-05-18 14:26 ` [PATCH v2 1/3] dt-bindings: nvmem: syscon: Add syscon backed nvmem bindings Krzysztof Kozlowski
2023-05-18 14:26 ` Krzysztof Kozlowski
2023-05-24 3:30 ` Marek Vasut
2023-05-24 3:30 ` Marek Vasut
[not found] ` <a954db86-c5b7-0c07-8881-0ceb39ac7337@linaro.org>
[not found] ` <e9d7b2de-ef57-80fa-f92b-6f66d413114a@denx.de>
2023-06-01 6:47 ` Krzysztof Kozlowski
2023-06-01 6:47 ` Krzysztof Kozlowski
2023-05-18 14:30 ` Krzysztof Kozlowski
2023-05-18 14:30 ` Krzysztof Kozlowski
2023-05-24 3:29 ` Marek Vasut
2023-05-24 3:29 ` Marek Vasut
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='02ca01d98fe6$ca371d80$5ea55880$@foss.st.com' \
--to=patrick.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@dh-electronics.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.