From: Roland Stigge <stigge@antcom.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: axel.lin@gmail.com, riyer@nvidia.com,
michael.hennerich@analog.com, grant.likely@secretlab.ca,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kevin.wells@nxp.com,
srinivas.bakki@nxp.com, devicetree-discuss@lists.ozlabs.org,
rob.herring@calxeda.com
Subject: Re: [PATCH RESEND v3 1/2] input: keyboard: Add keys driver for the LPC32xx SoC
Date: Fri, 18 May 2012 11:12:18 +0200 [thread overview]
Message-ID: <4FB61272.5080700@antcom.de> (raw)
In-Reply-To: <20120517173814.GA26948@core.coreip.homeip.net>
Hi Dmitry!
thanks for your suggestions, will include them into the next patch update.
On 05/17/2012 07:38 PM, Dmitry Torokhov wrote:
>> + of_property_read_u32(np, "keypad,num-rows", &rows);
>> + of_property_read_u32(np, "keypad,num-columns", &columns);
>> + if (!rows || rows != columns) {
>> + dev_err(dev, "rows and columns must be specified and be equal!\n");
>
> Why?
The LPC32xx key scanner hardware is always configured with a square
matrix (rows == columns). So I had the choice to force "keypad,num-rows"
== "keypad,num-columns" (as done currently) to show potential error to
the DTS/DTB provider, or ignore problems here and use
max("keypad,num-rows", "keypad,num-columns") for actual hardware setup.
(You can and will leave out unconnected keys in the keymap anyway.)
So do you think we should change my current approach here?
Thanks in advance,
Roland
next prev parent reply other threads:[~2012-05-18 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 20:25 [PATCH RESEND v3 1/2] input: keyboard: Add keys driver for the LPC32xx SoC Roland Stigge
2012-05-16 20:25 ` [PATCH RESEND v3 2/2] ARM: LPC32xx: Make platform use key driver Roland Stigge
2012-05-17 23:32 ` Rob Herring
2012-05-17 17:38 ` [PATCH RESEND v3 1/2] input: keyboard: Add keys driver for the LPC32xx SoC Dmitry Torokhov
2012-05-18 9:12 ` Roland Stigge [this message]
2012-05-17 23:31 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2012-05-05 12:00 Roland Stigge
2012-05-05 12:00 ` Roland Stigge
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=4FB61272.5080700@antcom.de \
--to=stigge@antcom.de \
--cc=axel.lin@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=kevin.wells@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=riyer@nvidia.com \
--cc=rob.herring@calxeda.com \
--cc=srinivas.bakki@nxp.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).