Messages in this thread | | | Date | Fri, 4 Feb 2022 18:47:49 +0000 | Subject | Re: [PATCH v5 00/12] Update the Icicle Kit device tree | From | Conor Dooley <> |
| |
On 04/02/2022 18:09, Palmer Dabbelt wrote: > On Mon, 31 Jan 2022 03:47:15 PST (-0800), conor.dooley@microchip.com wrote: >> From: Conor Dooley <conor.dooley@microchip.com> >> >> This series updates the Microchip Icicle Kit device tree by adding a >> host of peripherals, and some updates to the memory map. In addition, >> the device tree has been split into a third part, which contains "soft" >> peripherals that are in the fpga fabric. >> >> Several of the entries are for peripherals that have not get had their >> drivers upstreamed, so in those cases the dt bindings are included where >> appropriate in order to avoid the many "DT compatible string <x> appears >> un-documented" errors. >> >> Depends on mpfs clock driver binding (on clk/next) to provide >> dt-bindings/clock/microchip,mpfs-clock.h >> and on the other changes to the icicle/mpfs device tree from geert >> that are already in linux/riscv/for-next. >> >> Additionally, the interrupt-extended warnings on the plic/clint are >> cleared by [1] & [2]. >> >> [1] >> https://lore.kernel.org/linux-riscv/cover.1639744468.git.geert@linux-m68k.org/ >> >> [2] >> https://lore.kernel.org/linux-riscv/cover.1639744106.git.geert@linux-m68k.org/ >> >> <snip> > > Looks like Rob still has some feedback that still needs to be addressed.
Still not passing Rob's bot as it depends on a binding in clk-next & I also need to reword the descriptions in the PWM binding.
> I'm happy to take these via the RISC-V tree when the bindings are set
Great
> (assuming the DTs match whatever gets agreed upons), but also fine if > someone else wants to take it > Acked-by: Palmer Dabbelt <palmer@rivosinc.com> > > Either way, I'm going to drop this (and the v4, which was at the top of > my inbox) as it looks like there'll be at least a v6. Yup, hopefully v6 on Monday
Thanks, Conor.
| |