From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] i2c driver fixes for 2.6.0
Date: Tue, 30 Dec 2003 14:06:10 -0800 [thread overview]
Message-ID: <10728219702175@kroah.com> (raw)
In-Reply-To: <10728219704116@kroah.com>
ChangeSet 1.1496.8.30, 2003/12/17 15:52:23-08:00, khali@linux-fr.org
[PATCH] I2C: restore support for AMD8111 in i2c-amd756 driver
This patch restores support for the AMD8111 in the i2c-amd756 driver.
Credits go to Philip Pokorny for the original patch. I tweaked it a bit.
This isn't a bug fix and can be delayed until after 2.6.0 if you want.
drivers/i2c/busses/i2c-amd756.c | 16 ++++++++++------
1 files changed, 10 insertions(+), 6 deletions(-)
diff -Nru a/drivers/i2c/busses/i2c-amd756.c b/drivers/i2c/busses/i2c-amd756.c
--- a/drivers/i2c/busses/i2c-amd756.c Tue Dec 30 12:30:50 2003
+++ b/drivers/i2c/busses/i2c-amd756.c Tue Dec 30 12:30:50 2003
@@ -28,10 +28,12 @@
2002-04-08: Added nForce support. (Csaba Halasz)
2002-10-03: Fixed nForce PnP I/O port. (Michael Steil)
2002-12-28: Rewritten into something that resembles a Linux driver (hch)
+ 2003-11-29: Added back AMD8111 removed by the previous rewrite.
+ (Philip Pokorny)
*/
/*
- Supports AMD756, AMD766, AMD768 and nVidia nForce
+ Supports AMD756, AMD766, AMD768, AMD8111 and nVidia nForce
Note: we assume there can only be one device, with one SMBus interface.
*/
@@ -308,12 +310,13 @@
.name = "unset",
};
-enum chiptype { AMD756, AMD766, AMD768, NFORCE };
+enum chiptype { AMD756, AMD766, AMD768, NFORCE, AMD8111 };
static struct pci_device_id amd756_ids[] = {
{PCI_VENDOR_ID_AMD, 0x740B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, AMD756 },
{PCI_VENDOR_ID_AMD, 0x7413, PCI_ANY_ID, PCI_ANY_ID, 0, 0, AMD766 },
{PCI_VENDOR_ID_AMD, 0x7443, PCI_ANY_ID, PCI_ANY_ID, 0, 0, AMD768 },
+ {PCI_VENDOR_ID_AMD, 0x746B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, AMD8111 },
{PCI_VENDOR_ID_NVIDIA, 0x01B4, PCI_ANY_ID, PCI_ANY_ID, 0, 0, NFORCE },
{ 0, }
};
@@ -321,7 +324,8 @@
static int __devinit amd756_probe(struct pci_dev *pdev,
const struct pci_device_id *id)
{
- int nforce = (id->driver_data == NFORCE), error;
+ int nforce = (id->driver_data == NFORCE);
+ int error;
u8 temp;
if (amd756_ioport) {
@@ -368,7 +372,7 @@
amd756_adapter.dev.parent = &pdev->dev;
snprintf(amd756_adapter.name, I2C_NAME_SIZE,
- "SMBus AMD75x adapter at %04x", amd756_ioport);
+ "SMBus AMD756 adapter at %04x", amd756_ioport);
error = i2c_add_adapter(&amd756_adapter);
if (error) {
@@ -391,7 +395,7 @@
}
static struct pci_driver amd756_driver = {
- .name = "amd75x smbus",
+ .name = "amd756 smbus",
.id_table = amd756_ids,
.probe = amd756_probe,
.remove = __devexit_p(amd756_remove),
@@ -408,7 +412,7 @@
}
MODULE_AUTHOR("Merlin Hughes <merlin@merlin.org>");
-MODULE_DESCRIPTION("AMD756/766/768/nVidia nForce SMBus driver");
+MODULE_DESCRIPTION("AMD756/766/768/8111 and nVidia nForce SMBus driver");
MODULE_LICENSE("GPL");
module_init(amd756_init)
next prev parent reply other threads:[~2003-12-30 22:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 22:02 [BK PATCH] i2c driver fixes for 2.6.0 Greg KH
2003-12-30 22:06 ` [PATCH] " Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH [this message]
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
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=10728219702175@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
/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