X86 platform drivers
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: stable@vger.kernel.org
Cc: Ike Panhc <ike.pan@canonical.com>, joeyli <jlee@suse.com>,
	Carlos Corbacho <carlos@strangeworlds.co.uk>,
	mjg@redhat.com, platform-driver-x86@vger.kernel.org,
	Dmitry Torokhov <dtor@mail.ru>,
	Corentin Chary <corentincj@iksaif.net>,
	Thomas Renninger <trenn@suse.de>, Andrey <andrey.k.p@gmail.com>
Subject: [PATCH 3.0.y] acer-wmi: No wifi rfkill on Lenovo machines
Date: Wed, 14 Mar 2012 16:53:27 -0500	[thread overview]
Message-ID: <20120314215327.GA1510@burratino> (raw)
In-Reply-To: <1328258799-19665-1-git-send-email-ike.pan@canonical.com>

Hi Greg,

Please consider applying 461e74377cfc (acer-wmi: No wifi rfkill on
Lenovo machines, 2012-02-03) to the 3.2.y and 3.0.y trees.

Ike Panhc wrote:

> We have several reports which says acer-wmi is loaded on ideapads
> and register rfkill for wifi which can not be unblocked.
>
> Since ideapad-laptop also register rfkill for wifi and it works
> reliably, it will be fine acer-wmi is not going to register rfkill
> for wifi once VPC2004 is found.
>
> Also put IBM0068/LEN0068 in the list. Though thinkpad_acpi has no
> wifi rfkill capability, there are reports which says acer-wmi also
> block wireless on Thinkpad E520/E420.
>
> Signed-off-by: Ike Panhc <ike.pan@canonical.com>

The symptom was that that wifi just doesn't work on these machines
until the acer-wmi driver is unloaded.  Bug was present in
3.1.8 and Ubuntu's 3.0.0-12, possibly on some older kernels, too.

Andrey (cc-ed) confirmed that applying the patch against 3.2.y gets
wifi working again on his Ideapad Z570, so

  Tested-by: Andrey <andrey.k.p@gmail.com> # Ideapad Z570

References:
  http://bugs.debian.org/655941
  http://launchpad.net/bugs/875659
  https://bugzilla.redhat.com/show_bug.cgi?id=674353

Patch left unsnipped for reference.

Thanks,
Jonathan

> ---
>  drivers/platform/x86/acer-wmi.c |   30 +++++++++++++++++++++++++++++-
>  1 files changed, 29 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/platform/x86/acer-wmi.c b/drivers/platform/x86/acer-wmi.c
> index b848277..1e5290b 100644
> --- a/drivers/platform/x86/acer-wmi.c
> +++ b/drivers/platform/x86/acer-wmi.c
> @@ -679,6 +679,32 @@ static acpi_status AMW0_find_mailled(void)
>  	return AE_OK;
>  }
>  
> +static int AMW0_set_cap_acpi_check_device_found;
> +
> +static acpi_status AMW0_set_cap_acpi_check_device_cb(acpi_handle handle,
> +	u32 level, void *context, void **retval)
> +{
> +	AMW0_set_cap_acpi_check_device_found = 1;
> +	return AE_OK;
> +}
> +
> +static const struct acpi_device_id norfkill_ids[] = {
> +	{ "VPC2004", 0},
> +	{ "IBM0068", 0},
> +	{ "LEN0068", 0},
> +	{ "", 0},
> +};
> +
> +static int AMW0_set_cap_acpi_check_device(void)
> +{
> +	const struct acpi_device_id *id;
> +
> +	for (id = norfkill_ids; id->id[0]; id++)
> +		acpi_get_devices(id->id, AMW0_set_cap_acpi_check_device_cb,
> +				NULL, NULL);
> +	return AMW0_set_cap_acpi_check_device_found;
> +}
> +
>  static acpi_status AMW0_set_capabilities(void)
>  {
>  	struct wmab_args args;
> @@ -692,7 +718,9 @@ static acpi_status AMW0_set_capabilities(void)
>  	 * work.
>  	 */
>  	if (wmi_has_guid(AMW0_GUID2)) {
> -		interface->capability |= ACER_CAP_WIRELESS;
> +		if ((quirks != &quirk_unknown) ||
> +		    !AMW0_set_cap_acpi_check_device())
> +			interface->capability |= ACER_CAP_WIRELESS;
>  		return AE_OK;
>  	}
>  
> -- 
> 1.7.5.4
>

  parent reply	other threads:[~2012-03-14 21:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  6:31 [PATCH] acer-wmi: check wireless capability on AMW0_GUID2 machines Lee, Chun-Yi
2012-01-09  8:01 ` Carlos Corbacho
2012-01-09 10:00   ` joeyli
2012-01-09 22:15     ` Carlos Corbacho
2012-01-11  4:26       ` joeyli
2012-01-11 16:54         ` Ike Panhc
2012-01-12  0:21           ` joeyli
2012-01-25  1:18             ` Ike Panhc
2012-01-20  2:44           ` joeyli
2012-01-25  1:29             ` Ike Panhc
2012-01-25  1:57             ` [PATCH] acer-wmi: No wifi rfkill on Lenovo machines Ike Panhc
2012-01-25  2:14               ` Ike Panhc
2012-01-26  2:53                 ` joeyli
2012-02-03  8:46                   ` [PATCH v2] " Ike Panhc
2012-02-03  8:55                     ` Ike Panhc
2012-02-06  9:55                     ` joeyli
2012-02-11 19:10                     ` Jonathan Nieder
2012-02-21  9:22                       ` [PATCH resend] " Jonathan Nieder
2012-03-14 21:53                     ` Jonathan Nieder [this message]
2012-03-14 22:02                       ` [PATCH 3.0.y] " Greg KH
2012-03-14 22:17                         ` Jonathan Nieder
2012-03-16  4:03                           ` Ike Panhc
2012-03-16  6:11                             ` joeyli
2012-03-16 17:20                               ` Greg KH
2012-03-19  2:08                                 ` joeyli
2012-03-19 12:40                                   ` Andrey
2012-03-19 14:48                                     ` Jonathan Nieder
2012-01-24  0:04           ` [PATCH] acer-wmi: check wireless capability on AMW0_GUID2 machines joeyli

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=20120314215327.GA1510@burratino \
    --to=jrnieder@gmail.com \
    --cc=andrey.k.p@gmail.com \
    --cc=carlos@strangeworlds.co.uk \
    --cc=corentincj@iksaif.net \
    --cc=dtor@mail.ru \
    --cc=ike.pan@canonical.com \
    --cc=jlee@suse.com \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trenn@suse.de \
    /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