All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: dedekind@infradead.org
Cc: Grant Likely <grant.likely@secretlab.ca>,
	linuxppc-dev@ozlabs.org,
	devicetree-discuss <devicetree-discuss@ozlabs.org>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/3 v3] mtd: physmap_of: Add multiple regions and concatenation support
Date: Thu, 16 Apr 2009 14:52:25 +0200	[thread overview]
Message-ID: <200904161452.25393.sr@denx.de> (raw)
In-Reply-To: <1239884344.3390.213.camel@localhost.localdomain>

On Thursday 16 April 2009, Artem Bityutskiy 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. Additionally
> > partitions now can span over multiple chips:
> >
> >     mtd: physmap_of: Add multiple regions and concatenation support
> >     mtd/powerpc: Factor out MTD physmap bindings into mtd-physmap.txt
> >     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.

The result of these multiple "reg" tuples *is* multiple MTD devices. Not sure 
if this explains your comment/question. Please let me know if you still have 
some comments.

Thanks.

Best regards,
Stefan

WARNING: multiple messages have this Message-ID (diff)
From: Stefan Roese <sr@denx.de>
To: dedekind@infradead.org
Cc: linuxppc-dev@ozlabs.org,
	devicetree-discuss <devicetree-discuss@ozlabs.org>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/3 v3] mtd: physmap_of: Add multiple regions and concatenation support
Date: Thu, 16 Apr 2009 14:52:25 +0200	[thread overview]
Message-ID: <200904161452.25393.sr@denx.de> (raw)
In-Reply-To: <1239884344.3390.213.camel@localhost.localdomain>

On Thursday 16 April 2009, Artem Bityutskiy 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. Additionally
> > partitions now can span over multiple chips:
> >
> >     mtd: physmap_of: Add multiple regions and concatenation support
> >     mtd/powerpc: Factor out MTD physmap bindings into mtd-physmap.txt
> >     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.

The result of these multiple "reg" tuples *is* multiple MTD devices. Not sure 
if this explains your comment/question. Please let me know if you still have 
some comments.

Thanks.

Best regards,
Stefan

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

Thread overview: 14+ 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:05 ` Stefan Roese
2009-04-16 12:05 ` Stefan Roese
2009-04-16 12:19 ` Artem Bityutskiy
2009-04-16 12:19   ` Artem Bityutskiy
2009-04-16 12:19   ` Artem Bityutskiy
2009-04-16 12:52   ` Stefan Roese [this message]
2009-04-16 12:52     ` Stefan Roese
2009-04-16 13:09     ` Artem Bityutskiy
2009-04-16 13:09       ` Artem Bityutskiy
2009-04-16 13:09       ` Artem Bityutskiy
2009-04-16 12:58   ` Grant Likely
2009-04-16 12:58     ` Grant Likely
2009-04-16 12:58     ` Grant Likely

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