Message ID | 20220421085112.78858-1-miquel.raynal@bootlin.com (mailing list archive) |
---|---|
Headers | show |
Series | RZN1 DMA support | expand |
Hi Miquel, On Thu, Apr 21, 2022 at 10:51 AM Miquel Raynal <miquel.raynal@bootlin.com> wrote: > This is the series bringing DMA support to RZN1 platforms. > Other series follow with eg. UART and RTC support as well. Thanks for your series! > There is no other conflicting dependency with the other series, so this > series can now entirely be merged in the dmaengine tree I believe. > > Changes in v11: > * Renamed two defines. > * Changed the way the bitmap is declared. > * Updated the cover letter: this series can now go in through the > dmaengine tree. /me confused > Miquel Raynal (9): > dt-bindings: dmaengine: Introduce RZN1 dmamux bindings > dt-bindings: clock: r9a06g032-sysctrl: Reference the DMAMUX subnode > dt-bindings: dmaengine: Introduce RZN1 DMA compatible > soc: renesas: rzn1-sysc: Export function to set dmamux > dmaengine: dw: dmamux: Introduce RZN1 DMA router support > clk: renesas: r9a06g032: Probe possible children > dmaengine: dw: Add RZN1 compatible > ARM: dts: r9a06g032: Add the two DMA nodes > ARM: dts: r9a06g032: Describe the DMA router The last two DTS parts have to go in through the renesas-arm-dt and soc trees. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Hi Geert, geert@linux-m68k.org wrote on Mon, 25 Apr 2022 18:05:34 +0200: > Hi Miquel, > > On Thu, Apr 21, 2022 at 10:51 AM Miquel Raynal > <miquel.raynal@bootlin.com> wrote: > > This is the series bringing DMA support to RZN1 platforms. > > Other series follow with eg. UART and RTC support as well. > > Thanks for your series! > > > There is no other conflicting dependency with the other series, so this > > series can now entirely be merged in the dmaengine tree I believe. > > > > Changes in v11: > > * Renamed two defines. > > * Changed the way the bitmap is declared. > > * Updated the cover letter: this series can now go in through the > > dmaengine tree. > > /me confused > > > Miquel Raynal (9): > > dt-bindings: dmaengine: Introduce RZN1 dmamux bindings > > dt-bindings: clock: r9a06g032-sysctrl: Reference the DMAMUX subnode > > dt-bindings: dmaengine: Introduce RZN1 DMA compatible > > soc: renesas: rzn1-sysc: Export function to set dmamux > > dmaengine: dw: dmamux: Introduce RZN1 DMA router support > > clk: renesas: r9a06g032: Probe possible children > > dmaengine: dw: Add RZN1 compatible > > ARM: dts: r9a06g032: Add the two DMA nodes > > ARM: dts: r9a06g032: Describe the DMA router > > The last two DTS parts have to go in through the renesas-arm-dt and > soc trees. Yes, DT usually never go in through subsystem trees anyway, of course they should be taken in through the Renesas tree. For the other patches I think its simpler if everything goes through the dmaengine tree, but I'm fine either way, I'll let you discuss this with the DMA folks if you disagree. Thanks, Miquèl
Hi Miquel, On Tue, Apr 26, 2022 at 9:32 AM Miquel Raynal <miquel.raynal@bootlin.com> wrote: > geert@linux-m68k.org wrote on Mon, 25 Apr 2022 18:05:34 +0200: > > On Thu, Apr 21, 2022 at 10:51 AM Miquel Raynal > > <miquel.raynal@bootlin.com> wrote: > > > This is the series bringing DMA support to RZN1 platforms. > > > Other series follow with eg. UART and RTC support as well. > > > > Thanks for your series! > > > > > There is no other conflicting dependency with the other series, so this > > > series can now entirely be merged in the dmaengine tree I believe. > > > > > > Changes in v11: > > > * Renamed two defines. > > > * Changed the way the bitmap is declared. > > > * Updated the cover letter: this series can now go in through the > > > dmaengine tree. > > > > /me confused > > > > > Miquel Raynal (9): > > > dt-bindings: dmaengine: Introduce RZN1 dmamux bindings > > > dt-bindings: clock: r9a06g032-sysctrl: Reference the DMAMUX subnode > > > dt-bindings: dmaengine: Introduce RZN1 DMA compatible > > > soc: renesas: rzn1-sysc: Export function to set dmamux > > > dmaengine: dw: dmamux: Introduce RZN1 DMA router support > > > clk: renesas: r9a06g032: Probe possible children > > > dmaengine: dw: Add RZN1 compatible > > > ARM: dts: r9a06g032: Add the two DMA nodes > > > ARM: dts: r9a06g032: Describe the DMA router > > > > The last two DTS parts have to go in through the renesas-arm-dt and > > soc trees. > > Yes, DT usually never go in through subsystem trees anyway, of > course they should be taken in through the Renesas tree. For the other > patches I think its simpler if everything goes through the dmaengine > tree, but I'm fine either way, I'll let you discuss this with the DMA > folks if you disagree. Fine for me. I've acked the renesas-clk related patches, so they can go in through the dmaengine tree. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Hi Geert, geert@linux-m68k.org wrote on Wed, 27 Apr 2022 14:50:43 +0200: > Hi Miquel, > > On Tue, Apr 26, 2022 at 9:32 AM Miquel Raynal <miquel.raynal@bootlin.com> wrote: > > geert@linux-m68k.org wrote on Mon, 25 Apr 2022 18:05:34 +0200: > > > On Thu, Apr 21, 2022 at 10:51 AM Miquel Raynal > > > <miquel.raynal@bootlin.com> wrote: > > > > This is the series bringing DMA support to RZN1 platforms. > > > > Other series follow with eg. UART and RTC support as well. > > > > > > Thanks for your series! > > > > > > > There is no other conflicting dependency with the other series, so this > > > > series can now entirely be merged in the dmaengine tree I believe. > > > > > > > > Changes in v11: > > > > * Renamed two defines. > > > > * Changed the way the bitmap is declared. > > > > * Updated the cover letter: this series can now go in through the > > > > dmaengine tree. > > > > > > /me confused > > > > > > > Miquel Raynal (9): > > > > dt-bindings: dmaengine: Introduce RZN1 dmamux bindings > > > > dt-bindings: clock: r9a06g032-sysctrl: Reference the DMAMUX subnode > > > > dt-bindings: dmaengine: Introduce RZN1 DMA compatible > > > > soc: renesas: rzn1-sysc: Export function to set dmamux > > > > dmaengine: dw: dmamux: Introduce RZN1 DMA router support > > > > clk: renesas: r9a06g032: Probe possible children > > > > dmaengine: dw: Add RZN1 compatible > > > > ARM: dts: r9a06g032: Add the two DMA nodes > > > > ARM: dts: r9a06g032: Describe the DMA router > > > > > > The last two DTS parts have to go in through the renesas-arm-dt and > > > soc trees. > > > > Yes, DT usually never go in through subsystem trees anyway, of > > course they should be taken in through the Renesas tree. For the other > > patches I think its simpler if everything goes through the dmaengine > > tree, but I'm fine either way, I'll let you discuss this with the DMA > > folks if you disagree. > > Fine for me. I've acked the renesas-clk related patches, so they > can go in through the dmaengine tree. Perfect. Sounds like v12 is the right one \o/ Thanks for all the feedback you keep providing on all the RZ/N1 (correctly spelled this time;-) ) series. Cheers, Miquèl