1. 02 Feb, 2004 2 commits
    • Jean Delvare's avatar
      [PATCH] I2C: Handle read errors in w83l785ts · 4f91cc15
      Jean Delvare authored
      Here is a patch that adds proper read error handling in the w83l785ts
      driver. This is needed for this driver because on many Asus boards the
      BIOS or something accesses the chip in our back and causes collisions or
      something similar that causes many read errors. For now, these errors
      make the driver return temperature values of -1 from times to times.
      
      I have been working with James Bolt on this. See the thread on the
      lm_sensors mailing list for details. The patch is fairly well tested. It
      is against 2.6.2-rc3 + your current stack of patches as I know it.
      
      The "retry until it works" method is the best I could think of, since we
      have no information from Asus and I don't expect to get any. If it still
      doesn't work after an arbitrary number (5) of tries it returns the
      previously known value and generates an error in the logs. James' tests
      showed that it will probably never happen though (highest retry count
      was 3 and happened once out of 3000 reads) unless we lower the arbitrary
      number (but we don't want to, do we?)
      
      I inserted incremental delays as reads fail, I felt like it should help
      avoid collisions with whatever-is-bugging-us. Seems to work OK, but it's
      not perfect (since we sometimes need 3 retries) and I didn't test with a
      different policy (no delay, constant delay or different increment).
      4f91cc15
    • Jean Delvare's avatar
      [PATCH] I2C: Bring w83l785ts in compliance with sysfs naming conventions · 129ccc33
      Jean Delvare authored
      Here is a patch that brings the w83l785ts driver in compliance with
      sysfs naming conventions. This is pretty much the same problem and
      solution that occured very recently with the lm75 and lm78 drivers.
      
      The patch was tested to work fine by James Bolt.
      129ccc33
  2. 30 Jan, 2004 4 commits
    • David Martínez Moreno's avatar
      [PATCH] I2C: fix typos · f3e67ce5
      David Martínez Moreno authored
      Following patch fixes two typos and a missing full stop.
      f3e67ce5
    • Geert Uytterhoeven's avatar
      [PATCH] I2C: add Hydra i2c bus driver · 38b3e80a
      Geert Uytterhoeven authored
      Here's a new version, incorporating these comments, and making a few more
      changes:
        - Use struct definition in <asm/hydra.h> instead of #defined offset
        - Remove flushes are register writes, they are no longer needed
        - Use pci_resource_start() instead of dev->resource[].start
        - ioremap() the whole resource instead of the first 256 bytes
        - Check for errors returned by ioremap() and i2c_bit_add_bus()
        - Add resource management
        - Call iounmap() in hydra_remove() instead of in i2c_hydra_exit()
        - Let I2C_HYDRA depend on I2C and select I2C_ALGOBIT instead of depending on
          I2C_ALGOBIT
      38b3e80a
    • Michael Hunold's avatar
      [PATCH] dvb subsystem and saa7146 v4l fixes · 586a9edd
      Michael Hunold authored
      This fixes some issues in the dvb subsystem and some nasty things in the
      v4l saa7146 driver.
      
      [DVB]
       - dvb-core: aquire -> acquire spelling fix
       - nxt600 frontend: don't send zero-byte messages when probing the PLL
         type
       - Kconfig: add a note that says that the CI of the budget-CI card is
         not actually supported by the budget-CI driver
       - ttusb-dec: Check for presence of crc32 function.  Make unknown types
         of packet less likely to cause packet loss.
      
      [V4L]
       - saa7146: use kernel mint_t()/max_t() instead of homebrewn stuff
       - saa7146: disable video clipping before capturing for sure to prevent
         black pictures
       - saa7146: make sure to disable the right video dma upon device close
       - saa7146: don't free resources if disabling an already disabled video
         overlay
      586a9edd
    • Dominik Brodowski's avatar
      [PATCH] Validate ACPI CPU frequency values · a71d72ce
      Dominik Brodowski authored
      This is a simple fix for some of the problems with bad ACPI frequency values:
      
        Abort if the frequency field in _PSS is zero, as we're having a
        completely broken ACPI table then.
      
      A more complete overhaul of the acpi-cpufreq driver (where the cause of
      the problem lies) is in the latest acpi-test tree, but that's definitely
      something to be delayed for 2.6.3 -- and the same is true for the
      yet-to-be-written do_div64 conversion.
      a71d72ce
  3. 29 Jan, 2004 19 commits
    • Michael Schierl's avatar
      [PATCH] [APM] Is this the correct way to fix suspend bug introduced · 87903ac5
      Michael Schierl authored
      This fixes my APM problems (without them my laptop, Acer TravelMate
      210TEV (Celeron 700, 128 MB RAM), hangs after resuming from APM since
      2.6.0-test4).
      
      Modified based on comments from Pavel Machek <pavel@suse.cz>, who
      has acked the updated patch.
      87903ac5
    • Greg Kroah-Hartman's avatar
    • Kieran Morrissey's avatar
      [PATCH] PCI: pci.ids update · 07d880ac
      Kieran Morrissey authored
      - Replaces pci.ids with a snapshot from pciids.sf.net from 14 Jan 2004
      07d880ac
    • Kieran Morrissey's avatar
      [PATCH] PCI: name length change · 6a1bd126
      Kieran Morrissey authored
      - Changes gen-devlist.c to truncate long device names rather than reject
        the database
      - Changes PCI_NAME_SIZE to 96 (and PCI_NAME_HALF to 43) to allow all
        current pci.ids names to fit
      - Modifies gen-devlist.c to truncate at 89 characters rather than 79 -
        allows for two digit instance numbers to be added to the name as well
        while staying within the 96 characters allocated. No names in the
        current pci.ids are any longer than this.
      - Modifies names.c to no longer limit device name length when displaying
        both vendor and device name; the truncation is done by gen-devlist.c.
      6a1bd126
    • John Rose's avatar
      [PATCH] PCI: Allow pci hotplug drivers to initialize individual devices. · b323e1df
      John Rose authored
      This lets the PPC pci hotplug driver initialize single devices, not just
      entire slots.
      b323e1df
    • Leann Ogasawara's avatar
      [PATCH] PCI hotplug: pcihp_zt5550.c ioremap/iounmap audit · 66f070ba
      Leann Ogasawara authored
      insert missing iounmap()
      66f070ba
    • Ralf Bächle's avatar
      68e0f3a0
    • Linda Xie's avatar
    • Takayoshi Kochi's avatar
      [PATCH] PCI Hotplug: add address file and fix acpiphp bugs · 272b06a8
      Takayoshi Kochi authored
      This is the pending patch that adds 'address' file to show
      PCI-address and a few other minor fixes.
      As 2.6.0 is out, I'm resending the patch.
      Would you mind taking this?
      
      > > > Thanks.  I had a little time to try your patch today.  Sorry
      > > > to report that it isn't working for me.
      > > >
      > > > I first powered off (successfully the 1st time) a populated slot
      > > > and removed and reinserted the card into the same slot.  The slot
      > > > powered back up but I was then unable to power it off.  I believe
      > > > the following instruction that still exists in power_off_slot()
      > > > may be preventing the slot from being powered off more than once.
      > > >     func->flags &= (~FUNC_EXISTS);
      > > >
      > > > I then tried to insert an adapter in an un-populated slot.  For
      > > > some reason (which I don't understand yet) there was an enabling
      > > > error which I believe caused enable_device() to exit via a path
      > > > that bypassed the instruction that sets the FUNC_EXISTS flag.
      > > > I was then unable to power off the slot which I believe was due
      > > > to the FUNC_EXISTS flag not being set.
      > > >
      > > > I didn't have time to definitely confirmed the above theories.
      > > > I'll take a closer look at this tomorrow unless you are able
      > > > to diagnose using my vague clues :)
      > >
      > > It turns out that both of the above mentioned problems happened
      > > because the call to acpiphp_configure_slot() from enable_device()
      > > failed after inserting the card.  When this happens enable_device()
      > > exits without setting the FUNC_EXISTS flag for any of the slot
      > > functions.  Subsequent attempts to power off the same slot fail
      > > when power_off_slot() is unable to locate a function with both
      > > FUNC_HAS_EJ0 and FUNC_EXISTS flags set.
      > >
      > > The patch works okay when using a card that allows
      > > acpiphp_configure_slot() to succeed but I believe it should
      > > be improved to allow the slot to be powered off following
      > > device enablement errors.
      >
      > Thanks for testing and comments.
      > I really appreciate it.
      >
      > This problem turned out to be somewhat fragile state
      > transition:
      >
      > a lifecycle of a slot is (if there's no error)
      >
      >   function             state
      > ----------------------------------------------------
      > 0                      nothing
      > 1  power_on_slot()  -> SLOT_POWERDON
      > 2  enable_device()  -> SLOT_POWEREDON + SLOT_ENABLED
      > 3  disable_device() -> SLOT_POWEREDON
      > 4  power_off_slot() -> nothing
      >
      > but if any error occur during enable_device(), slot will remain
      > SLOT_POWERDON, but some functions on the card may not have
      > FUNC_EXISTS flags, which will eventually prevents powering
      > off in power_off_slot(), state transition from 1 to 4 directly.
      > I.e, the FUNC_EXISTS flag introduced more states to
      > complicate things.
      >
      > The FUNC_EXISTS flag was introduced after some discussion
      > between me and Irene Zubarev, but it has no more meaning
      > than that the function has corresponding 'pci_dev' structure.
      > So I eliminated the usage of FUNC_EXISTS and the result is
      > the patches attached to this mail (for both 2.4 and 2.6.
      > I think Greg already applied the 2.4 'cleanup' patch to his tree,
      > but it's not in Marcelo's release so I'm re-attaching to
      > this mail for anyone interested in this topic.  It's identical
      > to the one I posted earlier).
      > These patches don't include Gary's patch in his post last week,
      > so please apply separately.
      >
      > Please note that current acpiphp driver cannot handle a
      > PCI card that has a PCI-to-PCI bridge on it (support
      > for such cards is incomplete).  But if it's treated as
      > an error, it should be recoverable anyway.
      272b06a8
    • Martin Hicks's avatar
      [PATCH] PCI Hotplug: Trivial warning fix · 98e2380e
      Martin Hicks authored
      This just gets rid of a stupid compile warning.
      98e2380e
    • Matthew Wilcox's avatar
      [PATCH] PCI: fix pci_get_slot() bug · 73b6196b
      Matthew Wilcox authored
      On Wed, Dec 17, 2003 at 04:24:44PM -0800, Greg KH wrote:
      > I've applied the pci portions of this patch to my trees and will send it
      > on after 2.6.0 is out.
      
      James Bottomley found a bug in it; could you also apply:
      73b6196b
    • Greg Kroah-Hartman's avatar
      [PATCH] PCI: add .owner field to the config sysfs file to be "correct" · 70d7e120
      Greg Kroah-Hartman authored
      This is in case others copy this code (which has already happened...)
      70d7e120
    • Matthew Wilcox's avatar
      [PATCH] PCI: add pci_get_slot() function · 9648e089
      Matthew Wilcox authored
      tg3.c has a bug where it can find the wrong 5704 peer on a machine with
      PCI domains.  The problem is that pci_find_slot() can't distinguish
      whether it has the correct domain or not.
      
      This patch fixes that problem by introducing pci_get_slot().
      9648e089
    • Matthew Dobson's avatar
      [PATCH] PCI: add pci_bus sysfs class · 68b308e8
      Matthew Dobson authored
      This is needed to show pci bus topology to userspace properly.
      68b308e8
    • Matthew Wilcox's avatar
      [PATCH] PCI Hotplug: Better reporting of PCI frequency / bus mode problems for acpi driver · 78d65a24
      Matthew Wilcox authored
      When plugging a 33MHz card into a bus that's running at 66MHz, I'd like
      to see a better error message than:
      
      acpiphp_glue: notify_handler: unknown event type 0x5 for \_SB_.SBA0.PCI4.S2F0
      
      The following patch would give us:
      
      Device \_SB_.SBA0.PCI4.S2F0 cannot be configured due to a frequency mismatch
      
      which I think is clearer.
      78d65a24
    • Rolf Eike Beer's avatar
      [PATCH] PCI Hotplug: Fixup pcihp_skeleton.c · b2d96267
      Rolf Eike Beer authored
      The functions are not named *_skel_*, so it seems useful not to call them with
      this.
      b2d96267
    • Russell King's avatar
      [PATCH] Prevent PCI driver registration failure oopsing · b5849a35
      Russell King authored
      Greg,
      
      As discussed about six or so months ago, we agreed to hold off this
      patch until fairly late, due to its ability to catch duplicate PCI
      driver names.  Please note that I haven't attempted to reproduce the
      problem with recent kernels, and that all ARM kernel patches released
      since then have had this patch in.
      
      I'm guessing this will actually be 2.6.1 material since it probably
      doesn't show for PCI drivers which are part of the kernel tree.
      
      
      If pci_register_driver fails, the register the PCI driver structure
      will not be registered with the driver model.  pci_register_driver
      returns with negative value, and we then attempt to unregister the
      driver structure.  This leads to an oops in the driver model.
      
      The driver model does not return the number of devices it successfully
      bound the driver to, and neither does pci_register_driver() return
      this information.
      
      Therefore, all of the code below is redundant.
      
      (There's a little redundancy left in drivers/pci/pci-driver.c but it
      is harmless unlike this block.)
      b5849a35
    • David S. Miller's avatar
    • David S. Miller's avatar
      Merge cheetah.(none):/home/davem/src/BK/sparcwork-2.6 · ad3258ed
      David S. Miller authored
      into cheetah.(none):/home/davem/src/BK/sparc-2.6
      ad3258ed
  4. 28 Jan, 2004 6 commits
  5. 27 Jan, 2004 9 commits