* Grouping i2c bus drivers
@ 2008-06-27 12:52 Jean Delvare
[not found] ` <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
0 siblings, 1 reply; 15+ messages in thread
From: Jean Delvare @ 2008-06-27 12:52 UTC (permalink / raw)
To: Linux I2C
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,
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
^ permalink raw reply [flat|nested] 15+ messages in thread[parent not found: <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> @ 2008-06-27 13:44 ` Wolfram Sang [not found] ` <20080627134436.GC3931-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2008-06-30 9:56 ` Mike Rapoport ` (3 subsequent siblings) 4 siblings, 1 reply; 15+ messages in thread From: Wolfram Sang @ 2008-06-27 13:44 UTC (permalink / raw) To: Jean Delvare; +Cc: Linux I2C [-- Attachment #1.1: Type: text/plain, Size: 3919 bytes --] Hi Jean, On Fri, Jun 27, 2008 at 02:52:36PM +0200, Jean Delvare wrote: > 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: > > # 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 Embedded. > obj-$(CONFIG_I2C_ELEKTOR) += i2c-elektor.o It is not SMBus, but still PC (ISA). > obj-$(CONFIG_I2C_CPM) += i2c-cpm.o Embedded. > 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. > 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). > obj-$(CONFIG_I2C_PCA_PLATFORM) += i2c-pca-platform.o External means probably: Connected via some bus? This one is just memory mapped... > obj-$(CONFIG_I2C_PMCMSP) += i2c-pmcmsp.o > obj-$(CONFIG_I2C_PNX) += i2c-pnx.o > obj-$(CONFIG_I2C_SH7760) += i2c-sh7760.o Embedded. > obj-$(CONFIG_I2C_SH_MOBILE) += i2c-sh_mobile.o Embedded. > obj-$(CONFIG_I2C_SIBYTE) += i2c-sibyte.o PC? Looking at MODULE_DESCRIPTION. > 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, > -- > Jean Delvare > > _______________________________________________ > i2c mailing list > i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org > http://lists.lm-sensors.org/mailman/listinfo/i2c -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 189 bytes --] [-- Attachment #2: Type: text/plain, Size: 157 bytes --] _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <20080627134436.GC3931-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <20080627134436.GC3931-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> @ 2008-06-28 8:58 ` Jean Delvare [not found] ` <20080628105850.2c56f1a2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> 0 siblings, 1 reply; 15+ messages in thread From: Jean Delvare @ 2008-06-28 8:58 UTC (permalink / raw) To: Wolfram Sang; +Cc: Linux I2C Hi Wolfram, On Fri, 27 Jun 2008 15:44:36 +0200, Wolfram Sang wrote: > On Fri, Jun 27, 2008 at 02:52:36PM +0200, Jean Delvare wrote: > > 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: > > > > > # 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 > Embedded. Done. > > 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. > > obj-$(CONFIG_I2C_CPM) += i2c-cpm.o > Embedded. Done. > > 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. Done. > > 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). 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. > > 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. > > obj-$(CONFIG_I2C_PMCMSP) += i2c-pmcmsp.o > > obj-$(CONFIG_I2C_PNX) += i2c-pnx.o > > obj-$(CONFIG_I2C_SH7760) += i2c-sh7760.o > Embedded. Done. > > obj-$(CONFIG_I2C_SH_MOBILE) += i2c-sh_mobile.o > Embedded. Done. > > 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. > > 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 for your contribution! -- Jean Delvare _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <20080628105850.2c56f1a2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <20080628105850.2c56f1a2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> @ 2008-06-30 9:01 ` Peter Korsgaard [not found] ` <87d4lzjnzl.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org> 0 siblings, 1 reply; 15+ messages in thread From: Peter Korsgaard @ 2008-06-30 9:01 UTC (permalink / raw) To: Jean Delvare; +Cc: Linux I2C >>>>> "Jean" == Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> writes: >> > obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o >> > obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o Ocores should probably also be embedded. -- Bye, Peter Korsgaard _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <87d4lzjnzl.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <87d4lzjnzl.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org> @ 2008-06-30 12:45 ` Jean Delvare 0 siblings, 0 replies; 15+ messages in thread From: Jean Delvare @ 2008-06-30 12:45 UTC (permalink / raw) To: Peter Korsgaard; +Cc: Linux I2C On Mon, 30 Jun 2008 11:01:02 +0200, Peter Korsgaard wrote: > >>>>> "Jean" == Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> writes: > > >> > obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o > >> > obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o > > Ocores should probably also be embedded. Done, thanks. -- Jean Delvare _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Grouping i2c bus drivers [not found] ` <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> 2008-06-27 13:44 ` Wolfram Sang @ 2008-06-30 9:56 ` Mike Rapoport [not found] ` <4868ADCD.3080305-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org> 2008-06-30 11:06 ` Riku Voipio ` (2 subsequent siblings) 4 siblings, 1 reply; 15+ messages in thread From: Mike Rapoport @ 2008-06-30 9:56 UTC (permalink / raw) To: Jean Delvare; +Cc: Linux I2C Jean Delvare wrote: > 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 ] > 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. > (Of course, Kconfig has similar groups.) > > Thanks, -- Sincerely yours, Mike. _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <4868ADCD.3080305-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <4868ADCD.3080305-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org> @ 2008-07-02 14:42 ` Jean Delvare [not found] ` <20080702164207.76304a01-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> 0 siblings, 1 reply; 15+ messages in thread From: Jean Delvare @ 2008-07-02 14:42 UTC (permalink / raw) To: Mike Rapoport; +Cc: Linux I2C Hi Mike, On Mon, 30 Jun 2008 12:56:29 +0300, Mike Rapoport wrote: > Jean Delvare wrote: > > 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 ] > > > 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. 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. -- Jean Delvare _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <20080702164207.76304a01-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <20080702164207.76304a01-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> @ 2008-07-02 18:09 ` Uli Luckas 0 siblings, 0 replies; 15+ messages in thread From: Uli Luckas @ 2008-07-02 18:09 UTC (permalink / raw) To: i2c-GZX6beZjE8VD60Wz+7aTrA On Wednesday, 2. July 2008, Jean Delvare wrote: > Hi Mike, > > On Mon, 30 Jun 2008 12:56:29 +0300, Mike Rapoport wrote: > > Jean Delvare wrote: > > > 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 ] > > > > > 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. > > 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) > 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 -- ------- 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 i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Grouping i2c bus drivers [not found] ` <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> 2008-06-27 13:44 ` Wolfram Sang 2008-06-30 9:56 ` Mike Rapoport @ 2008-06-30 11:06 ` Riku Voipio [not found] ` <4868BE37.1090405-WgUW+8SLYMv1KXRcyAk9cg@public.gmane.org> 2008-06-30 11:46 ` Stefan Roese 2008-06-30 15:29 ` Mark Brown 4 siblings, 1 reply; 15+ messages in thread From: Riku Voipio @ 2008-06-30 11:06 UTC (permalink / raw) To: Jean Delvare; +Cc: Linux I2C Jean Delvare wrote: > 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. > > > # 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. > 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 i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <4868BE37.1090405-WgUW+8SLYMv1KXRcyAk9cg@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <4868BE37.1090405-WgUW+8SLYMv1KXRcyAk9cg@public.gmane.org> @ 2008-06-30 12:55 ` Jean Delvare [not found] ` <20080630145532.5a8452b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> 0 siblings, 1 reply; 15+ messages in thread From: Jean Delvare @ 2008-06-30 12:55 UTC (permalink / raw) To: Riku Voipio; +Cc: Linux I2C On Mon, 30 Jun 2008 14:06:31 +0300, Riku Voipio wrote: > Jean Delvare wrote: > > 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. > > > > > > # 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. Done, thanks. > > 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. -- Jean Delvare _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <20080630145532.5a8452b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <20080630145532.5a8452b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> @ 2008-06-30 14:04 ` Uli Luckas 2008-06-30 20:27 ` Ryan Mallon 1 sibling, 0 replies; 15+ messages in thread From: Uli Luckas @ 2008-06-30 14:04 UTC (permalink / raw) To: i2c-GZX6beZjE8VD60Wz+7aTrA On Monday, 30. June 2008, Jean Delvare wrote: > On Mon, 30 Jun 2008 14:06:31 +0300, Riku Voipio wrote: > > Jean Delvare wrote: > > > 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. > 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 -- ------- 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 i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Grouping i2c bus drivers [not found] ` <20080630145532.5a8452b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> 2008-06-30 14:04 ` Uli Luckas @ 2008-06-30 20:27 ` Ryan Mallon 1 sibling, 0 replies; 15+ messages in thread From: Ryan Mallon @ 2008-06-30 20:27 UTC (permalink / raw) To: Jean Delvare; +Cc: Linux I2C Jean Delvare wrote: > On Mon, 30 Jun 2008 14:06:31 +0300, Riku Voipio wrote: >> Jean Delvare wrote: >>> Hi all, >> 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 -- 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/oYd5yxfr4S2w@public.gmane.org Christchurch, 8013 Web: http://www.bluewatersys.com New Zealand Freecall Australia 1800 148 751 USA 1800 261 2934 _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Grouping i2c bus drivers [not found] ` <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> ` (2 preceding siblings ...) 2008-06-30 11:06 ` Riku Voipio @ 2008-06-30 11:46 ` Stefan Roese [not found] ` <200806301346.53185.sr-ynQEQJNshbs@public.gmane.org> 2008-06-30 15:29 ` Mark Brown 4 siblings, 1 reply; 15+ messages in thread From: Stefan Roese @ 2008-06-30 11:46 UTC (permalink / raw) To: i2c-GZX6beZjE8VD60Wz+7aTrA On Friday 27 June 2008, Jean Delvare wrote: > # 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 i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <200806301346.53185.sr-ynQEQJNshbs@public.gmane.org>]
* Re: Grouping i2c bus drivers [not found] ` <200806301346.53185.sr-ynQEQJNshbs@public.gmane.org> @ 2008-06-30 12:49 ` Jean Delvare 0 siblings, 0 replies; 15+ messages in thread From: Jean Delvare @ 2008-06-30 12:49 UTC (permalink / raw) To: Stefan Roese; +Cc: i2c-GZX6beZjE8VD60Wz+7aTrA On Mon, 30 Jun 2008 13:46:53 +0200, Stefan Roese wrote: > On Friday 27 June 2008, Jean Delvare wrote: > > # 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. Done, thanks. I wouldn't object to the driver being renamed, i2c-ibm_iic always sounded pretty odd to me. -- Jean Delvare _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Grouping i2c bus drivers [not found] ` <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> ` (3 preceding siblings ...) 2008-06-30 11:46 ` Stefan Roese @ 2008-06-30 15:29 ` Mark Brown 4 siblings, 0 replies; 15+ messages in thread From: Mark Brown @ 2008-06-30 15:29 UTC (permalink / raw) To: Jean Delvare; +Cc: Linux I2C On Fri, Jun 27, 2008 at 02:52:36PM +0200, Jean Delvare wrote: > obj-$(CONFIG_I2C_IOP3XX) += i2c-iop3xx.o This is another SoC processor so probably ought to be embedded. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c ^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2008-07-02 18:09 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-27 12:52 Grouping i2c bus drivers Jean Delvare
[not found] ` <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-27 13:44 ` Wolfram Sang
[not found] ` <20080627134436.GC3931-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-06-28 8:58 ` Jean Delvare
[not found] ` <20080628105850.2c56f1a2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-30 9:01 ` Peter Korsgaard
[not found] ` <87d4lzjnzl.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2008-06-30 12:45 ` Jean Delvare
2008-06-30 9:56 ` Mike Rapoport
[not found] ` <4868ADCD.3080305-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2008-07-02 14:42 ` Jean Delvare
[not found] ` <20080702164207.76304a01-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-02 18:09 ` Uli Luckas
2008-06-30 11:06 ` Riku Voipio
[not found] ` <4868BE37.1090405-WgUW+8SLYMv1KXRcyAk9cg@public.gmane.org>
2008-06-30 12:55 ` Jean Delvare
[not found] ` <20080630145532.5a8452b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-30 14:04 ` Uli Luckas
2008-06-30 20:27 ` Ryan Mallon
2008-06-30 11:46 ` Stefan Roese
[not found] ` <200806301346.53185.sr-ynQEQJNshbs@public.gmane.org>
2008-06-30 12:49 ` Jean Delvare
2008-06-30 15:29 ` Mark Brown
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox