Re: [PATCH v3 0/4] toshiba_acpi: Expanded hotkey support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On Mon, Mar 05, 2012 at 04:55:46PM -0800, Randy Dunlap wrote:
> On 03/05/2012 03:34 PM, Seth Forshee wrote:
> > On Mon, Mar 05, 2012 at 03:01:15PM -0800, Randy Dunlap wrote:
> >> On 03/05/2012 02:04 PM, Seth Forshee wrote:
> >>
> >>> On Mon, Feb 06, 2012 at 03:15:48PM +0000, Matthew Garrett wrote:
> >>>> On Mon, Feb 06, 2012 at 09:06:58AM -0600, Seth Forshee wrote:
> >>>>
> >>>>> Matthew: Just wondering if there are more issues that need to be
> >>>>> addressed with this round of patches, or if they're looking okay at this
> >>>>> point.
> >>>>
> >>>> I'm fine with them at this point, just waiting on Len to give feedback 
> >>>> on the ACPI patch.
> >>>
> >>> Well, I've been trying to get some comment on the ACPI patch, to no
> >>> avail. Unless there's some other option, I guess I'll just resend the
> >>> patches using an alternative method for getting the EC handle.
> >>
> >>
> >> I did test this patch series on 3.3-rc5 to see if it would
> >> help with the touchpad on/off key on my Toshiba Portege.
> >>
> >> The patch series didn't have any ill effects, nor did it help
> >> with the touchpad on/off key.  :(
> > 
> > Is it only that hotkey that doesn't work, or do the others fail to work
> > as well?
> I haven't tried any others.  Which ones do you suggest that I test?

Without knowing what buttons you have I'll just throw out some
suggestions. Wifi, sleep/hibernate, battery status, brightness up/down,
and various zoom buttons are some of the ones that I see on the NB505.

> > If it's only that key that doesn't work, I'd suggest using input-events
> > to determine exactly which device the other hotkey events are coming
> > from (it might be more than one) and to verify there really isn't any
> > event coming out for that key. If there's no event at all for the key,
> > check dmesg and see if any messages are printed there when you press the
> > touchpad key.
> I don't know about "input-events".  Where do I find it & info on it?

On Debian/Ubuntu it's in the input-utils package, I don't know about
other distros. Source is at

Basic instructions are to use lsinput to identify the device you want to
test, then pass the event device number as the argument to input-utils,
which will dump the raw events that come out for only that device. Your
hotkeys should come out of either the device named "Toshiba input
device" or "AT Translated Set 2 Keyboard", or some on both.

> I already tried using 'showkey' and it didn't see any keypress for the
> touchpad key.

Have you tried it with the -s argument to see if a scancode is produced?
Both the Toshiba and AT keyboard input devices should leave a message in
dmesg though if they see an unknown scancode though.


To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [XFree86]

Add to Google Powered by Linux