Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Clément Le Goffic" <clegoffic@baylibre.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Brian Masney <bmasney+clk@redhat.com>,
	Jerome Brunet <jbrunet+clk@baylibre.com>,
	Ulf Hansson <ulfh@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Marek Vasut <marek.vasut+renesas@mailbox.org>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Vinod Koul <vkoul@kernel.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Paul Elder <paul.elder+renesas@ideasonboard.com>,
	Sudeep Holla <sudeep.holla@kernel.org>,
	Cristian Marussi <cristian.marussi@arm.com>,
	arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v5 00/15] R-Car X5H Ironhide CPG/MDLC SCMI remapping support
Date: Fri, 20 Nov 2026 01:47:59 +0200	[thread overview]
Message-ID: <20261119234759.GB2324725@killaraus.ideasonboard.com> (raw)
In-Reply-To: <1e9c5ac3-d82b-4af9-9946-0302cadf7404@baylibre.com>

On Thu, Nov 19, 2026 at 03:47:15PM +0100, Clément Le Goffic wrote:
> On 11/18/26 8:44 PM, Geert Uytterhoeven wrote:
> > 	Hi all,
> > 
> > TL;DR:
> > 
> >     Describe hardware in DT, and perform mapping to abstractions offered
> >     by SCMI in Linux.
> 
> A question on the approach
> An SCMI variant DT could mark the CPG and MDLC status = "reserved" and point the consumers at arm,scmi, while the U-Boot IPL keeps the hardware DT.
> Since v4, the series assumes the SCMI ids are stable:
> 
> >   - Remove dependencies by making assumptions and dropping disputed
> >     items, to move this series forward:
> >       - Assume all SCMI IDs are stable.
> 
> If they are, why not using them in the DT directly?

As far as I understand, the assumption impacts the mdlc and cpg drivers
only, not their DT bindings. If (or rather, let's face it, when) a
firmware revision later breaks the assumption, we will be able to handle
it in those drivers without affecting DT.

I don't like this remapping driver much, in the sense that I wish it
wouldn't be needed, but it seems to me to be the best possible
compromise given the instability introduced by SCMI.

> On partitioning, the cover letter says:
> 
> >   - The clock, reset, and power domain IDs are not stable by design,
> >     causing DT incompatibilities.
> >     SCMI requires that the ID space exposed to an agent (i.e. Linux)
> >     starts at zero and is contiguous.  Hence any change in system
> >     partitioning (Application CPU core vs. Realtime CPU core,
> >     virtualization, ...) may mean a renumbering of all SCMI IDs,
> >     implying a massive change to the DT.
> 
> SCMI do not mandate that renumbering. The ids start at zero and are sequential, but nothing requires them to cover only the resources of one agent.
> The firmware can keep a single id space for all agents and restrict per agent what each one may use, the rest returning DENIED (SCMI 4.0, section 3.2.1).
> For virtualization, the spec has the hypervisor grant each VM its resources this way. A new VM then changes permissions, not ids.
> 
> With a single id space, a software configuration only changes which nodes are enabled, so one DT per software configuration, a base DT plus an overlay, is enough.
> If managing many configurations ever becomes a nightmare, tools exist for it, such as Lopper from devicetree-org [1], which generate one DT per execution domain from a single system DT.
> 
> That leaves the missing clock domain, which is a gap in SCMI itself.
> 
> [1] https://github.com/devicetree-org/lopper

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2026-11-19 23:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 19:44 [PATCH v5 00/15] R-Car X5H Ironhide CPG/MDLC SCMI remapping support Geert Uytterhoeven
2026-11-18 19:44 ` [PATCH v5 01/15] clk: renesas: r8a78000: Merge debug prints in r8a78000_clk_get() Geert Uytterhoeven
2026-11-20  2:57   ` Marek Vasut
2026-11-18 19:44 ` [PATCH v5 02/15] clk: renesas: r8a78000: Replace sentinel by explicit ID map size Geert Uytterhoeven
2026-11-20  3:02   ` Marek Vasut
2026-11-18 19:44 ` [PATCH v5 03/15] clk: renesas: r8a78000: Shrink IDs to 16 bits Geert Uytterhoeven
2026-11-20  3:04   ` Marek Vasut
2026-11-18 19:44 ` [PATCH v5 04/15] clk: renesas: r8a78000: Add clk_hw to clk_map Geert Uytterhoeven
2026-11-20  3:25   ` Marek Vasut
2026-11-18 19:44 ` [PATCH v5 05/15] clk: renesas: r8a78000: Add SCMI remapping support Geert Uytterhoeven
2026-11-20  3:45   ` Marek Vasut
2026-11-18 19:44 ` [PATCH v5 06/15] reset: Extract __reset_control_get_from_provider() Geert Uytterhoeven
2026-11-18 19:44 ` [PATCH v5 07/15] reset: Add reset_control_get_from_provider_exclusive() Geert Uytterhoeven
2026-11-18 19:44 ` [PATCH v5 08/15] pmdomain: Make genpd_get_from_provider() always return on first match Geert Uytterhoeven
2026-11-18 19:44 ` [PATCH v5 09/15] pmdomain: Make genpd_get_from_provider() return -EPROBE_DEFER Geert Uytterhoeven
2026-11-18 19:44 ` [PATCH v5 10/15] pmdomain: Make genpd_get_from_provider() public Geert Uytterhoeven
2026-11-18 19:44 ` [PATCH v5 11/15] pmdomain: renesas: r8a78000: Drop MDLC name comment Geert Uytterhoeven
2026-11-20  3:35   ` Marek Vasut
2026-11-18 19:45 ` [PATCH v5 12/15] pmdomain: renesas: r8a78000: Replace sentinel by explicit ID map size Geert Uytterhoeven
2026-11-20  3:36   ` Marek Vasut
2026-11-18 19:45 ` [PATCH v5 13/15] pmdomain: renesas: r8a78000: Shrink IDs to 16 bits Geert Uytterhoeven
2026-11-20  3:37   ` Marek Vasut
2026-11-18 19:45 ` [PATCH v5 14/15] pmdomain: renesas: r8a78000: Add SCMI remapping support Geert Uytterhoeven
2026-11-18 19:45 ` [PATCH v5 15/15] arm64: dts: renesas: ironhide: Enable SCMI devpd, sys, clock, and reset Geert Uytterhoeven
2026-11-19 14:47 ` [PATCH v5 00/15] R-Car X5H Ironhide CPG/MDLC SCMI remapping support Clément Le Goffic
2026-11-19 23:47   ` Laurent Pinchart [this message]

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=20261119234759.GB2324725@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=bmasney+clk@redhat.com \
    --cc=clegoffic@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=jbrunet+clk@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=p.zabel@pengutronix.de \
    --cc=paul.elder+renesas@ideasonboard.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sudeep.holla@kernel.org \
    --cc=ulfh@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=wsa+renesas@sang-engineering.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