public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Lee Jones <lee.jones@linaro.org>,
	Darren Hart <dvhart@linux.intel.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: Use ACPI companion to match only the first physical device
Date: Fri, 24 Oct 2014 13:08:33 +0300	[thread overview]
Message-ID: <544A2521.3080308@linux.intel.com> (raw)
In-Reply-To: <1414141950-228930-1-git-send-email-mika.westerberg@linux.intel.com>

On 10/24/2014 12:12 PM, Mika Westerberg wrote:
> Commit 6ab3430129e2 ("mfd: Add ACPI support") made the MFD subdevices to
> share the parent MFD ACPI companion device if no _HID/_CID is specified for
> the subdevice in mfd_cell description. However, since all the subdevices
> share the ACPI companion, the match and modalias generation logic started
> to use the ACPI companion as well resulting this:
>
>    # cat /sys/bus/platform/devices/HID-SENSOR-200041.6.auto/modalias
>    acpi:INT33D1:PNP0C50:
>
> instead of the expected one
>
>    # cat /sys/bus/platform/devices/HID-SENSOR-200041.6.auto/modalias
>    platform:HID-SENSOR-200041
>
> In other words the subdevice modalias is overwritten by the one taken from
> ACPI companion. This causes udev not to load the driver anymore.
>
> It is useful to be able to share the ACPI companion so that MFD subdevices
> (and possibly other devices as well) can access the ACPI resources even if
> they do not have ACPI representation in the namespace themselves.
>
> An example where this is used is Minnowboard LPC driver that creates GPIO
> as a subdevice among other things. Without the ACPI companion gpiolib is
> not is not able to lookup the corresponding GPIO controller from ACPI
> GpioIo resource.
>
> To fix this we restrict the match and modalias logic to be limited to the
> first physical device. The secondary devices will still be able to access
> the ACPI companion but they will be matched using traditional way.
>
> Reported-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
> Hi,
>
> This is a regression in v3.18-rc1+ and prevents udev from loading the
> modules in question. Alternative to this we can revert 6ab3430129e2 but
> then Minnowboard GPIOs do not work anymore.
>
>   drivers/acpi/scan.c | 71 +++++++++++++++++++++++++++++++++++++++++------------
>   1 file changed, 55 insertions(+), 16 deletions(-)
>
Tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>

       reply	other threads:[~2014-10-24 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1414141950-228930-1-git-send-email-mika.westerberg@linux.intel.com>
2014-10-24 10:08 ` Jarkko Nikula [this message]
2014-10-24 13:55 ` [PATCH] ACPI: Use ACPI companion to match only the first physical device Rafael J. Wysocki
2014-10-24 13:50   ` Mika Westerberg
2014-10-24 14:20   ` Rafael J. Wysocki
2014-10-24 14:10     ` Mika Westerberg
2014-10-24 14:57       ` Rafael J. Wysocki
2014-10-24 18:16         ` Mika Westerberg

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=544A2521.3080308@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=dvhart@linux.intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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