Re: [PATCH 0/6] soc: Add Baikal-T1 SoC APB/AXI EHB and L2-cache drivers

[Sergey Semin]

On Thu, Mar 26, 2020 at 03:12:46PM +0100, Arnd Bergmann wrote:
> On Fri, Mar 6, 2020 at 4:19 PM Arnd Bergmann <arnd@xxxxxxxx> wrote:
> >
> > On Fri, Mar 6, 2020 at 2:07 PM <Sergey.Semin@xxxxxxxxxxxxxxxxxxxx> wrote:
> > >
> > > From: Serge Semin <fancer.lancer@xxxxxxxxx>
> > >
> > > Aside from PCIe/SATA/DDR/I2C/CPU-reboot specific settings the Baikal-T1
> > > system controller provides three vendor-specific blocks. In particular
> > > there are two Errors Handler Blocks to detect and report an info regarding
> > > any problems discovered on the AXI and APB buses. These are the main buses
> > > utilized by the SoC devices to interact with each other. In addition there
> > > is a way to tune the MIPS P5600 CM2 L2-cache up by setting the Tag/Data/WS
> > > L2-to-RAM latencies. All of this functionality is implemented in the
> > > APB/AXI EHB and L2-cache control block drivers to be a part of the kernel soc
> > > subsystem (as being specific to the Baikal-T1 SoC) and introduced in the
> > > framework of this patchset.
> > >
> > > This patchset is rebased and tested on the mainline Linux kernel 5.6-rc4:
> > > commit 98d54f81e36b ("Linux 5.6-rc4").
> >
> > I have no objection to the drivers, but I wonder if these should be
> > in drivers/bus and drivers/memory instead of drivers/soc, which have
> > similar drivers already. The driver for the L2 cache is not really a
> > memory controller driver, but it may be close enough, and we
> > already have a couple of different things in there.
> 
> I don't see a reply to Rob's or my comments, so I assume you are not currently
> updating them and I will wait for a new version after the v5.7 merge window.
> 
> Dropping the series from patchwork for now, see [1].
> 
>        Arnd
> 
> [1] https://patchwork.kernel.org/project/linux-soc/list/

Yeah, sorry for the delay. I'll send an update very soon. A solution for
the ehb'es is settled. We agreed to move the drivers to the drivers/bus
subsystem. While we still don't know what to do with l2-cache driver.
Please see my last response to your comment on the cover-letter.

Regards,
-Sergey