From: Greg KH <gregkh@linuxfoundation.org>
To: "J. German Rivera" <German.Rivera@freescale.com>
Cc: arnd@arndb.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, stuart.yoder@freescale.com,
itai.katz@freescale.com, scottwood@freescale.com, agraf@suse.de,
bhamciu1@freescale.com, R89243@freescale.com,
bhupesh.sharma@freescale.com, nir.erez@freescale.com,
richard.schmitt@freescale.com, dan.carpenter@oracle.com
Subject: Re: [PATCH] staging: fsl-mc: up-rev version of MC interface code
Date: Wed, 16 Sep 2015 21:49:35 -0700 [thread overview]
Message-ID: <20150917044935.GA16404@kroah.com> (raw)
In-Reply-To: <1442348520-15837-1-git-send-email-German.Rivera@freescale.com>
On Tue, Sep 15, 2015 at 03:22:00PM -0500, J. German Rivera wrote:
> The DPAA2 management complex has a versioned binary interface
> that has to be kept in sync with the DPAA2 drivers. This patch
> uprevs the APIs that build MC commands and parse results.
> This uprev is needed to support object interrupts.
>
> MC binary interface changes
> -overall version from 6.0 to 8.0
> -dprc version from 3.0 to 4.0
> -dpbp and dpmcp versions from 2.0 to 2.1
> -new dprc commands -- set/get obj irq, set obj label,
> get obj descriptor
> -removed commands -- get portal paddr
> -object regions are reported as region offsets not physical
> addresses
>
> build/parse API changes
> -flags arg is added to all APIs for future extensibility,
> hardcoded priority bit is now a flag
> -IRQ-related args are consolidated into an irq_cfg struct
>
> Signed-off-by: J. German Rivera <German.Rivera@freescale.com>
> ---
> drivers/staging/fsl-mc/bus/dpbp.c | 141 ++++++---
> drivers/staging/fsl-mc/bus/dpmcp-cmd.h | 2 +-
> drivers/staging/fsl-mc/bus/dpmcp.c | 123 +++++---
> drivers/staging/fsl-mc/bus/dpmcp.h | 123 +++++---
> drivers/staging/fsl-mc/bus/dpmng.c | 14 +-
> drivers/staging/fsl-mc/bus/dprc-cmd.h | 7 +-
> drivers/staging/fsl-mc/bus/dprc-driver.c | 8 +-
> drivers/staging/fsl-mc/bus/dprc.c | 464 +++++++++++++++++++++++-----
> drivers/staging/fsl-mc/bus/mc-allocator.c | 6 +-
> drivers/staging/fsl-mc/bus/mc-bus.c | 54 +++-
> drivers/staging/fsl-mc/include/dpbp-cmd.h | 2 +-
> drivers/staging/fsl-mc/include/dpbp.h | 91 ++++--
> drivers/staging/fsl-mc/include/dpcon-cmd.h | 2 +-
> drivers/staging/fsl-mc/include/dpmng.h | 14 +-
> drivers/staging/fsl-mc/include/dprc.h | 313 +++++++++++++++----
> drivers/staging/fsl-mc/include/mc-cmd.h | 28 +-
> drivers/staging/fsl-mc/include/mc-private.h | 15 +-
> 17 files changed, 1052 insertions(+), 355 deletions(-)
This patch does many things all at once. Please break it up into
different logical patches, each one only doing one thing, and send it as
a series so that it can be properly reviewed and applied to the tree.
thanks,
greg k-h
prev parent reply other threads:[~2015-09-17 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 20:22 [PATCH] staging: fsl-mc: up-rev version of MC interface code J. German Rivera
2015-09-17 4:49 ` Greg KH [this message]
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=20150917044935.GA16404@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=German.Rivera@freescale.com \
--cc=R89243@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=bhamciu1@freescale.com \
--cc=bhupesh.sharma@freescale.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=itai.katz@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.erez@freescale.com \
--cc=richard.schmitt@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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