1. 06 Jan, 2005 8 commits
    • Deepak Saxena's avatar
      [PATCH] Update IOP3xx I2C bus driver · 57683a86
      Deepak Saxena authored
      The following patch is a major cleanup of the IOP3xx I2C bus driver
      that is found on Intel's IOP and IXP chipsets. The existing driver in
      the 2.6 tree uses hardcoded I/O addresses based on board configuration
      which is just going to get ugly as more chips use this unit. The update
      switches to using the driver model and passing in the I/O addresses
      via platform_device resources. The patch also updates the ID name to
      more closely match the actual usage of the device.
      
      I have tested this new driver on IXP46x systems and Dave Jiang has
      tested it on both IOP321 and IOP331 systems. ARM-specific patches
      to provide platform-level hooks will go upstream after this patch
      is integrated.
      
      An example of using the new driver (from IXP46x ARM code) follows:
      
      static struct resource ixp46x_i2c_resources[] = {
      	[0] = {
      		.start 	= 0xc8011000,
      		.end	= 0xc801101c,
      		.flags	= IORESOURCE_MEM,
      	},
      	[1] = {
      		.start 	= IRQ_IXP4XX_I2C,
      		.end	= IRQ_IXP4XX_I2C,
      		.flags	= IORESOURCE_IRQ
      	}
      };
      
      static struct platform_device ixp46x_i2c_controller = {
      	.name		= "IOP3xx-I2C",
      	.id		= 0,
      	.num_resources	= 2,
      	.resource	= &ixp46x_i2c_resources
      };
      
      static struct platform_device *ixp46x_devices[] __initdata = {
      	&ixp46x_i2c_controller
      };
      
      void __init ixp4xx_init(void)
      {
      	if (cpu_is_ixp46x()) {
      		platform_add_devices(ixp46x_devices,
      				ARRAY_SIZE(ixp46x_devices));
      	}
      }
      Signed-off-by: default avatarDeepak Saxena <dsaxena@plexity.net>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      57683a86
    • Jean Delvare's avatar
      [PATCH] I2C: Update fscher pwm functionality · 3e4e4173
      Jean Delvare authored
      This is a small update to the fscher hardware monitoring chip driver.
      More specifically it fixes two aspects of pwm:
      1* Use the new sysfs names (e.g. pwm1 instead of fan1_pwm).
      2* Better handling of out-of-range pwm values.
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      3e4e4173
    • David Brownell's avatar
      [PATCH] I2C: minor isp1301_omap tweaks · bc6f328c
      David Brownell authored
      Minor cleanups to the isp130_omap driver:  enable the right
      amount of VBUS current draw in non-OTG configurations; get rid
      of a warning from GCC 2.95.3 ("int" function returns no value);
      use kcalloc() not kmalloc+memset.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      bc6f328c
    • Jean Delvare's avatar
      [PATCH] I2C: Add byte commands to i2c-stub · 7413482b
      Jean Delvare authored
      While working on EEPROMs, DDC/EDID and the like these last few days, I
      wanted to use your i2c-stub driver to test my code. However, I noticed
      that it wouldn't handle byte commands, while both i2cdetect and the
      eeprom driver need it for proper operation. Thus I added this
      functionality to the driver. What do you think about it?
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      7413482b
    • Jean Delvare's avatar
      [PATCH] I2C: Fix MAX6657/8/9 detection in lm90 · 14f4eefa
      Jean Delvare authored
      I received no additional feedback about my MAX6657/8/9 detection fix.
      Since it was correct for the only chips I got a report for, I propose we
      apply it. After all, maybe people don't know they have such a chip
      because the detection was previously not correct.
      
      The patch below is the one I sent to the LM Sensors and Linux Kernel
      mailing-lists two weeks ago, unchanged. Thanks.
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      14f4eefa
    • Jean Delvare's avatar
      [PATCH] I2C: Improve VID code for the W83627THF · d3b02eff
      Jean Delvare authored
      This patch cleans up and improves the VID pins value retrieval for the
      W83627THF chip in the w83627hf driver. Tested successfully by Mark
      Hoffman. The previous code was using an unrelated lock and reading
      register values it didn't need. The new code supports 6-bit VID values
      (as defined by Intel VRM 10), and also ensures that the GPIO pins are
      possibly used as VID inputs.
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      d3b02eff
    • Jean Delvare's avatar
      [PATCH] I2C: Add secondary Super-I/O address support to · 3923b4dc
      Jean Delvare authored
      This patch adds support for the secondary Super-I/O address to the
      w83627hf driver. Most manufacturer use the primary address but at least
      the EPoX EP-9NDA3+ had a Winbond W83627THF at the secondary address.
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      3923b4dc
    • Mark M. Hoffman's avatar
      [PATCH] I2C: probe fewer addresses for asb100 (sensors) driver · 49054393
      Mark M. Hoffman authored
      This patch limits SMBus scanning for the asb100 sensor chip
      to just one address - the only one we've ever seen in practice.
      
      Signed-off-by Mark M. Hoffman <mhoffman@lightlink.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      49054393
  2. 22 Dec, 2004 2 commits
  3. 21 Dec, 2004 15 commits
  4. 20 Dec, 2004 5 commits
    • Andi Kleen's avatar
      [PATCH] x86_64: fix syscall/signal restart bug · 0233f53f
      Andi Kleen authored
      Fix a pretty bad bug that caused sometimes signals on x86-64
      to be restarted like system calls. This corrupted the RIP and
      in general caused undesirable effects.
      
      The problem happens because orig_rax is unsigned on x86-64,
      but it originally was signed when the signal code was written.
      And the if (orig_rax >= 0) ended up always true.
      And gcc didn't warn about this, because the warning is only in 
      -Wextra. 
      
      In 2.4 we still had a cast for it, but somehow it got dropped
      in 2.5.
      
      Credit goes to John Slice for tracking it down and Erich Boleyn
      for the original fix. All blame to me. I fixed it at another
      place too.
      Signed-off-by: default avatarAndi Kleen <ak@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      0233f53f
    • Thomas Graf's avatar
      [PKT_SCHED]: Provide compat policer stats in action policer · 59b17c27
      Thomas Graf authored
      This should go in before 2.6.10. It fixes a forgotten case to provide
      police backward compatibility statistics for old iproute2 versions
      running on a new kernel with actions enabled. Should make distributions
      happy with older iproute2 versions and all-included kernel configs
      since they probably favour actions over plain policer.
      
      Testing results:
        iproute2-2.4.7 on 2.6.10-rc3-bk8:
        cls-police: police creation succeeded
        cls-police: Sending 10 ICMP echo requests
        cls-police: police dumping succeeded with output:
        filter protocol ip pref 10 u32 
        filter protocol ip pref 10 u32 fh 800: ht divisor 1 
        filter protocol ip pref 10 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 10:12 
        police 3 action drop rate 2Kbit burst 10Kb mtu 2Kb 
          match 00010000/00ff0000 at 8
         Sent 420 bytes 10 pkts (dropped 0, overlimits 0)  <-- This would have been missing
        cls-police: police deletion succeeded
      
       iproute2-2.6.9 on 2.6.10-rc3-bk8:
       ...
        filter protocol ip pref 10 u32 
        filter protocol ip pref 10 u32 fh 800: ht divisor 1 
        filter protocol ip pref 10 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 10:12  (rule hit 10 success 10)
          match 00010000/00ff0000 at 8 (success 10 ) 
         police 0x4 rate 2000bit burst 10Kb mtu 2Kb action drop 
        ref 1 bind 1
         Sent 420 bytes 10 pkts (dropped 0, overlimits 0) 
       ...
      
       (Same results for fw classifier)
      Signed-off-by: default avatarThomas Graf <tgraf@suug.ch>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      59b17c27
    • Thomas Graf's avatar
      [PKT_SCHED]: Fix double locking in tcindex destroy path. · ee6fa69b
      Thomas Graf authored
      tcindex's destroy uses its own delete functions to destroy its
      configuration. The delete function (correctly) takes the qdisc_tree_lock
      to prevent list walkings from happening while removing from the list.
      The qdisc_tree_lock is already held if we're comming via the destroy
      path and thus a double locking takes place.
      Signed-off-by: default avatarThomas Graf <tgraf@suug.ch>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ee6fa69b
    • Stephen Hemminger's avatar
    • Linus Torvalds's avatar
      Merge bk://linux-scsi.bkbits.net/scsi-for-linus-2.6 · 39509e47
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.6/linux
      39509e47
  5. 18 Dec, 2004 3 commits
  6. 17 Dec, 2004 7 commits