mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Onur Özkan" <work@onurozkan.dev>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Chen-Yu Tsai" <wens@kernel.org>,
	"Jernej Skrabec" <jernej.skrabec@gmail.com>,
	"Samuel Holland" <samuel@sholland.org>,
	"Alim Akhtar" <alim.akhtar@samsung.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v1 1/2] arm64: dts: add missing sram-supply to mali gpu nodes
Date: Sun, 15 Feb 2026 11:27:16 +0100	[thread overview]
Message-ID: <738a4531-fec8-4ca7-98fd-a3971c666bd5@kernel.org> (raw)
In-Reply-To: <20260215100302.136719-1-work@onurozkan.dev>

On 15/02/2026 11:02, Onur Özkan wrote:
> Some arm64 Mali GPU DT nodes define mali-supply but
> are missing sram-supply.
> 
> As discussed in [1], sram-supply should be explicitly
> defined for all relevant compatibles. If there is no
> separate SRAM rail, it can reference the same regulator
> as mali-supply.

But is this then a sram-supply?

For me it seems you just want to get rid of the warning from [1] and
that is not correct patch. I don't care about that warning and you
should not add DTS changes just to remove the warning.

You should add a CORRECT supply, if one exist. If one does not exist,
you cannot add it.

Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597

> 
> This change adds the missing sram-supply properties to
> affected DT files. This aligns DTs with expected regulator
> modeling and avoids relying on implicit fallback behavior.
> 
> [1]: https://lore.kernel.org/all/20260213155937.6af75786@nimda/

That's not really relevant... and my first impression was that you miss
bindings. You should rather explain this all in terms of hardware or
bindings - e.g. this supply is or is not in the bindings and you are
adding it because it's missing.

> 
> Signed-off-by: Onur Özkan <work@onurozkan.dev>



Please split your patch per Soc subsystems.


> ---

...

> diff --git a/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi b/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi
> index a1fb354dea9f..aba7f7325d8c 100644
> --- a/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi
> +++ b/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi
> @@ -356,6 +356,7 @@ &dsi {
>  
>  &gpu {
>  	mali-supply = <&buck6_reg>;
> +	sram-supply = <&buck6_reg>;

There is no dedicated sram supply. It is probably routed internally, so
I don't think we should expose it.

Best regards,
Krzysztof

  parent reply	other threads:[~2026-02-15 10:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-15 10:02 Onur Özkan
2026-02-15 10:02 ` [PATCH v1 2/2] drm/panthor: treat sram as mandatory except mt8196 Onur Özkan
2026-02-15 22:21   ` Adam Ford
2026-02-16  9:44     ` Boris Brezillon
2026-02-16 11:44       ` AngeloGioacchino Del Regno
2026-02-16 12:43         ` Nicolas Frattaroli
2026-02-16 13:59           ` Liviu Dudau
2026-02-16 14:20             ` Boris Brezillon
2026-02-16 14:06           ` Boris Brezillon
2026-02-16  9:37   ` Boris Brezillon
2026-02-16 14:41     ` Onur Özkan
2026-02-16 15:20       ` Steven Price
2026-02-15 10:27 ` Krzysztof Kozlowski [this message]
2026-02-16 11:33 ` [PATCH v1 1/2] arm64: dts: add missing sram-supply to mali gpu nodes AngeloGioacchino Del Regno
2026-02-24 11:19 ` Chen-Yu Tsai

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=738a4531-fec8-4ca7-98fd-a3971c666bd5@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=heiko@sntech.de \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=magnus.damm@gmail.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@kernel.org \
    --cc=work@onurozkan.dev \
    /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

all inboxes | Powered by JetHome®