linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
	Wolfram Sang <wsa@the-dreams.de>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] i2c: Fix modalias for ACPI enumerated I2C devices
Date: Mon, 14 Oct 2013 14:18:44 +0300	[thread overview]
Message-ID: <525BD314.5010802@linux.intel.com> (raw)
In-Reply-To: <1381742625.2034.25.camel@rzhang1-mobl4>

On 10/14/2013 12:23 PM, Zhang Rui wrote:
> Hi,
>
> On Thu, 2013-10-10 at 17:17 +0300, Jarkko Nikula wrote:
>> There is a minor fault about ACPI enumerated I2C devices with their modalias
>> attribute. Now modalias is set by device instance not by hardware ID.
>> For example "i2c:INTABCD:00", "i2c:INTABCD:01" etc.
>>
>> This means each device instance gets different modalias which does match
>> with generated modules.alias. Currently this is not problem as matching can
>> happen also with "acpi:INTABCD" modalias.
>>
> IMO, this is not the proper fix for the modalias problem because ACPI
> enumerated I2C device may have compatible ids.
> Instead, we should export all the compatible ids as the modules alias of
> the ACPI enumerated I2C device.
>
> can you please take a look at the patch I sent out earlier?
> https://patchwork.kernel.org/patch/3034991/
> https://patchwork.kernel.org/patch/3035041/
> https://patchwork.kernel.org/patch/3035021/
I see. This makes sense as it avoids that same device has two different 
modaliases from both acpi and other subsystem.

How about modalias nodes in sysfs, should they also reflect what is 
matching uvent?

-- 
Jarkko

  reply	other threads:[~2013-10-14 11:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 14:17 [PATCH] i2c: Fix modalias for ACPI enumerated I2C devices Jarkko Nikula
     [not found] ` <1381414669-26115-1-git-send-email-jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2013-10-11 14:49   ` Mika Westerberg
     [not found]     ` <20131011144946.GS3521-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-10-11 22:16       ` Rafael J. Wysocki
2013-10-12  5:04         ` Mika Westerberg
     [not found]           ` <20131012050413.GY3521-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-10-12 13:45             ` Rafael J. Wysocki
     [not found]               ` <2878883.SYGmCkS5Bt-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2013-10-12 16:18                 ` Mika Westerberg
2013-10-14  6:45                   ` Jarkko Nikula
     [not found]                     ` <525B9321.5000906-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2013-10-14  8:16                       ` Mika Westerberg
2013-10-14  6:34           ` Jarkko Nikula
2013-10-14  8:13             ` Mika Westerberg
2013-10-14  9:23   ` Zhang Rui
2013-10-14 11:18     ` Jarkko Nikula [this message]
2013-10-14 12:47       ` Zhang Rui
2013-10-15 11:44         ` Zhang Rui
2013-10-15 20:37           ` Rafael J. Wysocki
     [not found]             ` <12043671.FjbAvIiH5B-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2013-10-15 20:48               ` Greg Kroah-Hartman
2013-10-15 21:24                 ` Rafael J. Wysocki
2013-10-15 23:31                   ` Greg Kroah-Hartman
2013-10-15 23:47                     ` Rafael J. Wysocki
2013-10-16  0:04                       ` Grant Likely
     [not found]                         ` <CACxGe6v3JHLKHqBXux=1mgm227S2dLafaqohKvzqsw1uo6tHyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-16  0:10                           ` Greg Kroah-Hartman
2013-10-16  7:16                         ` Jarkko Nikula
     [not found]                 ` <20131015204829.GA5212-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-10-15 21:40                   ` Rafael J. Wysocki

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=525BD314.5010802@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rui.zhang@intel.com \
    --cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).