From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Pawel Moll <Pawel.Moll@arm.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Ian Campbell <ian.campbell@citrix.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH 2/2] pinctrl: add generic pins and functions properties
Date: Tue, 06 Aug 2013 11:01:19 -0600 [thread overview]
Message-ID: <52012BDF.70401@wwwdotorg.org> (raw)
In-Reply-To: <20130806084131.GB23111@e106331-lin.cambridge.arm.com>
On 08/06/2013 02:41 AM, Mark Rutland wrote:
> On Mon, Aug 05, 2013 at 10:56:00PM +0100, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> pinctrl bindings can benefit from generic property names that define
>> which pins a "pin configuration node" affects, and which mux function
>> to select onto those pins. Document new properties for this purpose so
>> that other bindings may refer to them.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>> Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
>> index 31b0cb9..237823a 100644
>> --- a/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
>> +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
>> @@ -138,6 +138,9 @@ structure of the DT nodes that contain these properties.
>>
>> Supported generic properties are:
>>
>> +pins - the list of pins that properties in the node
>> + apply to
>> +function - the mux function to select
>
> I assume the type of these properties must be described in the more
> specific binding?
Yes, I think so. I guess I should also add entries into the section
right below this list which describes the values for each of the
properties that has values.
next prev parent reply other threads:[~2013-08-06 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 21:55 [PATCH 1/2] pinctrl: clean up pinconfig-generic documentation Stephen Warren
2013-08-05 21:56 ` [PATCH 2/2] pinctrl: add generic pins and functions properties Stephen Warren
2013-08-06 8:41 ` Mark Rutland
2013-08-06 17:01 ` Stephen Warren [this message]
2013-08-07 19:32 ` [PATCH 1/2] pinctrl: clean up pinconfig-generic documentation Linus Walleij
2013-08-07 19:41 ` Stephen Warren
2013-08-07 19:54 ` 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=52012BDF.70401@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.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 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.