From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>,
"mkl@pengutronix.de" <mkl@pengutronix.de>,
"wg@grandegger.com" <wg@grandegger.com>,
"horms@verge.net.au" <horms@verge.net.au>,
"magnus.damm@gmail.com" <magnus.damm@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Chris Paterson <Chris.Paterson2@renesas.com>
Subject: Re: [PATCH] arm64: dts: r8a7795: Add CAN FD support
Date: Wed, 2 Mar 2016 15:03:57 +0300 [thread overview]
Message-ID: <56D6D6AD.7080207@cogentembedded.com> (raw)
In-Reply-To: <SG2PR06MB1038FBA247777C89F70E2633C3BC0@SG2PR06MB1038.apcprd06.prod.outlook.com>
Hello.
On 3/2/2016 10:29 AM, 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/msg013
>>> 88.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.
>
> Thanks for the review.
>
> The SoC has CAN controller too
Yes, I figured. BTW, is the CAN-FD identical to the older CAN on the
hardware level? I haven't see you posting the CAN-FD driver yet...
> and hence I chose this node name to differentiate. A grep of canfd on sysfs would tell if the controller is enabled. The channels on "net" would still be named "canx".
>
> I'll change it if you still feel "can@e66c0000" is more appropriate.
It is -- the node names should be generic and ePAPR even has the "can"
name listed explicitly in the section 2.2.2.
> Thanks,
> Ramesh
MBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: r8a7795: Add CAN FD support
Date: Wed, 2 Mar 2016 15:03:57 +0300 [thread overview]
Message-ID: <56D6D6AD.7080207@cogentembedded.com> (raw)
In-Reply-To: <SG2PR06MB1038FBA247777C89F70E2633C3BC0@SG2PR06MB1038.apcprd06.prod.outlook.com>
Hello.
On 3/2/2016 10:29 AM, 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 at vger.kernel.org/msg013
>>> 88.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 at e66c0000 {
>>
>> The node name should still be "can at e66c0000", I think.
>
> Thanks for the review.
>
> The SoC has CAN controller too
Yes, I figured. BTW, is the CAN-FD identical to the older CAN on the
hardware level? I haven't see you posting the CAN-FD driver yet...
> and hence I chose this node name to differentiate. A grep of canfd on sysfs would tell if the controller is enabled. The channels on "net" would still be named "canx".
>
> I'll change it if you still feel "can at e66c0000" is more appropriate.
It is -- the node names should be generic and ePAPR even has the "can"
name listed explicitly in the section 2.2.2.
> Thanks,
> Ramesh
MBR, Sergei
next prev parent reply other threads:[~2016-03-02 12:03 UTC|newest]
Thread overview: 18+ 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 10:04 ` Ramesh Shanmugasundaram
2016-03-01 10:04 ` Ramesh Shanmugasundaram
2016-03-01 13:12 ` Sergei Shtylyov
2016-03-01 13:12 ` Sergei Shtylyov
2016-03-02 7:29 ` Ramesh Shanmugasundaram
2016-03-02 7:29 ` Ramesh Shanmugasundaram
2016-03-02 7:53 ` Simon Horman
2016-03-02 7:53 ` Simon Horman
2016-03-02 12:03 ` Sergei Shtylyov [this message]
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
2016-03-02 8:15 ` Ramesh Shanmugasundaram
2016-03-02 8:15 ` Ramesh Shanmugasundaram
2016-06-17 12:35 ` [PATCH v3] " Ramesh Shanmugasundaram
2016-06-17 12:35 ` Ramesh Shanmugasundaram
2016-06-21 1:38 ` Simon Horman
2016-06-21 1:38 ` 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=56D6D6AD.7080207@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 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.