public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: <balbi@ti.com>
Cc: <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, Sandeep Nair <sandeep_n@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.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 4/6] soc: ti: add Keystone Navigator QMSS driver
Date: Thu, 24 Apr 2014 09:18:43 -0400	[thread overview]
Message-ID: <53590F33.6070508@ti.com> (raw)
In-Reply-To: <20140424013053.GC13374@saruman.home>

On Wednesday 23 April 2014 09:30 PM, Felipe Balbi wrote:
> Hi,
> 
> On Wed, Apr 23, 2014 at 07:46:20PM -0400, Santosh Shilimkar wrote:
>> From: Sandeep Nair <sandeep_n@ti.com>
>>
>> The QMSS (Queue Manager Sub System) 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
>> Packet DMA.
>>
>> The Queue Manager is a hardware module that is responsible for accelerating
>> management of the packet queues. Packets are queued/de-queued by writing or
>> reading descriptor address to a particular memory mapped location. The PDSPs
>> perform QMSS related functions like accumulation, QoS, or event management.
>> Linking RAM registers are used to link the descriptors which are stored in
>> descriptor RAM. Descriptor RAM is configurable as internal or external memory.
>>
>> The QMSS driver manages the PDSP setups, linking RAM regions,
>> queue pool management (allocation, push, pop and notify) and descriptor
>> pool management. The specifics on the device tree bindings for
>> QMSS can be found in:
>> 	Documentation/devicetree/bindings/soc/keystone-navigator-qmss.txt
>>
>> 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>
>> Signed-off-by: Sandeep Nair <sandeep_n@ti.com>
>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
>>  drivers/Kconfig                  |    2 +
>>  drivers/soc/Kconfig              |    2 +
>>  drivers/soc/Makefile             |    5 +
>>  drivers/soc/ti/Kconfig           |   21 +
>>  drivers/soc/ti/Makefile          |    4 +
>>  drivers/soc/ti/knav_qmss.h       |  386 ++++++++
>>  drivers/soc/ti/knav_qmss_acc.c   |  591 +++++++++++++
>>  drivers/soc/ti/knav_qmss_queue.c | 1814 ++++++++++++++++++++++++++++++++++++++
>>  include/linux/soc/ti/knav_qmss.h |   90 ++
>>  9 files changed, 2915 insertions(+)
>>  create mode 100644 drivers/soc/Makefile
>>  create mode 100644 drivers/soc/ti/Kconfig
>>  create mode 100644 drivers/soc/ti/Makefile
>>  create mode 100644 drivers/soc/ti/knav_qmss.h
>>  create mode 100644 drivers/soc/ti/knav_qmss_acc.c
>>  create mode 100644 drivers/soc/ti/knav_qmss_queue.c
>>  create mode 100644 include/linux/soc/ti/knav_qmss.h
>>
>> diff --git a/drivers/Kconfig b/drivers/Kconfig
>> index 0e87a34..8993913 100644
>> --- a/drivers/Kconfig
>> +++ b/drivers/Kconfig
>> @@ -148,6 +148,8 @@ source "drivers/remoteproc/Kconfig"
>>  
>>  source "drivers/rpmsg/Kconfig"
>>  
>> +source "drivers/soc/Kconfig"
> 
> This hunk was already in patch one but in a different offset in this
> file.
> 
right.. I will drop this one... Thanks for spotting it

  reply	other threads:[~2014-04-24 13:19 UTC|newest]

Thread overview: 15+ 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
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-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 [this message]
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
2014-05-05 16:17   ` Rob Herring
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
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=53590F33.6070508@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.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=sandeep_n@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