[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140116122704.GD2617@katana>
Date: Thu, 16 Jan 2014 13:27:04 +0100
From: Wolfram Sang <wsa@...-dreams.de>
To: Zhang Rui <rui.zhang@...el.com>
Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-i2c@...r.kernel.org, linux-spi@...r.kernel.org,
broonie@...aro.org, gregkh@...uxfoundation.org,
rafael.j.wysocki@...el.com, grant.likely@...aro.org,
rob.herring@...xeda.com, jarkko.nikula@...ux.intel.com,
mika.westerberg@...ux.intel.com
Subject: Re: [PATCH 3/4] fix module autoloading for ACPI enumerated devices
> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> index d74c0b3..c4c5588 100644
> --- a/drivers/i2c/i2c-core.c
> +++ b/drivers/i2c/i2c-core.c
> @@ -104,6 +104,11 @@ static int i2c_device_match(struct device *dev, struct device_driver *drv)
> static int i2c_device_uevent(struct device *dev, struct kobj_uevent_env *env)
> {
> struct i2c_client *client = to_i2c_client(dev);
> + int rc;
> +
> + rc = acpi_device_uevent_modalias(dev, env);
> + if (rc != -ENODEV)
> + return rc;
>
> if (add_uevent_var(env, "MODALIAS=%s%s",
> I2C_MODULE_PREFIX, client->name))
I wonder why we don't have/need that with CONFIG_OF? Because probably
nobody is using modules with i2c devices there?
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists