Grouping i2c bus drivers
Hi all,
As was mentioned previously, I have decided to group the i2c bus drivers to make it easier for the users to know what they need (and also for me to know what drivers might be affected by a given problem.) Here is the list I have at the moment. There are still many drivers in the "Other" category. I suspect that many of these should move to the "Embedded" category, but I don't know for sure. So I would welcome comments and suggestions for improvements.
# PC SMBus host controller drivers
obj-$(CONFIG_I2C_ALI1535) += i2c-ali1535.o
obj-$(CONFIG_I2C_ALI1563) += i2c-ali1563.o
obj-$(CONFIG_I2C_ALI15X3) += i2c-ali15x3.o
obj-$(CONFIG_I2C_AMD756) += i2c-amd756.o
obj-$(CONFIG_I2C_AMD756_S4882) += i2c-amd756-s4882.o
obj-$(CONFIG_I2C_AMD8111) += i2c-amd8111.o
obj-$(CONFIG_I2C_I801) += i2c-i801.o
obj-$(CONFIG_I2C_NFORCE2) += i2c-nforce2.o
obj-$(CONFIG_I2C_NFORCE2_S4985) += i2c-nforce2-s4985.o
obj-$(CONFIG_I2C_PIIX4) += i2c-piix4.o
obj-$(CONFIG_I2C_SIS5595) += i2c-sis5595.o
obj-$(CONFIG_I2C_SIS630) += i2c-sis630.o
obj-$(CONFIG_I2C_SIS96X) += i2c-sis96x.o
obj-$(CONFIG_I2C_VIA) += i2c-via.o
obj-$(CONFIG_I2C_VIAPRO) += i2c-viapro.o
# Mac SMBus host controller drivers
obj-$(CONFIG_I2C_HYDRA) += i2c-hydra.o
obj-$(CONFIG_I2C_POWERMAC) += i2c-powermac.o
# Embebbed system I2C/SMBus host controller drivers
obj-$(CONFIG_I2C_AT91) += i2c-at91.o
obj-$(CONFIG_I2C_DAVINCI) += i2c-davinci.o
obj-$(CONFIG_I2C_GPIO) += i2c-gpio.o
obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o
obj-$(CONFIG_I2C_OMAP) += i2c-omap.o
obj-$(CONFIG_I2C_PXA) += i2c-pxa.o
obj-$(CONFIG_I2C_S3C2410) += i2c-s3c2410.o
obj-$(CONFIG_I2C_VERSATILE) += i2c-versatile.o
# External I2C/SMBus adapter drivers
obj-$(CONFIG_I2C_PARPORT) += i2c-parport.o
obj-$(CONFIG_I2C_PARPORT_LIGHT) += i2c-parport-light.o
obj-$(CONFIG_I2C_TAOS_EVM) += i2c-taos-evm.o
obj-$(CONFIG_I2C_TINY_USB) += i2c-tiny-usb.o
# Graphics adapter I2C/DDC channel drivers
obj-$(CONFIG_I2C_VOODOO3) += i2c-voodoo3.o
# Other I2C/SMBus bus drivers
obj-$(CONFIG_I2C_ACORN) += i2c-acorn.o
obj-$(CONFIG_I2C_AU1550) += i2c-au1550.o
obj-$(CONFIG_I2C_BLACKFIN_TWI) += i2c-bfin-twi.o
obj-$(CONFIG_I2C_ELEKTOR) += i2c-elektor.o
obj-$(CONFIG_I2C_CPM) += i2c-cpm.o
obj-$(CONFIG_I2C_IBM_IIC) += i2c-ibm_iic.o
obj-$(CONFIG_I2C_IOP3XX) += i2c-iop3xx.o
obj-$(CONFIG_I2C_ISCH) += i2c-isch.o
obj-$(CONFIG_I2C_MPC) += i2c-mpc.o
obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o
obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o
obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o
obj-$(CONFIG_I2C_PCA_ISA) += i2c-pca-isa.o
obj-$(CONFIG_I2C_PCA_PLATFORM) += i2c-pca-platform.o
obj-$(CONFIG_I2C_PMCMSP) += i2c-pmcmsp.o
obj-$(CONFIG_I2C_PNX) += i2c-pnx.o
obj-$(CONFIG_I2C_SH7760) += i2c-sh7760.o
obj-$(CONFIG_I2C_SH_MOBILE) += i2c-sh_mobile.o
obj-$(CONFIG_I2C_SIBYTE) += i2c-sibyte.o
obj-$(CONFIG_I2C_SIMTEC) += i2c-simtec.o
obj-$(CONFIG_I2C_STUB) += i2c-stub.o
obj-$(CONFIG_SCx200_ACB) += scx200_acb.o
obj-$(CONFIG_SCx200_I2C) += scx200_i2c.o
(Of course, Kconfig has similar groups.)
Thanks,
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Hi Jean,
Quoted 9 lines · Jean Delvare
Hi all,
As was mentioned previously, I have decided to group the i2c bus drivers to make it easier for the users to know what they need (and also for me to know what drivers might be affected by a given problem.) Here is the list I have at the moment. There are still many drivers in the "Other" category. I suspect that many of these should move to the "Embedded" category, but I don't know for sure. So I would welcome comments and suggestions for improvements.
From my first glimpse:
Quoted 38 lines
# PC SMBus host controller drivers
obj-$(CONFIG_I2C_ALI1535) += i2c-ali1535.o
obj-$(CONFIG_I2C_ALI1563) += i2c-ali1563.o
obj-$(CONFIG_I2C_ALI15X3) += i2c-ali15x3.o
obj-$(CONFIG_I2C_AMD756) += i2c-amd756.o
obj-$(CONFIG_I2C_AMD756_S4882) += i2c-amd756-s4882.o
obj-$(CONFIG_I2C_AMD8111) += i2c-amd8111.o
obj-$(CONFIG_I2C_I801) += i2c-i801.o
obj-$(CONFIG_I2C_NFORCE2) += i2c-nforce2.o
obj-$(CONFIG_I2C_NFORCE2_S4985) += i2c-nforce2-s4985.o
obj-$(CONFIG_I2C_PIIX4) += i2c-piix4.o
obj-$(CONFIG_I2C_SIS5595) += i2c-sis5595.o
obj-$(CONFIG_I2C_SIS630) += i2c-sis630.o
obj-$(CONFIG_I2C_SIS96X) += i2c-sis96x.o
obj-$(CONFIG_I2C_VIA) += i2c-via.o
obj-$(CONFIG_I2C_VIAPRO) += i2c-viapro.o# Mac SMBus host controller drivers
obj-$(CONFIG_I2C_HYDRA) += i2c-hydra.o
obj-$(CONFIG_I2C_POWERMAC) += i2c-powermac.o# Embebbed system I2C/SMBus host controller drivers
obj-$(CONFIG_I2C_AT91) += i2c-at91.o
obj-$(CONFIG_I2C_DAVINCI) += i2c-davinci.o
obj-$(CONFIG_I2C_GPIO) += i2c-gpio.o
obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o
obj-$(CONFIG_I2C_OMAP) += i2c-omap.o
obj-$(CONFIG_I2C_PXA) += i2c-pxa.o
obj-$(CONFIG_I2C_S3C2410) += i2c-s3c2410.o
obj-$(CONFIG_I2C_VERSATILE) += i2c-versatile.o# External I2C/SMBus adapter drivers
obj-$(CONFIG_I2C_PARPORT) += i2c-parport.o
obj-$(CONFIG_I2C_PARPORT_LIGHT) += i2c-parport-light.o
obj-$(CONFIG_I2C_TAOS_EVM) += i2c-taos-evm.o
obj-$(CONFIG_I2C_TINY_USB) += i2c-tiny-usb.o
Quoted 7 lines
# Graphics adapter I2C/DDC channel drivers
obj-$(CONFIG_I2C_VOODOO3) += i2c-voodoo3.o# Other I2C/SMBus bus drivers
obj-$(CONFIG_I2C_ACORN) += i2c-acorn.o
obj-$(CONFIG_I2C_AU1550) += i2c-au1550.o
obj-$(CONFIG_I2C_BLACKFIN_TWI) += i2c-bfin-twi.o
Embedded.
Quoted 1 line
obj-$(CONFIG_I2C_ELEKTOR) += i2c-elektor.o
It is not SMBus, but still PC (ISA).
Quoted 1 line
obj-$(CONFIG_I2C_CPM) += i2c-cpm.o
Embedded.
Quoted 4 lines
obj-$(CONFIG_I2C_IBM_IIC) += i2c-ibm_iic.o
obj-$(CONFIG_I2C_IOP3XX) += i2c-iop3xx.o
obj-$(CONFIG_I2C_ISCH) += i2c-isch.o
obj-$(CONFIG_I2C_MPC) += i2c-mpc.o
Embedded.
Quoted 4 lines
obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o
obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o
obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o
obj-$(CONFIG_I2C_PCA_ISA) += i2c-pca-isa.o
It is not SMBus, but still PC (ISA).
Quoted 1 line
obj-$(CONFIG_I2C_PCA_PLATFORM) += i2c-pca-platform.o
External means probably: Connected via some bus? This one is just memory mapped...
Quoted 3 lines
obj-$(CONFIG_I2C_PMCMSP) += i2c-pmcmsp.o
obj-$(CONFIG_I2C_PNX) += i2c-pnx.o
obj-$(CONFIG_I2C_SH7760) += i2c-sh7760.o
Embedded.
Quoted 1 line
obj-$(CONFIG_I2C_SH_MOBILE) += i2c-sh_mobile.o
Embedded.
Quoted 1 line
obj-$(CONFIG_I2C_SIBYTE) += i2c-sibyte.o
PC? Looking at MODULE_DESCRIPTION.
Quoted 15 lines
obj-$(CONFIG_I2C_SIMTEC) += i2c-simtec.o
obj-$(CONFIG_I2C_STUB) += i2c-stub.o
obj-$(CONFIG_SCx200_ACB) += scx200_acb.o
obj-$(CONFIG_SCx200_I2C) += scx200_i2c.o(Of course,
Kconfighas similar groups.)Thanks,
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Signature · 2 lines
Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2c
Hi Wolfram,
Quoted 49 lines · Wolfram Sang
Quoted 7 lines · Jean Delvare
As was mentioned previously, I have decided to group the i2c bus drivers to make it easier for the users to know what they need (and also for me to know what drivers might be affected by a given problem.) Here is the list I have at the moment. There are still many drivers in the "Other" category. I suspect that many of these should move to the "Embedded" category, but I don't know for sure. So I would welcome comments and suggestions for improvements.
From my first glimpse:
Quoted 38 lines
# PC SMBus host controller drivers
obj-$(CONFIG_I2C_ALI1535) += i2c-ali1535.o
obj-$(CONFIG_I2C_ALI1563) += i2c-ali1563.o
obj-$(CONFIG_I2C_ALI15X3) += i2c-ali15x3.o
obj-$(CONFIG_I2C_AMD756) += i2c-amd756.o
obj-$(CONFIG_I2C_AMD756_S4882) += i2c-amd756-s4882.o
obj-$(CONFIG_I2C_AMD8111) += i2c-amd8111.o
obj-$(CONFIG_I2C_I801) += i2c-i801.o
obj-$(CONFIG_I2C_NFORCE2) += i2c-nforce2.o
obj-$(CONFIG_I2C_NFORCE2_S4985) += i2c-nforce2-s4985.o
obj-$(CONFIG_I2C_PIIX4) += i2c-piix4.o
obj-$(CONFIG_I2C_SIS5595) += i2c-sis5595.o
obj-$(CONFIG_I2C_SIS630) += i2c-sis630.o
obj-$(CONFIG_I2C_SIS96X) += i2c-sis96x.o
obj-$(CONFIG_I2C_VIA) += i2c-via.o
obj-$(CONFIG_I2C_VIAPRO) += i2c-viapro.o# Mac SMBus host controller drivers
obj-$(CONFIG_I2C_HYDRA) += i2c-hydra.o
obj-$(CONFIG_I2C_POWERMAC) += i2c-powermac.o# Embebbed system I2C/SMBus host controller drivers
obj-$(CONFIG_I2C_AT91) += i2c-at91.o
obj-$(CONFIG_I2C_DAVINCI) += i2c-davinci.o
obj-$(CONFIG_I2C_GPIO) += i2c-gpio.o
obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o
obj-$(CONFIG_I2C_OMAP) += i2c-omap.o
obj-$(CONFIG_I2C_PXA) += i2c-pxa.o
obj-$(CONFIG_I2C_S3C2410) += i2c-s3c2410.o
obj-$(CONFIG_I2C_VERSATILE) += i2c-versatile.o# External I2C/SMBus adapter drivers
obj-$(CONFIG_I2C_PARPORT) += i2c-parport.o
obj-$(CONFIG_I2C_PARPORT_LIGHT) += i2c-parport-light.o
obj-$(CONFIG_I2C_TAOS_EVM) += i2c-taos-evm.o
obj-$(CONFIG_I2C_TINY_USB) += i2c-tiny-usb.o
Quoted 8 lines
Quoted 7 lines
# Graphics adapter I2C/DDC channel drivers
obj-$(CONFIG_I2C_VOODOO3) += i2c-voodoo3.o# Other I2C/SMBus bus drivers
obj-$(CONFIG_I2C_ACORN) += i2c-acorn.o
obj-$(CONFIG_I2C_AU1550) += i2c-au1550.o
obj-$(CONFIG_I2C_BLACKFIN_TWI) += i2c-bfin-twi.oEmbedded.
Done.
Quoted 2 lines
Quoted 1 line
obj-$(CONFIG_I2C_ELEKTOR) += i2c-elektor.o
It is not SMBus, but still PC (ISA).
Does ISA imply PC? I don't think so. Also, this is a do-it-yourself adapter for hobbyists if I remember correctly, not something you can find in a regular PC. So having it in the "PC" group would be confusing. If anything, I'd rather move it to the "External" group, even though it doesn't fit there perfectly either.
Quoted 2 lines
Quoted 1 line
obj-$(CONFIG_I2C_CPM) += i2c-cpm.o
Embedded.
Done.
Quoted 5 lines
Quoted 4 lines
obj-$(CONFIG_I2C_IBM_IIC) += i2c-ibm_iic.o
obj-$(CONFIG_I2C_IOP3XX) += i2c-iop3xx.o
obj-$(CONFIG_I2C_ISCH) += i2c-isch.o
obj-$(CONFIG_I2C_MPC) += i2c-mpc.oEmbedded.
Done.
Quoted 5 lines
Quoted 4 lines
obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o
obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o
obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o
obj-$(CONFIG_I2C_PCA_ISA) += i2c-pca-isa.oIt is not SMBus, but still PC (ISA).
Again, ISA doesn't imply PC. I seem to recall that this particular driver was written by someone NOT on a PC. Note that this driver will probably be deprecated someday anyway as the i2c-pca-platform is simply better.
Quoted 3 lines
Quoted 1 line
obj-$(CONFIG_I2C_PCA_PLATFORM) += i2c-pca-platform.o
External means probably: Connected via some bus? This one is just memory mapped...
External means outside of the computer. In practice: connected to a parallel port, serial port or USB port.
Quoted 4 lines
Quoted 3 lines
obj-$(CONFIG_I2C_PMCMSP) += i2c-pmcmsp.o
obj-$(CONFIG_I2C_PNX) += i2c-pnx.o
obj-$(CONFIG_I2C_SH7760) += i2c-sh7760.oEmbedded.
Done.
Quoted 2 lines
Quoted 1 line
obj-$(CONFIG_I2C_SH_MOBILE) += i2c-sh_mobile.o
Embedded.
Done.
Quoted 2 lines
Quoted 1 line
obj-$(CONFIG_I2C_SIBYTE) += i2c-sibyte.o
PC? Looking at
MODULE_DESCRIPTION.
No, it's a MIPS thing. Probably embedded but I don't know for sure.
Quoted 6 lines
Quoted 6 lines
obj-$(CONFIG_I2C_SIMTEC) += i2c-simtec.o
obj-$(CONFIG_I2C_STUB) += i2c-stub.o
obj-$(CONFIG_SCx200_ACB) += scx200_acb.o
obj-$(CONFIG_SCx200_I2C) += scx200_i2c.o(Of course,
Kconfighas similar groups.)
Thanks for your contribution!
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
"Jean" == Jean Delvare <[email protected]> writes:
obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o
obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o
Ocores should probably also be embedded.
Signature · 6 lines
Bye, Peter Korsgaard _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 10 lines · Jean Delvare
Hi all,
As was mentioned previously, I have decided to group the i2c bus drivers to make it easier for the users to know what they need (and also for me to know what drivers might be affected by a given problem.) Here is the list I have at the moment. There are still many drivers in the "Other" category. I suspect that many of these should move to the "Embedded" category, but I don't know for sure. So I would welcome comments and suggestions for improvements.
[ snip ]
Quoted 2 lines
obj-$(CONFIG_SCx200_ACB) += scx200_acb.o
obj-$(CONFIG_SCx200_I2C) += scx200_i2c.o
SCx200 are Geode GX/LX devices, so I think it also can be moved to embedded.
Quoted 3 lines
(Of course,
Kconfighas similar groups.)Thanks,
Signature · 8 lines
Sincerely yours, Mike. _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 11 lines · Jean Delvare
Hi all,
As was mentioned previously, I have decided to group the i2c bus drivers to make it easier for the users to know what they need (and also for me to know what drivers might be affected by a given problem.) Here is the list I have at the moment. There are still many drivers in the "Other" category. I suspect that many of these should move to the "Embedded" category, but I don't know for sure. So I would welcome comments and suggestions for improvements.
Quoted 6 lines
# Other I2C/SMBus bus drivers
obj-$(CONFIG_I2C_AU1550) += i2c-au1550.o
obj-$(CONFIG_I2C_IOP3XX) += i2c-iop3xx.o
obj-$(CONFIG_I2C_SIMTEC) += i2c-simtec.o
Wolfram picked others, these are embedded too.
Quoted 1 line
obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o
I'm not sure if one would classify pa semi dualcore 2GHz systems as "embedded", but this i2c controller is embedded into the PA SEMI cpu..
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 7 lines · Jean Delvare
# Other I2C/SMBus bus drivers
obj-$(CONFIG_I2C_ACORN) += i2c-acorn.o
obj-$(CONFIG_I2C_AU1550) += i2c-au1550.o
obj-$(CONFIG_I2C_BLACKFIN_TWI) += i2c-bfin-twi.o
obj-$(CONFIG_I2C_ELEKTOR) += i2c-elektor.o
obj-$(CONFIG_I2C_CPM) += i2c-cpm.o
obj-$(CONFIG_I2C_IBM_IIC) += i2c-ibm_iic.o
IBM-I2C is embedded too. It's used on IBM/AMCC PPC4xx embedded PPC's. Perhaps it would sense to rename this driver to i2c-ppc4xx at some time.
Best regards,
Stefan
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 6 lines · Peter Korsgaard
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
"Jean" == Jean Delvare <[email protected]> writes:
obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o
obj-$(CONFIG_I2C_OCORES) += i2c-ocores.oOcores should probably also be embedded.
Done, thanks.
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 11 lines · Stefan Roese
Quoted 7 lines · Jean Delvare
# Other I2C/SMBus bus drivers
obj-$(CONFIG_I2C_ACORN) += i2c-acorn.o
obj-$(CONFIG_I2C_AU1550) += i2c-au1550.o
obj-$(CONFIG_I2C_BLACKFIN_TWI) += i2c-bfin-twi.o
obj-$(CONFIG_I2C_ELEKTOR) += i2c-elektor.o
obj-$(CONFIG_I2C_CPM) += i2c-cpm.o
obj-$(CONFIG_I2C_IBM_IIC) += i2c-ibm_iic.oIBM-I2C is embedded too. It's used on IBM/AMCC PPC4xx embedded PPC's. Perhaps it would sense to rename this driver to i2c-ppc4xx at some time.
Done, thanks. I wouldn't object to the driver being renamed, i2c-ibm_iic always sounded pretty odd to me.
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 12 lines · Riku Voipio
Quoted 11 lines · Jean Delvare
Hi all,
As was mentioned previously, I have decided to group the i2c bus drivers to make it easier for the users to know what they need (and also for me to know what drivers might be affected by a given problem.) Here is the list I have at the moment. There are still many drivers in the "Other" category. I suspect that many of these should move to the "Embedded" category, but I don't know for sure. So I would welcome comments and suggestions for improvements.
Quoted 7 lines
Quoted 6 lines
# Other I2C/SMBus bus drivers
obj-$(CONFIG_I2C_AU1550) += i2c-au1550.o
obj-$(CONFIG_I2C_IOP3XX) += i2c-iop3xx.o
obj-$(CONFIG_I2C_SIMTEC) += i2c-simtec.oWolfram picked others, these are embedded too.
Done, thanks.
Quoted 5 lines
Quoted 1 line
obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o
I'm not sure if one would classify pa semi dualcore 2GHz systems as "embedded", but this i2c controller is embedded into the PA SEMI cpu..
By "embedded", I had "embedded systems" in mind, not whether the I2C controller was part of the CPU. So it's down to: what systems are using the PA Semi hardware.
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 4 lines · Jean Delvare
Quoted 3 lines · Riku Voipio
Quoted 1 line · Jean Delvare
obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o
Quoted 8 lines
Quoted 3 lines
I'm not sure if one would classify pa semi dualcore 2GHz systems as "embedded", but this i2c controller is embedded into the PA SEMI cpu..
By "embedded", I had "embedded systems" in mind, not whether the I2C controller was part of the CPU. So it's down to: what systems are using the PA Semi hardware.
I think neither notion of 'embedded' really does the right seperation for the link order problem.
The actual question is: "do we need the bus for early system initialization". Therfore we should maybe call this group of drivers "I2C system bus drivers".
Uli
Signature · 17 lines
------- ROAD ...the handyPC Company - - - ) ) ) Uli Luckas Software Development ROAD GmbH Bennigsenstr. 14 | 12159 Berlin | Germany fon: +49 (30) 230069 - 64 | fax: +49 (30) 230069 - 69 url: www.road.de Amtsgericht Charlottenburg: HRB 96688 B Managing directors: Hans-Peter Constien, Hubertus von Streit _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 1 line · Jean Delvare
obj-$(CONFIG_I2C_IOP3XX) += i2c-iop3xx.o
This is another SoC processor so probably ought to be embedded.
Signature · 6 lines
"You grabbed my hand and we fell into it, like a daydream - or a fever." _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 4 lines · Jean Delvare
Quoted 2 lines · Riku Voipio
Quoted 1 line · Jean Delvare
Hi all,
Quoted 8 lines
Quoted 3 lines
I'm not sure if one would classify pa semi dualcore 2GHz systems as "embedded", but this i2c controller is embedded into the PA SEMI cpu..
By "embedded", I had "embedded systems" in mind, not whether the I2C controller was part of the CPU. So it's down to: what systems are using the PA Semi hardware.
You could always call it embedded/system on chip.
~Ryan
Signature · 13 lines
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon Unit 5, Amuri Park
Phone: +64 3 3779127 404 Barbadoes St
Fax: +64 3 3779135 PO Box 13 889
Email: ryan-7Wk5F4Od5/[email protected] Christchurch, 8013
Web: http://www.bluewatersys.com New Zealand
Freecall Australia 1800 148 751 USA 1800 261 2934
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2cHi Mike,
Quoted 12 lines · Mike Rapoport
Quoted 10 lines · Jean Delvare
Hi all,
As was mentioned previously, I have decided to group the i2c bus drivers to make it easier for the users to know what they need (and also for me to know what drivers might be affected by a given problem.) Here is the list I have at the moment. There are still many drivers in the "Other" category. I suspect that many of these should move to the "Embedded" category, but I don't know for sure. So I would welcome comments and suggestions for improvements.
Quoted 6 lines
[ snip ]
Quoted 2 lines
obj-$(CONFIG_SCx200_ACB) += scx200_acb.o
obj-$(CONFIG_SCx200_I2C) += scx200_i2c.oSCx200 are Geode GX/LX devices, so I think it also can be moved to embedded.
As far as I know, the Geode uses I2C as a peripheral bus, much like PCs do, not a system bus as most embedded systems do. So, in the light of other discussions in this thread, it's probably better to not put these drivers in the "embedded" category (which might in turn be renamed to "System I2C host controller drivers (mostly embedded)" or similar.)
But honestly I'm not too sure what to do. Grouping by functionality makes sense for the user, but grouping by bus usage makes more sense if we end up splitting the bus drivers depending on the time at which they need to come up.
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
Quoted 19 lines · Jean Delvare
Hi Mike,
Quoted 16 lines · Mike Rapoport
Quoted 9 lines · Jean Delvare
Hi all,
As was mentioned previously, I have decided to group the i2c bus drivers to make it easier for the users to know what they need (and also for me to know what drivers might be affected by a given problem.) Here is the list I have at the moment. There are still many drivers in the "Other" category. I suspect that many of these should move to the "Embedded" category, but I don't know for sure. So I would welcome comments and suggestions for improvements.
[ snip ]
Quoted 2 lines
obj-$(CONFIG_SCx200_ACB) += scx200_acb.o
obj-$(CONFIG_SCx200_I2C) += scx200_i2c.o
Quoted 9 lines
Quoted 2 lines
SCx200 are Geode GX/LX devices, so I think it also can be moved to embedded.
As far as I know, the Geode uses I2C as a peripheral bus, much like PCs do, not a system bus as most embedded systems do. So, in the light of other discussions in this thread, it's probably better to not put these drivers in the "embedded" category (which might in turn be renamed to "System I2C host controller drivers (mostly embedded)" or similar.)
I fully agree. Using the embedded classification already lead to confusion in the subthread started by Riku Voipio (See my comment in that subthread)
Quoted 4 lines
But honestly I'm not too sure what to do. Grouping by functionality makes sense for the user, but grouping by bus usage makes more sense if we end up splitting the bus drivers depending on the time at which they need to come up.
We are talking about source code layout. I am not an expert for Kconfig but I guess we can present the drivers to the user in a completely source tree layout independent fashion.
regards,
Uli
Signature · 17 lines
------- ROAD ...the handyPC Company - - - ) ) ) Uli Luckas Software Development ROAD GmbH Bennigsenstr. 14 | 12159 Berlin | Germany fon: +49 (30) 230069 - 64 | fax: +49 (30) 230069 - 69 url: www.road.de Amtsgericht Charlottenburg: HRB 96688 B Managing directors: Hans-Peter Constien, Hubertus von Streit _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c