1. 19 10月, 2015 4 次提交
    • T
      ALSA: bebob: use correct type for __be32 data · fef586d5
      Takashi Sakamoto 提交于
      In former commit, metering is supported for BeBoB based models
      customized by M-Audio. The data in transaction is aligned to
      big-endianness, while in the driver code u16 typed variable is assigned
      to the data. This causes sparse warnings.
      
      bebob_maudio.c:651:31: warning: cast to restricted __be16
      bebob_maudio.c:651:31: warning: cast to restricted __be16
      bebob_maudio.c:651:31: warning: cast to restricted __be16
      bebob_maudio.c:651:31: warning: cast to restricted __be16
      
      This commit fixes this bug by using __be16 variable for the data.
      
      Fixes: 3149ac48('ALSA: bebob: Add support for M-Audio special Firewire series')
      Signed-off-by: NTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      fef586d5
    • T
      ALSA: fireworks: use u32 type for be32_to_cpup() macro · 463543ac
      Takashi Sakamoto 提交于
      In former commit, snd_efw_command_get_phys_meters() was added to handle
      metering data. The given buffer is used to save transaction result and to
      convert between endianness. But this causes sparse warnings.
      
      fireworks_command.c:269:25: warning: incorrect type in argument 1 (different base types)
      fireworks_command.c:269:25:    expected unsigned int [usertype] *p
      fireworks_command.c:269:25:    got restricted __be32 [usertype] *
      
      This commit fixes this bug.
      
      Fixes: bde8a8f2('ALSA: fireworks: Add transaction and some commands')
      Signed-off-by: NTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      463543ac
    • T
      ALSA: dice: assign converted data to the same type of variable · cbc6f280
      Takashi Sakamoto 提交于
      In former commit, u32 data was assigned to __be32 variable instead of an
      int variable. This is not enough solution because it still causes sparse
      warnings.
      
      dice.c:80:23: warning: incorrect type in assignment (different base types)
      dice.c:80:23:    expected restricted __be32 [usertype] value
      dice.c:80:23:    got unsigned int
      dice.c:81:21: warning: restricted __be32 degrades to integer
      dice.c:81:46: warning: restricted __be32 degrades to integer
      
      This commit fixes this bug.
      
      Fixes: 7c2d4c0c('ALSA: dice: Split transaction functionality into a file')
      Signed-off-by: NTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      cbc6f280
    • T
      ALSA: dice: correct variable types for __be32 data · 3e93d42a
      Takashi Sakamoto 提交于
      Some local variables in some functions are typed as unsigned int, while
      __be32 value is assigned to them. This causes sparse warnings.
      
      dice-stream.c:50:17: warning: incorrect type in assignment (different base types)
      dice-stream.c:50:17:    expected unsigned int [unsigned] channel
      dice-stream.c:50:17:    got restricted __be32 [usertype] <noident>
      dice-stream.c:74:17: warning: incorrect type in assignment (different base types)
      dice-stream.c:74:17:    expected unsigned int [unsigned] channel
      dice-stream.c:74:17:    got restricted __be32 [usertype] <noident>
      
      This commit fixes this bug.
      
      Fixes: 288a8d0c('ALSA: dice: Change the way to start stream')
      Signed-off-by: NTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      3e93d42a
  2. 18 10月, 2015 5 次提交
  3. 17 10月, 2015 2 次提交
  4. 16 10月, 2015 2 次提交
  5. 15 10月, 2015 6 次提交
  6. 13 10月, 2015 4 次提交
    • R
      ALSA: usb-audio: Fix max packet size calculation for USB audio · ab30965d
      Ricard Wanderlof 提交于
      Rounding must take place before multiplication with the frame size, since
      each packet contains a whole number of frames.
      
      We must also properly consider the data interval, as a larger data
      interval will result in larger packets, which, depending on the sampling
      frequency, can result in packet sizes that are less than integral
      multiples of the packet size for a lower data interval.
      
      Detailed explanation and rationale:
      
      The code before this commit had the following expression on line 613 to
      calculate the maximum isochronous packet size:
      
      	maxsize = ((ep->freqmax + 0xffff) * (frame_bits >> 3))
      			>> (16 - ep->datainterval);
      
      Here, ep->freqmax is the maximum assumed sample frequency, calculated from the
      nominal sample frequency plus 25%. It is ultimately derived from ep->freqn,
      which is in the units of frames per packet, from get_usb_full_speed_rate()
      or usb_high_speed_rate(), as applicable, in Q16.16 format.
      
      The expression essentially adds the Q16.16 equivalent of 0.999... (i.e.
      the largest number less than one) to the sample rate, in order to get a
      rate whose integer part is rounded up from the fractional value. The
      multiplication with (frame_bits >> 3) yields the number of bytes in a
      packet, and the (16 >> ep->datainterval) then converts it from Q16.16 back
      to an integer, taking into consideration the bDataInterval field of the
      endpoint descriptor (which describes how often isochronous packets are
      transmitted relative to the (micro)frame rate (125us or 1ms, for USB high
      speed and full speed, respectively)). For this discussion we will initially
      assume a bDataInterval of 0, so the second line of the expression just
      converts the Q16.16 value to an integer.
      
      In order to illustrate the problem, we will set frame_bits 64, which
      corresponds to a frame size of 8 bytes.
      
      The problem here is twofold. First, the rounding operation consists
      of the addition of 0x0.ffff and subsequent conversion to integer, but as the
      expression stands, the conversion to integer is done after multiplication
      with the frame size, rather than before. This results in the resulting
      maxsize becoming too large.
      
      Let's take an example. We have a sample rate of 96 kHz, so our ep->freqn is
      0xc0000 (see usb_high_speed_rate()). Add 25% (line 612) and we get 0xf0000.
      The calculated maxsize is then ((0xf0000 + 0x0ffff) * 8) >> 16 = 127 .
      However, if we do the number of bytes calculation in a less obscure way it's
      more apparent what the true corresponding packet size is: we get
      ceil(96000 * 1.25 / 8000) * 8 = 120, where 1.25 is the 25% from line 612,
      and the 8000 is the number of isochronous packets per second on a high
      speed USB connection (125 us microframe interval).
      
      This is fixed by performing the complete rounding operation prior to
      multiplication with the frame rate.
      
      The second problem is that when considering the ep->datainterval, this
      must be done before rounding, in order to take the advantage of the fact
      that if the number of bytes per packet is not an integer, the resulting
      rounded-up integer is not necessarily a factor of two when the data
      interval is increased by the same factor.
      
      For instance, assuming a freqency of 41 kHz, the resulting
      bytes-per-packet value for USB high speed is 41 kHz / 8000 = 5.125, or
      0x52000 in Q16.16 format. With a data interval of 1 (ep->datainterval = 0),
      this means that 6 frames per packet are needed, whereas with a data
      interval of 2 we need 10.25, i.e. 11 frames needed.
      
      Rephrasing the maxsize expression to:
      
      	maxsize = (((ep->freqmax << ep->datainterval) + 0xffff) >> 16) *
      			 (frame_bits >> 3);
      
      for the above 96 kHz example we instead get
      ((0xf0000 + 0xffff) >> 16) * 8 = 120 which is the correct value.
      
      We can also do the calculation with a non-integer sample rate which is when
      rounding comes into effect: say we have 44.1 kHz (resulting ep->freqn =
      0x58333, and resulting ep->freqmax 0x58333 * 1.25 = 0x6e3ff (rounded down)):
      
      Original maxsize = ((0x6e3ff + 0xffff) * 8) << 16 = 63 (63.124.. rounded down)
      True maxsize = ceil(44100 * 1.25 / 8000) * 8 = 7 * 8 = 56
      New maxsize = ((0x6e3ff + 0xffff) >> 16) * 8 = 7 * 8 = 56
      
      This is also corroborated by the wMaxPacketSize check on line 616. Assume
      that wMaxPacketSize = 104, with ep->maxpacksize then having the same value.
      As 104 < 127, we get maxsize = 104. ep->freqmax is then recalculated to
      (104 / 8) << 16 = 0xd0000 . Putting that rate into the original maxsize
      calculation yields a maxsize of ((0xd0000 + 0xffff) * 8) >> 16 = 111
      (with decimals 111.99988). Clearly, we should get back the 104 here,
      which we would with the new expression: ((0xd0000 + 0xffff) >> 16) * 8 = 104 .
      
      (The error has not been a problem because it only results in maxsize being
      a bit too big which just wastes a couple of bytes, either as a result of
      the first maxsize calculation, or because the resulting calculation will
      hit the wMaxPacketSize value before the packet is too big, resulting in
      fixing the size to wMaxPacketSize even though the packet is actually not
      too long.)
      
      Tested with an Edirol UA-5 both at 44.1 kHz and 96 kHz.
      Signed-off-by: NRicard Wanderlof <ricardw@axis.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      ab30965d
    • T
      Merge branch 'for-linus' into for-next · 3c69ea44
      Takashi Iwai 提交于
      3c69ea44
    • D
      ALSA: hda - Fix inverted internal mic on Lenovo G50-80 · e8d65a8d
      David Henningsson 提交于
      Add the appropriate quirk to indicate the Lenovo G50-80 has a stereo
      mic input where one channel has reverse polarity.
      
      Alsa-info available at:
      https://launchpadlibrarian.net/220846272/AlsaInfo.txt
      
      Cc: stable@vger.kernel.org
      BugLink: https://bugs.launchpad.net/bugs/1504778Signed-off-by: NDavid Henningsson <david.henningsson@canonical.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      e8d65a8d
    • V
      ALSA: hdac: Explicitly add io.h · 42f2bb1c
      Vinod Koul 提交于
      Compiling the hdac extended core on arm fails with below error:
      
        sound/hda/ext/hdac_ext_bus.c: In function 'hdac_ext_writel':
      >> sound/hda/ext/hdac_ext_bus.c:29:2: error: implicit declaration of
      >> function
      +'writel' [-Werror=implicit-function-declaration]
           writel(value, addr);
           ^
         sound/hda/ext/hdac_ext_bus.c: In function 'hdac_ext_readl':
      >> sound/hda/ext/hdac_ext_bus.c:34:2: error: implicit declaration of
      >> function
      +'readl' [-Werror=implicit-function-declaration]
           return readl(addr);
      
      This is fixed by explicitly including io.h
      
      Fixes: 99463b3a - ('ALSA: hda: provide default bus io ops extended hdac')
      Reported-by: Nkbuild test robot <lkp@intel.com>
      Suggested-by: NMark Brown <broonie@kernel.org>
      Signed-off-by: NVinod Koul <vinod.koul@intel.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      42f2bb1c
  7. 12 10月, 2015 14 次提交
  8. 09 10月, 2015 3 次提交