From: treding@nvidia.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM64: config: Enable MAX77620 pinctrl/gpio/rtc for Tegra210 P2180
Date: Thu, 16 Jun 2016 18:19:15 +0200 [thread overview]
Message-ID: <20160616161914.GD19360@ulmo.ba.sec> (raw)
In-Reply-To: <5762A648.2040704@nvidia.com>
On Thu, Jun 16, 2016 at 06:44:48PM +0530, Laxman Dewangan wrote:
> Hi Thierry,
>
> On Friday 10 June 2016 10:49 PM, Laxman Dewangan wrote:
> > NVIDIA's Tegra210 Jetson platform (P2180) uses the MAX77620 as PMIC.
> > Enable GPIO, Pincontrol and RTC driver for this device.
> >
> > Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> > ---
>
> Are you picking this change?
Can you please send this to linux-tegra at vger.kernel.org so that it can
properly be tracked?
Thanks,
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160616/60a46df6/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <treding@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: <will.deacon@arm.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] ARM64: config: Enable MAX77620 pinctrl/gpio/rtc for Tegra210 P2180
Date: Thu, 16 Jun 2016 18:19:15 +0200 [thread overview]
Message-ID: <20160616161914.GD19360@ulmo.ba.sec> (raw)
In-Reply-To: <5762A648.2040704@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
On Thu, Jun 16, 2016 at 06:44:48PM +0530, Laxman Dewangan wrote:
> Hi Thierry,
>
> On Friday 10 June 2016 10:49 PM, Laxman Dewangan wrote:
> > NVIDIA's Tegra210 Jetson platform (P2180) uses the MAX77620 as PMIC.
> > Enable GPIO, Pincontrol and RTC driver for this device.
> >
> > Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> > ---
>
> Are you picking this change?
Can you please send this to linux-tegra@vger.kernel.org so that it can
properly be tracked?
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-16 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 17:19 [PATCH V2] ARM64: config: Enable MAX77620 pinctrl/gpio/rtc for Tegra210 P2180 Laxman Dewangan
2016-06-10 17:19 ` Laxman Dewangan
2016-06-16 13:14 ` Laxman Dewangan
2016-06-16 13:14 ` Laxman Dewangan
2016-06-16 16:19 ` Thierry Reding [this message]
2016-06-16 16:19 ` Thierry Reding
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=20160616161914.GD19360@ulmo.ba.sec \
--to=treding@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.