From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: linuxppc-dev@ozlabs.org
Cc: ben@simtec.co.uk, linux-mtd@lists.infradead.org
Subject: OF compatible MTD platform RAM driver ?
Date: Mon, 10 Mar 2008 16:06:31 +0100 [thread overview]
Message-ID: <200803101606.39184.laurentp@cse-semaphore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Hi everybody,
as part of a ARCH=ppc to ARCH=powerpc migration process, I'm looking for an
OpenFirmware compatible way to handle a RAM-based MTD device.
On the platform_device based ppc architecture, the drivers/mtd/maps/plat-ram.c
driver handled "mtd-ram" platform devices. There is no such driver for the
OF-based powerpc architecture.
As a temporary workaround I hacked the physmap_of driver to
handle "direct-mapped" OF devices oh type "ram" by adding a corresponding
entry in the of_flash_match[] array. This seems to work fine.
What would be the preferred way to handle OF-compatible RAM-based MTD
devices ? The 3 ways I can think of are
1. porting the plat-ram driver to OF (the driver isn't used in the kernel tree
but I suspect it is used by out-of-tree boards)
2. creating a new plat-ram-of driver, much like the physmap_of driver comes
from the physmap driver
3. extending the physmap_of driver to handle RAM devices (in which case
references to "flash" in the function names should probably be replaced
by "mtd")
I live option 3 better so far.
Has anyone already worked on this ? Is there any defined device tree mapping
for MTD RAM devices ?
Best regards,
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-03-10 15:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 15:06 Laurent Pinchart [this message]
2008-03-10 17:00 ` OF compatible MTD platform RAM driver ? Rune Torgersen
2008-03-11 0:45 ` David Gibson
2008-03-11 10:39 ` Laurent Pinchart
2008-03-11 22:40 ` David Gibson
2008-03-25 14:36 ` Laurent Pinchart
2008-03-25 15:29 ` Sergei Shtylyov
2008-03-25 15:51 ` Laurent Pinchart
2008-03-25 16:23 ` Sergei Shtylyov
2008-03-25 16:44 ` Laurent Pinchart
2008-03-25 17:02 ` Sergei Shtylyov
2008-03-25 17:23 ` Laurent Pinchart
2008-03-25 17:37 ` Sergei Shtylyov
2008-03-25 17:56 ` Rune Torgersen
2008-03-25 18:14 ` Laurent Pinchart
2008-03-26 12:53 ` Sergei Shtylyov
2008-03-27 9:13 ` Laurent Pinchart
2008-03-27 10:03 ` David Gibson
2008-03-27 12:23 ` Sergei Shtylyov
2008-03-28 0:07 ` David Gibson
2008-03-28 12:31 ` Sergei Shtylyov
2008-03-27 14:31 ` Laurent Pinchart
2008-03-28 0:09 ` David Gibson
2008-03-30 18:15 ` Segher Boessenkool
2008-03-30 21:16 ` Paul Mackerras
2008-03-30 22:39 ` Segher Boessenkool
2008-03-31 0:42 ` Paul Mackerras
2008-03-31 0:59 ` Segher Boessenkool
2008-03-31 1:24 ` Segher Boessenkool
2008-03-31 8:21 ` Laurent Pinchart
2008-03-31 12:21 ` Segher Boessenkool
2008-03-26 15:06 ` Segher Boessenkool
2008-03-26 15:40 ` Sergei Shtylyov
2008-03-27 9:24 ` Laurent Pinchart
2008-03-30 18:12 ` Segher Boessenkool
2008-03-26 15:09 ` Segher Boessenkool
2008-03-11 15:00 ` Rune Torgersen
2008-03-11 22:41 ` David Gibson
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=200803101606.39184.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=ben@simtec.co.uk \
--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 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).