From: Guodong Xu <guodong.xu@linaro.org>
To: vkoul@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
dan.j.williams@intel.com
Cc: liyu65@hisilicon.com, suzhuangluan@hisilicon.com,
xuhongtao8@hisilicon.com, zhongkaihua@huawei.com,
xuezhiliang@hisilicon.com, xupeng7@huawei.com,
sunliang10@huawei.com, fengbaopeng@hisilicon.com,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Guodong Xu <guodong.xu@linaro.org>
Subject: [PATCH 0/3] k3dma: add support to reserved channels
Date: Fri, 22 Jun 2018 11:24:13 +0800 [thread overview]
Message-ID: <20180622032416.20133-1-guodong.xu@linaro.org> (raw)
This patchset fixes bug people found on hikey960 when allocating DMA
channels to peripherals such as SPI. It fails because the channel is
reserved, and is not accessible by kernel.
Patch 1 and 2 add support to reserved channels for K3 DMA. Patch 3
includes a removal of axi_config who controls DMA secure/non-secure
access permission but is actually set in early stage by bootloader.
Li Yu (3):
dt-bindings: k3dma: add optional property dma_min_chan
k3dma: add support to reserved minimum channels
k3dma: delete axi_config
Documentation/devicetree/bindings/dma/k3dma.txt | 6 ++++++
drivers/dma/k3dma.c | 16 ++++++++--------
2 files changed, 14 insertions(+), 8 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-22 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 3:24 Guodong Xu [this message]
2018-06-22 3:24 ` [PATCH 1/3] dt-bindings: k3dma: add optional property dma_min_chan Guodong Xu
2018-06-28 6:00 ` Vinod
2018-07-03 18:54 ` Rob Herring
2018-07-04 1:14 ` Guodong Xu
2018-07-06 3:17 ` Guodong Xu
2018-06-22 3:24 ` [PATCH 2/3] k3dma: add support to reserved minimum channels Guodong Xu
2018-06-28 6:02 ` Vinod
2018-07-06 3:05 ` Guodong Xu
2018-07-06 6:09 ` Vinod
2018-06-22 3:24 ` [PATCH 3/3] k3dma: delete axi_config Guodong Xu
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=20180622032416.20133-1-guodong.xu@linaro.org \
--to=guodong.xu@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=fengbaopeng@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liyu65@hisilicon.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sunliang10@huawei.com \
--cc=suzhuangluan@hisilicon.com \
--cc=vkoul@kernel.org \
--cc=xuezhiliang@hisilicon.com \
--cc=xuhongtao8@hisilicon.com \
--cc=xupeng7@huawei.com \
--cc=zhongkaihua@huawei.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).