linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
	 Gregory Clement <gregory.clement@bootlin.com>,
	 Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	 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>,
	linux-arm-kernel@lists.infradead.org,
	 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-pm@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] dt-binding: thermal: Convert marvell,armada-ap806-thermal to DT schema
Date: Fri, 01 Aug 2025 16:27:28 +0200	[thread overview]
Message-ID: <87qzxv5d7z.fsf@bootlin.com> (raw)
In-Reply-To: <20250702230030.2892116-1-robh@kernel.org> (Rob Herring's message of "Wed, 2 Jul 2025 18:00:29 -0500")

Hi Rob,

Sorry for the delay, I don't know why I forgot these.

...

> +properties:
> +  compatible:
> +    enum:
> +      - marvell,armada-ap806-thermal
> +      - marvell,armada-ap807-thermal
> +      - marvell,armada-cp110-thermal
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    description: overheat interrupt
> +    maxItems: 1
> +
> +  '#thermal-sensor-cells':
> +    description: Cell represents the channel ID. There is one sensor per
> +      channel. O refers to the thermal IP internal channel.
> +    const: 1
> +
> +required:
> +  - compatible
> +  - reg
> +
> +additionalProperties: false

IIRC on these Marvell designs, there was one (or more, I don't remember)
Application Processor (AP) and several Co-Processors (CP).

[On the AP]
The AP8XX overheat interrupt was not directly wired to the GIC but was
going through another intermediate IRQ controller named SEI (System
Error Interrupt).

      Thermal overheat IRQ -> SEI -> GIC

[On the CP]
There was one interrupt controller per CP11X named ICU, which would be
connected to the top level GIC through MSIs. The ICU was however split
into several sub-controllers reaching different areas on the GIC.

                                      MSI
      Thermal overheat IRQ -> ICU SEI -> GIC

As the OS could not guess the internal connexions, I believe we had to
include in the bindings the parent IRQ chip we were connected to. In the
case of the thermal over heat interrupts, they were all going through an
SEI controller (System Error Interrupt) which, if I still remember
correctly, was not the default parent, hence the use of
interrupts-parent/interrupts-extended in the examples.

This is all a bit cloudy in my mind, but I believe these properties
matter and with 'additionalProperties: false' and without
interrupts-parent/interrupts-extended allowed, a real world DT
snippet would not pass the binding checks.

> +examples:
> +  - |
> +    thermal-sensor@80 {
> +        compatible = "marvell,armada-ap806-thermal";
> +        reg = <0x80 0x10>;
> +        interrupts = <18>;

I do not know how accurate the example must be, but maybe the example
shall reflect the SEI connection as well.

> +        #thermal-sensor-cells = <1>;
> +    };

Thanks,
Miquèl


  parent reply	other threads:[~2025-08-01 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 23:00 [PATCH] dt-binding: thermal: Convert marvell,armada-ap806-thermal to DT schema Rob Herring (Arm)
2025-08-01 13:34 ` Rob Herring
2025-08-01 14:27 ` Miquel Raynal [this message]
2025-08-01 20:22   ` Rob Herring
2025-08-04  7:22     ` Miquel Raynal

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=87qzxv5d7z.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=thomas.petazzoni@bootlin.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).