linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: richard@nod.at (Richard Weinberger)
To: linux-arm-kernel@lists.infradead.org
Subject: at91: smc configuration using DT
Date: Tue, 16 Dec 2014 00:10:41 +0100	[thread overview]
Message-ID: <548F6A71.30304@nod.at> (raw)
In-Reply-To: <2463675.Tt7GDs0rfe@wuerfel>

Am 15.12.2014 um 23:56 schrieb Arnd Bergmann:
> On Monday 15 December 2014 23:47:48 Richard Weinberger wrote:
>>
>> I'm sure I'm missing something.
>>
>> One of my boards is still using board files and uses sam9_smc_configure() to
>> setup NAND timings. I'd like to convert it to DT but I fail to see how to configure the smc.
>> What is the device tree equivalent of sam9_smc_configure()?
>>
>>
> 
> I think it's actually missing, see the series "memory: add Atmel EBI
> (External Bus Interface) driver" from Boris Brezillon.

Thanks a lot for your quick reply, Arnd!

arch/arm/mach-at91/board-stamp9g20.c was removed by:

commit fb3642ebb52cfab8eaa52fea677abec4d92182a0
Author: Nicolas Ferre <nicolas.ferre@atmel.com>
Date:   Wed Nov 19 10:30:41 2014 +0100

    ARM: at91: remove at91sam9260/at91sam9g20 legacy boards files

    Remove old board files that use at91sam9260 or at91sam9g20 Atmel SoCs. The
    device tree is mature on these SoCs. It must be used now.

    Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>

How can this DT work for my board without proper NAND timings?

If I need Boris's patch set first I consider commit fb3642ebb a bit rude as it breaks
things.

*confused*,
//richard

  reply	other threads:[~2014-12-15 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 22:47 at91: smc configuration using DT Richard Weinberger
2014-12-15 22:56 ` Arnd Bergmann
2014-12-15 23:10   ` Richard Weinberger [this message]
2014-12-16 10:14     ` Nicolas Ferre
2014-12-16 10:21       ` Richard Weinberger

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=548F6A71.30304@nod.at \
    --to=richard@nod.at \
    --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 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).