linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] mtd: gpmi: add device tree support for mx6q and mx28
Date: Fri, 4 May 2012 10:39:07 +0800	[thread overview]
Message-ID: <4FA3414B.3050302@freescale.com> (raw)
In-Reply-To: <CAAQ0ZWTPhXNaMyFHyDnB4ez+VYpP=O1z8w-sYQiVspZSDBHuUw@mail.gmail.com>

? 2012?05?04? 10:28, Shawn Guo ??:
> On 4 May 2012 10:14, Huang Shijie<b32955@freescale.com>  wrote:
>> The mxs-dma is another driver (just as the pinctrl driver). I think it's
>> better to do the job in parallel.
>>
> The problem is if the patch gets applied on mtd tree as it is, the
> gpmi-nand will stop functioning on mtd tree.  Or you are fine with
even this patch is get applied. the gpmi-nand still can not work. I still
have to add the pinctl patch to it. So it have no difference on whether 
the mxs-dma driver is ready or not. :)
So let it go in parallel.

Best Regards
Huang Shijie


> that, since no in-tree board support is using the driver so far?  If
> you are fine with that, I'm fine too.
>
> Regards,
> Shawn
>

      reply	other threads:[~2012-05-04  2:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  6:13 [PATCH v3] mtd: gpmi: add device tree support for mx6q and mx28 Huang Shijie
2012-05-02 14:40 ` Shawn Guo
2012-05-03 10:54   ` Artem Bityutskiy
2012-05-03 12:38     ` Shawn Guo
2012-05-03 14:14       ` Huang Shijie
2012-05-03 14:23         ` Shawn Guo
2012-05-04  2:14           ` Huang Shijie
2012-05-04  2:28             ` Shawn Guo
2012-05-04  2:39               ` Huang Shijie [this message]

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=4FA3414B.3050302@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).