[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ed6pn7h6.ffs@tglx>
Date: Thu, 15 Aug 2024 17:14:45 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Samuel Holland <samuel.holland@...ive.com>, Anup Patel
<apatel@...tanamicro.com>, Emil Renner Berthing
<emil.renner.berthing@...onical.com>
Cc: linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org, Paul
Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Daniel Lezcano
<daniel.lezcano@...aro.org>
Subject: Re: [PATCH v1 0/9] Fix Allwinner D1 boot regression
On Thu, Aug 15 2024 at 09:41, Samuel Holland wrote:
> On 2024-08-15 9:16 AM, Anup Patel wrote:
>> Almost all RISC-V platforms (except this one) have SBI Timer always
>> available and Linux uses a better timer or Sstc extension whenever
>> it is available.
>
> So this is the immediate solution: add the CLINT to the firmware
> devicetree so that the SBI time extension works, and Linux will boot
> without any code changes, albeit with a higher-overhead clockevent
> device.
That does not matter for the boot process when the sun4i timer becomes
available afterwards. But how can this be retrofitted along with the
kernel update?
Thanks,
tglx
Powered by blists - more mailing lists