[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02eb0831-8fda-417b-840d-d7b5a87f0692@tuxon.dev>
Date: Mon, 26 Jan 2026 10:52:21 +0200
From: Claudiu Beznea <claudiu.beznea@...on.dev>
To: ryan.wanner@...rochip.com, mturquette@...libre.com, sboyd@...nel.org,
nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com,
bmasney@...hat.com, alexander.sverdlin@...il.com,
varshini.rajendran@...rochip.com
Cc: cristian.birsan@...rochip.com, balamanikandan.gunasundar@...rochip.com,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 06/31] clk: at91: clk-main: switch to clk parent data
On 1/16/26 22:06, ryan.wanner@...rochip.com wrote:
> From: Claudiu Beznea<claudiu.beznea@...on.dev>
>
> Use struct clk_parent_data instead of parent_hw for the main clock.
> So there is less usage of __clk_get_hw() in SoC specific clock drivers and
> simpler conversion of existing SoC specific clock drivers from parent_names to
> modern clk_parent_data structures. This will lead in the end at removing
> __clk_get_hw() in SoC specific drivers
> (that will be solved by subsequent commits).
>
> Signed-off-by: Claudiu Beznea<claudiu.beznea@...on.dev>
> [ryan.wanner@...rochip: Add SAMA7D65 and SAM9X75 SoCs to use parent_data.]
> Signed-off-by: Ryan Wanner<Ryan.Wanner@...rochip.com>
Reviewed-by: Claudiu Beznea <claudiu.beznea@...on.dev>
Powered by blists - more mailing lists