From: Conor Dooley <conor@kernel.org>
To: Binbin Zhou <zhoubinbin@loongson.cn>
Cc: Binbin Zhou <zhoubb.aaron@gmail.com>,
Huacai Chen <chenhuacai@loongson.cn>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Huacai Chen <chenhuacai@kernel.org>,
Xuerui Wang <kernel@xen0n.name>,
loongarch@lists.linux.dev, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: thermal: loongson,ls2k-thermal: Add compatible for Loongson-2K0300
Date: Fri, 10 Jul 2026 17:24:04 +0100 [thread overview]
Message-ID: <20260710-causal-goldsmith-ee44aa5e26fd@spud> (raw)
In-Reply-To: <20260710-game-late-9347baafa7ab@spud>
[-- Attachment #1: Type: text/plain, Size: 4068 bytes --]
On Fri, Jul 10, 2026 at 05:21:22PM +0100, Conor Dooley wrote:
> On Fri, Jul 10, 2026 at 04:24:59PM +0800, Binbin Zhou wrote:
> > Add a new compatible string `loongson,ls2k0300-thermal` for the thermal
> > sensor found on the Loongson-2K0300 SoC.
> >
> > The hardware differs from the existing SoCs in its register layout: it
> > requires two register regions (one for the thermal sensor control and
> > another for the CPU ID).
> >
> > Update the binding to describe this new requirement.
> >
> > Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn>
> > ---
> > .../thermal/loongson,ls2k-thermal.yaml | 68 ++++++++++++++-----
> > 1 file changed, 50 insertions(+), 18 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/thermal/loongson,ls2k-thermal.yaml b/Documentation/devicetree/bindings/thermal/loongson,ls2k-thermal.yaml
> > index 79e691b08341..b5cbfd201105 100644
> > --- a/Documentation/devicetree/bindings/thermal/loongson,ls2k-thermal.yaml
> > +++ b/Documentation/devicetree/bindings/thermal/loongson,ls2k-thermal.yaml
> > @@ -10,13 +10,11 @@ maintainers:
> > - zhanghongchen <zhanghongchen@loongson.cn>
> > - Yinbo Zhu <zhuyinbo@loongson.cn>
> >
> > -allOf:
> > - - $ref: /schemas/thermal/thermal-sensor.yaml#
> > -
> > properties:
> > compatible:
> > oneOf:
> > - enum:
> > + - loongson,ls2k0300-thermal
> > - loongson,ls2k1000-thermal
> > - loongson,ls2k2000-thermal
> > - items:
> > @@ -39,23 +37,46 @@ required:
> > - reg
> > - interrupts
> >
> > -if:
> > - properties:
> > - compatible:
> > - contains:
> > - enum:
> > - - loongson,ls2k2000-thermal
> > +allOf:
> > + - $ref: /schemas/thermal/thermal-sensor.yaml#
> >
> > -then:
> > - properties:
> > - reg:
> > - minItems: 2
> > - maxItems: 2
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - loongson,ls2k0300-thermal
> > + then:
> > + properties:
> > + reg:
> > + items:
> > + - description: Thermal base register region
> > + - description: CPU ID register region
> >
> > -else:
> > - properties:
> > - reg:
> > - maxItems: 1
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - loongson,ls2k1000-thermal
> > + then:
> > + properties:
> > + reg:
> > + items:
> > + - description: Thermal base register region
> > +
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - loongson,ls2k2000-thermal
> > + then:
> > + properties:
> > + reg:
> > + items:
> > + - description: Thermal base register region
> > + - description: Thermal data output register region
> >
> > unevaluatedProperties: false
> >
> > @@ -69,3 +90,14 @@ examples:
> > interrupts = <7 IRQ_TYPE_LEVEL_LOW>;
> > #thermal-sensor-cells = <1>;
> > };
> > +
> > + - |
> > + #include <dt-bindings/interrupt-controller/irq.h>
> > + thermal-sensor@16001500 {
> > + compatible = "loongson,ls2k0300-thermal";
> > + reg = <0x16001500 0x30>,
> > + <0x16003ff0 0x8>;
>
> Quite frankly, the address and size of this look like the second
> register region here is actually a few bytes in a syscon that is being
> misrepresented.
> What lies at the addresses immediately before and after 0x16003ff0?
Hmm, I just realised that the new device is the 0300, making this second
reg property the "cpuid" region. That makes this doubly suspect looking.
>
>
> Thanks,
> Conor.
>
> > + interrupt-parent = <&liointc1>;
> > + interrupts = <20 IRQ_TYPE_LEVEL_HIGH>;
> > + #thermal-sensor-cells = <1>;
> > + };
> > --
> > 2.52.0
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-10 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 8:24 [PATCH 0/2] thermal: loongson2: Add support for Loongson-2K0300 SoC Binbin Zhou
2026-07-10 8:24 ` [PATCH 1/2] dt-bindings: thermal: loongson,ls2k-thermal: Add compatible for Loongson-2K0300 Binbin Zhou
2026-07-10 16:21 ` Conor Dooley
2026-07-10 16:24 ` Conor Dooley [this message]
2026-07-10 8:25 ` [PATCH 2/2] thermal/drivers/loongson2: Add thermal driver support " Binbin Zhou
2026-07-10 8:36 ` sashiko-bot
2026-07-10 14:32 ` Huacai Chen
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=20260710-causal-goldsmith-ee44aa5e26fd@spud \
--to=conor@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=zhoubb.aaron@gmail.com \
--cc=zhoubinbin@loongson.cn \
/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