public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Guido Martínez" <guido@vanguardiasur.com.ar>
To: Tony Lindgren <tony@atomide.com>, Pekon Gupta <pekon@ti.com>
Cc: Jason Kridner <jkridner@gmail.com>,
	Robert Nelson <robertcnelson@gmail.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v1 1/3] ARM: dts: am335x-bone: add support for beaglebone NAND cape
Date: Thu, 26 Jun 2014 12:06:15 -0300	[thread overview]
Message-ID: <20140626150615.GA15648@fox> (raw)
In-Reply-To: <20140626104044.GJ28884@atomide.com>

Hi Tony, Pekon

On Thu, Jun 26, 2014 at 03:40:44AM -0700, Tony Lindgren wrote:
> * Pekon Gupta <pekon@ti.com> [140624 05:26]:
> > +
> > +&gpmc {
> > +	ranges = <0 0 0 0x01000000>;	/* address range = 16MB (minimum GPMC partition) */
> > +	nand@0,0 {
> > +		status = "disabled";
> > +		reg = <0 0 4>;		/* device IO registers */
> 
> Hmm so what about other capes potentially also using GPMC CS0?
> 
> Can you please do a check with two .dtsi files trying to use
> GPMC CS0 and see what the produced .dtb file looks like after
> decompiling it with dtc?
> 
> I'd assume the 16MB GPMC partition will be just fine for many
> devices and can be also be larger if NOR needs it so maybe it
> can be handled for almost all the cases.
> 
> The names for devices must be unique though to avoid them
> getting merged. And I don't know if gpmc.c skips disabled devices
> properly.
It doesn't. I've just sent a patch for it.

http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/266966.html

Regards,
Guido

> 
> Regards,
> 
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Guido Martínez, VanguardiaSur
www.vanguardiasur.com.ar

  reply	other threads:[~2014-06-26 15:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 12:24 [PATCH v1 0/3] ARM: dts: am335x-bone: Beaglebone cape DTS Pekon Gupta
2014-06-24 12:24 ` [PATCH v1 1/3] ARM: dts: am335x-bone: add support for beaglebone NAND cape Pekon Gupta
2014-06-25 15:27   ` Ezequiel Garcia
2014-06-26  5:43     ` Gupta, Pekon
2014-06-26 10:40   ` Tony Lindgren
2014-06-26 15:06     ` Guido Martínez [this message]
2014-07-01  7:01       ` Gupta, Pekon
2014-07-01 23:42         ` Guido Martínez
2014-07-02  5:29           ` Gupta, Pekon
2014-06-26 19:48   ` Guido Martínez
2014-06-27 21:06     ` Gupta, Pekon
2014-07-01  8:47       ` Tony Lindgren
2014-07-01  9:07         ` Gupta, Pekon
2014-07-01 13:28           ` Tony Lindgren
2014-06-24 12:24 ` [PATCH v1 2/3] ARM: dts: am335x-bone: add support for beaglebone NOR cape Pekon Gupta
2014-06-24 12:24 ` [PATCH v1 3/3] ARM: dts: am335x-bone: add support for beaglebone LCD4 cape Pekon Gupta
2014-06-24 15:03   ` Ezequiel Garcia
2014-06-25  4:38     ` Gupta, Pekon
2014-06-25 14:59       ` Ezequiel Garcia
2014-06-24 15:24   ` Jason Kridner
2014-06-25  5:49     ` Gupta, Pekon
2014-06-26  4:30       ` Jason Kridner
2014-06-26 15:40   ` Guido Martínez
2014-06-26 18:35     ` Darren Etheridge
2014-06-27 11:38       ` Gupta, Pekon
  -- strict thread matches above, loose matches on Subject: below --
2014-03-12 10:49 [PATCH v1 0/3] add parallel NAND support for TI's new OMAPx and AMxx platforms (Part-2) Pekon Gupta
2014-03-12 10:49 ` [PATCH v1 1/3] ARM: dts: am335x-bone: add support for beaglebone NAND cape Pekon Gupta
2014-03-12 14:35   ` Nishanth Menon
2014-03-12 18:26     ` Gupta, Pekon
2014-03-12 18:57       ` Nishanth Menon
2014-03-12 19:08         ` Robert Nelson
2014-03-12 19:28           ` Tony Lindgren
2014-03-12 20:51             ` Nishanth Menon
2014-03-12 21:13               ` Gupta, Pekon
2014-03-12 21:53                 ` Nishanth Menon
2014-03-13  6:19                   ` Gupta, Pekon
2014-03-13 13:03                     ` Nishanth Menon
2014-03-13 13:30                       ` Robert Nelson
2014-03-13 16:55                         ` Tony Lindgren

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=20140626150615.GA15648@fox \
    --to=guido@vanguardiasur.com.ar \
    --cc=jkridner@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=pekon@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=tony@atomide.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