From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: linux-can@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, nicolas.ferre@atmel.com,
plagnioj@jcrosoft.com
Subject: Re: [PATCH 1/3] can: at91_can: add dt support
Date: Mon, 11 Mar 2013 16:59:40 +0100 [thread overview]
Message-ID: <513DFF6C.2050408@pengutronix.de> (raw)
In-Reply-To: <20130311153956.GB3198@ludovic.desroches@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 2539 bytes --]
On 03/11/2013 04:39 PM, Ludovic Desroches wrote:
> On Mon, Mar 11, 2013 at 04:12:46PM +0100, Marc Kleine-Budde wrote:
>> On 03/11/2013 10:17 AM, Ludovic Desroches wrote:
>>> On Fri, Mar 08, 2013 at 06:44:05PM +0100, Marc Kleine-Budde wrote:
>>>> On 03/08/2013 06:30 PM, ludovic.desroches@atmel.com wrote:
>>>>> From: Ludovic Desroches <ludovic.desroches@atmel.com>
>>>>>
>>>>> Add device tree support.
>>>>>
>>>>> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
>>>>> ---
>>>>> .../devicetree/bindings/net/can/atmel-can.txt | 14 ++++
>>>>> drivers/net/can/at91_can.c | 75 ++++++++++++++++------
>>>>> 2 files changed, 70 insertions(+), 19 deletions(-)
>>>>> create mode 100644 Documentation/devicetree/bindings/net/can/atmel-can.txt
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/net/can/atmel-can.txt b/Documentation/devicetree/bindings/net/can/atmel-can.txt
>>>>> new file mode 100644
>>>>> index 0000000..69381db
>>>>> --- /dev/null
>>>>> +++ b/Documentation/devicetree/bindings/net/can/atmel-can.txt
>>>>> @@ -0,0 +1,14 @@
>>>>> +* AT91 CAN *
>>>>> +
>>>>> +Required properties:
>>>>> + - compatible: Should be "atmel,at91sam9263-can" or "atmel,at91sam9x5-can"
>>>>
>>>> On imx we use the oldest SoC with that IP available. Which strategy are
>>>> you following on at91?
>>>>
>>>
>>> We are using the same strategy.
>>
>> But "atmel,at91sam9x5-can" isn't a specific SoC, probably a SoC family.
>> Or are you using "atmel,at91sam9x5-can" for the other devices in the DT,
>> too.
>>
>
> You are right at91sam9x5 is not a specific SoC but a family of SoCs:
> at91sam9g25, at91sam9g35, at91sam9x25 and at91sam9x35. This compatible string
> is used for all the devices from and after the at91sam9x5 family: at91sam9n12,
> samad3x, etc.
>
>> I picked at91sam9x5-can for the non devicetree driver out of the blue,
>> as there was no scheme established, yet. I'm not hanging on that name,
>> I'd rather appreciate to follow the common at91 DT rules.
>
> It follows at91 Dt rules, we have atmel,at91sam9x5-i2c, atmel,at91sam9x5-gpio
> and others.
That's okay then, just wanted to clarify this. Can you send a v2, then
I'll apply the patches.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] can: at91_can: add dt support
Date: Mon, 11 Mar 2013 16:59:40 +0100 [thread overview]
Message-ID: <513DFF6C.2050408@pengutronix.de> (raw)
In-Reply-To: <20130311153956.GB3198@ludovic.desroches@atmel.com>
On 03/11/2013 04:39 PM, Ludovic Desroches wrote:
> On Mon, Mar 11, 2013 at 04:12:46PM +0100, Marc Kleine-Budde wrote:
>> On 03/11/2013 10:17 AM, Ludovic Desroches wrote:
>>> On Fri, Mar 08, 2013 at 06:44:05PM +0100, Marc Kleine-Budde wrote:
>>>> On 03/08/2013 06:30 PM, ludovic.desroches at atmel.com wrote:
>>>>> From: Ludovic Desroches <ludovic.desroches@atmel.com>
>>>>>
>>>>> Add device tree support.
>>>>>
>>>>> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
>>>>> ---
>>>>> .../devicetree/bindings/net/can/atmel-can.txt | 14 ++++
>>>>> drivers/net/can/at91_can.c | 75 ++++++++++++++++------
>>>>> 2 files changed, 70 insertions(+), 19 deletions(-)
>>>>> create mode 100644 Documentation/devicetree/bindings/net/can/atmel-can.txt
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/net/can/atmel-can.txt b/Documentation/devicetree/bindings/net/can/atmel-can.txt
>>>>> new file mode 100644
>>>>> index 0000000..69381db
>>>>> --- /dev/null
>>>>> +++ b/Documentation/devicetree/bindings/net/can/atmel-can.txt
>>>>> @@ -0,0 +1,14 @@
>>>>> +* AT91 CAN *
>>>>> +
>>>>> +Required properties:
>>>>> + - compatible: Should be "atmel,at91sam9263-can" or "atmel,at91sam9x5-can"
>>>>
>>>> On imx we use the oldest SoC with that IP available. Which strategy are
>>>> you following on at91?
>>>>
>>>
>>> We are using the same strategy.
>>
>> But "atmel,at91sam9x5-can" isn't a specific SoC, probably a SoC family.
>> Or are you using "atmel,at91sam9x5-can" for the other devices in the DT,
>> too.
>>
>
> You are right at91sam9x5 is not a specific SoC but a family of SoCs:
> at91sam9g25, at91sam9g35, at91sam9x25 and at91sam9x35. This compatible string
> is used for all the devices from and after the at91sam9x5 family: at91sam9n12,
> samad3x, etc.
>
>> I picked at91sam9x5-can for the non devicetree driver out of the blue,
>> as there was no scheme established, yet. I'm not hanging on that name,
>> I'd rather appreciate to follow the common at91 DT rules.
>
> It follows at91 Dt rules, we have atmel,at91sam9x5-i2c, atmel,at91sam9x5-gpio
> and others.
That's okay then, just wanted to clarify this. Can you send a v2, then
I'll apply the patches.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130311/abe11a34/attachment.sig>
next prev parent reply other threads:[~2013-03-11 15:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 17:30 [PATCH 0/3] dt and pinctrl support for at91_can ludovic.desroches
2013-03-08 17:30 ` ludovic.desroches at atmel.com
2013-03-08 17:30 ` [PATCH 1/3] can: at91_can: add dt support ludovic.desroches
2013-03-08 17:30 ` ludovic.desroches at atmel.com
2013-03-08 17:44 ` Marc Kleine-Budde
2013-03-08 17:44 ` Marc Kleine-Budde
[not found] ` <513A2365.5050803-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-03-11 9:17 ` Ludovic Desroches
2013-03-11 9:17 ` Ludovic Desroches
2013-03-11 9:17 ` Ludovic Desroches
2013-03-11 15:12 ` Marc Kleine-Budde
2013-03-11 15:12 ` Marc Kleine-Budde
2013-03-11 15:39 ` Ludovic Desroches
2013-03-11 15:59 ` Marc Kleine-Budde [this message]
2013-03-11 15:59 ` Marc Kleine-Budde
2013-03-11 15:39 ` Ludovic Desroches
[not found] ` <513DF46E.7000903-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-03-11 15:39 ` Ludovic Desroches
2013-03-08 17:30 ` [PATCH 2/3] can: at91_can: add pinctrl support ludovic.desroches
2013-03-08 17:30 ` ludovic.desroches at atmel.com
2013-03-08 17:37 ` Marc Kleine-Budde
2013-03-08 17:37 ` Marc Kleine-Budde
2013-03-08 18:46 ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-08 18:46 ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-08 17:30 ` [PATCH 3/3] can: Kconfig: CAN_AT91 depends on ARCH_AT91 ludovic.desroches
2013-03-08 17:30 ` ludovic.desroches at atmel.com
2013-03-08 17:44 ` Marc Kleine-Budde
2013-03-08 17:44 ` Marc Kleine-Budde
2013-03-11 9:24 ` Ludovic Desroches
2013-03-11 9:57 ` Marc Kleine-Budde
2013-03-11 9:57 ` Marc Kleine-Budde
2013-03-11 9:24 ` Ludovic Desroches
[not found] ` <513A2396.4080508-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-03-11 9:24 ` Ludovic Desroches
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=513DFF6C.2050408@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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.