linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 4/4] ARM: mxs/mx28evk: add GPMI-NAND device
Date: Wed, 18 Apr 2012 23:46:48 +0200	[thread overview]
Message-ID: <201204182346.48333.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAOMZO5Dr+qVMOpG6T03L-+i6qYkJRPUPT87hcJAs6DxHs+EcmA@mail.gmail.com>

Dear Fabio Estevam,

> On Thu, Apr 5, 2012 at 11:31 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > I have to do that to motivate people to add DT support for the drivers
> > they submit from the beginning.
> 
> Understand your point for new drivers.
> 
> If you take the GPMI driver for example: it has been available for a
> long time and there is no board using it in mainline.
> 
> So how can people easily test it and find bugs with this driver?
> Patching their own trees themselves? Sam Gandhi did extensive tests on
> NAND and found some DMA issues with it.
> 
> If we could have mx28evk supporting GPMI driver today it would
> estimulate people to use it and more issues can be found and fixed.
> 
> Waiting for DT support to be in place is just blocking the progress for
> mx28.

Sadly, I have to agree. I'm not against DT, but blocking it now is bogus.

> Please note that right now there is no dt support for mx28 in mainline.
> 
> If what blocks this patch "ARM: mxs/mx28evk: add GPMI-NAND device" to
> be accepted is the pin mux conflict, that would be easy to fix and
> Huang could do a v5 if you agree.
> 
> > Also I do not see much point to keep patching board files which are
> > to be removed.
> 
> I understand your point, but again, right now there is no dt support,
> so the only mechanism we have to register driver is via board files
> for mx28.
> 
> So it would be nice if you could still accept patches for mx28 while
> mx28 dt does not show up in mainline.
> 

Agreed


Best regards,
Marek Vasut

  parent reply	other threads:[~2012-04-18 21:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  7:07 [PATCH v8 0/4] add the GPMI-NAND support for imx23/imx28 Huang Shijie
2011-08-24  7:07 ` [PATCH v8 1/4] ARM: mxs: add " Huang Shijie
2011-08-24  7:07 ` [PATCH v8 2/4] ARM: mxs: add new a pad control Huang Shijie
2011-08-24  7:07 ` [PATCH v8 3/4] ARM: mxs/mx23evk: add GPMI-NAND device Huang Shijie
2011-08-24  7:07 ` [PATCH v8 4/4] ARM: mxs/mx28evk: " Huang Shijie
2012-04-05  0:44   ` Fabio Estevam
2012-04-05  0:45     ` Fabio Estevam
2012-04-05  1:08     ` Shawn Guo
2012-04-05  1:19       ` Fabio Estevam
2012-04-05  1:23         ` Shawn Guo
2012-04-05 16:12           ` Fabio Estevam
2012-04-06  2:31             ` Shawn Guo
     [not found]               ` <C7A5B00EFC707A46AB67997D0215216701B5C28A@mx1.grid-net.com>
2012-04-06  3:35                 ` Shawn Guo
2012-04-06  5:49               ` Fabio Estevam
2012-04-06  6:53                 ` Shawn Guo
2012-04-06 13:16                   ` Fabio Estevam
2012-04-06 13:46                     ` Shawn Guo
2012-04-06 13:56                       ` Fabio Estevam
2012-04-18 21:46                 ` Marek Vasut [this message]
2011-08-25 11:37 ` [PATCH v8 0/4] add the GPMI-NAND support for imx23/imx28 Artem Bityutskiy
2011-08-26  3:28   ` Huang Shijie
2011-08-26 13:35     ` Koen Beel
2011-09-16  2:28 ` 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=201204182346.48333.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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).