mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Steffen Trumtrar <s.trumtrar@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Kai Assman <kai.assmann@de.bosch.com>, barebox@lists.infradead.org
Subject: Re: [PATCH] clk: zynq: eval ps-clock-frequency from DT
Date: Tue, 09 May 2023 08:09:05 +0200	[thread overview]
Message-ID: <87pm7a2fw9.fsf@pengutronix.de> (raw)
In-Reply-To: <04c84b06-68df-2366-04bc-135f48ce9119@pengutronix.de>


On 2023-05-08 at 13:17 +02, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:

> On 08.05.23 09:24, Steffen Trumtrar wrote:
>> From: Kai Assman <kai.assmann@de.bosch.com>
>>
>> Currently the ps_clk_rate is locked to 33.3MHz. The devicetree
>> provides a property "ps-clock-frequency" that specifies this clock.
>>
>> If the property is found, overwrite ps_clk_rate otherwise stay at the
>> default 33.3MHz
>
> The commit message reads as is this is an upstream binding, but I find no
> usage, documentation or driver code parsing it in Linux v6.4-rc1.
>
> Is this a new barebox-specific binding? If so, the commit message should be
> reworded to make this clear. You can also drop a short .rst file into
> Documentation/devicetree/bindings/clocks to describe your new property.
>

Ha, you are right. I could have sworn to have seen this binding already
and didn't check :(

I'll change that.

>> Signed-off-by: Kai Assmann <kai.assmann@de.bosch.com>
>> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
>> ---
>>  drivers/clk/zynq/clkc.c | 3 +++
>>  1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/clk/zynq/clkc.c b/drivers/clk/zynq/clkc.c
>> index 8e4beda295..37a0fbadb5 100644
>> --- a/drivers/clk/zynq/clkc.c
>> +++ b/drivers/clk/zynq/clkc.c
>> @@ -388,6 +388,9 @@ static int zynq_clock_probe(struct device *dev)
>>  			return PTR_ERR(parent_res);
>>
>>  		slcr_offset = parent_res->start;
>> +
>> +		of_property_read_u32(dev->device_node, "ps-clock-frequency",
>> +				     (u32 *)&ps_clk_rate);
>
> Please do not cast compiler warnings away. You should change the type of
> ps_clk_rate instead to u32, so this code is 64-bit-safe.

Ack.


Thanks,
Steffen

--
Pengutronix e.K.                | Dipl.-Inform. Steffen Trumtrar |
Steuerwalder Str. 21            | https://www.pengutronix.de/    |
31137 Hildesheim, Germany       | Phone: +49-5121-206917-0       |
Amtsgericht Hildesheim, HRA 2686| Fax:   +49-5121-206917-5555    |



      reply	other threads:[~2023-05-09  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  7:24 Steffen Trumtrar
2023-05-08 11:17 ` Ahmad Fatoum
2023-05-09  6:09   ` Steffen Trumtrar [this message]

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=87pm7a2fw9.fsf@pengutronix.de \
    --to=s.trumtrar@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=kai.assmann@de.bosch.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