From: Andre Przywara <andre.przywara@arm.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Chen-Yu Tsai <wens@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Srinivas Kandagatla <srini@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Maxime Ripard <mripard@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: sun8i-r40: Add SID node and THS calibration
Date: Mon, 5 Oct 2026 11:02:05 +0200 [thread overview]
Message-ID: <2c75983e-5e63-4613-a9a8-055015d04bbf@arm.com> (raw)
In-Reply-To: <20261003012534.418820-5-otavio@ossystems.com.br>
Hi Otavio,
thanks for sending the patch!
On 10/3/26 03:25, Otavio Salvador wrote:
> Without the calibration cell, the THS driver leaves the sensor
> calibration registers at their reset value (0x800) and the reported
> temperatures drift from the real die temperature by a chip-dependent
> offset.
>
> Add the SID node at 0x01c1b000 and wire the thermal sensor to its
> factory calibration at eFuse offset 0x40, one 16-bit word for each of
> the two sensors.
>
> The R40 user manual gives the size of the thermal sensor key (32 bits)
> but not its offset. The vendor SDK key map names 0x48 "thermal_sensor",
> but that word is zero on all the boards checked. On an A40i running the
> Boardcon vendor kernel, the THS_0_1_CDATA register holds exactly the
> eFuse word at 0x40 (0x08780875), which confirms the location.
So in some U-Boot BSP sources on github I see
arch/arm/include/asm/arch-sun8iw11p1/sid.h putting the sensor at 0x34
(like the H3 or A64).
Can you check the values there? I see that Tina-Linux puts them at 0x40,
as you reported, and it's probably more reliable there than in the
U-Boot sources, but it's worth double checking.
The rest looks alright (checked the manual and how the compatible string
is handled in the driver), so if you can confirm that it's 0x40:
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Thanks,
Andre
>
> Tested on two Boardcon EMA40i (A40i) boards: THS_0_1_CDATA now holds
> the eFuse word at 0x40 of each chip (0x082d0822 and 0x083d0838) instead
> of the reset value 0x08000800.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> arch/arm/boot/dts/allwinner/sun8i-r40.dtsi | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/allwinner/sun8i-r40.dtsi b/arch/arm/boot/dts/allwinner/sun8i-r40.dtsi
> index f0ed802a9d08e..c7c9cad695ca4 100644
> --- a/arch/arm/boot/dts/allwinner/sun8i-r40.dtsi
> +++ b/arch/arm/boot/dts/allwinner/sun8i-r40.dtsi
> @@ -485,6 +485,18 @@ ohci1: usb@1c19400 {
> status = "disabled";
> };
>
> + sid: efuse@1c1b000 {
> + compatible = "allwinner,sun8i-r40-sid",
> + "allwinner,sun50i-a64-sid";
> + reg = <0x01c1b000 0x400>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + ths_calibration: thermal-sensor-calibration@40 {
> + reg = <0x40 0x4>;
> + };
> + };
> +
> ehci2: usb@1c1c000 {
> compatible = "allwinner,sun8i-r40-ehci", "generic-ehci";
> reg = <0x01c1c000 0x100>;
> @@ -832,7 +844,8 @@ ths: thermal-sensor@1c24c00 {
> clock-names = "bus", "mod";
> interrupts = <GIC_SPI 36 IRQ_TYPE_LEVEL_HIGH>;
> resets = <&ccu RST_BUS_THS>;
> - /* TODO: add nvmem-cells for calibration */
> + nvmem-cells = <&ths_calibration>;
> + nvmem-cell-names = "calibration";
> #thermal-sensor-cells = <1>;
> };
>
next prev parent reply other threads:[~2026-10-05 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 1:25 [PATCH 0/2] Add SID and THS calibration for Allwinner R40 Otavio Salvador
2026-10-03 1:25 ` [PATCH 1/2] dt-bindings: nvmem: SID: Add binding for R40 SID controller Otavio Salvador
2026-10-03 1:25 ` [PATCH 2/2] ARM: dts: sun8i-r40: Add SID node and THS calibration Otavio Salvador
2026-10-05 9:02 ` Andre Przywara [this message]
2026-10-05 15:49 ` Otavio Salvador
2026-10-05 17:54 ` Andre Przywara
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=2c75983e-5e63-4613-a9a8-055015d04bbf@arm.com \
--to=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=otavio@ossystems.com.br \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=srini@kernel.org \
--cc=wens@kernel.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 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®