[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5650e47d-97ab-49a3-8342-7aad9daa5a1c@tuxon.dev>
Date: Mon, 20 Oct 2025 22:41:43 +0300
From: Claudiu Beznea <claudiu.beznea@...on.dev>
To: Ryan.Wanner@...rochip.com, mturquette@...libre.com, sboyd@...nel.org,
alexandre.belloni@...tlin.com, nicolas.ferre@...rochip.com
Cc: linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, varshini.rajendran@...rochip.com
Subject: Re: [PATCH v4 05/31] clk: at91: clk-peripheral: switch to
clk_parent_data
Hi, Ryan,
On 9/19/25 00:15, Ryan.Wanner@...rochip.com wrote:
> From: Claudiu Beznea <claudiu.beznea@...on.dev>
>
> Use struct clk_parent_data instead of parent_hw for peripheral clocks.
Could you please explain also why as done in other patches?
The rest looks good to me.
Thank you,
Claudiu
Powered by blists - more mailing lists