From: Shawn Guo <shawn.guo@linaro.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: Fabio Estevam <festevam@gmail.com>,
Steev Klimaszewski <steev@genesi-usa.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] efikamx: reintroduce Genesi Efika MX Smarttop via device tree
Date: Fri, 10 Aug 2012 09:41:22 +0800 [thread overview]
Message-ID: <20120810014119.GD19617@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <CAKGA1bkOo=En2P18FaBpq_KAZ88kisikXhNTabvnDknQ-EwFjA@mail.gmail.com>
On Thu, Aug 09, 2012 at 09:29:39AM -0500, Matt Sealey wrote:
> The reason the new kernel depends on the new U-Boot is we're trying to
> do all pinmux configuration in U-Boot (and we do in-house, and it
> works). No pinctrl stuff in the kernel or device tree is required at
> this point. The Old Kernel will remux a few things redundantly or
> change drive strengths or whatever or add hysteresis to the UART port
> which is not board-burning but is not really necessary, but it will
> work. The new kernel will just be able to do what it does out of the
> box, which is how it should be (hence why I object to adding pinctrl
> setup...)
>
Then I will have to refuse to accept your patch, because I'm working on
a series to remove pinctrl_provide_dummies() from imx51_dt_init().
--
Regards,
Shawn
next prev parent reply other threads:[~2012-08-10 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 21:46 Matt Sealey
2012-08-08 15:15 ` Shawn Guo
2012-08-08 16:55 ` Matt Sealey
2012-08-08 17:19 ` Fabio Estevam
2012-08-09 14:29 ` Matt Sealey
2012-08-10 1:41 ` Shawn Guo [this message]
2012-08-10 13:36 ` Matt Sealey
2012-08-10 14:04 ` Shawn Guo
2012-08-10 14:26 ` Matt Sealey
2012-08-10 14:40 ` Shawn Guo
2012-08-10 14:42 ` Matt Sealey
2012-08-09 10:19 ` Mark Brown
2012-08-09 13:40 ` Matt Sealey
2012-08-09 14:17 ` Mark Brown
2012-08-13 15:42 ` Matt Sealey
2012-08-13 17:38 ` Mark Brown
2012-08-13 22:05 ` Matt Sealey
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=20120810014119.GD19617@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@genesi-usa.com \
--cc=steev@genesi-usa.com \
/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
all inboxes | Powered by JetHome®