From: Thierry Reding <thierry.reding@gmail.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: swarren@wwwdotorg.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: tegra: Add DT entry for keys used in Jetson-TX1
Date: Tue, 1 Mar 2016 15:28:12 +0100 [thread overview]
Message-ID: <20160301142812.GB26201@ulmo> (raw)
In-Reply-To: <1456751211-14341-1-git-send-email-ldewangan@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
On Mon, Feb 29, 2016 at 06:36:50PM +0530, Laxman Dewangan wrote:
> Add DT entry for keys used in Jetson-TX p2371-2180. This has
> three keys, POWER, VOLUME-UP and VOLUME-DOWN.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra210-p2371-2180.dts | 25 ++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
I've applied this with a slightly modified commit message and moved the
gpio-keys node into the tegra210-p2597.dtsi file, because the GPIO keys
are part of the P2597 I/O board.
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-01 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 13:06 [PATCH 1/2] arm64: tegra: Add DT entry for keys used in Jetson-TX1 Laxman Dewangan
[not found] ` <1456751211-14341-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-02-29 13:06 ` [PATCH 2/2] arm64: tegra: Jetson-TX1: Add DT entry for system PMIC MAX77620 Laxman Dewangan
[not found] ` <1456751211-14341-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-06 10:51 ` kbuild test robot
2016-03-01 14:28 ` Thierry Reding [this message]
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=20160301142812.GB26201@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.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 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).