All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms+renesas@verge.net.au>
To: linux-renesas-soc@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Magnus Damm <magnus.damm@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Marek Vasut <marek.vasut@gmail.com>,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	Simon Horman <horms+renesas@verge.net.au>
Subject: [PATCH 6/9] dt-bindings: can: rcar_canfd: document r8a77990 support
Date: Fri, 21 Jun 2019 11:11:13 +0200	[thread overview]
Message-ID: <485dccb48f7590939c6dee794e0a30512926c830.1561107729.git.horms+renesas@verge.net.au> (raw)
In-Reply-To: <cover.1561107729.git.horms+renesas@verge.net.au>

From: Marek Vasut <marek.vasut@gmail.com>

Document the support for rcar_canfd on R8A77990 SoC devices.

Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
Acked-by: David S. Miller <davem@davemloft.net>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
 Documentation/devicetree/bindings/net/can/rcar_canfd.txt | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
index 4720e916fbdd..41049fed5872 100644
--- a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
+++ b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
@@ -9,6 +9,7 @@ Required properties:
   - "renesas,r8a77965-canfd" for R8A77965 (R-Car M3-N) compatible controller.
   - "renesas,r8a77970-canfd" for R8A77970 (R-Car V3M) compatible controller.
   - "renesas,r8a77980-canfd" for R8A77980 (R-Car V3H) compatible controller.
+  - "renesas,r8a77990-canfd" for R8A77990 (R-Car E3) compatible controller.
 
   When compatible with the generic version, nodes must list the
   SoC-specific version corresponding to the platform first, followed by the
@@ -27,12 +28,12 @@ The name of the child nodes are "channel0" and "channel1" respectively. Each
 child node supports the "status" property only, which is used to
 enable/disable the respective channel.
 
-Required properties for "renesas,r8a7795-canfd", "renesas,r8a7796-canfd" and
-"renesas,r8a77965-canfd" compatible:
-In R8A7795, R8A7796 and R8A77965 SoCs, canfd clock is a div6 clock and can
-be used by both CAN and CAN FD controller at the same time. It needs to be
-scaled to maximum frequency if any of these controllers use it. This is done
-using the below properties:
+Required properties for "renesas,r8a7795-canfd", "renesas,r8a7796-canfd",
+"renesas,r8a77965-canfd" and "renesas,r8a77990-canfd" compatible:
+In R8A7795, R8A7796, R8A77965 and R8A77990 SoCs, canfd clock is a div6 clock
+and can be used by both CAN and CAN FD controller at the same time. It needs
+to be scaled to maximum frequency if any of these controllers use it. This is
+done using the below properties:
 
 - assigned-clocks: phandle of canfd clock.
 - assigned-clock-rates: maximum frequency of this clock.
-- 
2.11.0


WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms+renesas@verge.net.au>
To: linux-renesas-soc@vger.kernel.org
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Simon Horman <horms+renesas@verge.net.au>,
	"David S . Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org,
	Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: [PATCH 6/9] dt-bindings: can: rcar_canfd: document r8a77990 support
Date: Fri, 21 Jun 2019 11:11:13 +0200	[thread overview]
Message-ID: <485dccb48f7590939c6dee794e0a30512926c830.1561107729.git.horms+renesas@verge.net.au> (raw)
In-Reply-To: <cover.1561107729.git.horms+renesas@verge.net.au>

From: Marek Vasut <marek.vasut@gmail.com>

Document the support for rcar_canfd on R8A77990 SoC devices.

Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
Acked-by: David S. Miller <davem@davemloft.net>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
 Documentation/devicetree/bindings/net/can/rcar_canfd.txt | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
index 4720e916fbdd..41049fed5872 100644
--- a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
+++ b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
@@ -9,6 +9,7 @@ Required properties:
   - "renesas,r8a77965-canfd" for R8A77965 (R-Car M3-N) compatible controller.
   - "renesas,r8a77970-canfd" for R8A77970 (R-Car V3M) compatible controller.
   - "renesas,r8a77980-canfd" for R8A77980 (R-Car V3H) compatible controller.
+  - "renesas,r8a77990-canfd" for R8A77990 (R-Car E3) compatible controller.
 
   When compatible with the generic version, nodes must list the
   SoC-specific version corresponding to the platform first, followed by the
@@ -27,12 +28,12 @@ The name of the child nodes are "channel0" and "channel1" respectively. Each
 child node supports the "status" property only, which is used to
 enable/disable the respective channel.
 
-Required properties for "renesas,r8a7795-canfd", "renesas,r8a7796-canfd" and
-"renesas,r8a77965-canfd" compatible:
-In R8A7795, R8A7796 and R8A77965 SoCs, canfd clock is a div6 clock and can
-be used by both CAN and CAN FD controller at the same time. It needs to be
-scaled to maximum frequency if any of these controllers use it. This is done
-using the below properties:
+Required properties for "renesas,r8a7795-canfd", "renesas,r8a7796-canfd",
+"renesas,r8a77965-canfd" and "renesas,r8a77990-canfd" compatible:
+In R8A7795, R8A7796, R8A77965 and R8A77990 SoCs, canfd clock is a div6 clock
+and can be used by both CAN and CAN FD controller at the same time. It needs
+to be scaled to maximum frequency if any of these controllers use it. This is
+done using the below properties:
 
 - assigned-clocks: phandle of canfd clock.
 - assigned-clock-rates: maximum frequency of this clock.
-- 
2.11.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-06-21  9:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21  9:10 [GIT PULL] Renesas ARM Based SoC DT Bindings Updates for v5.3 Simon Horman
2019-06-21  9:10 ` Simon Horman
2019-06-21  9:11 ` [PATCH 1/9] dt-bindings: arm: renesas: Add HopeRun RZ/G2[M] boards Simon Horman
2019-06-21  9:11   ` Simon Horman
2019-06-21  9:11 ` [PATCH 2/9] dt-bindings: Add vendor prefix for HopeRun Simon Horman
2019-06-21  9:11   ` Simon Horman
2019-06-21  9:11 ` [PATCH 3/9] dt-bindings: can: rcar_can: Fix RZ/G2 CAN clocks Simon Horman
2019-06-21  9:11   ` Simon Horman
2019-06-21  9:11 ` [PATCH 4/9] dt-bindings: can: rcar_can: Add r8a774c0 support Simon Horman
2019-06-21  9:11   ` Simon Horman
2019-06-21  9:11 ` [PATCH 5/9] dt-bindings: can: rcar_canfd: document r8a77965 support Simon Horman
2019-06-21  9:11   ` Simon Horman
2019-06-21  9:11 ` Simon Horman [this message]
2019-06-21  9:11   ` [PATCH 6/9] dt-bindings: can: rcar_canfd: document r8a77990 support Simon Horman
2019-06-21  9:11 ` [PATCH 7/9] dt-bindings: can: rcar_canfd: document r8a774c0 support Simon Horman
2019-06-21  9:11   ` Simon Horman
2019-06-21  9:11 ` [PATCH 8/9] dt-bindings: timer: renesas, cmt: Document r8a779{5|65|90} CMT support Simon Horman
2019-06-21  9:11   ` Simon Horman
2019-06-21  9:11 ` [PATCH 9/9] dt-bindings: display: renesas: Add r8a774a1 support Simon Horman
2019-06-21  9:11   ` Simon Horman
2019-06-25 11:43 ` [GIT PULL] Renesas ARM Based SoC DT Bindings Updates for v5.3 Olof Johansson
2019-06-25 11:43   ` Olof Johansson

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=485dccb48f7590939c6dee794e0a30512926c830.1561107729.git.horms+renesas@verge.net.au \
    --to=horms+renesas@verge.net.au \
    --cc=daniel.lezcano@linaro.org \
    --cc=davem@davemloft.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=marek.vasut@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.