Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6q-arm2: move NANDF_CS pins out of 'hog'
Date: Tue, 16 Oct 2012 10:07:58 -0700	[thread overview]
Message-ID: <20121016170758.GA32415@quad.lixom.net> (raw)
In-Reply-To: <20121015133516.GC24393@S2101-09.ap.freescale.net>

On Mon, Oct 15, 2012 at 09:35:20PM +0800, Shawn Guo wrote:
> On Mon, Oct 15, 2012 at 08:45:48AM -0400, Huang Shijie wrote:
> > On Mon, Oct 15, 2012 at 4:48 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > > Commit 9e3c0066 (ARM: dts: imx6q-arm2: add pinctrl for uart and enet)
> > > defines NANDF_CS pins as gpio in 'hog', assuming these two pins are
> > > always used by usdhc3 in gpio mode as card-detection and
> > > write-protection on ARM2 board.  But it's not true.  These pins are
> > > shared by usdhc3 and gpmi-nand.  We should have the pins functional
> > > for gpmi-nand when usdhc3 is disabled.
> > >
> > > Move the pins out of 'hog', so that pins only work in gpio mode as CD
> > > and WP when usdhc3 is enabled, and otherwise they are available for
> > > gpmi-nand.
> > >
> > > Reported-by: Huang Shijie <b32955@freescale.com>
> > > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > > ---
> > > Huang,
> > >
> > > Please help test the patch to see if it fixes your problem, thanks.
> > 
> > yes, this patch fixes the problem.
> > thanks a lot.
> > 
> > Tested-by: Huang Shijie <shijie8@gmail.com>
> > 
> Arnd, Olof,
> 
> Can you please send it for later -rc, since it fixes a regression
> in -rc1?

Done, applied to fixes and will be sent up with the next batch for
3.7-rc2.


-Olof

      reply	other threads:[~2012-10-16 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  8:48 [PATCH] ARM: dts: imx6q-arm2: move NANDF_CS pins out of 'hog' Shawn Guo
2012-10-15 12:45 ` Huang Shijie
2012-10-15 13:35   ` Shawn Guo
2012-10-16 17:07     ` Olof Johansson [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=20121016170758.GA32415@quad.lixom.net \
    --to=olof@lixom.net \
    --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