From: Marek Vasut <marex@denx.de>
To: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>,
Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Lionel Debieve <lionel.debieve@foss.st.com>
Cc: linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] hwrng: stm32 - implement support for STM32MP25x platforms
Date: Tue, 15 Oct 2024 17:39:51 +0200 [thread overview]
Message-ID: <e5a21bb8-00c3-41f1-9a4d-856eb1465d45@denx.de> (raw)
In-Reply-To: <b06b5d09-190b-4567-aecd-4be1f1dee172@foss.st.com>
On 10/15/24 5:10 PM, Gatien CHEVALLIER wrote:
>
>
> On 10/14/24 20:55, Marek Vasut wrote:
>> On 10/14/24 2:36 PM, Gatien CHEVALLIER wrote:
>>>
>>>
>>> On 10/14/24 10:52, Marek Vasut wrote:
>>>> On 10/14/24 10:38 AM, Gatien CHEVALLIER wrote:
>>>>>
>>>>>
>>>>> On 10/11/24 18:17, Marek Vasut wrote:
>>>>>> On 10/11/24 5:41 PM, Gatien Chevallier wrote:
>>>>>>
>>>>>> [...]
>>>>>>
>>>>>>> @@ -551,6 +565,41 @@ static int stm32_rng_probe(struct
>>>>>>> platform_device *ofdev)
>>>>>>> priv->rng.read = stm32_rng_read;
>>>>>>> priv->rng.quality = 900;
>>>>>>> + if (!priv->data->nb_clock || priv->data->nb_clock > 2)
>>>>>>> + return -EINVAL;
>>>>>>> +
>>>>>>> + priv->clk_bulk = devm_kzalloc(dev, priv->data->nb_clock *
>>>>>>> sizeof(*priv->clk_bulk),
>>>>>>> + GFP_KERNEL);
>>>>>>> + if (!priv->clk_bulk)
>>>>>>> + return -ENOMEM;
>>>>>>
>>>>>> Try this:
>>>>>>
>>>>>> ret = devm_clk_bulk_get(dev, priv->data->nb_clock, priv->clk_bulk);
>>>>>> ...
>>>>>> // Swap the clock if they are not in the right order:
>>>>>> if (priv->data->nb_clock == 2 &&
>>>>>> strcmp(__clk_get_name(priv->clk_bulk[0].clk), "core"))
>>>>>> {
>>>>>> const char *id = priv->clk_bulk[1].id;
>>>>>> struct clk *clk = priv->clk_bulk[1].clk;
>>>>>> priv->clk_bulk[1].id = priv->clk_bulk[0].id;
>>>>>> priv->clk_bulk[1].clk = priv->clk_bulk[0].clk;
>>>>>> priv->clk_bulk[0].id = id;
>>>>>> priv->clk_bulk[0].clk = clk;
>>>>>> }
>>>>>>
>>>>>
>>>>> Hi Marek,
>>>>>
>>>>> This won't work as the name returned by this API is clk->core->name.
>>>>> AFAICT, it doesn't correspond to the names present in the device tree
>>>>> under the "clock-names" property.
>>>>> Any other idea or are you fine with what's below?
>>>> Hmmm, it is not great, but at least it reduces the changes
>>>> throughout the driver, so that is an improvement.
>>>>
>>>> I guess one could do some of_clk_get() and clk_is_match() in probe
>>>> to look up the clock in OF by name and then compare which clock is
>>>> which before swapping them in clk_bulk[] array, but that might be
>>>> too convoluted?
>>>
>>> Yes, probably too much. What's present in the patch is not close to
>>> perfection but has the advantage of being straightforward. If we agree
>>> on that, I'll send a V3 containing the modifications in the bindings
>>> file.
>> Errr, I'm sorry, maybe there is a way to do this better. Look at
>> drivers/clk/clk-bulk.c :
>>
>> 15 static int __must_check of_clk_bulk_get(struct device_node *np,
>> int num_clks,
>> 16 struct clk_bulk_data *clks)
>> 17 {
>> 18 int ret;
>> 19 int i;
>> 20
>> 21 for (i = 0; i < num_clks; i++) {
>> 22 clks[i].id = NULL;
>> 23 clks[i].clk = NULL;
>> 24 }
>> 25
>> 26 for (i = 0; i < num_clks; i++) {
>> 27 of_property_read_string_index(np, "clock-names",
>> i, &clks[i].id);
>> 28 clks[i].clk = of_clk_get(np, i);
>>
>> If I read this right, then clks[i].id should be the DT clock name. So
>> the swap conditional above could use .id to identify whether the first
>> position is core clock or not, like this:
>>
>> if (priv->data->nb_clock == 2 &&
>> strcmp(__clk_get_name(priv->clk_bulk[0].id), "core"))
>> ^^
>>
>> You might need to use devm_clk_bulk_get_all() to access the
>> of_clk_bulk_get() .
>>
>> Or am I missing something still ?
>
> Oooooh I see, devm_clk_bulk_get() and devm_clk_bulk_get_all() use
> a different path. I don't understand why, to be honest... The doc
> doesn't state this difference either.
Indeed, but maybe git log could clarify that ? I learnt about this
useful trick at last year Embedded Recipes:
$ git log -L:clk_bulk_get_all:drivers/clk/clk-bulk.c
> I'll give this a try while also correcting the issue that the robot
> highlighted.
Thank you !
next prev parent reply other threads:[~2024-10-15 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 15:41 [PATCH v2 0/4] Add support for stm32mp25x RNG Gatien Chevallier
2024-10-11 15:41 ` [PATCH v2 1/4] dt-bindings: rng: add st,stm32mp25-rng support Gatien Chevallier
2024-10-14 7:29 ` Krzysztof Kozlowski
2024-10-14 9:31 ` Gatien CHEVALLIER
2024-10-11 15:41 ` [PATCH v2 2/4] hwrng: stm32 - implement support for STM32MP25x platforms Gatien Chevallier
2024-10-11 16:17 ` Marek Vasut
2024-10-14 8:38 ` Gatien CHEVALLIER
2024-10-14 8:52 ` Marek Vasut
2024-10-14 12:36 ` Gatien CHEVALLIER
2024-10-14 18:55 ` Marek Vasut
2024-10-15 15:10 ` Gatien CHEVALLIER
2024-10-15 15:39 ` Marek Vasut [this message]
2024-10-16 7:54 ` Gatien CHEVALLIER
2024-10-15 6:46 ` kernel test robot
2024-10-11 15:41 ` [PATCH v2 3/4] hwrng: stm32 - update STM32MP15 RNG max clock frequency Gatien Chevallier
2024-10-11 16:17 ` Marek Vasut
2024-10-11 15:41 ` [PATCH v2 4/4] arm64: dts: st: add RNG node on stm32mp251 Gatien Chevallier
2024-10-11 16:17 ` Marek Vasut
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=e5a21bb8-00c3-41f1-9a4d-856eb1465d45@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gatien.chevallier@foss.st.com \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lionel.debieve@foss.st.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivia@selenic.com \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).