1. 09 9月, 2014 1 次提交
  2. 13 8月, 2014 1 次提交
  3. 12 2月, 2014 1 次提交
  4. 14 10月, 2013 1 次提交
  5. 13 9月, 2013 1 次提交
  6. 29 5月, 2013 1 次提交
    • T
      ALSA: PCI: Remove superfluous pci_set_drvdata(pci, NULL) at remove · 20a24225
      Takashi Iwai 提交于
      As drvdata is cleared to NULL at probe failure or at removal by the
      driver core, we don't have to call pci_set_drvdata(pci, NULL) any
      longer in each driver.
      
      The only remaining pci_set_drvdata(NULL) is in azx_firmware_cb() in
      hda_intel.c.  Since this function itself releases the card instance,
      we need to clear drvdata here as well, so that it won't be released
      doubly in the remove callback.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      20a24225
  7. 14 2月, 2013 1 次提交
  8. 07 1月, 2013 1 次提交
  9. 07 12月, 2012 1 次提交
  10. 25 10月, 2012 1 次提交
  11. 06 10月, 2012 1 次提交
  12. 06 6月, 2012 1 次提交
  13. 24 4月, 2012 1 次提交
  14. 16 3月, 2012 1 次提交
  15. 24 1月, 2012 1 次提交
  16. 16 1月, 2012 2 次提交
  17. 08 1月, 2012 4 次提交
  18. 19 12月, 2011 1 次提交
  19. 01 11月, 2011 2 次提交
  20. 14 9月, 2011 1 次提交
    • C
      ALSA: mpu401: clean up interrupt specification · dba8b469
      Clemens Ladisch 提交于
      The semantics of snd_mpu401_uart_new()'s interrupt parameters are
      somewhat counterintuitive:  To prevent the function from allocating its
      own interrupt, either the irq number must be invalid, or the irq_flags
      parameter must be zero.  At the same time, the irq parameter being
      invalid specifies that the mpu401 code has to work without an interrupt
      allocated by the caller.  This implies that, if there is an interrupt
      and it is allocated by the caller, the irq parameter must be set to
      a valid-looking number which then isn't actually used.
      
      With the removal of IRQF_DISABLED, zero becomes a valid irq_flags value,
      which forces us to handle the parameters differently.
      
      This patch introduces a new flag MPU401_INFO_IRQ_HOOK for when the
      device interrupt is handled by the caller, and makes the allocation of
      the interrupt to depend only on the irq parameter.  As suggested by
      Takashi, the irq_flags parameter was dropped because, when used, it had
      the constant value IRQF_DISABLED.
      Signed-off-by: NClemens Ladisch <clemens@ladisch.de>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      dba8b469
  21. 10 6月, 2011 2 次提交
    • T
      ALSA: use KBUILD_MODNAME for request_irq argument in sound/pci/* · 934c2b6d
      Takashi Iwai 提交于
      The name argument of request_irq() appears in /proc/interrupts, and
      it's quite ugly when the name entry contains a space or special letters.
      In general, it's simpler and more readable when the module name appears
      there, so let's replace all entries with KBUILD_MODNAME.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      934c2b6d
    • T
      ALSA: Use KBUILD_MODNAME for pci_driver.name entries · 3733e424
      Takashi Iwai 提交于
      The convention for pci_driver.name entry in kernel drivers seem to be
      the module name or equivalent ones.  But, so far, almost all PCI sound
      drivers use more verbose name like "ABC Xyz (12)", and these are fairly
      confusing when appearing as a file name.
      
      This patch converts the all pci_driver.name entries in sound/pci/* to
      use KBUILD_MODNAME for more unified appearance.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      3733e424
  22. 27 4月, 2011 1 次提交
  23. 26 4月, 2011 1 次提交
  24. 31 3月, 2011 1 次提交
  25. 20 2月, 2011 1 次提交
  26. 15 2月, 2011 1 次提交
  27. 19 1月, 2011 1 次提交
  28. 17 1月, 2011 1 次提交
  29. 17 10月, 2010 1 次提交
  30. 09 2月, 2010 1 次提交
  31. 25 6月, 2009 1 次提交
  32. 29 5月, 2009 2 次提交
  33. 07 4月, 2009 1 次提交