From: Vinod Koul <vkoul@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Rob Herring <robh+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-sh@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Remove shdma DT support
Date: Wed, 16 Jun 2021 16:08:59 +0530 [thread overview]
Message-ID: <YMnUw80/rUCFtO24@vkoul-mobl> (raw)
In-Reply-To: <cover.1623405675.git.geert+renesas@glider.be>
On 11-06-21, 12:18, Geert Uytterhoeven wrote:
> Hi all,
>
> Documentation/devicetree/bindings/dma/renesas,shdma.txt is one of the
> few^W57% of the DT bindings that haven't been converted to json-schema
> yet. These bindings were originally intended to cover all SH/R-Mobile
> SoCs, but the DMA multiplexer node and one DMA controller instance were
> only ever added to one .dtsi file, for R-Mobile APE6. Still, DMA
> support for R-Mobile APE6 was never completed to the point that it would
> actually work, cfr. commit a19788612f51b787 ("dmaengine: sh: Remove
> R-Mobile APE6 support"). Later, the mux idea was dropped when
> implementing support for DMA on (very similar) R-Car Gen2, cfr.
> renesas,rcar-dmac.yaml.
>
> Hence this series removes the Renesas SHDMA Device Tree bindings, the
> SHDMA DMA multiplexer driver, and the corresponding description in the
> R-Mobile APE6 DTS.
Applied 1 & 2, thanks
--
~Vinod
next prev parent reply other threads:[~2021-06-16 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 10:18 [PATCH 0/3] Remove shdma DT support Geert Uytterhoeven
2021-06-16 10:38 ` Vinod Koul [this message]
2021-06-16 10:42 ` John Paul Adrian Glaubitz
2021-06-16 11:18 ` 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=YMnUw80/rUCFtO24@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@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).