From: Ryan Wanner <ryan.wanner@microchip.com>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>,
<mturquette@baylibre.com>, <sboyd@kernel.org>,
<alexandre.belloni@bootlin.com>, <nicolas.ferre@microchip.com>
Cc: <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<varshini.rajendran@microchip.com>
Subject: Re: [PATCH v4 21/31] clk: at91: dt-compat: switch to parent_hw and parent_data
Date: Fri, 9 Jan 2026 10:03:42 -0700 [thread overview]
Message-ID: <0402804e-7575-42b2-9990-1b09fca80451@microchip.com> (raw)
In-Reply-To: <eed15c43-dde3-410b-b2a3-655f4acf8d97@tuxon.dev>
On 10/20/25 12:15, Claudiu Beznea wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hi, Ryan,
>
> On 9/19/25 00:16, Ryan.Wanner@microchip.com wrote:
>> From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
>>
>> Switch old dt-compat clocks to use parent_hw and parent_data. Having
>> parent_hw instead of parent names improves to clock registration
>> speed and re-parenting.
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
>> Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
>> ---
>> drivers/clk/at91/dt-compat.c | 80 +++++++++++++++++++++++++-----------
>> 1 file changed, 56 insertions(+), 24 deletions(-)
>>
>> diff --git a/drivers/clk/at91/dt-compat.c b/drivers/clk/at91/dt-compat.c
>> index fa8658d3be7b..9ca871b817e0 100644
>> --- a/drivers/clk/at91/dt-compat.c
>> +++ b/drivers/clk/at91/dt-compat.c
>> @@ -43,7 +43,8 @@ static void __init of_sama5d2_clk_audio_pll_frac_setup(struct device_node *np)
>>
>> parent_name = of_clk_get_parent_name(np, 0);
>>
>> - hw = at91_clk_register_audio_pll_frac(regmap, name, parent_name, NULL);
>> + hw = at91_clk_register_audio_pll_frac(regmap, name, NULL,
>> + &AT91_CLK_PD_NAME(parent_name));
>> if (IS_ERR(hw))
>> return;
>>
>> @@ -69,7 +70,8 @@ static void __init of_sama5d2_clk_audio_pll_pad_setup(struct device_node *np)
>>
>> parent_name = of_clk_get_parent_name(np, 0);
>>
>> - hw = at91_clk_register_audio_pll_pad(regmap, name, parent_name, NULL);
>> + hw = at91_clk_register_audio_pll_pad(regmap, name, NULL,
>> + &AT91_CLK_PD_NAME(parent_name));
>> if (IS_ERR(hw))
>> return;
>>
>> @@ -95,7 +97,7 @@ static void __init of_sama5d2_clk_audio_pll_pmc_setup(struct device_node *np)
>>
>> parent_name = of_clk_get_parent_name(np, 0);
>>
>> - hw = at91_clk_register_audio_pll_pmc(regmap, name, parent_name, NULL);
>> + hw = at91_clk_register_audio_pll_pmc(regmap, name, NULL, &AT91_CLK_PD_NAME(parent_name));
>> if (IS_ERR(hw))
>> return;
>>
>> @@ -129,6 +131,7 @@ static void __init of_sama5d2_clk_generated_setup(struct device_node *np)
>> struct clk_hw *hw;
>> unsigned int num_parents;
>> const char *parent_names[GENERATED_SOURCE_MAX];
>> + struct clk_parent_data parent_data[GENERATED_SOURCE_MAX];
>> struct device_node *gcknp, *parent_np;
>> struct clk_range range = CLK_RANGE(0, 0);
>> struct regmap *regmap;
>> @@ -149,6 +152,8 @@ static void __init of_sama5d2_clk_generated_setup(struct device_node *np)
>> if (IS_ERR(regmap))
>> return;
>>
>> + for (unsigned int i = 0; i < num_parents; i++)
>> + parent_data[i] = AT91_CLK_PD_NAME(parent_names[i]);
>> for_each_child_of_node(np, gcknp) {
>> int chg_pid = INT_MIN;
>>
>> @@ -171,7 +176,7 @@ static void __init of_sama5d2_clk_generated_setup(struct device_node *np)
>>
>> hw = at91_clk_register_generated(regmap, &pmc_pcr_lock,
>> &dt_pcr_layout, name,
>> - parent_names, NULL, NULL,
>> + NULL, parent_data, NULL,
>> num_parents, id, &range,
>> chg_pid);
>> if (IS_ERR(hw))
>> @@ -201,7 +206,7 @@ static void __init of_sama5d4_clk_h32mx_setup(struct device_node *np)
>>
>> parent_name = of_clk_get_parent_name(np, 0);
>>
>> - hw = at91_clk_register_h32mx(regmap, name, parent_name, NULL);
>> + hw = at91_clk_register_h32mx(regmap, name, NULL, &AT91_CLK_PD_NAME(parent_name));
>> if (IS_ERR(hw))
>> return;
>>
>> @@ -228,6 +233,8 @@ static void __init of_sama5d2_clk_i2s_mux_setup(struct device_node *np)
>> return;
>>
>> for_each_child_of_node(np, i2s_mux_np) {
>> + struct clk_parent_data parent_data[2];
>> +
>> if (of_property_read_u8(i2s_mux_np, "reg", &bus_id))
>> continue;
>>
>> @@ -238,8 +245,10 @@ static void __init of_sama5d2_clk_i2s_mux_setup(struct device_node *np)
>> if (ret != 2)
>> continue;
>>
>> + parent_data[0] = AT91_CLK_PD_NAME(parent_names[0]);
>> + parent_data[1] = AT91_CLK_PD_NAME(parent_names[1]);
>> hw = at91_clk_i2s_mux_register(regmap_sfr, i2s_mux_np->name,
>> - parent_names, NULL, 2, bus_id);
>> + NULL, parent_data, 2, bus_id);
>> if (IS_ERR(hw))
>> continue;
>>
>> @@ -269,7 +278,8 @@ static void __init of_at91rm9200_clk_main_osc_setup(struct device_node *np)
>> if (IS_ERR(regmap))
>> return;
>>
>> - hw = at91_clk_register_main_osc(regmap, name, parent_name, NULL, bypass);
>> + hw = at91_clk_register_main_osc(regmap, name, NULL,
>> + &AT91_CLK_PD_NAME(parent_name), bypass);
>> if (IS_ERR(hw))
>> return;
>>
>> @@ -323,7 +333,7 @@ static void __init of_at91rm9200_clk_main_setup(struct device_node *np)
>> if (IS_ERR(regmap))
>> return;
>>
>> - hw = at91_clk_register_rm9200_main(regmap, name, parent_name, NULL);
>> + hw = at91_clk_register_rm9200_main(regmap, name, NULL, &AT91_CLK_PD_NAME(parent_name));
>> if (IS_ERR(hw))
>> return;
>>
>> @@ -336,6 +346,7 @@ static void __init of_at91sam9x5_clk_main_setup(struct device_node *np)
>> {
>> struct clk_hw *hw;
>> const char *parent_names[2];
>> + struct clk_parent_data parent_data[2];
>> unsigned int num_parents;
>> const char *name = np->name;
>> struct regmap *regmap;
>> @@ -354,7 +365,9 @@ static void __init of_at91sam9x5_clk_main_setup(struct device_node *np)
>>
>> of_property_read_string(np, "clock-output-names", &name);
>>
>> - hw = at91_clk_register_sam9x5_main(regmap, name, parent_names, NULL,
>> + parent_data[0] = AT91_CLK_PD_NAME(parent_names[0]);
>> + parent_data[1] = AT91_CLK_PD_NAME(parent_names[1]);
>> + hw = at91_clk_register_sam9x5_main(regmap, name, NULL, parent_data,
>> num_parents);
>> if (IS_ERR(hw))
>> return;
>> @@ -396,6 +409,7 @@ of_at91_clk_master_setup(struct device_node *np,
>> struct clk_hw *hw;
>> unsigned int num_parents;
>> const char *parent_names[MASTER_SOURCE_MAX];
>> + struct clk_parent_data parent_data[MASTER_SOURCE_MAX];
>> const char *name = np->name;
>> struct clk_master_characteristics *characteristics;
>> struct regmap *regmap;
>> @@ -419,13 +433,15 @@ of_at91_clk_master_setup(struct device_node *np,
>> if (IS_ERR(regmap))
>> return;
>>
>> + for (unsigned int i = 0; i < MASTER_SOURCE_MAX; i++)
>> + parent_data[i] = AT91_CLK_PD_NAME(parent_names[i]);
>> hw = at91_clk_register_master_pres(regmap, "masterck_pres", num_parents,
>> - parent_names, NULL, layout,
>> + NULL, parent_data, layout,
>> characteristics, &mck_lock);
>> if (IS_ERR(hw))
>> goto out_free_characteristics;
>>
>> - hw = at91_clk_register_master_div(regmap, name, "masterck_pres", NULL,
>> + hw = at91_clk_register_master_div(regmap, name, NULL, &AT91_CLK_PD_HW(hw),
>> layout, characteristics,
>> &mck_lock, CLK_SET_RATE_GATE, 0);
>
> Looks like at91_clk_register_master_div() could be kept to use parent_hws
> instead of parent_data.
Looking into this more the register_master_div calls
at91_clk_register_master_internal() which is used for all of the SoCs.
Some of the SoCs that use this function only have the parents passed in
by name string and not clk_hw. Would it be wise to add another function
for this to account for clk_hw and parent name? Or keep the use of
parent_data?
Ryan
next prev parent reply other threads:[~2026-01-09 17:03 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 21:15 [PATCH v4 00/31] clk: at91: add support for parent_data and Ryan.Wanner
2025-09-18 21:15 ` [PATCH v4 01/31] clk: at91: pmc: add macros for clk_parent_data Ryan.Wanner
2025-10-20 19:40 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 02/31] clk: at91: pmc: Move macro to header file Ryan.Wanner
2025-09-18 21:15 ` [PATCH v4 03/31] clk: at91: sam9x75: switch to parent_hw and parent_data Ryan.Wanner
2025-10-20 19:38 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 04/31] clk: at91: clk-sam9x60-pll: use clk_parent_data Ryan.Wanner
2025-10-20 19:41 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 05/31] clk: at91: clk-peripheral: switch to clk_parent_data Ryan.Wanner
2025-10-20 19:41 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 06/31] clk: at91: clk-main: switch to clk parent data Ryan.Wanner
2025-10-20 19:42 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 07/31] clk: at91: clk-utmi: use clk_parent_data Ryan.Wanner
2025-10-20 19:43 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 08/31] clk: at91: clk-master: " Ryan.Wanner
2025-10-20 19:44 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 09/31] clk: at91: clk-programmable: " Ryan.Wanner
2025-09-18 21:15 ` [PATCH v4 10/31] clk: at91: clk-generated: " Ryan.Wanner
2025-10-20 19:39 ` Claudiu Beznea
2025-10-20 19:45 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 11/31] clk: at91: clk-usb: add support for clk_parent_data Ryan.Wanner
2025-10-20 19:17 ` Claudiu Beznea
2025-12-18 16:23 ` Ryan.Wanner
2025-12-23 14:00 ` claudiu beznea
2026-01-05 17:58 ` Ryan.Wanner
2026-01-10 15:03 ` Claudiu Beznea
2026-01-12 21:25 ` Ryan Wanner
2026-01-16 6:57 ` claudiu beznea
2025-09-18 21:15 ` [PATCH v4 12/31] clk: at91: clk-system: use clk_parent_data Ryan.Wanner
2025-09-18 21:15 ` [PATCH v4 13/31] clk: at91: sama7d65: switch to parent_hw and parent_data Ryan.Wanner
2025-10-20 19:14 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 14/31] clk: at91: clk-pll: add support for parent_hw Ryan.Wanner
2025-09-18 21:15 ` [PATCH v4 15/31] clk: at91: clk-audio-pll: " Ryan.Wanner
2025-09-18 21:15 ` [PATCH v4 16/31] clk: at91: clk-plldiv: " Ryan.Wanner
2025-10-20 19:12 ` Claudiu Beznea
2025-09-18 21:15 ` [PATCH v4 17/31] clk: at91: clk-h32mx: " Ryan.Wanner
2025-10-20 19:12 ` Claudiu Beznea
2025-09-18 21:16 ` [PATCH v4 18/31] clk: at91: clk-i2s-mux: " Ryan.Wanner
2025-10-20 19:13 ` Claudiu Beznea
2025-09-18 21:16 ` [PATCH v4 19/31] clk: at91: clk-smd: add support for clk_parent_data Ryan.Wanner
2025-10-20 19:14 ` Claudiu Beznea
2025-09-18 21:16 ` [PATCH v4 20/31] clk: at91: clk-slow: add support for parent_hw Ryan.Wanner
2025-10-20 19:17 ` Claudiu Beznea
2025-09-18 21:16 ` [PATCH v4 21/31] clk: at91: dt-compat: switch to parent_hw and parent_data Ryan.Wanner
2025-10-20 19:15 ` Claudiu Beznea
2026-01-09 17:03 ` Ryan Wanner [this message]
2026-01-10 15:07 ` Claudiu Beznea
2025-09-18 21:16 ` [PATCH v4 22/31] clk: at91: sam9x60: " Ryan.Wanner
2025-09-18 21:16 ` [PATCH v4 23/31] clk: at91: sama5d2: " Ryan.Wanner
2025-10-20 19:19 ` Claudiu Beznea
2025-09-18 21:16 ` [PATCH v4 24/31] clk: at91: sama5d3: " Ryan.Wanner
2025-09-18 21:16 ` [PATCH v4 25/31] clk: at91: sama5d4: " Ryan.Wanner
2025-09-18 21:16 ` [PATCH v4 26/31] clk: at91: at91sam9x5: " Ryan.Wanner
2025-10-20 19:19 ` Claudiu Beznea
2025-09-18 21:16 ` [PATCH v4 27/31] clk: at91: at91rm9200: " Ryan.Wanner
2025-09-18 21:16 ` [PATCH v4 28/31] clk: at91: at91sam9260: " Ryan.Wanner
2025-10-20 19:35 ` Claudiu Beznea
2025-09-18 21:16 ` [PATCH v4 29/31] clk: at91: at91sam9g45: " Ryan.Wanner
2025-09-18 21:16 ` [PATCH v4 30/31] clk: at91: at91sam9n12: " Ryan.Wanner
2025-09-18 21:16 ` [PATCH v4 31/31] clk: at91: at91sam9rl: switch to clk_parent_data Ryan.Wanner
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=0402804e-7575-42b2-9990-1b09fca80451@microchip.com \
--to=ryan.wanner@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=sboyd@kernel.org \
--cc=varshini.rajendran@microchip.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