From: sashiko-bot@kernel.org
To: erebion <erebion@erebion.eu>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 11/12] arm64: dts: qcom: sm6350-lena: Add PM6150L thermals
Date: Sun, 01 Nov 2026 23:44:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-192768@kernel.org> (raw)
In-Reply-To: <20261102-pdx213-upstream-3-v3-11-cdc3be96d257@erebion.eu>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] arm64: dts: qcom: wrong io-channels specifier on rear_cam_sensor
- [Low] arm64: dts: qcom: misplaced xo-thermal, unused includes, and style issues
--
commit ac86db420f5582034afb81e70777f975abaf47c9
Author: erebion <erebion@erebion.eu>
arm64: dts: qcom: sm6350-lena: Add PM6150L thermals
This commit adds ADC channels, ADC_TM channels, generic-adc-thermal sensors,
and thermal zones for the thermistors connected to PM6150L on the Sony Xperia
10 III (lena).
> diff --git a/arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dts b/arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dts
> index 4e9707712a651..487ef75f2f1de 100644
> --- a/arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dts
> +++ b/arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dts
> @@ -12,7 +12,9 @@
> #define PMK8350_SID 6
>
> #include <dt-bindings/firmware/qcom,scm.h>
> +#include <dt-bindings/gpio/gpio.h>
> #include <dt-bindings/iio/qcom,spmi-adc7-pmk8350.h>
> +#include <dt-bindings/input/input.h>
> #include <dt-bindings/leds/common.h>
> #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
> #include <dt-bindings/regulator/qcom,rpmh-regulator.h>
> @@ -70,6 +72,20 @@ lcdb_dummy: regulator-lcdb-dummy {
> regulator-boot-on;
> };
>
> + msm_therm_sensor: thermal-sensor-msm {
> + compatible = "generic-adc-thermal";
> + #thermal-sensor-cells = <0>;
> + io-channels = <&pm6150l_adc ADC5_AMUX_THM2_100K_PU>;
> + io-channel-names = "sensor-channel";
> + };
> +
> + rear_cam_sensor: thermal-sensor-rear-cam {
> + compatible = "generic-adc-thermal";
> + #thermal-sensor-cells = <0>;
> + io-channels = <&pm6150l_adc ADC5_GPIO6_100K_PU>;
> + io-channel-names = "sensor-channel";
> + };
[Severity: Medium]
Should rear_cam_sensor reference ADC5_GPIO2_100K_PU instead of
ADC5_GPIO6_100K_PU here?
On PM6150L, physical pin gpio6 is routed to ADC5_GPIO2_100K_PU (0x53), and
under &pm6150l_adc below the rear camera thermistor channel is defined as:
channel@53 {
reg = <ADC5_GPIO2_100K_PU>;
label = "rear_cam_therm";
When gadc_thermal_probe() calls devm_iio_channel_get() for rear_cam_sensor,
adc5_fwnode_xlate() in drivers/iio/adc/qcom-spmi-adc5.c searches the channels
registered under &pm6150l_adc for a matching channel number:
for (i = 0; i < adc->nchannels; i++)
if (adc->chan_props[i].channel == iiospec->args[0])
return i;
return -EINVAL;
Because no channel is registered for ADC5_GPIO6_100K_PU (and adc5_chans_pmic[]
only defines 100K pull-up GPIO channels up to ADC5_GPIO4_100K_PU), probing
rear_cam_sensor fails with -EINVAL and leaves rear-cam-thermal non-functional.
[ ... ]
> @@ -115,6 +131,99 @@ active-config0 {
[ ... ]
> + xo-thermal {
> + thermal-sensors = <&pmk8350_adc_tm 0>;
> +
> + trips {
> + active-config0 {
> + temperature = <125000>;
> + hysteresis = <1000>;
> + type = "passive";
> + };
> + };
> + };
> };
> };
>
> @@ -392,6 +501,99 @@ &mpss {
> status = "okay";
> };
>
> +&pm6150l_gpios {
> + pm6150l_adc_default: adc-default-state {
> + pins = "gpio6", "gpio7", "gpio10";
> + function = PMIC_GPIO_FUNC_NORMAL;
> + bias-high-impedance;
> + };
> +};
> +
> +&pm6150l_adc {
[ ... ]
> +&pm6150l_adc_tm {
> + status = "okay";
> +
> + pa-therm1@0 {
> + reg = <0>;
> + io-channels = <&pm6150l_adc ADC5_AMUX_THM1_100K_PU>;
> + qcom,hw-settle-time-us = <200>;
> + qcom,ratiometric;
> + };
> +
> + pa-therm0@1 {
> + reg = <1>;
> + io-channels = <&pm6150l_adc ADC5_AMUX_THM3_100K_PU>;
> + qcom,hw-settle-time-us = <200>;
> + qcom,ratiometric;
> + };
> +
> + rear-cam-flash-therm@2 {
> + reg = <2>;
> + io-channels = <&pm6150l_adc ADC5_GPIO3_100K_PU>;
> + qcom,hw-settle-time-us = <200>;
> + qcom,ratiometric;
> + };
[Severity: Low]
This isn't a runtime bug, but there are a few patch split and style issues
across this change:
1. Earlier in the series, commit ff24120a08d6 ("arm64: dts: qcom: sm6350-lena:
Add PMK8350 thermals") added xo-thermal, and the next commit f17bc49f693d
("arm64: dts: qcom: sm6350-lena: Add PM7250B thermals") accidentally removed
it. Re-adding xo-thermal here puts a PMK8350 thermal zone into the PM6150L
thermal patch. Could xo-thermal be kept in the PMK8350 patch instead?
2. The newly added dt-bindings/gpio/gpio.h and dt-bindings/input/input.h
includes at the top of the file do not appear to be used by this patch.
3. Label references at the bottom of the file are sorted alphabetically, so
should &pm6150l_gpios be placed after &pm6150l_flash rather than before
&pm6150l_adc?
4. The closing brace of rear-cam-flash-therm@2 has an extra tab of
indentation.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261102-pdx213-upstream-3-v3-0-cdc3be96d257@erebion.eu?part=11
next prev parent reply other threads:[~2026-11-01 23:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 23:32 [PATCH v3 00/12] Enable more nodes for the Xperia 10 III erebion
2026-11-01 23:32 ` [PATCH v3 01/12] arm64: dts: qcom: sm6350-lena: Add flash LED erebion
2026-11-01 23:38 ` sashiko-bot
2026-11-02 8:47 ` erebion
2026-11-01 23:32 ` [PATCH v3 02/12] arm64: dts: qcom: sm6350-lena: rename touch-en-regulator erebion
2026-11-01 23:38 ` sashiko-bot
2026-11-02 8:36 ` erebion
2026-11-02 11:57 ` Konrad Dybcio
2026-11-01 23:32 ` [PATCH v3 03/12] arm64: dts: qcom: sm6350-lena: Add qcom,rmtfs-mem node erebion
2026-11-02 11:58 ` Konrad Dybcio
2026-11-01 23:32 ` [PATCH v3 04/12] arm64: dts: qcom: sm6350-lena: Enable ADSP, CDSP, IPA & MPSS erebion
2026-11-01 23:41 ` sashiko-bot
2026-11-02 1:23 ` erebion
2026-11-02 11:59 ` Konrad Dybcio
2026-11-01 23:32 ` [PATCH v3 05/12] arm64: dts: qcom: sm6350-lena: Enable Bluetooth erebion
2026-11-01 23:45 ` sashiko-bot
2026-11-02 0:41 ` erebion
2026-11-01 23:32 ` [PATCH v3 06/12] arm64: dts: qcom: sm6350-lena: Enable wifi erebion
2026-11-01 23:32 ` [PATCH v3 07/12] arm64: dts: qcom: sm6350-lena: Enable PM7250B erebion
2026-11-02 11:59 ` Konrad Dybcio
2026-11-01 23:32 ` [PATCH v3 08/12] arm64: dts: qcom: sm6350-lena: Enable PMK8350 erebion
2026-11-01 23:42 ` sashiko-bot
2026-11-02 11:08 ` erebion
2026-11-01 23:32 ` [PATCH v3 09/12] arm64: dts: qcom: sm6350-lena: Add PMK8350 thermals erebion
2026-11-01 23:32 ` [PATCH v3 10/12] arm64: dts: qcom: sm6350-lena: Add PM7250B thermals erebion
2026-11-01 23:44 ` sashiko-bot
2026-11-02 0:05 ` erebion
2026-11-01 23:32 ` [PATCH v3 11/12] arm64: dts: qcom: sm6350-lena: Add PM6150L thermals erebion
2026-11-01 23:44 ` sashiko-bot [this message]
2026-11-02 0:35 ` erebion
2026-11-02 1:33 ` erebion
2026-11-02 12:20 ` erebion
2026-11-01 23:32 ` [PATCH v3 12/12] arm64: dts: qcom: sm6350-lena: enable remaining i2c busses erebion
2026-11-01 23:48 ` sashiko-bot
2026-11-02 11:24 ` erebion
2026-11-02 12:00 ` Konrad Dybcio
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=sashiko-outbox-192768@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=erebion@erebion.eu \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.