linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: 손신 <shin.son@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
	"'Bartlomiej Zolnierkiewicz'" <bzolnier@gmail.com>,
	"'Rafael J . Wysocki'" <rafael@kernel.org>,
	"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
	"'Zhang Rui'" <rui.zhang@intel.com>,
	"'Lukasz	Luba'" <lukasz.luba@arm.com>,
	"'Rob Herring'" <robh@kernel.org>,
	"'Conor Dooley'" <conor+dt@kernel.org>,
	"'Alim Akhtar'" <alim.akhtar@samsung.com>,
	"'Henrik Grimler'" <henrik@grimler.se>
Cc: <linux-pm@vger.kernel.org>, <linux-samsung-soc@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 1/3] dt-bindings: thermal: samsung: Add a hw-sensor-indices property
Date: Mon, 15 Sep 2025 17:51:38 +0900	[thread overview]
Message-ID: <060601dc261d$f2f2d5a0$d8d880e0$@samsung.com> (raw)
In-Reply-To: <b453e64b-b3db-4b8f-ba9d-0da7e55fe057@kernel.org>

Hello, Krzysztof Kozlowski.

> -----Original Message-----
> From: Krzysztof Kozlowski [mailto:krzk@kernel.org]
> Sent: Monday, September 15, 2025 1:29 PM
> To: Shin Son <shin.son@samsung.com>; Bartlomiej Zolnierkiewicz
> <bzolnier@gmail.com>; Rafael J . Wysocki <rafael@kernel.org>; Daniel
> Lezcano <daniel.lezcano@linaro.org>; Zhang Rui <rui.zhang@intel.com>;
> Lukasz Luba <lukasz.luba@arm.com>; Rob Herring <robh@kernel.org>; Conor
> Dooley <conor+dt@kernel.org>; Alim Akhtar <alim.akhtar@samsung.com>;
> Henrik Grimler <henrik@grimler.se>
> Cc: linux-pm@vger.kernel.org; linux-samsung-soc@vger.kernel.org;
> devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCH v3 1/3] dt-bindings: thermal: samsung: Add a hw-
> sensor-indices property
> 
> On 15/09/2025 06:07, Shin Son wrote:
> > The exynosautov920 TMU requires per-sensor interrupt enablement for
> > its critical trip points.
> >
> > - **samsung,hw-sensor-indices**: List of sensor indices physically
> >                                  monitored by this TMU block.
> > 				 Indicies not listed exist in the SoC
> > 				 register map but are not part of
> > 				 this TMU instance
> 
> Not much improved here. Same comment as before. That's not even correct
> syntax but some oddly formatted code. I asked to drop it and instead
> describe hardware. This is not a place to write some **code** or whatever
> this paragraph is about to represent.

Understood—sorry for the confusion. I'll remove the code-like formatting and replace it with a plain, hardware-focused
Description as requested.

> 
> >
> > Additionally, add myself to the bindings' maintainers list, as I plan
> > to actively work on the exynosautov920 TMU support and handle further
> > updates in this area.
> > I also restrict 'samsung,hw-sensor-indices' to the V920 variant. To
> > ensure properties introduced in 'if/then' blocks are recognized, I
> > replace 'addtionalProperties: false' with 'unevaluatedProperties: false'.
> 
> No, don't do that.

Understood. I'll keep 'addtionalProperties: false' as is and promote 'samsung,hw-sensor-indices' to the common sections.

> 
> >
> > Signed-off-by: Shin Son <shin.son@samsung.com>
> > ---
> >  .../thermal/samsung,exynos-thermal.yaml       | 40 ++++++++++++++++++-
> >  1 file changed, 38 insertions(+), 2 deletions(-)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yam
> > l
> > b/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yam
> > l index 29a08b0729ee..448c68986b10 100644
> > ---
> > a/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yam
> > l
> > +++ b/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal
> > +++ .yaml
> > @@ -8,6 +8,7 @@ title: Samsung Exynos SoC Thermal Management Unit
> > (TMU)
> >
> >  maintainers:
> >    - Krzysztof Kozlowski <krzk@kernel.org>
> > +  - Shin Son <shin.son@samsung.com>
> >
> >  description: |
> >    For multi-instance tmu each instance should have an alias correctly
> > numbered @@ -27,6 +28,7 @@ properties:
> >        - samsung,exynos5420-tmu-ext-triminfo
> >        - samsung,exynos5433-tmu
> >        - samsung,exynos7-tmu
> > +      - samsung,exynosautov920-tmu
> >
> >    clocks:
> >      minItems: 1
> > @@ -62,7 +64,7 @@ properties:
> >      minItems: 1
> >
> >    '#thermal-sensor-cells':
> > -    const: 0
> > +    enum: [0, 1]
> >
> >    vtmu-supply:
> >      description: The regulator node supplying voltage to TMU.
> > @@ -97,6 +99,8 @@ allOf:
> >          reg:
> >            minItems: 2
> >            maxItems: 2
> > +        '#thermal-sensor-cells':
> > +          const: 0
> >    - if:
> >        properties:
> >          compatible:
> > @@ -119,6 +123,8 @@ allOf:
> >          reg:
> >            minItems: 1
> >            maxItems: 1
> > +        '#thermal-sensor-cells':
> > +          const: 0
> >
> >    - if:
> >        properties:
> > @@ -139,8 +145,38 @@ allOf:
> >          reg:
> >            minItems: 1
> >            maxItems: 1
> > +        '#thermal-sensor-cells':
> > +          const: 0
> >
> > -additionalProperties: false
> > +  - if:
> > +      properties:
> > +        compatible:
> > +          contains:
> > +            const: samsung,exynosautov920-tmu
> > +    then:
> > +      properties:
> > +        clocks:
> > +          minItems: 1
> > +          maxItems: 1
> > +        reg:
> > +          minItems: 1
> > +          maxItems: 1
> > +        '#thermal-sensor-cells':
> > +          const: 1
> > +        samsung,hw-sensor-indices:
> > +          description:
> > +            List of thermal sensor indices physically monitored by this
> TMU instance.
> > +            Indices not listed correspond to registers that exist in the
> SoC
> > +            but are not connected to this TMU hardware block.
> > +          $ref: /schemas/types.yaml#/definitions/uint32-array
> 
> I don't understand what is happening here with this binding. See writing
> schema and example-schema.
> 
> 
> 
> Best regards,
> Krzysztof

Understood. I'll rework the binding to follow the 'writing schema' and 'example-schema' guidance
and include these changes in v4.

Thanks.
Best regards,
Shin Son




  reply	other threads:[~2025-09-15  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250915040734epcas2p4746a8f668f570e362f65ae39cc9e11ef@epcas2p4.samsung.com>
2025-09-15  4:07 ` [PATCH v3 0/3] Add exynosautov920 thermal support Shin Son
2025-09-15  4:07   ` [PATCH v3 1/3] dt-bindings: thermal: samsung: Add a hw-sensor-indices property Shin Son
2025-09-15  4:28     ` Krzysztof Kozlowski
2025-09-15  8:51       ` 손신 [this message]
2025-09-15  4:07   ` [PATCH v3 2/3] thermal: exynos_tmu: Support new hardware and update TMU interface Shin Son
2025-09-15  4:07   ` [PATCH v3 3/3] arm64: dts: exynosautov920: Add tmu hardware binding Shin Son

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='060601dc261d$f2f2d5a0$d8d880e0$@samsung.com' \
    --to=shin.son@samsung.com \
    --cc=alim.akhtar@samsung.com \
    --cc=bzolnier@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=henrik@grimler.se \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).