All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Poulain <loic.poulain@intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: johannes@sipsolutions.net, linville@tuxdriver.com,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/5] net: rfkill: gpio: Implement host wake up support
Date: Thu, 09 Oct 2014 10:08:47 +0200	[thread overview]
Message-ID: <5436428F.5080803@intel.com> (raw)
In-Reply-To: <20141009073854.GA9108@kuha.fi.intel.com>

Thanks Heikki, I'll rework these patches accordingly.

Regards,
Loic

On 09/10/2014 09:38, Heikki Krogerus wrote:
> On Wed, Oct 08, 2014 at 04:09:50PM +0200, Loic Poulain wrote:
>> Thanks, it sounds good to use a label instead of index.
>> However:
>> - DSD is only compatible with BIOS ACPI 5.1
>> - gpiod_get_index does not take care of con_id (label) parameter in case of
>> ACPI (acpi_find_gpio).
>> - gpiod_get calls gpiod_get_index with index 0.
>>
>> Any patch ongoing to support con_id parameter with ACPI?
> Yes. This is the latest version being review as we speak:
> https://lkml.org/lkml/2014/10/6/530
>
> It is really important you get your firmware fixed. We simply can not
> rely on the order of the resources like GPIOs in the resource
> templates. They may be different on every second
> board/BIOS/configuration/whatever. It's even possible for a ACPI
> device object to have two (or more) different resource templates
> describing the same GPIOs in different order which are then selected
> based on some magic condition, for example user selection in BIOS setup.
>
> The existing hardware works with the drivers we have now, and it's not
> possible to change the BIOS/system firmware on those so we just have
> to live with them and rely on being able to pick the correct resources
> based on index. But everything new _must_ use _DSD properties, and
> ACPI 5.1 in general.
>
> So basically your BIOS must produce the ACPI tables according to ACPI
> 5.1. If you are worried about support for ACPI 5.1 in kernel, don't
> worry about it, it's almost ready. And in the meantime, _DSD is just
> something kernel will ignore.
>
>
> Cheers,
>

-- 
Intel Open Source Technology Center
http://oss.intel.com/


  reply	other threads:[~2014-10-09  8:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08  8:34 [PATCH 1/5] net: rfkill: gpio: Configurable GPIO idx Loic Poulain
2014-10-08  8:34 ` [PATCH 2/5] net: rfkill: gpio: Implement PM hooks Loic Poulain
2014-10-08  8:34 ` [PATCH 3/5] net: rfkill: gpio: Implement host wake up support Loic Poulain
2014-10-08 11:38   ` Heikki Krogerus
2014-10-08 14:09     ` Loic Poulain
2014-10-09  7:38       ` Heikki Krogerus
2014-10-09  8:08         ` Loic Poulain [this message]
2014-10-08  8:34 ` [PATCH 4/5] net: rfkill: gpio: Add OBDA8723 ACPI ID Loic Poulain
2014-10-08  8:34 ` [PATCH 5/5] net: rfkill: gpio: Add BCM47521 " Loic Poulain
2014-10-08  8:53 ` [PATCH 1/5] net: rfkill: gpio: Configurable GPIO idx Johannes Berg
2014-10-08  9:28   ` Loic Poulain
2014-10-08 10:27 ` Heikki Krogerus

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=5436428F.5080803@intel.com \
    --to=loic.poulain@intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.