From: Tony Lindgren <tony@atomide.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Roger Quadros <rogerq@ti.com>,
wg@grandegger.com, wsa@the-dreams.de, mugunthanvnm@ti.com,
george.cherian@ti.com, balbi@ti.com, nsekhar@ti.comnm@ti.com,
sergei.shtylyov@cogentembedded.com, linux-omap@vger.kernel.org,
linux-can@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 06/10] ARM: dts: am4372: Add DCAN nodes
Date: Thu, 13 Nov 2014 09:40:44 -0800 [thread overview]
Message-ID: <20141113174044.GN26481@atomide.com> (raw)
In-Reply-To: <5464C609.9070800@pengutronix.de>
* Marc Kleine-Budde <mkl@pengutronix.de> [141113 06:55]:
> On 11/13/2014 03:49 PM, Roger Quadros wrote:
> > On 11/13/2014 04:44 PM, Marc Kleine-Budde wrote:
> >> On 11/13/2014 03:40 PM, Roger Quadros wrote:
> >>> On 11/13/2014 04:07 PM, Marc Kleine-Budde wrote:
> >>>> On 11/13/2014 01:22 PM, Roger Quadros wrote:
> >>>>> The SoC contains 2 DCAN modules. Add them.
> >>>>>
> >>>>> Signed-off-by: Roger Quadros <rogerq@ti.com>
> >>>>> ---
> >>>>> arch/arm/boot/dts/am4372.dtsi | 22 ++++++++++++++++++++++
> >>>>> 1 file changed, 22 insertions(+)
> >>>>>
> >>>>> diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
> >>>>> index 899c57c..12fb1db 100644
> >>>>> --- a/arch/arm/boot/dts/am4372.dtsi
> >>>>> +++ b/arch/arm/boot/dts/am4372.dtsi
> >>>>> @@ -901,6 +901,28 @@
> >>>>> compatible = "mmio-sram";
> >>>>> reg = <0x40300000 0x40000>; /* 256k */
> >>>>> };
> >>>>> +
> >>>>> + dcan0: can@481cc000 {
> >>>>> + compatible = "ti,am3352-d_can";
> >>>>
> >>>> You should add "ti,am4372-d_can" as first compatible here.
> >>>>
> >>> We don't have a separate compatible id for am4372-d_can
> >>> as it the IP exactly same as am3352-d_can.
> >>
> >> Having the "ti,am4372-d_can" compatible gives you the freedom to add
> >> some spacial handling for the IP if there turns that you need to without
> >> needing to modify the device tree. (We do this on imx.)
> >
> > Agreed. On OMAP platforms we don't add new compatible IDs unless we really need to.
> > Can we add "ti,am4372-d_can" even if it is not mentioned in Documentation/devicetree/bindings?
> >
> > Tony what is your preference?
>
> I don't insist, do it the Omap way :)
I agree it's good to add if we need to add custom handling later on.
Regards,
Tony
next prev parent reply other threads:[~2014-11-13 17:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 12:22 [PATCH v4 00/10] ARM: dts: TI: Add CAN support Roger Quadros
2014-11-13 12:22 ` [PATCH v4 01/10] ARM: dts: dra7: Add syscon regmap for CORE CONTROL area Roger Quadros
2014-11-13 12:22 ` [PATCH v4 02/10] ARM: dts: DRA7: Add DCAN nodes Roger Quadros
2014-11-13 12:22 ` [PATCH v4 03/10] ARM: dts: dra7-evm: Add CAN support Roger Quadros
2014-11-13 12:22 ` [PATCH v4 04/10] ARM: dts: dra72-evm: " Roger Quadros
2014-11-13 12:22 ` [PATCH v4 05/10] ARM: dts: am4372: Add control module syscon node Roger Quadros
2014-11-13 12:22 ` [PATCH v4 06/10] ARM: dts: am4372: Add DCAN nodes Roger Quadros
2014-11-13 14:07 ` Marc Kleine-Budde
2014-11-13 14:40 ` Roger Quadros
2014-11-13 14:44 ` Marc Kleine-Budde
2014-11-13 14:49 ` Roger Quadros
2014-11-13 14:54 ` Marc Kleine-Budde
2014-11-13 17:40 ` Tony Lindgren [this message]
2014-11-14 16:22 ` Roger Quadros
2014-11-14 18:07 ` Tony Lindgren
2014-11-17 13:08 ` [PATCH v5 " Roger Quadros
2014-11-21 23:50 ` Tony Lindgren
2014-11-22 0:08 ` Tony Lindgren
2014-11-24 9:58 ` Roger Quadros
2014-11-24 11:11 ` Roger Quadros
2014-11-24 15:49 ` Tony Lindgren
2014-11-24 16:05 ` Tony Lindgren
2014-11-13 12:22 ` [PATCH v4 07/10] arm: dts: am437x-gp: Add dcan support Roger Quadros
2014-11-13 12:22 ` [PATCH v4 08/10] ARM: dts: am33xx: Add control module syscon node Roger Quadros
2014-11-13 12:22 ` [PATCH v4 09/10] ARM: dts: am33xx: Update DCAN nodes Roger Quadros
2014-11-13 16:03 ` Wolfram Sang
2014-11-13 12:22 ` [PATCH v4 10/10] ARM: dts: am335x-evm: Add DCAN1 details Roger Quadros
2014-11-18 20:42 ` [PATCH v4 00/10] ARM: dts: TI: Add CAN 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=20141113174044.GN26481@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=mkl@pengutronix.de \
--cc=mugunthanvnm@ti.com \
--cc=nsekhar@ti.comnm \
--cc=rogerq@ti.com \
--cc=wg@grandegger.com \
--cc=wsa@the-dreams.de \
/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).