1. 06 8月, 2008 1 次提交
    • P
      ALSA: snd_usb_audio: fix SB Extigy IR Remote regression · b9c196e1
      Phillip Michael Jordan 提交于
      The support for the SB Extigy's remote seems to be broken in all
      recent ALSA versions, including 1.0.17. The driver detects the event
      correctly, then submits a URB to query the RC code. On the Extigy, the
      URB is submitted with a length of 2 bytes. My hardware, however, only
      replies with 1 byte, containing the correct RC button code. The
      current implementation discards this as being too short. (line 1784 of
      usbmixer.c)
      
      This patch specifies a "minimum packet length" in the remote control
      configuration. I've left the values for the Audigy 2/Live! the same as
      the packet length, as I'm assuming the existing code works with them.
      (I don't have the hardware to confirm) This fixes the Extigy RC
      support, e.g. for use with Lirc.
      Signed-off-by: NPhillip Michael Jordan <phil@philjordan.eu>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NJaroslav Kysela <perex@perex.cz>
      b9c196e1
  2. 01 2月, 2008 2 次提交
  3. 16 10月, 2007 2 次提交
  4. 16 5月, 2007 1 次提交
  5. 09 1月, 2007 1 次提交
  6. 02 12月, 2006 1 次提交
  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. 23 9月, 2006 1 次提交
  9. 23 6月, 2006 2 次提交
  10. 31 3月, 2006 1 次提交
  11. 22 3月, 2006 2 次提交
  12. 03 1月, 2006 1 次提交
  13. 04 11月, 2005 1 次提交
  14. 12 9月, 2005 1 次提交
    • T
      [ALSA] Replace with kzalloc() - others · 561b220a
      Takashi Iwai 提交于
      Documentation,SA11xx UDA1341 driver,Generic drivers,MPU401 UART,OPL3
      OPL4,Digigram VX core,I2C cs8427,I2C lib core,I2C tea6330t,L3 drivers
      AK4114 receiver,AK4117 receiver,PDAudioCF driver,PPC PMAC driver
      SPARC AMD7930 driver,SPARC cs4231 driver,Synth,Common EMU synth
      USB generic driver,USB USX2Y
      Replace kcalloc(1,..) with kzalloc().
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      561b220a
  15. 28 7月, 2005 1 次提交
  16. 22 6月, 2005 1 次提交
    • J
      [ALSA] Remove redundant NULL checks before kfree · 4d572776
      Jesper Juhl 提交于
      Timer Midlevel,ALSA sequencer,ALSA<-OSS sequencer,Digigram VX core
      I2C tea6330t,GUS Library,VIA82xx driver,VIA82xx-modem driver
      CA0106 driver,CS46xx driver,EMU10K1/EMU10K2 driver,YMFPCI driver
      Digigram VX Pocket driver,Common EMU synth,USB generic driver,USB USX2Y
      Checking a pointer for NULL before calling kfree() on it is redundant,
      kfree() deals with NULL pointers just fine.
      This patch removes such checks from sound/
      
      This patch also makes another, but closely related, change.
      It avoids casting pointers about to be kfree()'ed.
      Signed-off-by: NJesper Juhl <juhl-lkml@dif.dk>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      4d572776
  17. 29 5月, 2005 11 次提交
  18. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4