From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Boris BREZILLON <boris.brezillon@free-electrons.com>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] ARM: at91/soc: add basic support for new sama5d2 SoC
Date: Tue, 28 Jul 2015 10:54:50 +0200 [thread overview]
Message-ID: <55B7435A.2060205@atmel.com> (raw)
In-Reply-To: <20150629150421.GB485@piout.net>
Le 29/06/2015 17:04, Alexandre Belloni a écrit :
> On 29/06/2015 at 14:46:51 +0200, Nicolas Ferre wrote :
>> Le 18/06/2015 17:21, Alexandre Belloni a écrit :
>>> Hi,
>>>
>>> On 18/06/2015 at 15:18:28 +0200, Nicolas Ferre wrote :
>>>> diff --git a/Documentation/arm/Atmel/README b/Documentation/arm/Atmel/README
>>>> index c53a19b4aab2..6650a8ffaa64 100644
>>>> --- a/Documentation/arm/Atmel/README
>>>> +++ b/Documentation/arm/Atmel/README
>>>> @@ -90,6 +90,12 @@ the Atmel website: http://www.atmel.com.
>>>> + Datasheet
>>>> http://www.atmel.com/Images/Atmel-11238-32-bit-Cortex-A5-Microcontroller-SAMA5D4_Datasheet.pdf
>>>>
>>>> + * ARM Cortex-A5 + NEON based SoCs
>>>> + - sama5d2 family
>>>> + - sama5d27
>>>> + + Datasheet
>>>> + Coming soon
>>>
>>> Shouldn't that go directly before or after the sama5d4 family ?
>>
>> This is "after" sama5d4: I sorted this file according to SoC release
>> date whereas I sorted the other entries in alpa-numerial order (sama5d2
>> placed before sama5d3).
>>
>> Is it what you answered?
>>
>
> No, I meant doing something like:
>
> * ARM Cortex-A5 + NEON based SoCs
> - sama5d4 family
> - sama5d41
> - sama5d42
> - sama5d43
> - sama5d44 (device superset)
> + Datasheet
> http://www.atmel.com/Images/Atmel-11238-32-bit-Cortex-A5-Microcontroller-SAMA5D4_Datasheet.pdf
> - sama5d2 family
> - sama5d27
> + Datasheet
> Coming soon
>
> Else, you end up with two "ARM Cortex-A5 + NEON based SoCs" sections.
Oh, yes. Sure, I'll modify this.
Do you think that it's worth sending another series or I can take it for
the pull-request when it's modified?
Bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: at91/soc: add basic support for new sama5d2 SoC
Date: Tue, 28 Jul 2015 10:54:50 +0200 [thread overview]
Message-ID: <55B7435A.2060205@atmel.com> (raw)
In-Reply-To: <20150629150421.GB485@piout.net>
Le 29/06/2015 17:04, Alexandre Belloni a ?crit :
> On 29/06/2015 at 14:46:51 +0200, Nicolas Ferre wrote :
>> Le 18/06/2015 17:21, Alexandre Belloni a ?crit :
>>> Hi,
>>>
>>> On 18/06/2015 at 15:18:28 +0200, Nicolas Ferre wrote :
>>>> diff --git a/Documentation/arm/Atmel/README b/Documentation/arm/Atmel/README
>>>> index c53a19b4aab2..6650a8ffaa64 100644
>>>> --- a/Documentation/arm/Atmel/README
>>>> +++ b/Documentation/arm/Atmel/README
>>>> @@ -90,6 +90,12 @@ the Atmel website: http://www.atmel.com.
>>>> + Datasheet
>>>> http://www.atmel.com/Images/Atmel-11238-32-bit-Cortex-A5-Microcontroller-SAMA5D4_Datasheet.pdf
>>>>
>>>> + * ARM Cortex-A5 + NEON based SoCs
>>>> + - sama5d2 family
>>>> + - sama5d27
>>>> + + Datasheet
>>>> + Coming soon
>>>
>>> Shouldn't that go directly before or after the sama5d4 family ?
>>
>> This is "after" sama5d4: I sorted this file according to SoC release
>> date whereas I sorted the other entries in alpa-numerial order (sama5d2
>> placed before sama5d3).
>>
>> Is it what you answered?
>>
>
> No, I meant doing something like:
>
> * ARM Cortex-A5 + NEON based SoCs
> - sama5d4 family
> - sama5d41
> - sama5d42
> - sama5d43
> - sama5d44 (device superset)
> + Datasheet
> http://www.atmel.com/Images/Atmel-11238-32-bit-Cortex-A5-Microcontroller-SAMA5D4_Datasheet.pdf
> - sama5d2 family
> - sama5d27
> + Datasheet
> Coming soon
>
> Else, you end up with two "ARM Cortex-A5 + NEON based SoCs" sections.
Oh, yes. Sure, I'll modify this.
Do you think that it's worth sending another series or I can take it for
the pull-request when it's modified?
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2015-07-28 8:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 13:18 [PATCH 0/3] introducing Atmel sama5d2 SoC Nicolas Ferre
2015-06-18 13:18 ` Nicolas Ferre
2015-06-18 13:18 ` [PATCH 1/3] ARM: at91/soc: add basic support for new " Nicolas Ferre
2015-06-18 13:18 ` Nicolas Ferre
2015-06-18 15:21 ` Alexandre Belloni
2015-06-18 15:21 ` Alexandre Belloni
2015-06-29 12:46 ` Nicolas Ferre
2015-06-29 12:46 ` Nicolas Ferre
2015-06-29 15:04 ` Alexandre Belloni
2015-06-29 15:04 ` Alexandre Belloni
2015-07-28 8:54 ` Nicolas Ferre [this message]
2015-07-28 8:54 ` Nicolas Ferre
2015-07-28 9:38 ` Nicolas Ferre
2015-07-28 9:38 ` Nicolas Ferre
2015-06-18 13:18 ` [PATCH 2/3] ARM: at91/dt: add basic dtsi for " Nicolas Ferre
2015-06-18 13:18 ` Nicolas Ferre
2015-06-18 13:18 ` [PATCH 3/3] ARM: at91/dt: add minimal sama5d2 Xplained board Nicolas Ferre
2015-06-18 13:18 ` Nicolas Ferre
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=55B7435A.2060205@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@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.