devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
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>
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 1/3] dt-bindings: thermal: samsung: Add tmu-name and sensor-index-ranges properties
Date: Sat, 30 Aug 2025 11:06:49 +0200	[thread overview]
Message-ID: <f6acdd01-8847-4282-b375-f8e564be81d2@kernel.org> (raw)
In-Reply-To: <20250825064929.188101-2-shin.son@samsung.com>

On 25/08/2025 08:49, Shin Son wrote:
> The exynosautov920 TMU requires per-sensor interrupt enablement
> for its critical trip points.
> Add two new DT properties to the Samsung thermal bindings
> to support this requirement:
> 
> - **tmu-name**: an explicit identifier for each TMU,
> 		used to skip specific sensors
> (e.g., sensor 5 is temporarily disabled on the TMU_SUB1 block).
> 
> - **sensor-index-ranges**: defines valid sensor index ranges
> 			   for the driver’s bitmap in private data,
> 			   enabling per-sensor interrupt setup and data access.
> 
> Signed-off-by: Shin Son <shin.son@samsung.com>
> ---
>  .../thermal/samsung,exynos-thermal.yaml       | 23 ++++++++++++++++++-
>  1 file changed, 22 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml b/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml
> index 29a08b0729ee..420fb7a944e3 100644
> --- a/Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml
> +++ 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>

This needs also explanation in commit msg.

>  
>  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,11 +64,29 @@ properties:
>      minItems: 1
>  
>    '#thermal-sensor-cells':
> -    const: 0
> +    enum:
> +      - 0
> +      - 1
>  
>    vtmu-supply:
>      description: The regulator node supplying voltage to TMU.
>  
> +  tmu-name:

Generic property? Where is it defined.

> +    description: The TMU hardware name.

Anyway, you do not get instance IDs. I talked about this at OSSE25.


> +    $ref: /schemas/types.yaml#/definitions/string-array
> +    minItems: 1
> +    maxItems: 1
> +
> +  sensor-index-ranges:

Where is the property defined? You keep adding generic properties.

> +    description: |
> +      Valid Sensor index ranges for the TMU hardware.

I don't understand what is this for.

> +
> +      Note:: On the ExynosautoV920 variant, the fifth sensor in the TMU SUB1 is disabled,
> +      so the driver skips it when matching by tmu-name.

That's not name, so why are you referring to tmu-name? And driver has
nothing to do here. Describe hardware.

None of this is really correct. :/


Best regards,
Krzysztof

  reply	other threads:[~2025-08-30  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250825064933epcas2p37665fae32f51b04a43e5395d76759143@epcas2p3.samsung.com>
2025-08-25  6:49 ` [PATCH 0/3] Add exynosautov920 thermal support Shin Son
     [not found]   ` <CGME20250825064933epcas2p33e2b4566b5911fef8d7127900fc10002@epcas2p3.samsung.com>
2025-08-25  6:49     ` [PATCH 1/3] dt-bindings: thermal: samsung: Add tmu-name and sensor-index-ranges properties Shin Son
2025-08-30  9:06       ` Krzysztof Kozlowski [this message]
2025-09-02  8:54         ` 손신
     [not found]   ` <CGME20250825064933epcas2p1e138f8c874f634123590af3bf63e49bd@epcas2p1.samsung.com>
2025-08-25  6:49     ` [PATCH 2/3] thermal: exynos_tmu: Support new hardware and update TMU interface Shin Son
     [not found]   ` <CGME20250825064933epcas2p40a7c491366097f90add675bc36822ef9@epcas2p4.samsung.com>
2025-08-25  6:49     ` [PATCH 3/3] arm64: dts: exynosautov920: Add tmu hardware binding Shin Son
2025-08-30  9:08       ` Krzysztof Kozlowski
2025-09-02  9:06         ` 손신
2025-09-02  9:30           ` Krzysztof Kozlowski

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=f6acdd01-8847-4282-b375-f8e564be81d2@kernel.org \
    --to=krzk@kernel.org \
    --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=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 \
    --cc=shin.son@samsung.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).