On Wed, Nov 23, 2022 at 09:16:55PM +0530, Anup Patel wrote: > On Wed, Nov 23, 2022 at 7:17 PM Conor Dooley <conor.dooley@xxxxxxxxxxxxx> wrote: > > > Adding a new timer DT node would mean, the RISC-V timer driver > > > will now be probed using the compatible to the new DT node whereas > > > the RISC-V timer driver is currently probed using CPU DT nodes. > > > > In that case, we would have to retain the ability to match against the > > "riscv". Spitballing: > > - add a new timer node > > - keep matching against "riscv" > > - look up a timer node during init w/ of_find_matching_node() that > > contains any new timer properties > > > > I think it's unlikely that this will be the last time we have to add > > some timer properties & we should avoid doing odd things in a DT to suit > > an operating system? > > > > Would something along those lines work Anup, or am I, yet again, missing > > something? > > I was already working on v3 along these lines. I will try to post a v3 this > week itself. Cool, I'll keep my eyes peeled :) Thanks Anup!
