From: Rob Herring <robh@kernel.org>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
chris.paterson2@renesas.com, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, socketcan@hartkopp.net,
magnus.damm@gmail.com, linux-can@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, horms@verge.net.au,
mkl@pengutronix.de, linux-arm-kernel@lists.infradead.org,
galak@codeaurora.org, ulrich.hecht+renesas@gmail.com,
wg@grandegger.com
Subject: Re: [PATCH] can: rcar_canfd: Add Classical CAN only mode support
Date: Tue, 21 Jun 2016 08:29:58 -0500 [thread overview]
Message-ID: <20160621132958.GA5283@rob-hp-laptop> (raw)
In-Reply-To: <1466434007-50873-1-git-send-email-ramesh.shanmugasundaram@bp.renesas.com>
On Mon, Jun 20, 2016 at 03:46:47PM +0100, Ramesh Shanmugasundaram wrote:
> The controller can operate in one of the two global modes
> - CAN FD only mode (default)
> - Classical CAN (CAN2.0) only mode
>
> This patch adds support for Classical CAN only mode. It can be enabled
> by defining the optional device tree property "renesas,can-nofd" of this
> node.
>
> Note: R-Car Gen3 h/w manual v0.51E shows bit6 of RSCFDnCFDGCFG as
> reserved, which is incorrect. This bit is same as RSCFDnGCFG.
>
> Signed-off-by: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
> ---
> Hi Marc, All,
>
> This patch is based on top of can-next(tag:linux-can-next-for-4.8-20160617).
>
> Thanks,
> Ramesh.
> ---
> .../devicetree/bindings/net/can/rcar_canfd.txt | 9 +-
> drivers/net/can/rcar/rcar_canfd.c | 355 ++++++++++++++-------
> 2 files changed, 249 insertions(+), 115 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
> index d45182b..a343359 100644
> --- a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
> +++ b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
> @@ -32,6 +32,12 @@ below properties.
> - assigned-clocks: phandle of canfd clock.
> - assigned-clock-rates: maximum frequency of this clock.
>
> +Optional property:
> +The controller can operate in either CAN FD only mode (default) or
> +Classical CAN only mode. The mode is global to both the channels. In order to
> +enable the later, define the following optional property.
> + - renesas,can-nofd: puts the controller in Classical CAN only mode.
renesas,no-can-fd would be a bit more readable.
> +
> Example
> -------
>
> @@ -63,11 +69,12 @@ SoC common .dtsi file:
>
> Board specific .dts file:
>
> -E.g. below enables Channel 1 alone in the board.
> +E.g. below enables Channel 1 alone in the board in Classical CAN only mode.
>
> &canfd {
> pinctrl-0 = <&canfd1_pins>;
> pinctrl-names = "default";
> + renesas,can-nofd;
Now we have a mixture of tabs and spaces.
> status = "okay";
>
> channel1 {
next prev parent reply other threads:[~2016-06-21 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 14:46 [PATCH] can: rcar_canfd: Add Classical CAN only mode support Ramesh Shanmugasundaram
2016-06-21 13:29 ` Rob Herring [this message]
2016-06-22 12:31 ` [PATCH v2 0/2] can: rcar_canfd: Add Classical CAN & lower state transition support Ramesh Shanmugasundaram
2016-06-22 12:31 ` [PATCH v2 1/2] can: rcar_canfd: Add Classical CAN only mode support Ramesh Shanmugasundaram
2016-06-24 16:12 ` Rob Herring
2016-06-22 12:31 ` [PATCH v2 2/2] can: rcar_canfd: Add back-to-error-active support Ramesh Shanmugasundaram
2016-06-22 20:34 ` [PATCH v2 0/2] can: rcar_canfd: Add Classical CAN & lower state transition support Marc Kleine-Budde
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=20160621132958.GA5283@rob-hp-laptop \
--to=robh@kernel.org \
--cc=chris.paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=socketcan@hartkopp.net \
--cc=ulrich.hecht+renesas@gmail.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