linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: dedekind@infradead.org
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
	linux-mtd@lists.infradead.org,
	devicetree-discuss <devicetree-discuss@ozlabs.org>
Subject: Re: [PATCH 0/3 v3] mtd: physmap_of: Add multiple regions and concatenation support
Date: Thu, 16 Apr 2009 06:58:22 -0600	[thread overview]
Message-ID: <fa686aa40904160558p613f43cbo361a500adee10d34@mail.gmail.com> (raw)
In-Reply-To: <1239884344.3390.213.camel@localhost.localdomain>

On Thu, Apr 16, 2009 at 6:19 AM, Artem Bityutskiy
<dedekind@infradead.org> wrote:
> On Thu, 2009-04-16 at 14:05 +0200, Stefan Roese wrote:
>> This patchset adds support to handle multiple non-identical chips in one
>> flash device tree node. It also adds concat support to physmap_of. This
>> makes it possible to support e.g. the Intel P30 48F4400 chip which
>> internally consists of 2 non-identical NOR chips on one die. Additionall=
y
>> partitions now can span over multiple chips:
>>
>> =9A =9A mtd: physmap_of: Add multiple regions and concatenation support
>> =9A =9A mtd/powerpc: Factor out MTD physmap bindings into mtd-physmap.tx=
t
>> =9A =9A mtd/powerpc: Describe multiple "reg" tuples usage
>>
>> v2 addresses all comments from Grant Likely, including factoring out the
>> MTD dts bindings documentation into a separate file.
>>
>> v3 addresses all comments (again from Grant).
>
> Sorry for my ignorance, but could you please explain why regions
> exists as an MTD concept? Why different regions could not be
> represented as different MTD devices? The benefit is - simplicity.

Trying to describe MTD partitions that span device boundaries in the
device tree is far simpler if a single node is used.  It is also a
common case for hardware designers to drop down multiple NOR devices
to be used as a single flash region, so it makes sense to describe it
as a single device.

g.

>
> Thanks.
>
> --
> Best regards,
> Artem Bityutskiy (=E2=C9=D4=C0=C3=CB=C9=CA =E1=D2=D4=A3=CD)
>
>



--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

      parent reply	other threads:[~2009-04-16 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 12:05 [PATCH 0/3 v3] mtd: physmap_of: Add multiple regions and concatenation support Stefan Roese
2009-04-16 12:19 ` Artem Bityutskiy
2009-04-16 12:52   ` Stefan Roese
2009-04-16 13:09     ` Artem Bityutskiy
2009-04-16 12:58   ` Grant Likely [this message]

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=fa686aa40904160558p613f43cbo361a500adee10d34@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=dedekind@infradead.org \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@denx.de \
    /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).