From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Kumar Gala <galak@codeaurora.org>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 0/6] soc: ti: Add Keystone Navigator drivers
Date: Wed, 21 May 2014 05:01:04 +0900 [thread overview]
Message-ID: <20140520200104.GA27786@kroah.com> (raw)
In-Reply-To: <537B5F5E.9080703@ti.com>
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@linuxfoundation.org>
> > Cc: Kumar Gala <galak@codeaurora.org>
> > Cc: Olof Johansson <olof@lixom.net>
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: Grant Likely <grant.likely@linaro.org>
> > Cc: Rob Herring <robh+dt@kernel.org>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> >
> 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
next prev parent reply other threads:[~2014-05-20 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 23:46 [PATCH v2 0/6] soc: ti: Add Keystone Navigator drivers Santosh Shilimkar
[not found] ` <1398296783-1176-1-git-send-email-santosh.shilimkar-l0cyMroinI0@public.gmane.org>
2014-04-23 23:46 ` [PATCH v2 1/6] soc: Introduce drivers/soc place-holder for SOC specific drivers Santosh Shilimkar
2014-04-23 23:46 ` [PATCH v2 2/6] firmware: add Keystone QMSS PDSP accumulator firmware blob Santosh Shilimkar
2014-04-23 23:46 ` [PATCH v2 3/6] Documentation: dt: soc: add Keystone Navigator QMSS bindings Santosh Shilimkar
2014-05-05 16:18 ` Rob Herring
2014-04-23 23:46 ` [PATCH v2 4/6] soc: ti: add Keystone Navigator QMSS driver Santosh Shilimkar
2014-04-24 1:30 ` Felipe Balbi
2014-04-24 13:18 ` Santosh Shilimkar
2014-04-24 14:57 ` Felipe Balbi
2014-04-23 23:46 ` [PATCH v2 5/6] Documentation: dt: soc: add Keystone Navigator DMA bindings Santosh Shilimkar
[not found] ` <1398296783-1176-6-git-send-email-santosh.shilimkar-l0cyMroinI0@public.gmane.org>
2014-05-05 16:17 ` Rob Herring
[not found] ` <CAL_Jsq+uZscamuezWsHrwf_OuxucXOG4kT8V9xCzmBnF9cpEXA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-07 14:22 ` Santosh Shilimkar
2014-04-23 23:46 ` [PATCH v2 6/6] soc: ti: add Keystone Navigator DMA support Santosh Shilimkar
2014-05-20 13:57 ` [PATCH v2 0/6] soc: ti: Add Keystone Navigator drivers Santosh Shilimkar
2014-05-20 20:01 ` Greg Kroah-Hartman [this message]
2014-05-20 20:08 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140520200104.GA27786@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).