linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>,
	mkl@pengutronix.de, wg@grandegger.com, horms@verge.net.au,
	magnus.damm@gmail.com, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org
Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-can@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	chris.paterson2@renesas.com
Subject: Re: [PATCH] arm64: dts: r8a7795: Add CAN FD support
Date: Tue, 1 Mar 2016 16:12:24 +0300	[thread overview]
Message-ID: <56D59538.2060100@cogentembedded.com> (raw)
In-Reply-To: <1456826640-23237-1-git-send-email-ramesh.shanmugasundaram@bp.renesas.com>

Hello.

On 3/1/2016 1:04 PM, Ramesh Shanmugasundaram wrote:

> Adds CAN FD controller node for r8a7795.
>
> Note: CAN FD controller register base address specified in R-Car Gen3
> Hardware User Manual v0.5E is incorrect. The correct address is:
>
> CAN FD - 0xe66c0000
>
> Signed-off-by: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
> ---
> Hi All,
>
>     This patch is based on linux-next (tag:next-20160225) with the following
>     patches applied on top.
>
>     [PATCH v2] arm64: dts: r8a7795: Add CAN external clock support
>     [PATCH] arm64: dts: r8a7795: Add CAN support
>
>     The respective CAN subsystem changes are submitted separately here (https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg01388.html)
>
> Thanks,
> Ramesh
> ---
>   arch/arm64/boot/dts/renesas/r8a7795.dtsi | 24 ++++++++++++++++++++++++
>   1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> index a88f8d8..5049ba6 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> @@ -553,6 +553,30 @@
>   			status = "disabled";
>   		};
>
> +		canfd: canfd@e66c0000 {

    The node name should still be "can@e66c0000", I think.

MBR, Sergei

  reply	other threads:[~2016-03-01 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 10:04 [PATCH] arm64: dts: r8a7795: Add CAN FD support Ramesh Shanmugasundaram
2016-03-01 13:12 ` Sergei Shtylyov [this message]
2016-03-02  7:29   ` Ramesh Shanmugasundaram
2016-03-02  7:53     ` Simon Horman
2016-03-02 12:03     ` Sergei Shtylyov
     [not found] ` <1456826640-23237-1-git-send-email-ramesh.shanmugasundaram-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2016-03-02  8:15   ` [PATCH v2] " Ramesh Shanmugasundaram

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=56D59538.2060100@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --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=robh+dt@kernel.org \
    --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).