From: Felipe Balbi <felipe.balbi@nokia.com>
To: "ext Arce, Abraham" <x0066660@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP4 keypad driver
Date: Thu, 8 Apr 2010 07:42:23 +0300 [thread overview]
Message-ID: <20100408044223.GB6228@nokia.com> (raw)
In-Reply-To: <27F9C60D11D683428E133F85D2BB4A53043CB21399@dlee03.ent.ti.com>
On Thu, Apr 08, 2010 at 03:16:08AM +0200, ext Arce, Abraham wrote:
>Hi,
>
>I need some help to figure out the best way to incorporate omap4 keypad in linux omap.
>
>First approach, I have a patch that creates a new file, omap4-keypad.c with the following implementations:
>
> - Based on matrix keypac logic
> - Using hwmod framework
> - Using threaded irq
>
>Second approach, to change existing omap-keypad.c to matrix keypad
>
>Not clear on the path to follow... Thanks for your comments.
isn't that part of the twl6030 pmic ? If so you need a better name for
it, something like twl6030-keypad.c
In that case I don't know why do you care about hwmod, but I would need
to see the patch anyways.
Well, if you need example code, look at
drivers/input/keyboard/twl4030_keypad.c
The driver should be sent to linux-input@vger.kernel.org and
linux-omap@vger.kernel.org. Be sure that it patches
scripts/checkpatch.pl --strict and that you're not adding any sparse
warnings. Double check Documentation/CodingStyle,
Documentation/SubmittingPatches, Documentation/SubmittingDrivers and
Documentation/SubmitChecklist.
Be sure that the new driver, comes on one patch of its own and the
arch/arm/*omap* changes should come in a separate patch and a third one
for defconfig changes.
The rest we can sort out when you send the patch.
--
balbi
next prev parent reply other threads:[~2010-04-08 4:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 1:16 OMAP4 keypad driver Arce, Abraham
2010-04-08 4:42 ` Felipe Balbi [this message]
2010-04-08 5:43 ` Shilimkar, Santosh
2010-04-08 5:50 ` Felipe Balbi
2010-04-08 5:56 ` Shilimkar, Santosh
2010-04-08 15:21 ` Kevin Hilman
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=20100408044223.GB6228@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=x0066660@ti.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 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.