[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKdam541af1bU8_64gTZva9VS0R3dTR=3L3J50o9HgHH+WaPYQ@mail.gmail.com>
Date: Mon, 23 Apr 2012 21:10:45 +0530
From: "Poddar, Sourav" <sourav.poddar@...com>
To: Stephen Warren <swarren@...dotorg.org>
Cc: devicetree-discuss@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-input@...r.kernel.org, Benoit Cousson <b-cousson@...com>,
Rob Herring <rob.herring@...xeda.com>,
Grant Likely <grant.likely@...retlab.ca>,
Felipe Balbi <balbi@...com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCHv3 1/2] drivers: input: keypad: Add device tree support
Hi Stephen,
On Mon, Apr 23, 2012 at 8:56 PM, Stephen Warren <swarren@...dotorg.org> wrote:
> On 04/23/2012 09:27 AM, Sourav Poddar wrote:
>> Update the Documentation with omap4 keypad device tree
>> binding information.
>> Add device tree support for omap4 keypad driver.
>
> Shouldn't this use the already-defined matrix keyboard bindings at
> Documentation/devicetree/bindings/input/matrix-keymap.txt?
>
True, that is one way of describing the linux-keymap, but i think it can be
done either ways.
Are you hinting at getting rid of Documentation for each seperate modules and
just use a single Documentation/devicetree/bindings/input/matrix-keymap.txt?
> (I asked this before, but don't recall seeing any response explaining
> why a new binding was needed. Sorry if I missed it.)
Sorry, It was I who missed it.
~Sourav
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists