On Sat, 15 Mar 2025 10:24:14 +0100, Christian Marangi wrote:
> It's currently possible to make the bootloader crash on calling
> clk_set_rate caused by the loop in clk_clean_rate_cache.
>
> The loop assume that every child of the clock node are also clock
> device but this is not always the case.
Il giorno mar 8 apr 2025 alle ore 07:56 Michael Nazzareno Trimarchi
ha scritto:
>
> Hi
>
> Il lun 7 apr 2025, 22:03 Fabio Estevam ha scritto:
>>
>> On Mon, Apr 7, 2025 at 4:58 PM Michael Nazzareno Trimarchi
>> wrote:
>>
>> > Can you review it and pick if needed?
>>
>> This is not assigned to me
On Sat, Mar 15, 2025 at 10:24:14AM +0100, Christian Marangi wrote:
> It's currently possible to make the bootloader crash on calling
> clk_set_rate caused by the loop in clk_clean_rate_cache.
>
> The loop assume that every child of the clock node are also clock
> device but this is not always the
Hi
Il lun 7 apr 2025, 22:03 Fabio Estevam ha scritto:
> On Mon, Apr 7, 2025 at 4:58 PM Michael Nazzareno Trimarchi
> wrote:
>
> > Can you review it and pick if needed?
>
> This is not assigned to me in patchwork as it is not i.MX related.
>
> Someone else needs to handle it.
>
I was thinking t
On Mon, Apr 7, 2025 at 4:58 PM Michael Nazzareno Trimarchi
wrote:
> Can you review it and pick if needed?
This is not assigned to me in patchwork as it is not i.MX related.
Someone else needs to handle it.
Hi Fabio
On Mon, Apr 7, 2025 at 9:55 PM Christian Marangi
wrote:
> On Sat, Mar 15, 2025 at 10:24:14AM +0100, Christian Marangi wrote:
> > It's currently possible to make the bootloader crash on calling
> > clk_set_rate caused by the loop in clk_clean_rate_cache.
> >
> > The loop assume that ever
Hi
On Sat, Mar 15, 2025 at 10:24 AM Christian Marangi
wrote:
> It's currently possible to make the bootloader crash on calling
> clk_set_rate caused by the loop in clk_clean_rate_cache.
>
> The loop assume that every child of the clock node are also clock
> device but this is not always the case
It's currently possible to make the bootloader crash on calling
clk_set_rate caused by the loop in clk_clean_rate_cache.
The loop assume that every child of the clock node are also clock
device but this is not always the case. For example it's common for a
clock to bind to a reset device or also e
8 matches
Mail list logo