From: Stefan Roese <sr@denx.de>
To: linux-mtd@lists.infradead.org, linuxppc-dev@ozlabs.org
Cc: Grant Likely <grant.likely@secretlab.ca>,
devicetree-discuss <devicetree-discuss@ozlabs.org>
Subject: [PATCH 0/3 v3] mtd: physmap_of: Add multiple regions and concatenation support
Date: Thu, 16 Apr 2009 14:05:03 +0200 [thread overview]
Message-ID: <200904161405.04100.sr@denx.de> (raw)
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).
Thanks,
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Roese <sr@denx.de>
To: linux-mtd@lists.infradead.org, linuxppc-dev@ozlabs.org
Cc: devicetree-discuss <devicetree-discuss@ozlabs.org>
Subject: [PATCH 0/3 v3] mtd: physmap_of: Add multiple regions and concatenation support
Date: Thu, 16 Apr 2009 14:05:03 +0200 [thread overview]
Message-ID: <200904161405.04100.sr@denx.de> (raw)
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).
Thanks,
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
To: linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Cc: devicetree-discuss
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
Subject: [PATCH 0/3 v3] mtd: physmap_of: Add multiple regions and concatenation support
Date: Thu, 16 Apr 2009 14:05:03 +0200 [thread overview]
Message-ID: <200904161405.04100.sr@denx.de> (raw)
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).
Thanks,
Stefan
next reply other threads:[~2009-04-16 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 12:05 Stefan Roese [this message]
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:19 ` Artem Bityutskiy
2009-04-16 12:19 ` Artem Bityutskiy
2009-04-16 12:19 ` Artem Bityutskiy
2009-04-16 12:52 ` Stefan Roese
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=200904161405.04100.sr@denx.de \
--to=sr@denx.de \
--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.