public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>,
	Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Diederik de Haas <didi.debian@cknow.org>,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v2 3/3] dt-bindings: thermal: rockchip: tighten grf requirements
Date: Sun, 21 Sep 2025 23:20:51 +0100	[thread overview]
Message-ID: <20250921-abroad-decibel-5b81c0680693@spud> (raw)
In-Reply-To: <wtwdpqi4tk3ixzmrvdyv2aguf6pjlmnz6q5gvhlajl2hk6mdys@fmkugriedhqe>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

On Fri, Sep 19, 2025 at 08:35:12PM +0200, Sebastian Reichel wrote:
> Hi,
> 
> On Wed, Aug 20, 2025 at 08:48:23PM +0100, Conor Dooley wrote:
> > On Wed, Aug 20, 2025 at 07:40:49PM +0200, Sebastian Reichel wrote:
> > > Instead of having an optional rockchip,grf property, forbid using it on
> > > platforms without registers in a GRF being needed for thermal monitoring
> > > and make it mandatory on the platforms actually needing it.
> > 
> > I am assuming that "needing it" means that it was actually mandatory but
> > the binding was just missing the required required entry. If so
> > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> 
> I just noticed, that I never replied: The GRF configuration is
> required for proper functionality as far as I can tell. Technically
> it might be skipped, if the bootloader already configured the
> registers correctly. but I don't think this is something anyone wants
> to rely on and with the same argument we could describe almost any
> resource as optional :) The upstream kernel DT always had the GRF
> specified for these platforms (and thus most likely has never been
> tested without it).

Acked-by: Conor Dooley <conor.dooley@microchip.com>

(ik I gave it already, but for clarity)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-09-21 22:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20 17:40 [PATCH v2 0/3] thermal: rockchip: shut up GRF warning Sebastian Reichel
2025-08-20 17:40 ` [PATCH v2 1/3] thermal: rockchip: unify struct rockchip_tsadc_chip format Sebastian Reichel
2025-08-20 20:11   ` Heiko Stübner
2025-08-22  3:11   ` Dragan Simic
2025-08-20 17:40 ` [PATCH v2 2/3] thermal: rockchip: shut up GRF warning Sebastian Reichel
2025-08-20 20:14   ` Heiko Stübner
2025-08-21 12:41   ` Diederik de Haas
2025-08-22  3:15   ` Dragan Simic
2025-08-20 17:40 ` [PATCH v2 3/3] dt-bindings: thermal: rockchip: tighten grf requirements Sebastian Reichel
2025-08-20 19:48   ` Conor Dooley
2025-09-19 18:35     ` Sebastian Reichel
2025-09-21 22:20       ` Conor Dooley [this message]
2025-08-22  3:20   ` Dragan Simic
2025-09-19 15:55 ` [PATCH v2 0/3] thermal: rockchip: shut up GRF warning Daniel Lezcano

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=20250921-abroad-decibel-5b81c0680693@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=didi.debian@cknow.org \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.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=linux-rockchip@lists.infradead.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rui.zhang@intel.com \
    --cc=sebastian.reichel@collabora.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