linux-stable.git/drivers/platform, branch v4.1.41

platform/x86: acer-wmi: setup accelerometer when machine has appropriate notify event

2017-06-13T13:29:16+00:00

[ Upstream commit 98d610c3739ac354319a6590b915f4624d9151e6 ]

The accelerometer event relies on the ACERWMID_EVENT_GUID notify.
So, this patch changes the codes to setup accelerometer input device
when detected ACERWMID_EVENT_GUID. It avoids that the accel input
device created on every Acer machines.

In addition, patch adds a clearly parsing logic of accelerometer hid
to acer_wmi_get_handle_cb callback function. It is positive matching
the "SENR" name with "BST0001" device to avoid non-supported hardware.

Reported-by: Bjørn Mork 
Cc: Darren Hart 
Signed-off-by: Lee, Chun-Yi 
[andy: slightly massage commit message]
Signed-off-by: Andy Shevchenko 

Signed-off-by: Sasha Levin

goldfish: Sanitize the broken interrupt handler

2017-05-17T19:06:59+00:00

[ Upstream commit 6cf18e6927c0b224f972e3042fb85770d63cb9f8 ]

This interrupt handler is broken in several ways:

  - It loops forever when the op code is not decodeable

  - It never returns IRQ_HANDLED because the only way to exit the loop
    returns IRQ_NONE unconditionally.

The whole concept of this is broken. Creating devices in an interrupt
handler is beyond any point of sanity.

Make it at least behave halfways sane so accidental users do not have to
deal with a hard to debug lockup.

Fixes: e809c22b8fb028 ("goldfish: add the goldfish virtual bus")
Reported-by: Gabriel C 
Signed-off-by: Thomas Gleixner 
Acked-by: Linus Torvalds 
Cc: stable@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Sasha Levin

hp-wmi: Fix wifi cannot be hard-unblocked

2016-08-16T12:25:07+00:00

[ Upstream commit fc8a601e1175ae351f662506030f9939cb7fdbfe ]

Several users reported wifi cannot be unblocked as discussed in [1].
This patch removes the use of the 2009 flag by BIOS but uses the actual
WMI function calls - it will be skipped if WMI reports unsupported.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=69131

Signed-off-by: Alex Hung 
Tested-by: Evgenii Shatokhin 
Cc: stable@vger.kernel.org
Signed-off-by: Darren Hart 
Signed-off-by: Sasha Levin

ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

2016-04-18T12:51:08+00:00

[ Upstream commit 4db9675d927a71faa66e5ab128d2390d6329750b ]

Some Lenovo ideapad models lack a physical rfkill switch.
On Lenovo models ideapad Y700 Touch-15ISK and ideapad Y700-15ISK,
ideapad-laptop would wrongly report all radios as blocked by
hardware which caused wireless network connections to fail.

Add these models without an rfkill switch to the no_hw_rfkill list.

Signed-off-by: John Dahlstrom 
Cc:  # 3.17.x-: 4fa9dab: ideapad_laptop: Lenovo G50-30 fix rfkill reports wireless blocked
Cc: 
Signed-off-by: Darren Hart 
Signed-off-by: Sasha Levin

intel_scu_ipcutil: underflow in scu_reg_access()

2016-02-28T05:04:23+00:00

[ Upstream commit b1d353ad3d5835b16724653b33c05124e1b5acf1 ]

"count" is controlled by the user and it can be negative.  Let's prevent
that by making it unsigned.  You have to have CAP_SYS_RAWIO to call this
function so the bug is not as serious as it could be.

Fixes: 5369c02d951a ('intel_scu_ipc: Utility driver for intel scu ipc')
Signed-off-by: Dan Carpenter 
Cc: stable@vger.kernel.org
Signed-off-by: Darren Hart 
Signed-off-by: Sasha Levin

ideapad-laptop: Add Lenovo Yoga 700 to no_hw_rfkill dmi list

2016-02-15T20:45:19+00:00

[ Upstream commit 6b31de3e698582fe0b8f7f4bab15831b73204800 ]

Like the Yoga 900 models the Lenovo Yoga 700 does not have a
hw rfkill switch, and trying to read the hw rfkill switch through the
ideapad module causes it to always reported blocking breaking wifi.

This commit adds the Lenovo Yoga 700 to the no_hw_rfkill dmi list, fixing
the wifi breakage.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1295272
Tested-by: 
Cc: stable@vger.kernel.org
Signed-off-by: Josh Boyer 
Signed-off-by: Darren Hart 
Signed-off-by: Sasha Levin

ideapad-laptop: Add Lenovo Yoga 900 to no_hw_rfkill dmi list

2016-02-15T20:45:19+00:00

[ Upstream commit f71c882dd4cfe4aa88ea07b1402ddd43605d4aef ]

Like some of the other Yoga models the Lenovo Yoga 900 does not have a
hw rfkill switch, and trying to read the hw rfkill switch through the
ideapad module causes it to always reported blocking breaking wifi.

This commit adds the Lenovo Yoga 900 to the no_hw_rfkill dmi list, fixing
the wifi breakage.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1275490
Cc: stable@vger.kernel.org
Reported-and-tested-by: Kevin Fenzi 
Signed-off-by: Hans de Goede 
Signed-off-by: Darren Hart 
Signed-off-by: Sasha Levin

ideapad-laptop: Add Lenovo ideapad Y700-17ISK to no_hw_rfkill dmi list

2016-02-03T21:23:20+00:00

[ Upstream commit edde316acb5f07c04abf09a92f59db5d2efd14e2 ]

One of the newest ideapad models also lacks a physical hw rfkill switch,
and trying to read the hw rfkill switch through the ideapad module
causes it to always reported blocking breaking wifi.

Fix it by adding this model to the DMI list.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1286293
Cc: stable@vger.kernel.org
Signed-off-by: Josh Boyer 
Signed-off-by: Darren Hart 
Signed-off-by: Sasha Levin

toshiba_acpi: Initialize hotkey_event_type variable

2016-01-23T04:54:09+00:00

commit d2f20619942fe4618160a7fa3dbdcbac335cff59 upstream.

Commit 53147b6cabee5e8d1997b5682fcc0c3b72ddf9c2 ("toshiba_acpi: Fix
hotkeys registration on some toshiba models") fixed an issue on some
laptops regarding hotkeys registration, however, if failed to address
the initialization of the hotkey_event_type variable, and thus, it can
lead to potential unwanted effects as the variable is being checked.

This patch initializes such variable to avoid such unwanted effects.

Signed-off-by: Azael Avalos 
Signed-off-by: Darren Hart 
Signed-off-by: Greg Kroah-Hartman

toshiba_acpi: Fix hotkeys registration on some toshiba models

2015-10-22T21:43:11+00:00

commit 53147b6cabee5e8d1997b5682fcc0c3b72ddf9c2 upstream.

Commit a2b3471b5b13 ("toshiba_acpi: Use the Hotkey Event Type function
for keymap choosing") changed the *setup_keyboard function to query for
the Hotkey Event Type to help choose the correct keymap, but turns out
that here are certain Toshiba models out there not implementing this
feature, and thus, failing to continue the input device registration and
leaving such laptops without hotkey support.

This patch changes such check, and instead of returning an error if
the Hotkey Event Type is not present, we simply inform userspace about it,
changing the message printed from err to notice, making the function
responsible for registering the input device to continue.

This issue was found on a Toshiba Portege Z30-B, but there might be
some other models out there affected by this regression as well.

Signed-off-by: Azael Avalos 
Signed-off-by: Darren Hart 
Signed-off-by: Greg Kroah-Hartman