linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Rob Herring <robherring2@gmail.com>
Cc: grant.likely@secretlab.ca, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org, plagnioj@jcrosoft.com
Subject: Re: [PATCH V3 1/2] ARM: at91: dt: at91sam9g45 family and board device tree files
Date: Tue, 25 Oct 2011 13:06:36 +0200	[thread overview]
Message-ID: <4EA6983C.5080303@atmel.com> (raw)
In-Reply-To: <4EA579E7.7000002@gmail.com>

On 10/24/2011 04:44 PM, Rob Herring :
> On 10/24/2011 09:05 AM, Nicolas Ferre wrote:
>> Create a new device tree source file for Atmel at91sam9g45 SoC family.
>> The Evaluation Kit at91sam9m10g45ek includes it.
>> This first basic support will be populated as drivers and boards will be
>> converted to device tree.
>> Contains serial, dma and interrupt controllers.
>>
>> The generic board file still takes advantage of platform data for early serial
>> init. As we need a storage media and the NAND flash driver is not converted to
>> DT yet, we keep old initialization for it.
>>
> 
> This comment is out of date for serial.

Well, not for early serial actually.

>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>> ---
>> V3:
>> - additional clock lookup for device tree handling
>> - devices disabled in dtsi file so that only useful devices are
>>   enabled in dts files
>>
>> V2: foundation for AT91SAM generic support
>> - device tree focused board file
>> - inclusion of USART DT support
>> - early USART and NAND still using platform data
>>
> 
> Reviewed-by: Rob Herring <rob.herring@calxeda.com>

Thanks Rob for your review. I send a pull request to Arnd on this material.

Best regards,
-- 
Nicolas Ferre

  reply	other threads:[~2011-10-25 11:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 10:00 [PATCH V2] AT91: dt: at91sam9g45 family and board device tree files Nicolas Ferre
2011-10-03  8:52 ` Russell King - ARM Linux
2011-10-05 13:00 ` Rob Herring
2011-10-07 12:56   ` Nicolas Ferre
2011-10-18 10:07     ` Nicolas Ferre
2011-10-18 20:44       ` Rob Herring
2011-10-19  8:03         ` Nicolas Ferre
2011-10-20  2:06           ` Rob Herring
2011-10-24 14:05             ` [PATCH V3 1/2] ARM: at91: " Nicolas Ferre
2011-10-24 14:05               ` [PATCH V3 2/2] ARM: at91: add at91sam9g20 and Calao USB A9G20 DT support Nicolas Ferre
2011-10-24 14:09                 ` [PATCH V3 (bugfix to fold)] ARM: at91: usb_a9g20.dts: fix memory location Nicolas Ferre
2011-10-24 14:49                 ` [PATCH V3 2/2] ARM: at91: add at91sam9g20 and Calao USB A9G20 DT support Rob Herring
2011-10-24 14:12               ` [PATCH V3 1/2] ARM: at91: dt: at91sam9g45 family and board device tree files Baruch Siach
2011-10-24 14:32                 ` Nicolas Ferre
2011-10-24 14:44               ` Rob Herring
2011-10-25 11:06                 ` Nicolas Ferre [this message]
2011-10-24 14:34       ` [PATCH V2] AT91: " Grant Likely
2011-10-24 14:42         ` 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=4EA6983C.5080303@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=robherring2@gmail.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 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).