From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Robert Dolca <robert.dolca@gmail.com>
Cc: Robert Dolca <robert.dolca@intel.com>,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Daniel Baluta <daniel.baluta@intel.com>
Subject: Re: [PATCH RFC] i2c: Use ID table to detect ACPI I2C devices
Date: Wed, 20 May 2015 12:48:29 +0300 [thread overview]
Message-ID: <20150520094829.GS1490@lahna.fi.intel.com> (raw)
In-Reply-To: <CAFPB+YfvJiL7yNidDQJqq=XbF1hA4QwdBhbVYrwB=wpLkJUOwA@mail.gmail.com>
On Wed, May 20, 2015 at 12:39:22PM +0300, Robert Dolca wrote:
> Currently, if the name used for DT (in dts) matches one of the names
> specified in the id table you will have a match. Isn't that an
> intended behavior?
I thought one needs to put IDs to the driver .of_match_table. This is
also what i2c_device_match() is expecting, if I read it right.
BTW, how modules are supposed to be matched if we allow putting ACPI
identifiers to i2c_device_id table?
next prev parent reply other threads:[~2015-05-20 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 14:03 [PATCH RFC] i2c: Use ID table to detect ACPI I2C devices Robert Dolca
2015-05-19 23:35 ` Rafael J. Wysocki
2015-05-20 7:47 ` Mika Westerberg
2015-05-20 9:39 ` Robert Dolca
2015-05-20 9:48 ` Mika Westerberg [this message]
[not found] ` <20150520094829.GS1490-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2015-05-20 10:49 ` Robert Dolca
[not found] ` <CAFPB+YcggLY9vwtYREX_YVVJFrTYHTQYnBtvMcicvLgo5MX-+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-20 10:57 ` Mika Westerberg
[not found] ` <20150520105753.GT1490-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2015-05-20 13:07 ` Robert Dolca
[not found] ` <CAFPB+Ydw4Ywo4dt5NB-Aed6gtt89h2kMucXtgJa42vwommZerw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-20 13:57 ` Mika Westerberg
2015-05-20 21:32 ` Robert Dolca
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=20150520094829.GS1490@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=daniel.baluta@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.dolca@gmail.com \
--cc=robert.dolca@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).