[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df43411e-8982-74f5-6148-e7281c37dada@starfivetech.com>
Date: Tue, 23 May 2023 10:56:43 +0800
From: Xingyu Wu <xingyu.wu@...rfivetech.com>
To: Conor Dooley <conor.dooley@...rochip.com>,
Torsten Duwe <duwe@....de>
CC: <linux-riscv@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<yanhong.wang@...rfivetech.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
Conor Dooley <conor@...nel.org>,
Emil Renner Berthing <kernel@...il.dk>,
"Rob Herring" <robh+dt@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
"Hal Feng" <hal.feng@...rfivetech.com>,
William Qiu <william.qiu@...rfivetech.com>,
<linux-kernel@...r.kernel.org>, <linux-clk@...r.kernel.org>
Subject: Re: [PATCH v4 1/7] dt-bindings: clock: Add StarFive JH7110 PLL clock
generator
On 2023/5/19 22:16, Conor Dooley wrote:
> On Fri, May 19, 2023 at 03:57:33PM +0200, Torsten Duwe wrote:
>> On Fri, May 12, 2023 at 10:20:30AM +0800, Xingyu Wu wrote:
>> [...]
>> > #ifndef __DT_BINDINGS_CLOCK_STARFIVE_JH7110_CRG_H__
>> > #define __DT_BINDINGS_CLOCK_STARFIVE_JH7110_CRG_H__
>> >
>> > +/* PLL clocks */
>> > +#define JH7110_CLK_PLL0_OUT 0
>> > +#define JH7110_CLK_PLL1_OUT 1
>> > +#define JH7110_CLK_PLL2_OUT 2
>>
>> In U-Boot commit 58c9c60b Yanhong Wang added:
>>
>> +
>> +#define JH7110_SYSCLK_PLL0_OUT 190
>> +#define JH7110_SYSCLK_PLL1_OUT 191
>> +#define JH7110_SYSCLK_PLL2_OUT 192
>> +
>> +#define JH7110_SYSCLK_END 193
>>
>> in that respective file.
>>
>> > +#define JH7110_PLLCLK_END 3
>> > +
>> > /* SYSCRG clocks */
>> > #define JH7110_SYSCLK_CPU_ROOT 0
>>
>> If the symbolic names referred to the same items, would it be possible
>> to keep the two files in sync somehow?
>
> Ohh, that's not good.. If you pass the U-Boot dtb to Linux it won't
> understand the numbering. The headers are part of the dt-binding :/
Because PLL driver is separated from SYSCRG drivers in Linux, the numbering
starts from 0. But in Uboot, the PLL driver is included in the SYSCRG driver,
and the number follows the SYSCRG.
Best regards,
Xingyu Wu
Powered by blists - more mailing lists