From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: felipe.balbi@nokia.com
Cc: ext Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] omap-keypad fixes for OMAP2
Date: Thu, 2 Oct 2008 16:32:31 +0300 [thread overview]
Message-ID: <200810021632.31667.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <20081002130641.GG9133@gandalf.research.nokia.com>
On Thursday 02 October 2008 16:06:41 Felipe Balbi wrote:
> On Thu, Oct 02, 2008 at 04:01:17PM +0300, ext Peter Ujfalusi wrote:
> >
> > Hello,
> >
> > the diff between l-o and mainline are these commits regarding to omap-keypad.c:
> >
> > commit fdee8764947cde1e6933e7d981ce5b9de00e83e6
> > Author: Tony Lindgren <tony@atomide.com>
> > Merge current mainline tree into linux-omap tree
> >
> > commit ed39c59ff267249e7e789ea3bb64afc1e9afb5bd
> > Author: Russell King <rmk@dyn-67.arm.linux.org.uk>
> > omap: fix a load of "warning: symbol 'xxx' was not declared. Should it be static?"
> >
> > commit e85a9daa48453a4e7ffedf174b4358cdb444fbbb
> > Author: David Brownell <dbrownell@users.sourceforge.net>
> > some drivers switch away from OMAP-specific GPIO calls
> >
> > Should I take the relevant parts from these commits and send it to linux-input?
> >
> > Also there are other things broken in the omap-keypad driver.
> > One thing came to my mind is in the omap_kp_enable_store:
> > No matter what platform the code is running it tries to
> > enable/disable IRQ number 33 (IH2_BASE + 1), which is not a nice thing
> > to do...
>
> you can pass the irq number via a struct resource and use
> platform_get_irq() on driver probe and exit calls to handle the
> request_irq() and free_irq();
>
> Then you're sure the irq is correct as long as the struct resource as
> well initialized.
Yes, I know that, I just mentioned that other things are still broken in the omap-keypad driver.
In the OMAP1 board files the resource is filled in, but in the driver you can see this:
static ssize_t omap_kp_enable_store(struct device *dev, struct device_attribute *attr,
const char *buf, size_t count)
.
.
if (state != kp_enable) {
if (state)
enable_irq(INT_KEYBOARD);
else
disable_irq(INT_KEYBOARD);
kp_enable = state;
}
.
.
So, pretty much not a sane thing to do...
It is easy to fix, but that was not my point.
I'll make a patch to fix this one.
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-10-02 13:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 5:28 [PATCH 0/2] omap-keypad fixes for OMAP2 Peter Ujfalusi
2008-10-02 5:28 ` [PATCH 1/2] OMAP2: omap-keypad: interrupt disable fix Peter Ujfalusi
2008-10-02 5:28 ` [PATCH 2/2] OMAP2: omap-keypad: Enable more than 6 rows Peter Ujfalusi
2008-10-02 6:12 ` [PATCH 0/2] omap-keypad fixes for OMAP2 Tony Lindgren
2008-10-02 13:01 ` Peter Ujfalusi
2008-10-02 13:06 ` Felipe Balbi
2008-10-02 13:32 ` Peter Ujfalusi [this message]
2008-10-02 13:48 ` Felipe Balbi
2008-10-02 15:16 ` David Brownell
2008-10-02 15:17 ` David Brownell
2008-10-03 6:24 ` Tony Lindgren
2008-10-03 6:25 ` Tony Lindgren
2008-10-17 22:02 ` Tony Lindgren
2008-10-23 5:55 ` Peter Ujfalusi
2008-10-23 15:51 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2008-10-23 5:51 Peter Ujfalusi
2008-10-29 3:55 ` 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=200810021632.31667.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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.