From: Haiying Wang <Haiying.Wang@nxp.com>
To: <linux-kernel@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <stuyoder@gmail.com>, <roy.pledge@nxp.com>,
Haiying Wang <Haiying.Wang@nxp.com>
Subject: [PATCH 0/3] bus: fsl-mc: dpio: udpate QMan CENA region
Date: Thu, 20 Apr 2017 15:34:15 -0400 [thread overview]
Message-ID: <1492716858-24509-1-git-send-email-Haiying.Wang@nxp.com> (raw)
This patchset allows the NXP's DPAA2 QMan Software portal
CENA region to be cacheable as designed for the performance
goal. Besides, the write allocate stash feature of the QMan
requires the non-shareable attribute for this cache-enabled
memory.
So this patchset extends the arm64 ioremap with cache-enable
and non-shareable first, then enables the CENA portal memory
access in the QBMan driver, at last changes the ioremap call
in dpio driver where the software portal CENA memory is
mapped to be the correct one.
Haiying Wang (3):
arm64: extend ioremap for cacheable non-shareable memory
bus: fsl-mc: dpio: enable qbman CENA portal memory access
bus: fsl-mc: dpio: change CENA regs to be cacheable
arch/arm64/include/asm/io.h | 1 +
arch/arm64/include/asm/pgtable-prot.h | 1 +
drivers/staging/fsl-mc/bus/dpio/dpio-driver.c | 6 +++---
drivers/staging/fsl-mc/bus/dpio/qbman-portal.c | 23 +++++++++++++++++------
4 files changed, 22 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2017-04-20 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 19:34 Haiying Wang [this message]
2017-04-20 19:34 ` [PATCH 1/3] arm64: extend ioremap for cacheable non-shareable memory Haiying Wang
2017-04-21 9:11 ` Mark Rutland
2017-04-21 14:30 ` Roy Pledge
2017-04-25 13:42 ` Mark Rutland
2017-04-20 19:34 ` [PATCH 2/3] bus: fsl-mc: dpio: enable qbman CENA portal memory access Haiying Wang
2017-04-21 9:25 ` Mark Rutland
2017-04-21 14:37 ` Catalin Marinas
2017-04-20 19:34 ` [PATCH 3/3] bus: fsl-mc: dpio: change CENA regs to be cacheable Haiying Wang
2017-04-21 9:27 ` Mark Rutland
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=1492716858-24509-1-git-send-email-Haiying.Wang@nxp.com \
--to=haiying.wang@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roy.pledge@nxp.com \
--cc=stuyoder@gmail.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).