From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Hanumant Singh <hanumant@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Andersson <Bjorn.Andersson@sonymobile.com>,
"Bird, Tim" <Tim.Bird@sonymobile.com>,
ext Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] pinctrl: msm: Add support for MSM TLMM pinmux
Date: Mon, 29 Jul 2013 11:32:49 -0600 [thread overview]
Message-ID: <51F6A741.6070300@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdZLFD-KAvZdUUvQKje3vAH1D0EJMW9PSK8VSp3Xs4eiGA@mail.gmail.com>
On 07/29/2013 10:37 AM, Linus Walleij wrote:
> On Wed, Jul 24, 2013 at 11:41 PM, Hanumant Singh
> <hanumant@codeaurora.org> wrote:
>
>> Add a new device tree enabled pinctrl driver for
>> Qualcomm MSM SoC's. This driver provides an extensible
>> framework to interface all MSM's that use a TLMM pinmux,
>> with the pinctrl subsytem.
>>
>> This driver is split into two parts: the pinctrl interface
>> and the TLMM version specific implementation. The pinctrl
>> interface parses the device tree and registers with the pinctrl
>> subsytem. The TLMM version specific implementation supports
>> pin configuration/register programming for the different
>> pin types present on a given TLMM pinmux version.
>>
>> Add support only for TLMM version 3 pinmux right now,
>> as well as, only two of the different pin types present on the
>> TLMM v3 pinmux.
>> Pintype 1: General purpose pins.
>> Pintype 2: SDC pins.
>
> I guess this is the v4 patch set?
>
> Please include a small changelog so I can keep track of
> things...
>
>
>> Change-Id: I065d874cd2c6fd002d5b3cb4b355445bb6912bf4
>
> This thing is not interesting to the kernel community.
>
>> diff --git a/Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt
>> new file mode 100644
>> index 0000000..0f17a94
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt
>
> This needs to be broken out and sent for separate review on
> the devicetree@vger.kernel.org mailing list.
It certainly should be reviewed there, although I don't think the
binding .txt file needs to be a separate patch. At present, it's quite
typical to include the binding doc with the first driver that implements
it, although that may change in the future; we'll see.
next prev parent reply other threads:[~2013-07-29 17:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 21:41 [PATCH] pinctrl: msm: Add support for MSM TLMM pinmux Hanumant Singh
2013-07-29 16:37 ` Linus Walleij
2013-07-29 17:32 ` Stephen Warren [this message]
2013-07-30 21:10 ` hanumant
2013-07-30 21:22 ` Stephen Warren
2013-07-31 0:01 ` Hanumant Singh
2013-07-31 0:08 ` Stephen Warren
2013-07-31 0:13 ` Hanumant Singh
2013-07-31 3:59 ` Stephen Warren
2013-07-31 19:46 ` Hanumant Singh
2013-07-31 21:06 ` Stephen Warren
2013-08-01 0:17 ` Hanumant Singh
2013-08-06 23:45 ` Hanumant Singh
2013-08-07 16:00 ` Stephen Warren
2013-08-14 19:16 ` Linus Walleij
2013-07-29 23:39 ` Bjorn Andersson
2013-08-07 18:07 ` Hanumant Singh
2013-08-14 19:29 ` Linus Walleij
2013-08-15 17:44 ` Hanumant Singh
2013-08-15 20:47 ` Linus Walleij
2013-08-15 21:28 ` Hanumant Singh
2013-08-28 8:32 ` Linus Walleij
2013-08-15 21:50 ` Josh Cartwright
2013-08-15 21:58 ` Hanumant Singh
2013-08-15 23:10 ` Josh Cartwright
2013-08-15 23:14 ` Hanumant Singh
-- strict thread matches above, loose matches on Subject: below --
2013-06-21 21:52 Hanumant Singh
2013-06-24 12:18 ` Linus Walleij
2013-06-25 17:41 ` hanumant
2013-06-27 8:26 ` Linus Walleij
2013-06-27 15:17 ` hanumant
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=51F6A741.6070300@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=Tim.Bird@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=hanumant@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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