mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: <dmitry.torokhov@gmail.com>
Cc: <grant.likely@secretlab.ca>, <rob.herring@calxeda.com>,
	<swarren@nvidia.com>, <devicetree-discuss@lists.ozlabs.org>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-input@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH V2 0/4] input: keyboard: tegra: cleanups and DT supports
Date: Sat, 5 Jan 2013 13:15:06 +0530	[thread overview]
Message-ID: <1357371910-3164-1-git-send-email-ldewangan@nvidia.com> (raw)

This patch series:
 - fix build warning,
 - use devm_* for allocation,
 - make column/rows configuration through DT and 
 - remove the rarely used  key mapping table.

Changes from V1:
- renames the rows and pins property array.
- nit cleanups.

Laxman Dewangan (4):
  input: keyboard: tegra: fix build warning
  input: keyboard: tegra: use devm_* for resource allocation
  input: keyboard: tegra: add support for rows/cols configuration from
    dt
  input: keyboard: tegra: remove default key mapping

 .../bindings/input/nvidia,tegra20-kbc.txt          |   22 ++
 drivers/input/keyboard/tegra-kbc.c                 |  345 ++++++--------------
 2 files changed, 118 insertions(+), 249 deletions(-)


             reply	other threads:[~2013-01-05  7:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05  7:45 Laxman Dewangan [this message]
2013-01-05  7:45 ` [PATCH v2 1/4] input: keyboard: tegra: fix build warning Laxman Dewangan
2013-01-05  7:45 ` [PATCH v2 2/4] input: keyboard: tegra: use devm_* for resource allocation Laxman Dewangan
2013-01-05  8:06   ` Dmitry Torokhov
2013-01-05 11:20     ` Laxman Dewangan
2013-01-05 23:18       ` Dmitry Torokhov
2013-01-06 11:00         ` Laxman Dewangan
2013-01-06 19:27     ` Thierry Reding
2013-01-06 19:57       ` Dmitry Torokhov
2013-01-09  7:07         ` Thierry Reding
2013-01-09  9:19           ` Dmitry Torokhov
2013-01-09  9:23             ` Thierry Reding
2013-01-14 15:49               ` Thierry Reding
2013-01-14 16:16                 ` Greg Kroah-Hartman
2013-01-14 22:15                   ` Thierry Reding
2013-01-14 22:24                     ` Arnd Bergmann
2013-01-15  6:44                       ` Thierry Reding
2013-01-15 12:32                       ` Wolfram Sang
2013-01-15 13:06                 ` Wolfram Sang
2013-01-15 15:44                   ` Thierry Reding
2013-01-16  6:35                     ` Wolfram Sang
2013-02-09  9:04             ` Grant Likely
2013-01-05  7:45 ` [PATCH v2] input: keyboard: tegra: add support for rows/cols configuration from dt Laxman Dewangan
2013-01-05  7:45 ` [PATCH v2 4/4] input: keyboard: tegra: remove default key mapping Laxman Dewangan

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=1357371910-3164-1-git-send-email-ldewangan@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@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

all inboxes | Powered by JetHome®