[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <91c80c8e-729d-46ac-bb05-2cdcdb95ba1e@tuxon.dev>
Date: Mon, 9 Dec 2024 14:22:06 +0200
From: Claudiu Beznea <claudiu.beznea@...on.dev>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: mturquette@...libre.com, sboyd@...nel.org, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, biju.das.jz@...renesas.com,
prabhakar.mahadev-lad.rj@...renesas.com, lgirdwood@...il.com,
broonie@...nel.org, magnus.damm@...il.com, linus.walleij@...aro.org,
perex@...ex.cz, tiwai@...e.com, p.zabel@...gutronix.de,
linux-renesas-soc@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-sound@...r.kernel.org, linux-gpio@...r.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
Subject: Re: [PATCH v3 02/25] clk: versaclock3: Prepare for the addition of
5L35023 device
Hi, Geert,
On 09.12.2024 14:16, Geert Uytterhoeven wrote:
> Hi CLaudiu,
>
> On Mon, Dec 9, 2024 at 12:14 PM Claudiu Beznea <claudiu.beznea@...on.dev> wrote:
>> On 09.12.2024 12:57, Geert Uytterhoeven wrote:
>>> On Wed, Nov 13, 2024 at 2:35 PM Claudiu <claudiu.beznea@...on.dev> wrote:
>>>> From: Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
>>>>
>>>> The 5P35023 and 5L35035 Versa 3 clock generator variants are different but
>>>> the versaclock3 driver could be used with small adjustments. The features
>>>> that are implemented in driver and differs b/w variants are the PLL2 Fvco
>>>> and clock sel bit for SE2 clock. Adjust the driver to prepare for the
>>>> addition of 5L35023 device.
>>>>
>>>> Reviewed-by: Biju Das <biju.das.jz@...renesas.com>
>>>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
>>>
>>> Thanks for your patch!
>>>
>>>> --- a/drivers/clk/clk-versaclock3.c
>>>> +++ b/drivers/clk/clk-versaclock3.c
>>>> @@ -166,12 +167,17 @@ struct vc3_div_data {
>>>> struct vc3_hw_data {
>>>> struct clk_hw hw;
>>>> struct regmap *regmap;
>>>> - const void *data;
>>>> + void *data;
>>>>
>>>> u32 div_int;
>>>> u32 div_frc;
>>>> };
>>>
>>>> @@ -698,8 +706,6 @@ static struct vc3_hw_data clk_pll[] = {
>>>> .num = VC3_PLL2,
>>>> .int_div_msb_offs = VC3_PLL2_FB_INT_DIV_MSB,
>>>> .int_div_lsb_offs = VC3_PLL2_FB_INT_DIV_LSB,
>>>> - .vco_min = VC3_PLL2_VCO_MIN,
>>>> - .vco_max = VC3_PLL2_VCO_MAX
>>>> },
>>>> .hw.init = &(struct clk_init_data) {
>>>> .name = "pll2",
>>>
>>>> @@ -1029,9 +1037,16 @@ static int vc3_probe(struct i2c_client *client)
>>>> clk_pfd[i].hw.init->name);
>>>> }
>>>>
>>>> + data = i2c_get_match_data(client);
>>>> +
>>>> /* Register pll's */
>>>> for (i = 0; i < ARRAY_SIZE(clk_pll); i++) {
>>>> clk_pll[i].regmap = regmap;
>>>> + if (i == VC3_PLL2) {
>>>> + struct vc3_pll_data *pll_data = clk_pll[i].data;
>>>> +
>>>> + pll_data->vco = data->pll2_vco;
>>>
>>> You cannot modify the global clk_pll[] data, as it is shared when
>>> there are multiple instances.
>>
>> By "multiple instances" do you mean, multiple versa3 devices using this
>> driver? Do you know if we have such a board integrated, ATM?
>
> Exactly.
> Currently there are no such (upstream) users for 5p35023,
> but e.g. the Beacon RZ/G2M kit has two 5p49v6965 instances.
Are you OK with keeping it as is for the RZ/G3S SSIF support and returning
back later with a solution for the scenario you pointed out? Although, ATM,
I don't have a board to test it.
Thank you,
Claudiu
>
> Gr{oetje,eeting}s,
>
> Geert
>
Powered by blists - more mailing lists