From: Rob Herring <robh@kernel.org>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: linus.walleij@linaro.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
devicetree@vger.kernel.org, pdeschrijver@nvidia.com,
josephl@nvidia.com, smangipudi@nvidia.com, ldewangan@nvidia.com,
vidyas@nvidia.com
Subject: Re: [PATCH V3 1/4] dt-binding: Tegra194 pinctrl support
Date: Fri, 24 May 2019 15:19:08 -0500 [thread overview]
Message-ID: <20190524201908.GA13368@bogus> (raw)
In-Reply-To: <1558007594-14824-1-git-send-email-kyarlagadda@nvidia.com>
On Thu, May 16, 2019 at 05:23:11PM +0530, Krishna Yarlagadda wrote:
> Add binding doc for Tegra 194 pinctrl driver
>
> Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
> ---
> Changes in V3:
> remove optional fields not supported by pins published here
>
> .../bindings/pinctrl/nvidia,tegra194-pinmux.txt | 107 +++++++++++++++++++++
> 1 file changed, 107 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra194-pinmux.txt
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-05-24 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 11:53 [PATCH V3 1/4] dt-binding: Tegra194 pinctrl support Krishna Yarlagadda
2019-05-16 11:53 ` [PATCH V3 2/4] pinctrl: tegra: Support 32 bit register access Krishna Yarlagadda
2019-06-01 17:22 ` Linus Walleij
2019-05-16 11:53 ` [PATCH V3 3/4] pinctrl: tegra: Add Tegra194 pinmux driver Krishna Yarlagadda
2019-05-17 11:34 ` Vidya Sagar
2019-05-24 11:18 ` Linus Walleij
2019-06-01 17:24 ` Linus Walleij
2019-05-16 11:53 ` [PATCH V3 4/4] soc/tegra: select pinctrl for Tegra194 Krishna Yarlagadda
2019-06-01 17:26 ` Linus Walleij
2019-06-13 8:47 ` Thierry Reding
2019-05-17 11:33 ` [PATCH V3 1/4] dt-binding: Tegra194 pinctrl support Vidya Sagar
2019-05-24 20:19 ` Rob Herring [this message]
2019-06-01 17:21 ` 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=20190524201908.GA13368@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=josephl@nvidia.com \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@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=pdeschrijver@nvidia.com \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vidyas@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 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).