1. 17 7月, 2012 2 次提交
  2. 16 7月, 2012 2 次提交
  3. 18 6月, 2012 1 次提交
  4. 10 4月, 2012 1 次提交
  5. 29 3月, 2012 1 次提交
  6. 28 3月, 2012 1 次提交
  7. 06 2月, 2012 1 次提交
  8. 19 12月, 2011 1 次提交
  9. 01 11月, 2011 4 次提交
  10. 22 9月, 2011 1 次提交
  11. 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
  12. 27 7月, 2011 1 次提交
  13. 31 3月, 2011 1 次提交
  14. 02 11月, 2010 1 次提交
  15. 08 9月, 2010 1 次提交
  16. 07 9月, 2010 1 次提交
  17. 13 8月, 2010 2 次提交
    • R
      ALSA: ISA: Remove snd-sgalaxy · cbaa9f60
      René Herman 提交于
      Its hardware is handled more fully by the new azt1605/azt2316 drivers.
      Signed-off-by: NRene Herman <rene.herman@gmail.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      cbaa9f60
    • R
      ALSA: ISA: New Aztech Sound Galaxy driver · 49531192
      René Herman 提交于
      This is a new driver for Aztech Sound Galaxy ISA soundcards based on the
      AZT1605 and AZT2316 chipsets. It's constructed as two seperate drivers
      for either chipset generated from the same source file, with (very)
      minimal ifdeffery.
      
      The drivers check the SB DSP version to decide if they are being loaded
      for the right chip. AZT1605 returns 2.1 by default and AZT2316 3.1.
      This isn't full-proof as the DSP version can actually be set through
      software but it's close enough -- as far as I've been able to see, the
      DSP version can not be stored in the EEPROM and the cards will therefore
      startup with the defaults.
      
      This distinction could (with the same success rate) also be used to
      decide which chip we're looking at at runtime meaning a single, merged
      driver is also an option but I feel it's actually nicer this way. A
      merged driver would have to postpone translating the passed in resource
      values to the card configuration until it knew which one it was looking
      at and would need to postpone erring out on mpu_irq=10 for azt1605 and
      mpu_irq=3 for azt2316.
      
      The drivers have been tested on various cards. For snd-azt1605:
      
      FCC-ID I38-MMSN811: Aztech Sound Galaxy Nova 16 Extra
      FCC-ID I38-MMSN822: Aztech Sound Galaxy Pro 16 II
      
      and for snd-azt2316:
      
      FCC-ID I38-MMSN824: Aztech Sound Galaxy Pro 16 AB
      FCC-ID I38-MMSN826: Trust Sound Expert DeLuxe Wave 32 (05201)
      FCC-ID I38-MMSN830: Trust Sound Expert DeLuxe 16+ (05202)
      FCC-ID I38-MMSN837: Packard Bell ISA Soundcard 030069
      FCC-ID I38-MMSN846: Trust Sound Expert DeLuxe 16-3D (06300)
      FCC-ID I38-MMSN847: Trust Sound Expert DeLuxe Wave 32-3D (06301)
      FCC-ID I38-MMSN852: Aztech Sound Galaxy Waverider Pro 32-3D
      
      826 and 846 were also marketed directly by Aztech and then known as:
      
      FCC-ID I38-MMSN826: Aztech Sound Galaxy Waverider 32+
      FCC-ID I38-MMSN846: Aztech Sound Galaxy Nova 16 Extra II-3D
      
      Together, these cover the AZT1605 and AT2316A, AZT2316R and AZT2316-S
      chipsets. All cards work fully -- full-duplex PCM, MIDI and FM. Full
      duplex is a little flaky on some.
      
      I38-MSN811 tends to not work in full-duplex but sometimes does with the
      highest success rate being achieved when you first start the capture and
      then a playback instead of the other way around (it's a CS4231-KL
      codec).
      
      The cards with an AD1845XP codec (my I38-MMSN826 and one of my
      I38-MMSN830s) are also somewhat duplex-challenged. Sometimes full-duplex
      works, sometimes not and this varies from try to try. This seems likely
      to be a timing problem somewhere inside wss-lib.
      
      I38-MMSN826 has an additional "ICS2115 WaveFront" wavetable synth
      onboard that isn't supported yet. The wavetable synths on I38-MMSN847
      and I38-MMSN852 are wired directly to the standard MPU-401 UART and the
      AUX1 input on the codec and work without problem.
      
      CD-ROM audio on the cards is routed to the codec "Line" input, Line-In
      to its Aux input, and FM/Wavetable to its AUX1 input. I did not rename
      the controls due to the capture source enumeration: I see that
      capture-source overrides are hardcoded in wss-lib and this is just too
      ugly to live.
      
      Versus the old snd-sgalaxy driver these drivers add support for the
      models without a configuration EEPROM (which are common), full-duplex,
      MPU-401 UART and OPL3. In the future they might grow support for that
      ICS2115 WaveFront synth on 826 and an hwdep interface to write to the
      EEPROM on the models that have one.
      Signed-off-by: NRene Herman <rene.herman@gmail.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      49531192
  18. 29 7月, 2010 2 次提交
  19. 17 5月, 2010 1 次提交
    • D
      ALSA: es1688: add pedantic range checks · b0fb75ad
      Dan Carpenter 提交于
      Smatch complains that if (dev == SNDRV_CARDS) we're one past the end of
      the array.  That's unlikely to happen in real life, I suppose.
      
      Also smatch complains about "strcpy(card->shortname, pcm->name);"
      The "pcm->name" buffer is 80 characters and "card->shortname" is 32
      characters.  If you follow the call paths it turns out we never actually
      use more than 16 characters so it's not a problem.  But anyway, let's
      make it easy for people auditing this in the future.
      Signed-off-by: NDan Carpenter <error27@gmail.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      b0fb75ad
  20. 10 5月, 2010 2 次提交
  21. 26 4月, 2010 1 次提交
  22. 13 4月, 2010 3 次提交
  23. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  24. 09 3月, 2010 1 次提交
  25. 05 3月, 2010 1 次提交
  26. 04 3月, 2010 1 次提交
  27. 08 1月, 2010 1 次提交
  28. 25 12月, 2009 1 次提交
  29. 21 12月, 2009 2 次提交