Skip to contentSkip to conversation

i2c: iSMT SMBus patch for Intel Avoton DeviceIDs

PATCH Applied Seth Heasley 3 participants 7 messages Feb 21, 2013 – Mar 22, 2013

Subsystems (2)
I2C subsystem host drivers I2C/smbus ismt driver
lore
Share & tools
lore

Seth Heasley

author
#0 lore raw

PATCH 1/1 i2c: iSMT SMBus patch for Intel Avoton DeviceIDs

This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton SOC.

Signed-off-by Seth Heasley <[email protected]>
---
 drivers/i2c/busses/i2c-ismt.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
drivers/i2c/busses/i2c-ismt.c +2 -0
index 3f7a9cb..45bccf1 100644
@@ -80,6 +80,7 @@
 /* PCI DIDs for the Intel SMBus Message Transport (SMT) Devices */
 #define PCI_DEVICE_ID_INTEL_S1200_SMT0	0x0c59
 #define PCI_DEVICE_ID_INTEL_S1200_SMT1	0x0c5a
+#define PCI_DEVICE_ID_INTEL_AVOTON_SMT	0x1f15
 
 #define ISMT_DESC_ENTRIES	32	/* number of descriptor entries */
 #define ISMT_MAX_RETRIES	3	/* number of SMBus retries to attempt */

@@ -185,6 +186,7 @@ struct ismt_priv {
 static const DEFINE_PCI_DEVICE_TABLE(ismt_ids) = {
 	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_S1200_SMT0) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_S1200_SMT1) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_AVOTON_SMT) },
 	{ 0, }
 };
Signature · 1 line
1.7.4.4
maintainer
#1 lore raw
Quoted 3 lines · Seth Heasley

This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton SOC.

Signed-off-by Seth Heasley <[email protected]>

Is there a part number (I.e. S1200) that we can use in the name, rather than the project code name? That would seem to be more in keeping with the previous naming scheeme directly above it
Neil

author
#2 lore raw

Hi Neil,

Quoted 7 lines
Quoted 1 line

This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton

SOC.

Quoted 2 lines
Signed-off-by Seth Heasley <[email protected]>

Is there a part number (I.e. S1200) that we can use in the name, rather than the project code name? That would seem to be more in keeping with the previous naming scheeme directly above it Neil

The difference here is that the S1200 name is already publicly released, whereas the naming for Avoton hasn't been announced.

Regards,
-Seth

maintainer
#3 lore raw
Quoted 12 lines · Seth

Hi Neil,

Quoted 7 lines
Quoted 1 line

This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton

SOC.

Quoted 2 lines
Signed-off-by Seth Heasley <[email protected]>

Is there a part number (I.e. S1200) that we can use in the name, rather than the project code name? That would seem to be more in keeping with the previous naming scheeme directly above it Neil

The difference here is that the S1200 name is already publicly released, whereas the naming for Avoton hasn't been announced.

Do you know when the announcement will be? Is it sufficiently soon that we can just wait for it?

Neil

Quoted 3 lines

Regards,
-Seth

author
#4 lore raw
Quoted 5 lines
Quoted 1 line

The difference here is that the S1200 name is already publicly released,

whereas the naming for Avoton hasn't been announced.

Quoted 1 line

Do you know when the announcement will be? Is it sufficiently soon that we can just wait for it?

I don't, and actually couldn't tell you if I did. The codename usage is consistent with how we deal with all products since the patches have to go in well in advance of product launch.

-Seth

maintainer Acked-by
#5 lore raw
Quoted 8 lines · Seth
Quoted 5 lines
Quoted 1 line

The difference here is that the S1200 name is already publicly released,

whereas the naming for Avoton hasn't been announced.

Quoted 1 line

Do you know when the announcement will be? Is it sufficiently soon that we can just wait for it?

I don't, and actually couldn't tell you if I did. The codename usage is consistent with how we deal with all products since the patches have to go in well in advance of product launch.

Meh, ok, I guess we cal always fix it up when the product has an actual name

Acked-by Neil Horman <[email protected]>
Quoted 7 lines

-Seth
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/