devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Samuel Holland <samuel@sholland.org>
Cc: Maxime Ripard <mripard@kernel.org>,
	dmaengine@vger.kernel.org,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Vinod Koul <vkoul@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	linux-sunxi@lists.linux.dev, Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: dma: sun50i-a64: Add compatible for D1
Date: Mon, 29 Nov 2021 17:13:42 -0600	[thread overview]
Message-ID: <YaVepmEInHXCPvQA@robh.at.kernel.org> (raw)
In-Reply-To: <20211119052702.14392-2-samuel@sholland.org>

On Thu, 18 Nov 2021 23:26:58 -0600, Samuel Holland wrote:
> D1 has a DMA controller similar to the one in other Allwinner SoCs.
> Add its compatible, and include it in the list of variants with a
> separate MBUS clock gate.
> 
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
> 
>  .../bindings/dma/allwinner,sun50i-a64-dma.yaml           | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2021-11-29 23:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19  5:26 [PATCH 0/4] dmaengine: sun6i: Allwinner D1 support Samuel Holland
2021-11-19  5:26 ` [PATCH 1/4] dt-bindings: dma: sun50i-a64: Add compatible for D1 Samuel Holland
2021-11-29 23:13   ` Rob Herring [this message]
2021-11-19  5:26 ` [PATCH 2/4] dmaengine: sun6i: Do not use virt_to_phys Samuel Holland
2021-11-19  5:27 ` [PATCH 3/4] dmaengine: sun6i: Add support for 34-bit physical addresses Samuel Holland
2021-11-22  8:45   ` Maxime Ripard
2021-11-19  5:27 ` [PATCH 4/4] dmaengine: sun6i: Add support for the D1 variant Samuel Holland
2021-11-22  8:45 ` [PATCH 0/4] dmaengine: sun6i: Allwinner D1 support Maxime Ripard

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=YaVepmEInHXCPvQA@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mripard@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=samuel@sholland.org \
    --cc=vkoul@kernel.org \
    --cc=wens@csie.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).