All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Florian Vaussard <florian.vaussard@epfl.ch>
Cc: Benoit Cousson <b-cousson@ti.com>, Daniel Mack <zonque@gmail.com>,
	linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo
Date: Fri, 1 Feb 2013 14:16:18 -0800	[thread overview]
Message-ID: <20130201221618.GB22517@atomide.com> (raw)
In-Reply-To: <1359395648-2137-1-git-send-email-florian.vaussard@epfl.ch>

* Florian Vaussard <florian.vaussard@epfl.ch> [130128 09:57]:
> Hello,
> 
> This is more an RFC serie, as an issue is still unclear to me.
> Building on the work of Daniel Mack for the GPMC controller (staged
> in Tony's tree [1]), it was easy to add the GPMC controller to OMAP3.
> 
> The issue comes from the Overo on-board NAND, as the amount of flash
> depends on the revision. Currently, partitions are handled in the board
> file using MTDPART_SIZ_FULL, but looking at the ofpart parser, the size
> given to the parser must be fixed.
> 
> So how should we handle such case? Having several dtsi depending
> on the Overo's revision would be a mess to my sense, considering
> the non-conditional include inside the expansion boards' dts.
> Or would it make sense to extend the DT binding for partitions?

Yes makes sense to extend the binding to use the full flash memory
if the size can be probed.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo
Date: Fri, 1 Feb 2013 14:16:18 -0800	[thread overview]
Message-ID: <20130201221618.GB22517@atomide.com> (raw)
In-Reply-To: <1359395648-2137-1-git-send-email-florian.vaussard@epfl.ch>

* Florian Vaussard <florian.vaussard@epfl.ch> [130128 09:57]:
> Hello,
> 
> This is more an RFC serie, as an issue is still unclear to me.
> Building on the work of Daniel Mack for the GPMC controller (staged
> in Tony's tree [1]), it was easy to add the GPMC controller to OMAP3.
> 
> The issue comes from the Overo on-board NAND, as the amount of flash
> depends on the revision. Currently, partitions are handled in the board
> file using MTDPART_SIZ_FULL, but looking at the ofpart parser, the size
> given to the parser must be fixed.
> 
> So how should we handle such case? Having several dtsi depending
> on the Overo's revision would be a mess to my sense, considering
> the non-conditional include inside the expansion boards' dts.
> Or would it make sense to extend the DT binding for partitions?

Yes makes sense to extend the binding to use the full flash memory
if the size can be probed.

Regards,

Tony

  parent reply	other threads:[~2013-02-01 22:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 17:54 [PATCH 0/2] ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo Florian Vaussard
2013-01-28 17:54 ` Florian Vaussard
2013-01-28 17:54 ` [PATCH 1/2] ARM: dts: OMAP3: Add GPMC controller Florian Vaussard
2013-01-28 17:54   ` Florian Vaussard
2013-02-04  9:27   ` Javier Martinez Canillas
2013-02-04  9:27     ` Javier Martinez Canillas
2013-02-04 10:36     ` Florian Vaussard
2013-02-04 10:36       ` Florian Vaussard
     [not found]       ` <510F8F49.9020800-p8DiymsW2f8@public.gmane.org>
2013-02-04 11:57         ` Javier Martinez Canillas
2013-02-04 11:57           ` Javier Martinez Canillas
2013-02-04 17:32           ` Tony Lindgren
2013-02-04 17:32             ` Tony Lindgren
2013-02-04 18:15             ` Javier Martinez Canillas
2013-02-04 18:15               ` Javier Martinez Canillas
2013-02-05 17:23           ` Florian Vaussard
2013-02-05 17:23             ` Florian Vaussard
2013-02-05 19:40             ` Javier Martinez Canillas
2013-02-05 19:40               ` Javier Martinez Canillas
2013-02-16 13:09   ` Anil Kumar
2013-02-16 13:09     ` Anil Kumar
2013-02-16 16:44     ` Javier Martinez Canillas
2013-02-16 16:44       ` Javier Martinez Canillas
2013-02-18 12:26       ` Cousson, Benoit
2013-02-18 12:26         ` Cousson, Benoit
2013-02-19  1:00   ` Jon Hunter
2013-02-19  1:00     ` Jon Hunter
2013-03-14 16:01   ` Benoit Cousson
2013-03-14 16:01     ` Benoit Cousson
2013-01-28 17:54 ` [PATCH 2/2] ARM: dts: OMAP3: Add NAND memory for Overo products Florian Vaussard
2013-01-28 17:54   ` Florian Vaussard
2013-02-01 22:16 ` Tony Lindgren [this message]
2013-02-01 22:16   ` [PATCH 0/2] ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo Tony Lindgren
2013-02-04  8:58   ` Florian Vaussard
2013-02-04  8:58     ` Florian Vaussard

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=20130201221618.GB22517@atomide.com \
    --to=tony@atomide.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=florian.vaussard@epfl.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=zonque@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 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.