[PATCH 6.6 1/4] riscv: dts: starfive: add assigned-clock* to limit frquency

Conor Dooley conor.dooley at microchip.com
Mon Sep 9 04:17:08 PDT 2024


On Mon, Sep 09, 2024 at 12:38:23PM +0200, Krzysztof Kozlowski wrote:
> On 09/09/2024 12:17, Conor Dooley wrote:
> > On Mon, Sep 09, 2024 at 03:46:27PM +0800, WangYuli wrote:
> >> From: William Qiu <william.qiu at starfivetech.com>
> >>
> >> In JH7110 SoC, we need to go by-pass mode, so we need add the
> >> assigned-clock* properties to limit clock frquency.
> >>
> >> Signed-off-by: William Qiu <william.qiu at starfivetech.com>
> >> Reviewed-by: Emil Renner Berthing <emil.renner.berthing at canonical.com>
> >> Signed-off-by: Conor Dooley <conor.dooley at microchip.com>
> >> Signed-off-by: WangYuli <wangyuli at uniontech.com>
> > 
> > What makes any of the patches in this 4 patch series stable material?
> 
> That's for stable? It needs to follow stable process rules, so proper
> commit ID.

[6.6] in the subject and Sasha/Greg/stable list on CC, so I figure it is
for stable, yeah. Only one of these patches is a "fix", and not really a
functional one, so I would like to know why this stuff is being
backported. I think under some definition of "new device IDs and quirks"
it could be suitable, but it'd be a looser definition than I personally
agree with!

Oh, and also, the 4 patches aren't threaded - you should fix that
WangYuli.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-riscv/attachments/20240909/da4a968c/attachment.sig>


More information about the linux-riscv mailing list