From: Huang Shijie <b32955@freescale.com>
To: Subodh Nijsure <snijsure@grid-net.com>
Cc: shawn.guo@linaro.org, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, dedekind1@gmail.com
Subject: Re: [PATCH 1/2] mtd: gpmi: add device tree support to gpmi-nand
Date: Fri, 4 May 2012 12:30:43 +0800 [thread overview]
Message-ID: <4FA35B73.8080008@freescale.com> (raw)
In-Reply-To: <4FA34EAD.1010302@grid-net.com>
Hi,
> Any chance you can add some information on what kind of mtd tests were
> done with this code change and on what platform?
I did bonnie++ test, and mtd_speed test on mx28evk board.
>
> Also if one wanted to test this patch say on mx28 based hardware, one
> should apply this patch against arm-soc tree, top of the 3.5-next tree?
If you only want to test this on mx28 based hardware, you can just apply
this patch against the arm-soc tree, top of the 3.5-next tree.
But you still need some extra mxs-dma patches (and maybe do some
hardcode for pinctl) to make the gpmi-nand driver work.
Best Regards
Huang Shijie
WARNING: multiple messages have this Message-ID (diff)
From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] mtd: gpmi: add device tree support to gpmi-nand
Date: Fri, 4 May 2012 12:30:43 +0800 [thread overview]
Message-ID: <4FA35B73.8080008@freescale.com> (raw)
In-Reply-To: <4FA34EAD.1010302@grid-net.com>
Hi,
> Any chance you can add some information on what kind of mtd tests were
> done with this code change and on what platform?
I did bonnie++ test, and mtd_speed test on mx28evk board.
>
> Also if one wanted to test this patch say on mx28 based hardware, one
> should apply this patch against arm-soc tree, top of the 3.5-next tree?
If you only want to test this on mx28 based hardware, you can just apply
this patch against the arm-soc tree, top of the 3.5-next tree.
But you still need some extra mxs-dma patches (and maybe do some
hardcode for pinctl) to make the gpmi-nand driver work.
Best Regards
Huang Shijie
next prev parent reply other threads:[~2012-05-04 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 3:13 [PATCH 1/2] mtd: gpmi: add device tree support to gpmi-nand Huang Shijie
2012-05-04 3:13 ` Huang Shijie
2012-05-04 3:13 ` [PATCH 2/2] mtd: gpmi: add gpmi support for mx6q Huang Shijie
2012-05-04 3:13 ` Huang Shijie
2012-05-04 3:36 ` [PATCH 1/2] mtd: gpmi: add device tree support to gpmi-nand Subodh Nijsure
2012-05-04 3:36 ` Subodh Nijsure
2012-05-04 4:30 ` Huang Shijie [this message]
2012-05-04 4:30 ` Huang Shijie
2012-05-04 9:41 ` Artem Bityutskiy
2012-05-04 9:41 ` Artem Bityutskiy
2012-05-04 10:26 ` Huang Shijie
2012-05-04 10:26 ` Huang Shijie
2012-05-04 10:37 ` Artem Bityutskiy
2012-05-04 10:37 ` 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=4FA35B73.8080008@freescale.com \
--to=b32955@freescale.com \
--cc=dedekind1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shawn.guo@linaro.org \
--cc=snijsure@grid-net.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 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.