From: Crane Cai <crane.cai-5C7GfCeVMHo@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] I2C: Add support for new AMD SMBus devices
Date: Thu, 10 Sep 2009 09:55:09 +0800 [thread overview]
Message-ID: <20090910015509.GA3147@crane-desktop> (raw)
In-Reply-To: <20090909111026.21e85f54-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
On Wed, Sep 09, 2009 at 11:10:26AM +0200, Jean Delvare wrote:
> This is better, however I still have concerns:
>
> * Your device ID comparison is fragile. Are you absolutely certain that
> you know _all_ the SMBus devices that were released by AMD in the
> past? If anything, I'd rather have a single comparison on the first
> device ID that _will_ be supported by the i2c-piix4 driver.
>
> * Are you absolutely certain that AMD will never ever release an
> incompatible SMBus device in the future? I doubt it. In the past,
> various vendors have changed their implementations. Intel changed
> twice (i2c-piix4 -> i2c-i801 -> i2c-isch), AMD once already
> (i2c-amd756 -> i2c-amd8111), VIA once (i2c-via -> i2c-viapro), nVidia
> once (i2c-amd756 -> i2c-nforce2), etc. If history repeats itself (and
> it often does), I wouldn't be surprised to see future AMD SMBus chips
> not compatible with the i2c-piix4 driver, while with your patch
> applied, the driver would claim to support them. Binding a driver to
> an unsupported chip can have unpredictable, potentially bad
> consequences, and I'd rather have the driver not bind immediately to
> new supported devices than bind to unsupported ones.
>
> * With your patch, the i2c-piix4 driver would load automatically on
> systems which do not need it (all old AMD-based PC systems.) While a
> minor issue, this is still a waste of boot time and memory for these
> users. I am not aware of any precedent of this.
>
> So, all in all, I'd rather simply add the IDs of new supported devices
> as they are released, rather than implement this broad matching
> mechanism.
Thank you for your greate comments. I agree with you. And a new patch will be
submitted which will use VID DID to check.
--
Best Regards,
- Crane
prev parent reply other threads:[~2009-09-10 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 1:49 [PATCH v2] I2C: Add support for new AMD SMBus devices Crane Cai
2009-09-09 8:12 ` Jean Delvare
2009-09-09 9:10 ` Jean Delvare
[not found] ` <20090909111026.21e85f54-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-10 1:55 ` Crane Cai [this message]
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=20090910015509.GA3147@crane-desktop \
--to=crane.cai-5c7gfcevmho@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).