devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Dong Aisheng <b29396@freescale.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Shawn Guo <shawn.guo@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org,
	linus.walleij@stericsson.com, swarren@wwwdotorg.org,
	kernel@pengutronix.de, grant.likely@secretlab.ca,
	rob.herring@calxeda.com
Subject: Re: [PATCH v2 1/3] pinctrl: pinctrl-imx: add imx pinctrl core driver
Date: Tue, 24 Apr 2012 11:02:23 +0200	[thread overview]
Message-ID: <CACRpkdah8Mr2riXGJXZ2VEYXdORyLznPYG0s-O05vYiGYjQcdw@mail.gmail.com> (raw)
In-Reply-To: <1334933916-12971-1-git-send-email-b29396@freescale.com>

On Fri, Apr 20, 2012 at 4:58 PM, Dong Aisheng <b29396@freescale.com> wrote:

> From: Dong Aisheng <dong.aisheng@linaro.org>
>
> The driver has mux and config support while the gpio is still
> not supported.
> For select input setting, the driver will handle it internally
> and do not need user to take care of it.
>
> The pinctrl-imx core driver will parse the dts file and dynamically
> create the pinmux functions and groups.
>
> Each IMX SoC pinctrl driver should register pins with a pin register map
> including mux register and config register and select input map to core
> for proper operations.
>
> Signed-off-by: Dong Aisheng <dong.aisheng@linaro.org>

I'm pretty happy with this driver and would love to merge it.

However it'd be nice to have someone else ACK it first.
Someone like Sascha or Shawn would work fine :D

Yours,
Linus Walleij

  parent reply	other threads:[~2012-04-24  9:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20 14:58 [PATCH v2 1/3] pinctrl: pinctrl-imx: add imx pinctrl core driver Dong Aisheng
2012-04-20 14:58 ` [PATCH v2 2/3] pinctrl: pinctrl-imx: add imx6q pinctrl driver Dong Aisheng
2012-04-20 14:58 ` [PATCH v2 3/3] ARM: imx6q: switch to use " Dong Aisheng
2012-04-24  8:56   ` Linus Walleij
2012-04-24  9:08     ` Wolfram Sang
2012-04-24  9:43       ` Dong Aisheng
     [not found]     ` <CACRpkdbbdkhN-hVF6vP4j6bP-Nsdft5UjjpAVhcKn6KSpEbcuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-24  9:15       ` Dong Aisheng
2012-04-24  9:51   ` Richard Zhao
     [not found]     ` <20120424095116.GA28063-iWYTGMXpHj9ITqJhDdzsOjpauB2SiJktrE5yTffgRl4@public.gmane.org>
2012-04-24 10:36       ` Dong Aisheng
2012-04-24 12:46   ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-24 14:04     ` Dong Aisheng
2012-04-24 14:48       ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-24  9:02 ` Linus Walleij [this message]
     [not found] ` <1334933916-12971-1-git-send-email-b29396-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-04-25  7:04   ` [PATCH v2 1/3] pinctrl: pinctrl-imx: add imx pinctrl core driver Richard Zhao
2012-04-25 12:10 ` Dong Aisheng

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=CACRpkdah8Mr2riXGJXZ2VEYXdORyLznPYG0s-O05vYiGYjQcdw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=b29396@freescale.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawn.guo@linaro.org \
    --cc=swarren@wwwdotorg.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).