From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [PATCH RFC] i2c: Use ID table to detect ACPI I2C devices Date: Wed, 20 May 2015 12:48:29 +0300 Message-ID: <20150520094829.GS1490@lahna.fi.intel.com> References: <1432044209-27858-1-git-send-email-robert.dolca@intel.com> <20150520074708.GQ1490@lahna.fi.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Robert Dolca Cc: Robert Dolca , linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org, "linux-kernel@vger.kernel.org" , Wolfram Sang , "Rafael J. Wysocki" , Len Brown , Daniel Baluta List-Id: linux-i2c@vger.kernel.org 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?