From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: ben@simtec.co.uk, linuxppc-dev@ozlabs.org,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 1/2] [MTD] Add support for RAM & ROM mappings in the physmap_of MTD driver.
Date: Fri, 25 Apr 2008 13:53:10 +0200 [thread overview]
Message-ID: <200804251353.13698.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <480F19B9.1070403@ru.mvista.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On Wednesday 23 April 2008 13:12, Sergei Shtylyov wrote:
> David Woodhouse wrote:
>
> >>>>Ok. I'll submit a new patch as soon as we agree on a compatible name.
>
> >>>Did we?
>
> >> IIRC, The latest agreement was that we don't need the "compatible" and
> >>will match on node name.
>
> > Ok. Is there a current patch I should be merging?
>
> Looks like it was decided to revert to the platform device method, not
> sure why -- so, no changes. Laurent?
Last thing I heard was that the device tree should not encode a device's
expected usage, so memory nodes should not have any compatible property that
would automatically associated them to an MTD driver. I've been adviced to
add platform-specific code to instantiate a platform device manually
(possibly checking if the required memory node is present in the device
tree). This arguably makes sense, but adds more platform-specific code.
So, no need for a patch so far.
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee 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 prev parent reply other threads:[~2008-04-25 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 12:44 [PATCH 1/2] [MTD] Add support for RAM & ROM mappings in the physmap_of MTD driver Laurent Pinchart
2008-03-26 14:45 ` Segher Boessenkool
2008-03-26 15:26 ` Sergei Shtylyov
2008-03-26 15:34 ` Segher Boessenkool
2008-03-26 23:37 ` David Gibson
2008-03-27 9:26 ` Laurent Pinchart
2008-04-22 20:09 ` David Woodhouse
2008-04-22 20:16 ` Sergei Shtylyov
2008-04-22 20:18 ` David Woodhouse
2008-04-23 11:12 ` Sergei Shtylyov
2008-04-25 11:53 ` Laurent Pinchart [this message]
2008-04-28 16:26 ` [PATCH 1/2] [MTD] Add support for RAM & ROMmappings " Rune Torgersen
2008-04-28 20:30 ` Scott Wood
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=200804251353.13698.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=ben@simtec.co.uk \
--cc=david@gibson.dropbear.id.au \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sshtylyov@ru.mvista.com \
/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).