linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Rob Herring <robh+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>
Cc: 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,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] Remove shdma DT support
Date: Fri, 11 Jun 2021 12:18:38 +0200	[thread overview]
Message-ID: <cover.1623405675.git.geert+renesas@glider.be> (raw)

	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.

I plan to queue [PATCH 3/3] in renesas-devel for v5.15.

Thanks for your comments!

Geert Uytterhoeven (3):
  dt-bindings: dmaengine: Remove SHDMA Device Tree bindings
  dmaengine: sh: Remove unused shdma-of driver
  ARM: dts: r8a73a4: Remove non-functional DMA support

 .../devicetree/bindings/dma/renesas,shdma.txt | 84 -------------------
 arch/arm/boot/dts/r8a73a4.dtsi                | 44 ----------
 drivers/dma/sh/Makefile                       |  2 +-
 drivers/dma/sh/shdma-of.c                     | 76 -----------------
 4 files changed, 1 insertion(+), 205 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/dma/renesas,shdma.txt
 delete mode 100644 drivers/dma/sh/shdma-of.c

-- 
2.25.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2021-06-11 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 10:18 Geert Uytterhoeven [this message]
2021-06-16 10:38 ` [PATCH 0/3] Remove shdma DT support Vinod Koul
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=cover.1623405675.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --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 \
    --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).