Re: [PATCH v2 0/5] Rework SCMI Clock driver clk_ops setup procedure

From: Sudeep Holla <sudeep.holla@arm.com>
To: mturquette@baylibre.com, sboyd@kernel.org
Cc: Cristian Marussi <cristian.marussi@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
	james.quinlan@broadcom.com, f.fainelli@gmail.com,
	vincent.guittot@linaro.org, peng.fan@oss.nxp.com,
	michal.simek@amd.com, quic_sibis@quicinc.com,
	quic_nkela@quicinc.com, souvik.chakravarty@arm.com
Subject: Re: [PATCH v2 0/5] Rework SCMI Clock driver clk_ops setup procedure
Date: Thu, 4 Apr 2024 15:25:38 +0100	[thread overview]
Message-ID: <Zg64Yk-COGfS7cTD@bogus> (raw)
In-Reply-To: <20240325210025.1448717-1-cristian.marussi@arm.com>

Hi Stephen,

On Mon, Mar 25, 2024 at 09:00:20PM +0000, Cristian Marussi wrote:
> Hi,
>

[...]

>
> This rework introduces a dynamic allocation mechanism to be able to
> configure the required clk_ops at run-time when the SCMI clocks are
> enumerated.
>
> Only one single clk_ops is generated for each of the features combinations
> effectively found in the set of returned SCMI resources.
>
> Once this preliminary rework is done in 1/5, the following patches use this
> new clk_ops schema to introduce a number of restricted clk_ops depending on
> the specific retrieved SCMI clocks characteristics.
>

Let me know if you are happy with this changes. There is no strict
dependency on the changes in SCMI tree ATM, so I can provide reviewed-by
if you would like to take it via clk tree. If you prefer me to take it
via SCMI tree, please provide Ack if you are OK with the changes.

--
Regards,
Sudeep