Hi Miquel,
On Thu, Apr 7, 2022 at 10:16 AM Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote:
> sboyd@xxxxxxxxxx wrote on Wed, 06 Apr 2022 17:45:09 -0700:
> > Quoting Miquel Raynal (2022-04-06 09:18:47)
> > > Here is a first series bringing DMA support to RZN1 platforms. Soon a
> > > second series will come with changes made to the UART controller
> > > driver, in order to interact with the RZN1 DMA controller.
> > >
> > > Stephen acked the sysctrl patch (in the clk driver) but somehow I feel
> > > like it would be good to have this patch applied on both sides
> > > (dmaengine and clk) because more changes will depend on the addition of
> > > this helper, that are not related to DMA at all. I'll let you folks
> > > figure out what is best.
> >
> > Are you sending more patches in the next 7 weeks or so that will touch
> > the same area? If so, then it sounds like I'll need to take the clk
> > patch through clk tree. I don't know what is best because I don't have
> > the information about what everyone plans to do in that file.
>
> This series brings DMA support and needs to access the dmamux registers
> that are in the sysctrl area.
>
> I've sent an RTC series which needs to access this area as well, but
> it is not fully ready yet as it was advised to go for a reset
> controller in this case. The reset controller would be registered by
> the clock driver, so yes it would touch the same file.
>
> Finally, there is an USB series that is coming soon, I don't know if
> it will be ready for merge for 5.19, but it needs to access a specific
> register in this area as well (h2mode).
>
> So provided that we are able to contribute this reset driver quickly
> enough, I would argue that it is safer to merge the clk changes in the
> clk tree.
The clk tree or the renesas-clk tree? ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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
