From: Linus Walleij <linus.walleij@linaro.org>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>,
Stephen Warren <swarren@wwwdotorg.org>
Cc: "thierry.reding@gmail.com" <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-tegra@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Joseph Lo <josephl@nvidia.com>,
Suresh Mangipudi <smangipudi@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
vidyas@nvidia.com
Subject: Re: [PATCH 2/2] pinctrl: tegra: Add Tegra194 pinmux driver
Date: Fri, 26 Apr 2019 09:11:00 +0200 [thread overview]
Message-ID: <CACRpkdbnzB690mPncGGe2fKMBx3kDN+RPBEbowBsvsXO23gOGw@mail.gmail.com> (raw)
In-Reply-To: <1556247378-3335-2-git-send-email-kyarlagadda@nvidia.com>
On Fri, Apr 26, 2019 at 4:56 AM Krishna Yarlagadda
<kyarlagadda@nvidia.com> wrote:
> Tegra194 has PCIE L5 rst and clkreq pins which need to be controlled
> dynamically at runtime. This driver supports change pinmux for these
> pins. Pinmux for rest of the pins is set statically by bootloader and
> will not be changed by this driver
>
> Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
> Signed-off-by: Suresh Mangipudi <smangipudi@nvidia.com>
Paging Stephen Warren about this patch, an ACK from Thierry would
be nice too.
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-04-26 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 2:56 [PATCH 1/2] dt-binding: Tegra194 pinctrl support Krishna Yarlagadda
2019-04-26 2:56 ` [PATCH 2/2] pinctrl: tegra: Add Tegra194 pinmux driver Krishna Yarlagadda
2019-04-26 4:46 ` Vidya Sagar
2019-04-26 7:11 ` Linus Walleij [this message]
2019-04-26 13:16 ` Thierry Reding
2019-04-26 13:05 ` [PATCH 1/2] dt-binding: Tegra194 pinctrl support Thierry Reding
2019-04-26 13:07 ` Thierry Reding
2019-05-02 0:46 ` Rob Herring
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=CACRpkdbnzB690mPncGGe2fKMBx3kDN+RPBEbowBsvsXO23gOGw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=josephl@nvidia.com \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--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=swarren@wwwdotorg.org \
--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).