From: "Luke-Jr" <luke@dashjr.org>
To: felipe.balbi@nokia.com
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Solution: N810 keyboard regression
Date: Sat, 6 Jun 2009 18:15:35 -0500 [thread overview]
Message-ID: <200906061815.48026.luke@dashjr.org> (raw)
In-Reply-To: <20090606224204.GA16764@nokia.com>
On Saturday 06 June 2009 05:42:04 pm Felipe Balbi wrote:
> Are you sure that was the commit that changed it ?
> that commit is only getting rid of the debug() macro and making use of
> dev_vdbg().
Oops, looks like I put the wrong commit at fault. The correct one is:
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-
omap-2.6.git;a=commit;h=bb739803dce613ed58e8b35ae52af439ab7496bf
> If you had just followed git blame you'd see that was already the
> default value on n810's lm8323 platform_data since the initial import of
> that code into linux-omap.
According to the removed code in the above commit, the default value (outside
of and not specified in n810's lm8323 platform_data) was 12.
> I do recall testing my patches on n810 before sending them upstream and
> they were working. How are you testing this ? which tree are you using ?
I am testing the latest Linux-OMAP kernel on my N810 with Nokia's flasher and
--load --boot options. (Userspace is Gentoo)
> did you try changing that keysize calculation ?
No, I wanted to get the opinion of someone who knows how that code actually is
supposed to work before I try randomly changing things I don't understand.
> Do you see irqs comming? Any debugging messages ?
There were no debugging messages when the broken keys were pressed, nor did a
dbg I added to the driver get triggered for them.
Luke
next prev parent reply other threads:[~2009-06-06 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 21:51 Solution: N810 keyboard regression Luke-Jr
2009-06-06 22:42 ` Felipe Balbi
2009-06-06 23:15 ` Luke-Jr [this message]
2009-06-08 9:01 ` Felipe Balbi
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=200906061815.48026.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=felipe.balbi@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox