Re: [PATCH v2 0/6] soc: ti: Add Keystone Navigator drivers

[Greg Kroah-Hartman]

On Tue, May 20, 2014 at 09:57:50AM -0400, Santosh Shilimkar wrote:
> Greg,
> 
> On Wednesday 23 April 2014 07:46 PM, Santosh Shilimkar wrote:
> > Here is an updated version of the Keystone Navigator drivers after
> > addressing comments from earlier version [1].
> > 
> > The QMSS found on Keystone SOCs is one of the main hardware sub
> > system which forms the backbone of the Keystone Multi-core Navigator.
> > QMSS consist of queue managers, packed-data structure processors(PDSP),
> > linking RAM, descriptor pools and infrastructure DMA.
> > 
> > After the discussion and alignment [2] on Navigator DMA, now we pair
> > this driver along with QMSS. Initially this driver was proposed as DMA
> > engine driver but since the hardware is not typical DMA engine and doesn't
> > comply with typical DMA engine driver needs, that approach was naked.
> > 
> > These two drivers works as infrastructure drivers for subsystems like
> > Ethernet subsystem, SRIO subsystem, Crypto Engines etc on Keystone
> > SOC families. Testing is done with NetCP(ethernet) subsystem drivers.
> > 
> > I would like to get these drivers merged in upcoming(3.16) window, so
> > any help in terms of review is appreciated. Thanks
> > 
> > Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> > Cc: Kumar Gala <galak@xxxxxxxxxxxxxx>
> > Cc: Olof Johansson <olof@xxxxxxxxx>
> > Cc: Arnd Bergmann <arnd@xxxxxxxx>
> > Cc: Grant Likely <grant.likely@xxxxxxxxxx>
> > Cc: Rob Herring <robh+dt@xxxxxxxxxx>
> > Cc: Mark Rutland <mark.rutland@xxxxxxx>
> > 
> I plan to respin v3 of the series for the few device tree related
> comments I received from Rob H (thanks Rob). Can you please have a
> look and gsee if you have any comments so that I can include them
> in next version.

I am so far behind in patch review, please just redo them based on
other's comments and resend, don't wait for me.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/