From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: tegra: dalmore: populate key mapping
Date: Mon, 13 May 2013 13:29:02 -0600 [thread overview]
Message-ID: <51913EFE.6030103@wwwdotorg.org> (raw)
In-Reply-To: <1365594454-20614-1-git-send-email-ldewangan@nvidia.com>
On 04/10/2013 05:47 AM, Laxman Dewangan wrote:
> Keys on Dalmore interfaced through Tegra KBC controller
> in key matrix topology.
>
> Add the key mapping for the keys.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> The system is booted on Dalmore SKU1000 with the fastboot.
I don't intend applying these two patches.
For Dalmore, there are two SKUs, one using KBC and one using GPIOs for
the buttons/keys. The SKU that uses GPIOs is far more common, so we've
decided to support that one upstream.
We aren't actively pursuing Pluto support upstream; it's likely that
I'll send a patch to remove tegra114-pluto.dts in the near future.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: tegra: dalmore: populate key mapping
Date: Mon, 13 May 2013 13:29:02 -0600 [thread overview]
Message-ID: <51913EFE.6030103@wwwdotorg.org> (raw)
In-Reply-To: <1365594454-20614-1-git-send-email-ldewangan@nvidia.com>
On 04/10/2013 05:47 AM, Laxman Dewangan wrote:
> Keys on Dalmore interfaced through Tegra KBC controller
> in key matrix topology.
>
> Add the key mapping for the keys.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> The system is booted on Dalmore SKU1000 with the fastboot.
I don't intend applying these two patches.
For Dalmore, there are two SKUs, one using KBC and one using GPIOs for
the buttons/keys. The SKU that uses GPIOs is far more common, so we've
decided to support that one upstream.
We aren't actively pursuing Pluto support upstream; it's likely that
I'll send a patch to remove tegra114-pluto.dts in the near future.
next prev parent reply other threads:[~2013-05-13 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 11:47 [PATCH 1/2] ARM: tegra: dalmore: populate key mapping Laxman Dewangan
2013-04-10 11:47 ` Laxman Dewangan
2013-04-10 11:47 ` Laxman Dewangan
[not found] ` <1365594454-20614-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-04-10 11:47 ` [PATCH 2/2] ARM: tegra: pluto: " Laxman Dewangan
2013-04-10 11:47 ` Laxman Dewangan
2013-04-10 11:47 ` Laxman Dewangan
2013-05-13 19:29 ` Stephen Warren [this message]
2013-05-13 19:29 ` [PATCH 1/2] ARM: tegra: dalmore: " Stephen Warren
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=51913EFE.6030103@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.