From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] Input: keyboard - add device tree bindings for simple key matrixes
Date: Tue, 13 Mar 2012 21:42:05 -0700 [thread overview]
Message-ID: <20120314044205.GA3964@core.coreip.homeip.net> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17761F11FF@HQMAIL01.nvidia.com>
On Tue, Jan 03, 2012 at 02:37:44PM -0800, Stephen Warren wrote:
> Olof Johansson wrote at Tuesday, January 03, 2012 2:37 PM:
> > This adds a simple device tree binding for simple key matrix data and
> > a helper to fill in the platform data.
> >
> > The implementation is in a shared file outside if drivers/input/keyboard
> > since some drivers in drivers/input/misc might be making use of it
> > as well.
> >
> > Changes since v3:
> > * Dropped compatible field in matrix-keymap.txt
> > * Dropped linux,fn-key
> > * Dropped linux,fn-keymap optional property but included guideline on
> > naming convention
> > * Now passing property name in to the helper function (or will assume
> > "linux,keymap" if passed NULL)
>
> > diff --git a/drivers/input/of_keymap.c b/drivers/input/of_keymap.c
>
> > +struct matrix_keymap_data *
> > +matrix_keyboard_of_fill_keymap(struct device_node *np, char *propname)
> > +{
> ...
> > + kd = kmalloc(sizeof(*kd), GFP_KERNEL);
> > + if (!kd)
> > + return NULL;
>
> Should that use kzalloc in case struct matrix_keymap_data grows some
> new fields that people will assume are set to zero since the struct
> would usually be in .data? Still, people should probably grep the code
> when making such changes...
>
> Otherwise,
>
> Acked-by: Stephen Warren <swarren@nvidia.com>
>
Applied, thanks everyone.
--
Dmitry
next prev parent reply other threads:[~2012-03-14 4:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 22:52 [PATCH] Input: keyboard - add device tree bindings for simple key matrixes Olof Johansson
2011-12-28 23:30 ` Rob Herring
2011-12-28 23:37 ` Olof Johansson
2011-12-29 6:16 ` Stephen Warren
2011-12-29 6:34 ` Olof Johansson
2011-12-29 7:01 ` Stephen Warren
2011-12-29 7:06 ` Olof Johansson
2011-12-29 19:28 ` Rob Herring
2012-01-02 4:11 ` Thomas Abraham
2012-01-02 7:21 ` Grant Likely
2012-01-03 17:44 ` Olof Johansson
2011-12-29 18:42 ` [PATCH v2] " Olof Johansson
2011-12-29 21:14 ` Rob Herring
2011-12-29 21:33 ` Olof Johansson
2011-12-29 22:05 ` Dmitry Torokhov
2011-12-29 22:26 ` Olof Johansson
2012-01-02 6:09 ` [PATCH v3] " Olof Johansson
2012-01-02 18:39 ` Simon Glass
2012-01-03 15:43 ` Olof Johansson
2012-01-03 16:22 ` Simon Glass
2012-01-03 16:29 ` Russell King - ARM Linux
2012-01-03 16:44 ` Dmitry Torokhov
2012-01-03 16:48 ` Olof Johansson
2012-01-03 17:06 ` Russell King - ARM Linux
2012-01-03 17:57 ` Dmitry Torokhov
2012-01-03 17:46 ` Stephen Warren
2012-01-03 21:37 ` [PATCH v4] " Olof Johansson
2012-01-03 22:37 ` Stephen Warren
2012-01-08 1:05 ` Simon Glass
2012-03-14 4:42 ` Dmitry Torokhov [this message]
2012-01-03 22:28 ` [PATCH] Input: tegra-kbc - add device tree support Olof Johansson
2012-01-03 22:42 ` Stephen Warren
2012-01-03 22:58 ` Olof Johansson
2012-01-03 23:21 ` Dmitry Torokhov
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=20120314044205.GA3964@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).