Devicetree
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	linux-renesas-soc@vger.kernel.org,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: renesas: r8a78000-ironhide: enable to use SCMI
Date: Wed, 27 May 2026 10:14:01 +0200	[thread overview]
Message-ID: <ahanyVCJoqk9Hl8x@shikoro> (raw)
In-Reply-To: <CAMuHMdXpGLYrSMNgkqUGhhBJPuQKt-KZGGsXsbchAixbYRvD9w@mail.gmail.com>

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

Hi Geert,

we are missing you here! :)

> > +                       scmi_clk: protocol@14 {
> > +                               reg = <0x14>;
> > +                               #clock-cells = <1>;
> > +                       };
> 
> I am a bit reluctant to apply this patch: with all current firmware
> versions, the system will lock up after "clk: Disabling unused clocks",
> unless "clk_ignore_unused" is used, or unless out-of-tree SCMI
> quirk handling patches are applied.

Yeah, I understand. Maybe we leave out only the scmi_clk hunk and
send it separately once it works upstream?

All the best,

   Wolfram


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

  reply	other threads:[~2026-05-27  8:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  7:47 [PATCH v2 0/2] arm64: renesas: r8a78000-ironhide: enable SCMI Wolfram Sang
2026-05-19  7:47 ` [PATCH v2 1/2] arm64: renesas: r8a78000: add MFIS, MFIS SCP and transport nodes Wolfram Sang
2026-05-19  8:05   ` sashiko-bot
2026-05-19  8:38     ` Wolfram Sang
2026-05-27  7:42   ` Geert Uytterhoeven
2026-05-19  7:47 ` [PATCH v2 2/2] arm64: renesas: r8a78000-ironhide: enable to use SCMI Wolfram Sang
2026-05-19  8:17   ` sashiko-bot
2026-05-19  8:39     ` Wolfram Sang
2026-05-27  7:49   ` Geert Uytterhoeven
2026-05-27  8:14     ` Wolfram Sang [this message]
2026-05-28 13:30       ` Geert Uytterhoeven

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=ahanyVCJoqk9Hl8x@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --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