1. 14 Jan, 2004 11 commits
    • Jean Delvare's avatar
      [PATCH] I2C: Fix w83781d temp · c5de19fc
      Jean Delvare authored
      This patch fixes the temperature handling in the w83781d driver:
      1* Fix bad magnitude.
      2* Use MMH's lm75.h.
      3* Allow negative temperatures.
      c5de19fc
    • Jean Delvare's avatar
      [PATCH] I2C: New chip driver: lm90 · 1c607b39
      Jean Delvare authored
      This is my LM90/ADM1032 i2c chip driver ported to Linux 2.6
      1c607b39
    • Jean Delvare's avatar
      [PATCH] I2C: New parport bus drivers · e4de8405
      Jean Delvare authored
      These are replacements for the i2c-philips-par, i2c-elv and i2c-velleman
      drivers, as well as for the i2c-old i2c-parport driver as found under
      drivers/media/video in linux 2.4. My reason for writing them, as already
      discussed on the sensors and linux-kernel mailing-lists, is that all
      these drivers basically do the same thing, so I thought it would be
      easier to maintain a single driver instead of four. As Simon Vogl
      pointed out that using a direct I/O access (as done in i2c-elv and
      i2c-velleman) could be prefered over clean parport access (as done in
      i2c-philips-par) on embedded devices, I finally wrote two drivers
      instead of one. But both drivers support all devices, it's just a matter
      of how they are accessed (and wether the driver depends on the parport
      driver).
      
      I made it so that the definition of the adapters (i.e. how to set and
      get SDA and SCL, basically) is completely separated from the code
      itself. Thus, adding support for a new adapter is simply adding a new
      set of data to the definition table, describing how the adapter works,
      in a single file.
      
      This means that all simple parallel port adapters are virtually
      supported. The i2c-pport driver we have in i2c CVS isn't supported yet
      because it works a bit differently, but I believe that extending the
      current driver(s) to support it should be possible (although it can be
      discussed wether it's worth it).
      
      You'll have to pass the type parameter that is correct for your board:
       0 = Philips
       2 = Velleman
       3 = ELV
       4 = ADM evaluation board
      
      I could only test with my ADM eval board, and it worked OK with
      both drivers. If they are confirmed to work, we could get rid of all
      other parallel port i2c drivers in 2.6.
      ***
      
      I think we should mark the i2c-philips-par, i2c-elv and i2c-velleman drivers as "deprecated" in i2c/busses/Kconfig. Is there a standard way to do so (like there is "&& EXPERIMENTAL" for new drivers)?
      
      Thanks.
      e4de8405
    • Jean Delvare's avatar
      [PATCH] I2C: i2c-rpx.c doesn't need ioports.h nor parport.h · 7aea5de4
      Jean Delvare authored
      One more simple patch... These headers are useless as far as I can see.
      7aea5de4
    • Jean Delvare's avatar
      [PATCH] I2C: Typo in i2c/busses/Kconfig · 6f48ec0f
      Jean Delvare authored
      Another simple patch for your collection. BTW I don't think that i2c-rpx
      can be used in 2.6 since it relies on an algorithm that hasn't been
      ported yet.
      6f48ec0f
    • Jean Delvare's avatar
      [PATCH] I2C: saa7146.h doesn't need i2c.h · 547a3e6d
      Jean Delvare authored
      547a3e6d
    • Eugene Surovegin's avatar
      [PATCH] I2C: IBM IIC compile fix · e1dfc0be
      Eugene Surovegin authored
      please apply this trivial one-liner. It fixes compilation of IBM IIC
      driver.
      e1dfc0be
    • Mark M. Hoffman's avatar
      [PATCH] I2C: link asb100 in the proper order · 32d2c4f8
      Mark M. Hoffman authored
      * Jean Delvare <khali@linux-fr.org> [2004-01-09 22:58:58 +0100]:
      
      > Shouldn't the asb100 be listed first, the same way the w83781d is, since
      > it has subclients? I would even put asb100 before w83781d, since for now
      > the w83781d driver will try to handle ASB100 chips too, thus preventing
      > the asb100 driver from being used if both drivers are built-in.
      
      You're right, thanks
      
      * * * * *
      
      This patch fixes the link order for asb100 sensors chip driver.
      32d2c4f8
    • Mark M. Hoffman's avatar
      [PATCH] I2C: Add ported sensor chip driver: asb100 · dd7f69c7
      Mark M. Hoffman authored
      This patch adds support for the ASB100 Bach sensor chip, which
      is found on some Asus mainboards.  The port corresponds to
      lm_sensors CVS revision 1.5.  The patch applies to and was tested
      against 2.6.1-rc1.
      dd7f69c7
    • Jean Delvare's avatar
      [PATCH] I2C: documentation update · 1e272f7f
      Jean Delvare authored
      > > They should be converted.  From module.h:
      > > 	/* DEPRECATED: Do not use. */
      > > 	#define MODULE_PARM(var,type) 	\
      > > 	...
      >
      > Note that realistically, it's not going away in 2.6, so mass migration
      > doesn't really win anything.  However, I never implemented mixing old
      > and new style in the same module, so if you're adding a parameter, it
      > makes sense to convert them all.
      
      OK, I don't have much time for a mass conversion anyway. Greg, could you
      please apply the following patch to the "porting-clients" document so
      that at least the new drivers don't need to be converted afterwards?
      1e272f7f
    • Tom Rini's avatar
      [PATCH] I2C: module_parm fixes for i2c-piix4.c · b85bec13
      Tom Rini authored
      b85bec13
  2. 12 Jan, 2004 1 commit
  3. 09 Jan, 2004 3 commits
  4. 08 Jan, 2004 25 commits