From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd/gpmi : add gpmi support for mx6q
Date: Thu, 16 Feb 2012 10:38:26 +0800 [thread overview]
Message-ID: <4F3C6C22.2010003@freescale.com> (raw)
In-Reply-To: <20120216021841.GG30946@r65073-Latitude-D630>
Hi,
> On Thu, Feb 16, 2012 at 09:56:10AM +0800, Huang Shijie wrote:
>> Hi,
>>> The imx6q only supports DT boot, but I do not see you are adding DT
>>> probe for the driver, so I'm wondering how you tested the driver on
>>> imx6q.
>>>
>> This patch is just the first patch for mx6q. My following patches will
>> add DT to the gpmi nand driver for mx6q. Due to the dependency
>> issue, I will send the patches
>> in the following order:
>> [1] mtd/gpmi: add gpmi support for mx6q.
>> [2] [PATCH v5] patch set about the MXS-DMA
>> [3] add DT support to gpmi for mx6q.
>>
> It should be:
>
> 1. MXS-DMA series
> 2. Add imx6q support with DT probe
>
I ever did so in this order. But the mxs-dma series delayed for long
time( I missed the CCs).
But Artem's tree is faster to merge patch.
>> I tested this patch based on our bsp code.
>>
> This is wrong approach. You are submitting patches to mainline, so
> you should test your patches on mainline tree.
>
Beside the DT, the gpmi nand driver is the same.
Is the mainline tree ready now? How can i to set the pinmux for gpmi?
BR
Huang Shijie
next prev parent reply other threads:[~2012-02-16 2:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 5:20 [PATCH] mtd/gpmi : add gpmi support for mx6q Huang Shijie
2012-02-13 11:58 ` Bityutskiy, Artem
2012-02-13 14:41 ` Wolfram Sang
2012-02-13 14:45 ` Fabio Estevam
2012-02-13 15:05 ` 答复: " Huang Shijie-B32955
2012-02-13 15:34 ` Bityutskiy, Artem
2012-02-13 15:48 ` 答复: " Huang Shijie-B32955
2012-02-13 16:13 ` Artem Bityutskiy
2012-02-13 16:22 ` Bityutskiy, Artem
2012-02-15 18:37 ` Shawn Guo
2012-02-16 1:56 ` Huang Shijie
2012-02-16 2:18 ` Shawn Guo
2012-02-16 2:38 ` Huang Shijie [this message]
2012-02-16 4:51 ` Shawn Guo
2012-02-16 5:42 ` Huang Shijie
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=4F3C6C22.2010003@freescale.com \
--to=b32955@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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).