Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: horms+renesas@verge.net.au, Magnus Damm <magnus.damm@gmail.com>,
	geert+renesas@glider.be,
	Konstantin.Kozhevnikov@cogentembedded.com,
	sergei.shtylyov@cogentembedded.com
Subject: [PATCH/RFC 00/02] Remove undocumented IMR-LX4 device nodes
Date: Mon, 21 Jan 2019 20:49:55 +0900	[thread overview]
Message-ID: <154807139502.25511.1919986589060151108.sendpatchset@octo> (raw)

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes
[PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented
IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem
undocumented and no driver exists in upstream my gut feeling says these DT
nodes were part of an upstreaming attempt that got suspended half-way through.

In case DT binding documentation is in-flight and queued up somewhere
(ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the
IMR-LX4 devices. It would also make sense to add device nodes to other
more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes
with a DT binding but without a driver seems a bit suboptimal compared to
testing against an actual driver.

Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---

 Developed on top of v5.0-rc3

 arch/arm64/boot/dts/renesas/r8a7795.dtsi |   40 ------------------------------
 arch/arm64/boot/dts/renesas/r8a7796.dtsi |   20 ---------------
 2 files changed, 60 deletions(-)

             reply	other threads:[~2019-01-21 11:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 11:49 Magnus Damm [this message]
2019-01-21 11:50 ` [PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes Magnus Damm
2019-01-23  9:59   ` Simon Horman
2019-01-23 15:43     ` Sergei Shtylyov
2019-01-21 11:50 ` [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: " Magnus Damm
2019-01-21 11:52 ` [PATCH/RFC 00/02] Remove undocumented " Geert Uytterhoeven
2019-01-21 12:01   ` Magnus Damm
2019-01-23 18:19     ` Sergei Shtylyov
2019-01-28 12:58       ` Simon Horman
2019-03-25 11:03         ` Simon Horman
2019-03-25 15:53           ` Sergei Shtylyov
2019-03-27 12:11             ` Simon Horman
2019-03-27 12:15               ` Simon Horman

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=154807139502.25511.1919986589060151108.sendpatchset@octo \
    --to=magnus.damm@gmail.com \
    --cc=Konstantin.Kozhevnikov@cogentembedded.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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