From: Artem Bityutskiy <dedekind@infradead.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss@ozlabs.org,
"Vitaly Wool" <vwool@ru.mvista.com>,
"Albrecht Dreß" <albrecht.dress@arcor.de>,
"Wolfram Sang" <w.sang@pengutronix.de>,
linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
"Ken MacLeod" <ken@bitsko.slc.ut.us>,
"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd/maps: add mtd-ram support to physmap_of
Date: Sun, 09 Aug 2009 08:17:23 +0300 [thread overview]
Message-ID: <1249795043.9157.37.camel@localhost> (raw)
In-Reply-To: <fa686aa40908072243x56d2160fk688149f4b7b912ae@mail.gmail.com>
On Fri, 2009-08-07 at 23:43 -0600, Grant Likely wrote:
> On Fri, Jul 17, 2009 at 6:39 AM, Wolfram Sang<w.sang@pengutronix.de> wrote:
> > Use physmap_of to access RAMs as mtd and add documenation for it. This approach
> > is a lot less intrusive as adding an of-wrapper around plat-ram.c. As most
> > extensions of plat-ram.c (e.g. custom map-functions) can't be mapped to the
> > device tree anyhow, extending physmap_of seems to be the cleanest approach.
> >
> > Tested with a phyCORE-MPC5121e.
> >
> > Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
>
> Looks good to me.
>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
This patch is sitting in my l2-mtd-2.6.git tree.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind@infradead.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss@ozlabs.org,
"Vitaly Wool" <vwool@ru.mvista.com>,
"Albrecht Dreß" <albrecht.dress@arcor.de>,
linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
"Ken MacLeod" <ken@bitsko.slc.ut.us>,
"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd/maps: add mtd-ram support to physmap_of
Date: Sun, 09 Aug 2009 08:17:23 +0300 [thread overview]
Message-ID: <1249795043.9157.37.camel@localhost> (raw)
In-Reply-To: <fa686aa40908072243x56d2160fk688149f4b7b912ae@mail.gmail.com>
On Fri, 2009-08-07 at 23:43 -0600, Grant Likely wrote:
> On Fri, Jul 17, 2009 at 6:39 AM, Wolfram Sang<w.sang@pengutronix.de> wrote:
> > Use physmap_of to access RAMs as mtd and add documenation for it. This approach
> > is a lot less intrusive as adding an of-wrapper around plat-ram.c. As most
> > extensions of plat-ram.c (e.g. custom map-functions) can't be mapped to the
> > device tree anyhow, extending physmap_of seems to be the cleanest approach.
> >
> > Tested with a phyCORE-MPC5121e.
> >
> > Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
>
> Looks good to me.
>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
This patch is sitting in my l2-mtd-2.6.git tree.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind@infradead.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss@ozlabs.org,
"Vitaly Wool" <vwool@ru.mvista.com>,
"Albrecht Dreß" <albrecht.dress@arcor.de>,
linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
"Ken MacLeod" <ken@bitsko.slc.ut.us>,
"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd/maps: add mtd-ram support to physmap_of
Date: Sun, 09 Aug 2009 08:17:23 +0300 [thread overview]
Message-ID: <1249795043.9157.37.camel@localhost> (raw)
In-Reply-To: <fa686aa40908072243x56d2160fk688149f4b7b912ae@mail.gmail.com>
On Fri, 2009-08-07 at 23:43 -0600, Grant Likely wrote:
> On Fri, Jul 17, 2009 at 6:39 AM, Wolfram Sang<w.sang@pengutronix.de> wrote:
> > Use physmap_of to access RAMs as mtd and add documenation for it. This approach
> > is a lot less intrusive as adding an of-wrapper around plat-ram.c. As most
> > extensions of plat-ram.c (e.g. custom map-functions) can't be mapped to the
> > device tree anyhow, extending physmap_of seems to be the cleanest approach.
> >
> > Tested with a phyCORE-MPC5121e.
> >
> > Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
>
> Looks good to me.
>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
This patch is sitting in my l2-mtd-2.6.git tree.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2009-08-09 5:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 12:39 [PATCH] mtd/maps: add mtd-ram support to physmap_of Wolfram Sang
2009-07-17 12:39 ` Wolfram Sang
2009-07-17 12:39 ` Wolfram Sang
2009-07-31 19:47 ` Albrecht Dreß
2009-07-31 19:47 ` Albrecht Dreß
2009-08-08 5:43 ` Grant Likely
2009-08-08 5:43 ` Grant Likely
2009-08-09 5:17 ` Artem Bityutskiy [this message]
2009-08-09 5:17 ` Artem Bityutskiy
2009-08-09 5:17 ` Artem Bityutskiy
2009-08-10 16:19 ` Wolfram Sang
2009-08-10 16:19 ` Wolfram Sang
2009-08-10 16:19 ` Wolfram Sang
2009-08-10 16:25 ` Artem Bityutskiy
2009-08-10 16:25 ` Artem Bityutskiy
2009-08-10 16:25 ` Artem Bityutskiy
2009-08-11 5:55 ` Artem Bityutskiy
2009-08-11 5:55 ` Artem Bityutskiy
2009-08-11 5:55 ` Artem Bityutskiy
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=1249795043.9157.37.camel@localhost \
--to=dedekind@infradead.org \
--cc=albrecht.dress@arcor.de \
--cc=devicetree-discuss@ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--cc=ken@bitsko.slc.ut.us \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=vwool@ru.mvista.com \
--cc=w.sang@pengutronix.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 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.