From: David Brownell <david-b@pacbell.net>
To: linux-omap@vger.kernel.org
Subject: [patch 2.6.28-rc5 0/5] twl4030 irq assignments
Date: Wed, 19 Nov 2008 17:09:28 -0800 [thread overview]
Message-ID: <200811191709.28974.david-b@pacbell.net> (raw)
The following patches remove some needless dependencies from
TWL4030 support, supporting non-OMAP builds and in some cases,
non-SDP (etc) builds.
- keypad driver ... use platform_get_irq(), no board dependencies
- BCI driver ... likewise
- MADC driver ... use platform_get_irq()
- power button ... still pretty hacky, there's no device here
- removes the now-dead symbols, and OMAP-dependency
Build-tested.
With this, I think the keypad driver becomes ready to go upstream,
after related twl4030-core updates. At least, it's ready for review.
(Including: Why pass the keypad module id to kpread/kpwrite, it's
the only one ever used? Why does Kconfig mention GPIOs, since they
aren't used?)
The point of these patches is that last one, which lets non-OMAP
folk do test builds and easily make updates when APIs change.
Yeah, it's a strange notion, but not everyone does OMAP builds. ;)
- Dave
next reply other threads:[~2008-11-20 1:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 1:09 David Brownell [this message]
2008-11-25 23:31 ` [patch 2.6.28-rc5 0/5] twl4030 irq assignments Tony Lindgren
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=200811191709.28974.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.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 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.