Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753790AbbHYGcO (ORCPT ); Tue, 25 Aug 2015 02:32:14 -0400 Received: from lists.s-osg.org ([54.187.51.154]:59650 "EHLO lists.s-osg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751501AbbHYGcK (ORCPT ); Tue, 25 Aug 2015 02:32:10 -0400 From: Javier Martinez Canillas To: linux-kernel@vger.kernel.org Cc: Javier Martinez Canillas , Wolfram Sang , linux-i2c@vger.kernel.org Subject: [RESEND PATCH 1/7] i2c: core: Export I2C module alias information in dummy driver Date: Tue, 25 Aug 2015 08:31:11 +0200 Message-Id: <1440484277-32675-2-git-send-email-javier@osg.samsung.com> X-Mailer: git-send-email 2.4.3 In-Reply-To: <1440484277-32675-1-git-send-email-javier@osg.samsung.com> References: <1440484277-32675-1-git-send-email-javier@osg.samsung.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1234 Lines: 36 The I2C core always reports the MODALIAS uevent as "i2c:" regardless of the mechanism that was used to register the device (i.e: OF or board code) and the table that is used later to match the driver with the device (i.e: I2C id table or OF match table). So drivers needs to export the I2C id table and this be built into the module or udev won't have the necessary information to autoload the needed driver module when the device is added. Signed-off-by: Javier Martinez Canillas --- drivers/i2c/i2c-core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c index a6780289c61d..46536834920c 100644 --- a/drivers/i2c/i2c-core.c +++ b/drivers/i2c/i2c-core.c @@ -1041,6 +1041,7 @@ static const struct i2c_device_id dummy_id[] = { { "dummy", 0 }, { }, }; +MODULE_DEVICE_TABLE(i2c, dummy_id); static int dummy_probe(struct i2c_client *client, const struct i2c_device_id *id) -- 2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/