dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: vkoul@kernel.org
Cc: dmaengine@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: [PATCH 0/2] dmaengine: rcar-dmac: Add dma-channel-mask property support
Date: Wed, 28 Aug 2019 20:13:53 +0900	[thread overview]
Message-ID: <1566990835-27028-1-git-send-email-yoshihiro.shimoda.uh@renesas.com> (raw)

This patch series is based on
 - renesas-drivers.git / renesas-drivers-2019-08-13-v5.3-rc4 tag
 - and the following patch series:
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=165881

The commit e2d896c08ca3 ("Documentation: bindings: dma: Add binding for
dma-channel-mask") adds the generic property and R-Car also has such
use cases so that I made this patch series. Before adding the property
support, I made a clean-up patch as the patch 1/2.

Yoshihiro Shimoda (2):
  dmaengine: rcar-dmac: Don't set DMACHCLR bit 0 to 1 if iommu is mapped
  dmaengine: rcar-dmac: Add dma-channel-mask property support

 drivers/dma/sh/rcar-dmac.c | 32 ++++++++++++++++++++++++--------
 1 file changed, 24 insertions(+), 8 deletions(-)

-- 
2.7.4


             reply	other threads:[~2019-08-28 11:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 11:13 Yoshihiro Shimoda [this message]
2019-08-28 11:13 ` [PATCH 1/2] dmaengine: rcar-dmac: Don't set DMACHCLR bit 0 to 1 if iommu is mapped Yoshihiro Shimoda
2019-08-31  8:49   ` Simon Horman
2019-09-02  8:36   ` Geert Uytterhoeven
2019-09-02  9:21     ` Yoshihiro Shimoda
2019-09-02  8:52   ` Geert Uytterhoeven
2019-09-02  9:25     ` Yoshihiro Shimoda
2019-08-28 11:13 ` [PATCH 2/2] dmaengine: rcar-dmac: Add dma-channel-mask property support Yoshihiro Shimoda
2019-08-31  8:50   ` Simon Horman
2019-09-02  8:50   ` Geert Uytterhoeven

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=1566990835-27028-1-git-send-email-yoshihiro.shimoda.uh@renesas.com \
    --to=yoshihiro.shimoda.uh@renesas.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=vkoul@kernel.org \
    /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).