From: swarren@nvidia.com (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] pinctrl: move the core per-device handlers to core
Date: Thu, 09 Feb 2012 20:58:23 -0800 [thread overview]
Message-ID: <4F34A3EF.3070207@nvidia.com> (raw)
In-Reply-To: <1328814050-22715-1-git-send-email-linus.walleij@linaro.org>
On 02/09/2012 11:00 AM, Linus Walleij wrote:
> After discussing with some people involved with pin control, we agreed
> that it will just cause trouble to have separate handles for pin muxing
> and pin configuration in callers - they will definately want to set all
> pin aspects regarding muxing and other configuration with one single
> call.
>
> These three patches take the first step in this transformation by moving
> the per-device handles over to core code, and renaming all related
> functions with the pinctrl_* prefix.
The series,
Acked-by: Stephen Warren <swarren@nvidia.com>
Note that this series will cause some compile breakage in the series I
previously posted to add a pinctrl-tegra driver and convert mach-tegra
to use it. The following patches in that series should still be OK:
pinctrl: add a driver for NVIDIA Tegra
ARM: tegra: Select PINCTRL Kconfig variables
... so you can still go ahead and apply those, but the following will be
broken:
ARM: tegra: Switch to new pinctrl driver
ARM: tegra: Remove pre-pinctrl pinmux driver
also the separately posted:
ARM: tegra: Add pinmux board file for Cardhu
I'll probably hold off reposting those last 3; with any luck they'll be
eclipsed by my implementing full DT binding support in the near future,
given our consensus on that topic following discussion at Linaro Connect.
--
nvpublic
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Olof Johansson <olof@lixom.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawn.guo@freescale.com>,
Thomas Abraham <thomas.abraham@linaro.org>,
Dong Aisheng <dong.aisheng@linaro.org>,
Rajendra Nayak <rajendra.nayak@linaro.org>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
Barry Song <21cnbao@gmail.com>, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 0/3] pinctrl: move the core per-device handlers to core
Date: Thu, 09 Feb 2012 20:58:23 -0800 [thread overview]
Message-ID: <4F34A3EF.3070207@nvidia.com> (raw)
In-Reply-To: <1328814050-22715-1-git-send-email-linus.walleij@linaro.org>
On 02/09/2012 11:00 AM, Linus Walleij wrote:
> After discussing with some people involved with pin control, we agreed
> that it will just cause trouble to have separate handles for pin muxing
> and pin configuration in callers - they will definately want to set all
> pin aspects regarding muxing and other configuration with one single
> call.
>
> These three patches take the first step in this transformation by moving
> the per-device handles over to core code, and renaming all related
> functions with the pinctrl_* prefix.
The series,
Acked-by: Stephen Warren <swarren@nvidia.com>
Note that this series will cause some compile breakage in the series I
previously posted to add a pinctrl-tegra driver and convert mach-tegra
to use it. The following patches in that series should still be OK:
pinctrl: add a driver for NVIDIA Tegra
ARM: tegra: Select PINCTRL Kconfig variables
... so you can still go ahead and apply those, but the following will be
broken:
ARM: tegra: Switch to new pinctrl driver
ARM: tegra: Remove pre-pinctrl pinmux driver
also the separately posted:
ARM: tegra: Add pinmux board file for Cardhu
I'll probably hold off reposting those last 3; with any luck they'll be
eclipsed by my implementing full DT binding support in the near future,
given our consensus on that topic following discussion at Linaro Connect.
--
nvpublic
next prev parent reply other threads:[~2012-02-10 4:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 19:00 [PATCH 0/3] pinctrl: move the core per-device handlers to core Linus Walleij
2012-02-09 19:00 ` Linus Walleij
2012-02-10 4:58 ` Stephen Warren [this message]
2012-02-10 4:58 ` Stephen Warren
2012-02-10 20:51 ` Linus Walleij
2012-02-10 20:51 ` Linus Walleij
2012-02-11 6:18 ` Stephen Warren
2012-02-11 6:18 ` Stephen Warren
2012-02-13 19:48 ` Linus Walleij
2012-02-13 19:48 ` Linus Walleij
2012-02-13 20:01 ` Stephen Warren
2012-02-13 20:01 ` Stephen Warren
2012-02-16 18:49 ` Linus Walleij
2012-02-16 18:49 ` Linus Walleij
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=4F34A3EF.3070207@nvidia.com \
--to=swarren@nvidia.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 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.