From: Artem Bityutskiy <dedekind@infradead.org>
To: Stefan Roese <sr@denx.de>
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 15:19:04 +0300 [thread overview]
Message-ID: <1239884344.3390.213.camel@localhost.localdomain> (raw)
In-Reply-To: <200904161405.04100.sr@denx.de>
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.
Thanks.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-04-16 12:19 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 [this message]
2009-04-16 12:52 ` Stefan Roese
2009-04-16 13:09 ` Artem Bityutskiy
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=1239884344.3390.213.camel@localhost.localdomain \
--to=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).