public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Belwon <igor.belwon@mentallysanemainliners.org>
To: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: exynos990: Rename and sort PMU nodes
Date: Sun, 5 Jan 2025 13:03:45 +0100	[thread overview]
Message-ID: <Z3p1IV0rVH9dPQ_C@debian> (raw)
In-Reply-To: <bb1e89a5-a83e-4e68-9568-073f9c4a8af9@gmail.com>

On Sun, Jan 05, 2025 at 01:39:04PM +0200, Ivaylo Ivanov wrote:
> On 1/5/25 13:16, Igor Belwon wrote:
> > These nodes were sorted by name, but it's nice to have the same class of
> > devices together. As such, drop the pmu suffix and add "pmu" as a prefix.
> > This keeps consistency between other Exynos SoCs too.
>
> Well, most SoC device trees still have it as a suffix. Perhaps it'd be better to
> apply this change for all exynos device trees instead of waiting for other
> people to apply it separately?
>
> Best regards,
> Ivaylo

Hi Ivaylo,

The newly-merged 9810 SoC had it hand-fixed by Krzysztof while being
merged [1], and there is a current patch to fix it on 8895 [2].
That's all the SoCs with Mongoose cores (and the Mongoose PMU breaks
sorting). Only 990 is missing this change.

[1] https://lore.kernel.org/linux-samsung-soc/d1c6d2f2-f733-4cbe-8108-c9c9aaa417cc@kernel.org/
[2] https://lore.kernel.org/linux-samsung-soc/20241222145257.31451-1-krzysztof.kozlowski@linaro.org/

Thanks and best regards,
Igor

  reply	other threads:[~2025-01-05 12:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 11:16 [PATCH] arm64: dts: exynos990: Rename and sort PMU nodes Igor Belwon
2025-01-05 11:39 ` Ivaylo Ivanov
2025-01-05 12:03   ` Igor Belwon [this message]
2025-01-05 12:10     ` Markuss Broks
2025-01-05 12:18       ` Igor Belwon

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=Z3p1IV0rVH9dPQ_C@debian \
    --to=igor.belwon@mentallysanemainliners.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ivo.ivanov.ivanov1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh@kernel.org \
    /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