From: Jean Delvare <khali@linux-fr.org>
To: Nathan Lutchansky <lutchann@litech.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH 1/5] call i2c_probe from i2c core
Date: Mon, 15 Aug 2005 23:55:31 +0200 [thread overview]
Message-ID: <20050815235531.2a7d2bb6.khali@linux-fr.org> (raw)
In-Reply-To: <20050815175257.GB24959@litech.org>
Hi Nathan,
> Index: linux-2.6.13-rc6+gregkh/include/linux/i2c.h
> ===================================================================
You should probably be using the --no-index option of quilt 0.42 (if you
are using quilt as I presumed), as I heard Linus doesn't like these
index lines in the patches he receives.
> --- linux-2.6.13-rc6+gregkh.orig/drivers/i2c/i2c-core.c
> +++ linux-2.6.13-rc6+gregkh/drivers/i2c/i2c-core.c
> @@ -193,9 +193,16 @@ int i2c_add_adapter(struct i2c_adapter *
> /* inform drivers of new adapters */
> list_for_each(item,&drivers) {
> driver = list_entry(item, struct i2c_driver, list);
> - if (driver->flags & I2C_DF_NOTIFY)
> - /* We ignore the return code; if it fails, too bad */
> - driver->attach_adapter(adap);
> + if (driver->flags & I2C_DF_NOTIFY) {
> + /* We ignore the return codes; if it fails, too bad */
> + if (driver->attach_adapter)
> + driver->attach_adapter(adap);
> + if (driver->detect_client && driver->address_data &&
> + ((driver->class & adap->class) ||
> + driver->class == 0))
> + i2c_probe(adap, driver->address_data,
> + driver->detect_client);
> + }
> }
>
> out_unlock:
> @@ -307,7 +314,13 @@ int i2c_add_driver(struct i2c_driver *dr
> if (driver->flags & I2C_DF_NOTIFY) {
> list_for_each(item,&adapters) {
> adapter = list_entry(item, struct i2c_adapter, list);
> - driver->attach_adapter(adapter);
> + if (driver->attach_adapter)
> + driver->attach_adapter(adapter);
> + if (driver->detect_client && driver->address_data &&
> + ((driver->class & adapter->class) ||
> + driver->class == 0))
> + i2c_probe(adapter, driver->address_data,
> + driver->detect_client);
> }
> }
Couldn't we check for the return value of driver->attach_adapter()? That
way this function could conditionally prevent i2c_probe() from being
run. This is just a random proposal, I don't know if some drivers would
have an interest in doing that.
Also, maybe we can put this new code in a separate function to be called
from both i2c_add_adapter and i2c_add_driver, so as to not duplicate
code? Or would this be too much overhead? It could be made inline then.
Again, just a random thought.
> --- linux-2.6.13-rc6+gregkh.orig/Documentation/i2c/writing-clients
> +++ linux-2.6.13-rc6+gregkh/Documentation/i2c/writing-clients
Thanks for the documentation update. However, you didn't update
i2c/porting-clients accordingly. Could you please?
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2005-08-15 21:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 17:51 [PATCH 0/5] improve i2c probing Nathan Lutchansky
2005-08-15 17:52 ` [PATCH 1/5] call i2c_probe from i2c core Nathan Lutchansky
2005-08-15 21:55 ` Jean Delvare [this message]
2005-08-16 3:14 ` Nathan Lutchansky
2005-08-16 12:13 ` Jean Delvare
2005-08-15 17:53 ` [PATCH 2/5] remove attach_adapter from i2c hwmon drivers Nathan Lutchansky
2005-08-15 22:00 ` Jean Delvare
2005-08-15 17:54 ` [PATCH 3/5] remove attach_adapter from misc i2c chip drivers Nathan Lutchansky
2005-08-15 17:54 ` [PATCH 4/5] add i2c_probe_device and i2c_remove_device Nathan Lutchansky
2005-08-15 22:14 ` Jean Delvare
2005-08-16 3:33 ` Nathan Lutchansky
2005-08-16 16:38 ` Jean Delvare
2005-08-15 17:55 ` [PATCH 5/5] new flag to disable i2c probing for an adapter Nathan Lutchansky
2005-08-15 21:39 ` [PATCH 0/5] improve i2c probing Jean Delvare
2005-08-16 3:05 ` Nathan Lutchansky
2005-08-16 20:30 ` Jean Delvare
2005-08-18 18:54 ` Greg KH
2005-08-20 0:11 ` Nathan Lutchansky
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=20050815235531.2a7d2bb6.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=lutchann@litech.org \
/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