[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16cfbc63-ab19-40fb-a885-6726f829d7d3@tuxon.dev>
Date: Sat, 31 Jan 2026 16:04:22 +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 26/31] clk: at91: at91sam9x5: switch to parent_data and
parent_hw
On 1/16/26 22:07, ryan.wanner@...rochip.com wrote:
> From: Claudiu Beznea<claudiu.beznea@...on.dev>
>
> Switch AT91SAM9X5 clocks to use parent_data and parent_hw where possible.
> Having parent_data instead of parent names improves to clock registration
> speed and re-parenting. Update clock registration functions to use
> clk_hw.
Same here as in patch 24/31.
>
> Signed-off-by: Claudiu Beznea<claudiu.beznea@...on.dev>
> Signed-off-by: Ryan Wanner<Ryan.Wanner@...rochip.com>
With that addressed:
Reviewed-by: Claudiu Beznea <claudiu.beznea@...on.dev>
Powered by blists - more mailing lists