[PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks

[Stephen Boyd]

Quoting Stefan Wahren (2022-07-11 04:55:36)
> Am 11.07.22 um 09:02 schrieb Ivan T. Ivanov:
> > On 2022-07-10 14:12, Stefan Wahren wrote:
> >> Am 10.05.22 um 15:30 schrieb Maxime Ripard:
> >>> On Tue, May 10, 2022 at 01:20:18PM +0000, Guillaume Gardet wrote:
> >>>> May I ask what's the status/plan of this patch series?
> >>> As far as I know it hasn't been merged yet.
> >>>
> >>>> It seems it has not been merged yet, and I know we are a bit late in
> >>>> the 5.18 schedule, but I think this is a good fix for 5.18.
> >>> Fix for what? I don't think this series fix any bug?
> >>
> >> i think this series (or at least parts of it) is a workaround for this
> >> issue [1].
> >
> > No, not really. Bug which this patch set fixes is this one [2].
> 
> Both are related. In your case the device tree defines a clock ID which 
> isn't define in the kernel driver. So the behavior (abort probing in 
> case of invalid DTB) is correct to me. But the log message isn't helpful 
> to end users.
> 
> This is broken by design, since we need to synchronize videocore 
> firmware, kernel and DTB at the same time. Maybe this works for 
> Raspberry Pi OS, but not for all users.
> 
> We need to fix this driver before add new clocks.
> 

Please resend this series. I didn't follow the discussion.