From: Laxman Dewangan <ldewangan@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: <linus.walleij@linaro.org>, <mark.rutland@arm.com>,
<swarren@wwwdotorg.org>, <thierry.reding@gmail.com>,
<gnurou@gmail.com>, <yamada.masahiro@socionext.com>,
<jonathanh@nvidia.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 1/2] pinctrl: tegra: Add DT binding for io pads control
Date: Tue, 15 Nov 2016 17:15:04 +0530 [thread overview]
Message-ID: <582AF540.1070800@nvidia.com> (raw)
In-Reply-To: <20161114193432.wi5ljtp3t46wt2c7@rob-hp-laptop>
On Tuesday 15 November 2016 01:04 AM, Rob Herring wrote:
> On Wed, Nov 09, 2016 at 06:36:21PM +0530, Laxman Dewangan wrote:
> +
> + audio {
> + pins = "audio", "dmic", "sdmmc3";
> What's the purpose of grouping these?
Just to show that multiple IO pads can be provided here as this is from
pinctrl dt binding.
next prev parent reply other threads:[~2016-11-15 12:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 13:06 [PATCH V2 0/2] pinctrl: tegra: Add support for IO pad control Laxman Dewangan
2016-11-09 13:06 ` [PATCH V2 1/2] pinctrl: tegra: Add DT binding for io pads control Laxman Dewangan
2016-11-14 19:34 ` Rob Herring
2016-11-15 11:45 ` Laxman Dewangan [this message]
2016-11-15 18:48 ` Jon Hunter
2016-11-21 9:16 ` Laxman Dewangan
2016-11-09 13:06 ` [PATCH V2 2/2] pinctrl: tegra: Add driver to configure voltage and power of io pads Laxman Dewangan
2016-11-15 8:59 ` Linus Walleij
2016-11-15 15:07 ` Jon Hunter
2016-11-21 9:36 ` Laxman Dewangan
2016-11-21 11:08 ` Jon Hunter
2016-11-21 12:49 ` Laxman Dewangan
2016-11-21 20:37 ` Jon Hunter
2016-11-22 8:13 ` Laxman Dewangan
2016-11-21 6:04 ` kbuild test robot
2016-11-21 21:01 ` Jon Hunter
2016-11-22 8:15 ` Laxman Dewangan
2016-11-22 9:45 ` Joe Perches
2016-11-22 9:32 ` Laxman Dewangan
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=582AF540.1070800@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=yamada.masahiro@socionext.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).