From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: "Fabrizio Castro" <fabrizio.castro@bp.renesas.com>,
"Simon Horman" <horms@verge.net.au>,
"Magnus Damm" <magnus.damm@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Thierry Reding" <treding@nvidia.com>,
"Andreas Färber" <afaerber@suse.de>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Kevin Hilman" <khilman@baylibre.com>,
"Johan Hovold" <johan@kernel.org>,
"Lukasz Majewski" <lukma@denx.de>,
"Michal Simek" <monstr@monstr.eu>,
"Michal Vokáč" <michal.vokac@ysoft.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Ben Whitten" <ben.whitten@gmail.com>,
"Chris Paterson" <Chris.Paterson2@renesas.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-clk@vger.kernel.org, "Biju Das" <biju.das@bp.renesas.com>,
linux-kernel@vger.kernel.org, ebiharaml@si-linux.co.jp
Subject: [PATCH 09/11] dt-bindings: can: rcar_can: Fix RZ/G2 CAN clocks
Date: Wed, 16 Jan 2019 18:37:52 +0000 [thread overview]
Message-ID: <1547663874-29411-10-git-send-email-fabrizio.castro@bp.renesas.com> (raw)
In-Reply-To: <1547663874-29411-1-git-send-email-fabrizio.castro@bp.renesas.com>
According to the latest information, the clock options for CAN on RZ/G2
are the same as the ones available on R-Car Gen3
Fixes: 868b7c0f43e6 ("dt-bindings: can: rcar_can: Add r8a774a1 support")
Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Reviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>
---
Documentation/devicetree/bindings/net/can/rcar_can.txt | 12 +++---------
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/can/rcar_can.txt b/Documentation/devicetree/bindings/net/can/rcar_can.txt
index 7fcf501..b463e12 100644
--- a/Documentation/devicetree/bindings/net/can/rcar_can.txt
+++ b/Documentation/devicetree/bindings/net/can/rcar_can.txt
@@ -28,13 +28,8 @@ Required properties:
- reg: physical base address and size of the R-Car CAN register map.
- interrupts: interrupt specifier for the sole interrupt.
-- clocks: phandles and clock specifiers for 2 CAN clock inputs for RZ/G2
- devices.
- phandles and clock specifiers for 3 CAN clock inputs for every other
- SoC.
-- clock-names: 2 clock input name strings for RZ/G2: "clkp1", "can_clk".
- 3 clock input name strings for every other SoC: "clkp1", "clkp2",
- "can_clk".
+- clocks: phandles and clock specifiers for 3 CAN clock inputs.
+- clock-names: 3 clock input name strings: "clkp1", "clkp2", and "can_clk".
- pinctrl-0: pin control group to be used for this controller.
- pinctrl-names: must be "default".
@@ -50,8 +45,7 @@ using the below properties:
Optional properties:
- renesas,can-clock-select: R-Car CAN Clock Source Select. Valid values are:
<0x0> (default) : Peripheral clock (clkp1)
- <0x1> : Peripheral clock (clkp2) (not supported by
- RZ/G2 devices)
+ <0x1> : Peripheral clock (clkp2)
<0x3> : External input clock
Example
--
2.7.4
next prev parent reply other threads:[~2019-01-16 18:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 18:37 [PATCH 00/11] Add basic EK874 support Fabrizio Castro
2019-01-16 18:37 ` [PATCH 01/11] dt-bindings: Add vendor prefix for Silicon Linux Fabrizio Castro
2019-01-17 10:44 ` Simon Horman
2019-01-17 11:17 ` Andreas Färber
2019-01-17 12:19 ` Simon Horman
2019-01-17 12:23 ` Chris Paterson
2019-01-22 1:14 ` Rob Herring
2019-02-14 16:21 ` Fabrizio Castro
2019-02-15 6:52 ` Lukasz Majewski
2019-02-15 9:09 ` Andreas Färber
2019-03-01 12:03 ` Fabrizio Castro
2019-03-04 9:40 ` Simon Horman
2019-01-16 18:37 ` Fabrizio Castro [this message]
2019-01-17 12:01 ` [PATCH 09/11] dt-bindings: can: rcar_can: Fix RZ/G2 CAN clocks Simon Horman
2019-01-22 1:15 ` Rob Herring
2019-03-01 11:52 ` Fabrizio Castro
2019-01-16 18:37 ` [PATCH 11/11] dt-bindings: can: rcar_canfd: document r8a774c0 support Fabrizio Castro
2019-01-17 12:11 ` Simon Horman
2019-01-22 1:15 ` Rob Herring
2019-03-01 11:56 ` Fabrizio Castro
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=1547663874-29411-10-git-send-email-fabrizio.castro@bp.renesas.com \
--to=fabrizio.castro@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=afaerber@suse.de \
--cc=alexandre.belloni@bootlin.com \
--cc=ben.whitten@gmail.com \
--cc=biju.das@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ebiharaml@si-linux.co.jp \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=johan@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lukma@denx.de \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=michal.vokac@ysoft.com \
--cc=mkl@pengutronix.de \
--cc=monstr@monstr.eu \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=treding@nvidia.com \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).