From: Marek Vasut <marex@denx.de>
To: "Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>
Cc: "Artem Bityutskiy" <artem.bityutskiy@linux.intel.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
"Lothar Waßmann" <LW@karo-electronics.de>
Subject: Re: [PATCH] mtd: mxc_nand: Make use of supplied pinctrl data
Date: Tue, 8 Jan 2013 21:22:46 +0100 [thread overview]
Message-ID: <201301082122.46815.marex@denx.de> (raw)
In-Reply-To: <20130108195826.GD7360@game.jcrosoft.org>
Dear Jean-Christophe PLAGNIOL-VILLARD,
> On 15:28 Mon 07 Jan , Marek Vasut wrote:
> > The MXC NAND driver doesn't consider the pinctrl data supplied via DT,
> > which will result in NAND pins not being properly configured.
> >
> > Make the driver use pinctrl, but to prevent breakage on various boards,
> > do not fail if the pinctrl data are not available, only print a warning
> > message.
>
> nack
>
> we will at bus level
Can you please elaborate? I don't understand what you're complaining about at
all, sorry.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: mxc_nand: Make use of supplied pinctrl data
Date: Tue, 8 Jan 2013 21:22:46 +0100 [thread overview]
Message-ID: <201301082122.46815.marex@denx.de> (raw)
In-Reply-To: <20130108195826.GD7360@game.jcrosoft.org>
Dear Jean-Christophe PLAGNIOL-VILLARD,
> On 15:28 Mon 07 Jan , Marek Vasut wrote:
> > The MXC NAND driver doesn't consider the pinctrl data supplied via DT,
> > which will result in NAND pins not being properly configured.
> >
> > Make the driver use pinctrl, but to prevent breakage on various boards,
> > do not fail if the pinctrl data are not available, only print a warning
> > message.
>
> nack
>
> we will at bus level
Can you please elaborate? I don't understand what you're complaining about at
all, sorry.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-01-08 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 14:28 [PATCH] mtd: mxc_nand: Make use of supplied pinctrl data Marek Vasut
2013-01-07 14:28 ` Marek Vasut
2013-01-07 17:13 ` Sascha Hauer
2013-01-07 17:13 ` Sascha Hauer
2013-01-08 19:58 ` Jean-Christophe PLAGNIOL-VILLARD
2013-01-08 19:58 ` Jean-Christophe PLAGNIOL-VILLARD
2013-01-08 20:22 ` Marek Vasut [this message]
2013-01-08 20:22 ` Marek Vasut
2013-01-09 6:41 ` Shawn Guo
2013-01-09 6:41 ` Shawn Guo
2013-01-09 9:08 ` Marek Vasut
2013-01-09 9:08 ` Marek Vasut
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=201301082122.46815.marex@denx.de \
--to=marex@denx.de \
--cc=LW@karo-electronics.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
--cc=s.hauer@pengutronix.de \
/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.