From: "J. German Rivera" <German.Rivera@freescale.com>
To: <gregkh@linuxfoundation.org>, <arnd@arndb.de>,
<devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>
Cc: <stuart.yoder@freescale.com>, <itai.katz@freescale.com>,
<leoli@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: [PATCH v3 0/6] staging: fsl-mc: up-rev version of MC interface code
Date: Wed, 23 Sep 2015 16:10:57 -0500 [thread overview]
Message-ID: <1443042663-21580-1-git-send-email-German.Rivera@freescale.com> (raw)
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
Changes in v3:
Addressed comments from Gerg K-H:
- Removed re-formatting of parameters in function calls
- Removed extra blank lines
Addressed comments from Stuart Yoder:
- Removed indentation changes and parameter alignment changes
in header files
Changes in v2:
Split single patch into a patch series as requested by Greg K-H.
The new patch series consists of the following patches:
Patch 1: Add new flags field to MC command header
Patch 2: uprev binary interface for dpmng objects to v8.0
Patch 3: up-rev binary interface for dpbp objects to v2.0
Patch 4: up-rev binary interface for dpmcp objects to v2.0
Patch 5: up-rev binary interface for dpcon objects to v2.0
Patch 6: up-rev binary interface for dprc objects to v4.0
next reply other threads:[~2015-09-23 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 21:10 J. German Rivera [this message]
2015-09-23 21:10 ` [PATCH v3 1/6] staging: fsl-mc: Add new flags field to MC command header J. German Rivera
2015-09-23 21:10 ` [PATCH v3 2/6] staging: fsl-mc: uprev dpmng binary interface to v8.0 J. German Rivera
2015-09-23 21:11 ` [PATCH v3 3/6] staging: fsl-mc: up-rev dpbp binary interface to v2.0 J. German Rivera
2015-09-23 21:11 ` [PATCH v3 4/6] staging: fsl-mc: up-rev dpmcp " J. German Rivera
2015-09-23 21:11 ` [PATCH v3 5/6] staging: fsl-mc: up-rev dpcon " J. German Rivera
2015-09-23 21:11 ` [PATCH v3 6/6] staging: fsl-mc: up-rev dprc binary interface to v4.0 J. German Rivera
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=1443042663-21580-1-git-send-email-German.Rivera@freescale.com \
--to=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=gregkh@linuxfoundation.org \
--cc=itai.katz@freescale.com \
--cc=leoli@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
all inboxes | Powered by JetHome®