1. 16 10月, 2007 2 次提交
  2. 20 7月, 2007 1 次提交
  3. 12 7月, 2007 1 次提交
    • A
      PCI: Change all drivers to use pci_device->revision · 44c10138
      Auke Kok 提交于
      Instead of all drivers reading pci config space to get the revision
      ID, they can now use the pci_device->revision member.
      
      This exposes some issues where drivers where reading a word or a dword
      for the revision number, and adding useless error-handling around the
      read. Some drivers even just read it for no purpose of all.
      
      In devices where the revision ID is being copied over and used in what
      appears to be the equivalent of hotpath, I have left the copy code
      and the cached copy as not to influence the driver's performance.
      
      Compile tested with make all{yes,mod}config on x86_64 and i386.
      Signed-off-by: NAuke Kok <auke-jan.h.kok@intel.com>
      Acked-by: NDave Jones <davej@redhat.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      44c10138
  4. 11 5月, 2007 1 次提交
  5. 09 2月, 2007 2 次提交
  6. 20 12月, 2006 4 次提交
  7. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  8. 13 7月, 2006 1 次提交
  9. 03 7月, 2006 1 次提交
  10. 23 6月, 2006 3 次提交
  11. 28 4月, 2006 1 次提交
  12. 22 1月, 2006 1 次提交
  13. 03 1月, 2006 6 次提交
  14. 11 11月, 2005 1 次提交
  15. 04 11月, 2005 4 次提交
  16. 12 9月, 2005 2 次提交
    • T
      [ALSA] Replace with kzalloc() - pci stuff · e560d8d8
      Takashi Iwai 提交于
      AD1889 driver,ATIIXP driver,ATIIXP-modem driver,AZT3328 driver
      BT87x driver,CMIPCI driver,CS4281 driver,ENS1370/1+ driver
      ES1938 driver,ES1968 driver,FM801 driver,Intel8x0 driver
      Intel8x0-modem driver,Maestro3 driver,SonicVibes driver,VIA82xx driver
      VIA82xx-modem driver,AC97 Codec,AK4531 codec,au88x0 driver
      CA0106 driver,CS46xx driver,EMU10K1/EMU10K2 driver,HDA Codec driver
      HDA generic driver,HDA Intel driver,ICE1712 driver,ICE1724 driver
      KORG1212 driver,MIXART driver,NM256 driver,Trident driver,YMFPCI driver
      Replace kcalloc(1,..) with kzalloc().
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      e560d8d8
    • J
      [ALSA] snd-ca0106, snd-emu10k1: Add symlink in the sys tree. · 025cd2f6
      James Courtier-Dutton 提交于
      CA0106 driver,EMU10K1/EMU10K2 driver
      A thread appeared on the LKML. This patch implements the fix.
      
      Question:
      in sysfs, /sys/bus/*/drivers lists the driver names, with their exported .name (eg. '.name = 'EMU10K1_Audigy'' in the module code, from now on 'driver name'). In /sys/modules, the kernel modules are listed with their module name, eg. snd_emu10k1. However, it seems to me that in sysfs, there is no way in particular to tell, which module has which .name. That is, that snd_emu10k1 is EMU10K1_Audigy and vice versa.
      
      I wonder whether it wouldn't be possible to add a symlink to the particular module from the driver, and/or from the module to the driver, so the list of devices handled by the module and the module name would be accessible. This way, I would know which driver name corresponds to which module name and vice versa.
      
      Answer:
      For PCI drivers, just add the line:
      	.owner = THIS_MODULE,
      
      to their struct pci_driver definition and you will get the symlink
      created for you.
      Signed-off-by: NJames Courtier-Dutton <James@superbug.co.uk>
      025cd2f6
  17. 30 8月, 2005 1 次提交
  18. 22 6月, 2005 6 次提交
  19. 29 5月, 2005 1 次提交