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 V3 3/3] pinctrl: palmas: add pincontrol driver
Date: Tue, 06 Aug 2013 12:54:53 -0600 [thread overview]
Message-ID: <5201467D.9020803@wwwdotorg.org> (raw)
In-Reply-To: <1375794755-6246-4-git-send-email-ldewangan@nvidia.com>
On 08/06/2013 07:12 AM, Laxman Dewangan wrote:
> TI Palmas series Power Management IC have multiple pins which can be
> configured for different functionality. This pins can be configured
> for different function. Also their properties like pull up/down,
> open drain enable/disable are configurable.
>
> Add support for pincontrol driver Palmas series device like TPS65913,
> TPS80036. The driver supports to be register from DT only.
I think this binding is reasonable enough, so that part,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-08-06 18:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 13:12 [PATCH V3 0/3] pinctrl: add pincontrol driver for palmas device Laxman Dewangan
2013-08-06 13:12 ` [PATCH V3 1/3] pinctrl: add utility functions for add map/configs Laxman Dewangan
2013-08-14 18:05 ` Linus Walleij
2013-08-06 13:12 ` [PATCH V3 2/3] pinctrl: pinconf-generic: add generic APIs for mapping pinctrl node Laxman Dewangan
2013-08-06 18:54 ` Stephen Warren
2013-08-14 18:09 ` Linus Walleij
2013-08-06 13:12 ` [PATCH V3 3/3] pinctrl: palmas: add pincontrol driver Laxman Dewangan
2013-08-06 18:54 ` Stephen Warren [this message]
2013-08-13 13:28 ` Laxman Dewangan
2013-08-14 18:16 ` Linus Walleij
2013-08-14 18:15 ` 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=5201467D.9020803@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;
as well as URLs for NNTP newsgroup(s).