All of lore.kernel.org
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] AT91: dt: simple device tree support for at91sam9g45 family
Date: Mon, 08 Aug 2011 20:59:27 +0100	[thread overview]
Message-ID: <4E40401F.4030309@atmel.com> (raw)
In-Reply-To: <20110807035751.GC7667@ponder.secretlab.ca>

On 08/07/2011 04:57 AM, Grant Likely wrote:
> On Fri, Aug 05, 2011 at 05:24:53PM +0100, Nicolas Ferre wrote:
>> Add basic device tree support for at91sam9g45 SoC family and the
>> at91sam9m10g45ek board.
>> DT is been used to describe the at91sam9g45 SoC memory and AIC. It also
>> adds the dmaengine driver.
>>
>> Signed-off-by: Nicolas Ferre<nicolas.ferre@atmel.com>
>
> Hi Nicolas,
>
> Looks like a great start.  I was glad we could work on this last week.

Yes, that was enriching.

> Some comments below.

I will have to rework this series for sure but I have limited access to 
my git tree/emails this week... I plan to come back to this next week.

>> ---
>>   arch/arm/mach-at91/Kconfig               |    8 ++++++
>>   arch/arm/mach-at91/Makefile.boot         |    2 +
>>   arch/arm/mach-at91/at91sam9g45_devices.c |    3 +-
>>   arch/arm/mach-at91/board-sam9m10g45ek.c  |   36 ++++++++++++++++++++++++++++++
>>   4 files changed, 48 insertions(+), 1 deletions(-)

[..]

Best regards,
-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org
Subject: Re: [RFC PATCH 2/2] AT91: dt: simple device tree support for at91sam9g45 family
Date: Mon, 08 Aug 2011 20:59:27 +0100	[thread overview]
Message-ID: <4E40401F.4030309@atmel.com> (raw)
In-Reply-To: <20110807035751.GC7667@ponder.secretlab.ca>

On 08/07/2011 04:57 AM, Grant Likely wrote:
> On Fri, Aug 05, 2011 at 05:24:53PM +0100, Nicolas Ferre wrote:
>> Add basic device tree support for at91sam9g45 SoC family and the
>> at91sam9m10g45ek board.
>> DT is been used to describe the at91sam9g45 SoC memory and AIC. It also
>> adds the dmaengine driver.
>>
>> Signed-off-by: Nicolas Ferre<nicolas.ferre@atmel.com>
>
> Hi Nicolas,
>
> Looks like a great start.  I was glad we could work on this last week.

Yes, that was enriching.

> Some comments below.

I will have to rework this series for sure but I have limited access to 
my git tree/emails this week... I plan to come back to this next week.

>> ---
>>   arch/arm/mach-at91/Kconfig               |    8 ++++++
>>   arch/arm/mach-at91/Makefile.boot         |    2 +
>>   arch/arm/mach-at91/at91sam9g45_devices.c |    3 +-
>>   arch/arm/mach-at91/board-sam9m10g45ek.c  |   36 ++++++++++++++++++++++++++++++
>>   4 files changed, 48 insertions(+), 1 deletions(-)

[..]

Best regards,
-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 2/2] AT91: dt: simple device tree support for at91sam9g45 family
Date: Mon, 08 Aug 2011 20:59:27 +0100	[thread overview]
Message-ID: <4E40401F.4030309@atmel.com> (raw)
In-Reply-To: <20110807035751.GC7667@ponder.secretlab.ca>

On 08/07/2011 04:57 AM, Grant Likely wrote:
> On Fri, Aug 05, 2011 at 05:24:53PM +0100, Nicolas Ferre wrote:
>> Add basic device tree support for at91sam9g45 SoC family and the
>> at91sam9m10g45ek board.
>> DT is been used to describe the at91sam9g45 SoC memory and AIC. It also
>> adds the dmaengine driver.
>>
>> Signed-off-by: Nicolas Ferre<nicolas.ferre@atmel.com>
>
> Hi Nicolas,
>
> Looks like a great start.  I was glad we could work on this last week.

Yes, that was enriching.

> Some comments below.

I will have to rework this series for sure but I have limited access to 
my git tree/emails this week... I plan to come back to this next week.

>> ---
>>   arch/arm/mach-at91/Kconfig               |    8 ++++++
>>   arch/arm/mach-at91/Makefile.boot         |    2 +
>>   arch/arm/mach-at91/at91sam9g45_devices.c |    3 +-
>>   arch/arm/mach-at91/board-sam9m10g45ek.c  |   36 ++++++++++++++++++++++++++++++
>>   4 files changed, 48 insertions(+), 1 deletions(-)

[..]

Best regards,
-- 
Nicolas Ferre

  reply	other threads:[~2011-08-08 19:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 16:24 AT91: dt: basic device tree showcase Nicolas Ferre
2011-08-05 16:24 ` Nicolas Ferre
2011-08-05 16:24 ` Nicolas Ferre
2011-08-05 16:24 ` [RFC PATCH 1/2] AT91: dt: at91sam9g45 family and board device tree files Nicolas Ferre
2011-08-05 16:24   ` Nicolas Ferre
2011-08-05 16:24   ` Nicolas Ferre
2011-08-07  3:44   ` Grant Likely
2011-08-07  3:44     ` Grant Likely
2011-08-07  3:44     ` Grant Likely
2011-08-05 16:24 ` [RFC PATCH 2/2] AT91: dt: simple device tree support for at91sam9g45 family Nicolas Ferre
2011-08-05 16:24   ` Nicolas Ferre
2011-08-05 16:24   ` Nicolas Ferre
2011-08-07  3:57   ` Grant Likely
2011-08-07  3:57     ` Grant Likely
2011-08-07  3:57     ` Grant Likely
2011-08-08 19:59     ` Nicolas Ferre [this message]
2011-08-08 19:59       ` Nicolas Ferre
2011-08-08 19:59       ` 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=4E40401F.4030309@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.