From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: linus.walleij@linaro.org, ian.campbell@citrix.com,
rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, rob@landley.net, sameo@linux.intel.com,
lee.jones@linaro.org, grant.likely@linaro.org,
broonie@kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
gg@slimlogic.co.uk, kishon@ti.com
Subject: Re: [PATCH V2 2/3] pinctrl: pinconf-generic: add generic APIs for mapping pinctrl node
Date: Mon, 05 Aug 2013 15:42:44 -0600 [thread overview]
Message-ID: <52001C54.7020908@wwwdotorg.org> (raw)
In-Reply-To: <1375688014-6117-3-git-send-email-ldewangan@nvidia.com>
On 08/05/2013 01:33 AM, Laxman Dewangan wrote:
> Add generic APIs to map the DT node and its sub node in pinconf generic
> driver. These APIs can be used from driver to parse the DT node who
> diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> index aeb3c99..52fb521 100644
> --- a/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> @@ -174,3 +174,19 @@ All parameters not listed here, do not take an argument.
>
> More in-depth documentation on these parameters can be found in
> <include/linux/pinctrl/pinconfig-generic.h>
> +
> +Generic pinconfig option also support the defining of pins and functions.
> +The properties are:
> +pinctrl-pins: This property tells the name of pins or list of pins for which
> + configuration is needed. The valid pin names are device/chip specific and
> + it can be found from the device/chip specific binding documents.
> +pinctrl-function: This property tells the configuration of the pins on to the
> + given function. The valid functions are device/chip specific and it can be
> + found from the device/chip specific binding documents.
This text feels like it's just been bolted on the end rather than
integrated into the existing description of generic pinconfig options.
Also, the existing text for generic pinconfig options doesn't feel at
all right to me. I'll send a patch to clean that up, and integrate these
new properties.
I would name the new properties just pins and functions, given their
scope is explicitly limited to pinctrl configuration nodes, so
"pinctrl-" is a little redundant.
With the properties renamed, and this patch rebased on top of the patch
I'll send out later, this patch,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-08-05 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 7:33 [PATCH V2 0/3] pinctrl: add pincontrol driver for palmas device Laxman Dewangan
2013-08-05 7:33 ` [PATCH V2 1/3] pinctrl: add utility functions for add map/configs Laxman Dewangan
2013-08-05 21:37 ` Stephen Warren
2013-08-06 12:25 ` Laxman Dewangan
2013-08-05 7:33 ` [PATCH V2 2/3] pinctrl: pinconf-generic: add generic APIs for mapping pinctrl node Laxman Dewangan
2013-08-05 21:42 ` Stephen Warren [this message]
2013-08-05 7:33 ` [PATCH V2 3/3] pinctrl: palmas: add pincontrol driver Laxman Dewangan
2013-08-05 7:44 ` Lee Jones
2013-08-05 22:04 ` Stephen Warren
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=52001C54.7020908@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=kishon@ti.com \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sameo@linux.intel.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