Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 26 5月, 2015 2 次提交
  3. 28 4月, 2015 1 次提交
    • L
      ASoC: dmaengine_pcm: Make FLAG_NO_RESIDUE internal · acde50a7
      由 Lars-Peter Clausen 提交于 
      Whether residue can be reported or not is not a property of the audio
controller but of the DMA controller. The FLAG_NO_RESIDUE was initially
added when the DMAengine framework had no support for describing the residue
reporting capabilities of the controller. Support for this was added quite a
while ago and recently the DMAengine framework started to complain if a
driver does not describe its capabilities and a lot of patches have been
merged that add support for this where it was missing. So it should be safe
to assume that driver on actively used platforms properly implement the DMA
capabilities API.

This patch makes the FLAG_NO_RESIDUE internal and no longer allows audio
controller drivers to manually set the flag. If a DMA driver against
expectations does not support reporting its capabilities for now the generic
DMAengine PCM driver will now emit a warning and simply assume that residue
reporting is not supported. In the future this might be changed to aborting
with an error.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NMark Brown <broonie@kernel.org>
      acde50a7
  5. 27 4月, 2015 1 次提交
  7. 12 4月, 2015 2 次提交
  9. 02 4月, 2015 2 次提交
  11. 03 3月, 2015 1 次提交
  13. 10 2月, 2015 1 次提交
    • P
      ASoC: atmel_ssc_dai: Allow more rates · b6d6c6e9
      由 Peter Rosin 提交于 
      When the SSC acts as BCK master, use a ratnum rule to limit
the rate instead of only doing the standard rates. When the SSC
acts as BCK slave, allow any BCK frequency up to the SSC master
clock, divided by either of 2, 3 or 6.

Put a cap at 384kHz. Who's /ever/ going to need more than that?

The divider of 2, 3 or 6 is selected based on the Serial Clock Ratio
Considerations section from the SSC documentation:

    The Transmitter and the Receiver can be programmed to operate
    with the clock signals provided on either the TK or RK pins.
    This allows the SSC to support many slave-mode data transfers.
    In this case, the maximum clock speed allowed on the RK pin is:
    - Peripheral clock divided by 2 if Receiver Frame Synchro is input
    - Peripheral clock divided by 3 if Receiver Frame Synchro is output
    In addition, the maximum clock speed allowed on the TK pin is:
    - Peripheral clock divided by 6 if Transmit Frame Synchro is input
    - Peripheral clock divided by 2 if Transmit Frame Synchro is output
Signed-off-by: NPeter Rosin <peda@axentia.se>
Acked-by: NBo Shen <voice.shen@atmel.com>
Signed-off-by: NMark Brown <broonie@kernel.org>
      b6d6c6e9
  15. 02 2月, 2015 1 次提交
  17. 30 1月, 2015 4 次提交
  19. 28 1月, 2015 2 次提交
  21. 15 1月, 2015 1 次提交
  23. 07 1月, 2015 2 次提交
  25. 08 12月, 2014 1 次提交
  27. 02 12月, 2014 2 次提交
  29. 10 11月, 2014 1 次提交
    • T
      ALSA: pcm: Add snd_pcm_stop_xrun() helper · 1fb8510c
      由 Takashi Iwai 提交于 
      Add a new helper function snd_pcm_stop_xrun() to the standard sequnce
lock/snd_pcm_stop(XRUN)/unlock by a single call, and replace the
existing open codes with this helper.

The function checks the PCM running state to prevent setting the wrong
state, too, for more safety.
Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      1fb8510c
  31. 03 11月, 2014 1 次提交
    • P
      ASoC: atmel_ssc_dai: Match the CMR divider only in full duplex. · eb58960e
      由 Peter Rosin 提交于 
      The CMR divider register is shared by playback and capture. The SSC driver
therefore tries to enforce rules so that the needed register content do
not conflict during simultaneous playback/capture. However, the
implementation also prevents changing the register content in
half-duplex scenarios, which is needed when using the OSS API.

Thus, only lock the divider if there is a stream in the other direction.

Fixes the below program to not fail with the atmel ssc dai in master mode.

int
main(void)
{
	int fd;
	int format;
	int channels;
	int speed;

	if ((fd = open("/dev/dsp", O_WRONLY, 0)) == -1) {
		perror("open");
		return 1;
	}
	format = AFMT_S16_LE;
	if (ioctl(fd, SNDCTL_DSP_SETFMT, &format) == -1) {
		perror("SNDCTL_DSP_SETFMT");
		return 1;
	}
	channels = 2;
	if (ioctl(fd, SNDCTL_DSP_CHANNELS, &channels) == -1) {
		perror("SNDCTL_DSP_CHANNELS");
		return 1;
	}
	speed = 22025;
	if (ioctl(fd, SNDCTL_DSP_SPEED, &speed) == -1) {
		perror("SNDCTL_DSP_SPEED");
		return 1;
	}
	return 0;
}
Signed-off-by: NPeter Rosin <peda@axentia.se>
Acked-by: NBo Shen <voice.shen@atmel.com>
Signed-off-by: NMark Brown <broonie@kernel.org>
      eb58960e
  33. 20 10月, 2014 1 次提交
  35. 21 6月, 2014 1 次提交
  37. 10 6月, 2014 1 次提交
  39. 20 5月, 2014 1 次提交
  41. 13 5月, 2014 1 次提交
    • L
      ASoC: atmel-pcm-pdc: Remove broken suspend/resume code · b74f7be9
      由 Lars-Peter Clausen 提交于 
      Suspend/resume support for the atmel-pcm-pdc driver was broken in commit
f0fba2ad ("ASoC: multi-component - ASoC Multi-Component Support"). It
essentially reverted the modifications done in commit 10cab262 ("ASoC: Change
how suspend and resume obtain the PCM runtime"). The suspend and resume handlers
at the beginning check if dai->runtime is not NULL, but dai->runtime is always
NULL, hence the code never runs. Considering that nobody noticed any problems in
the last 4 years since the code was broken and that the driver does not set
SNDRV_PCM_INFO_RESUME, which means applications are expected to stop and restart
the audio stream during suspend/resume, it is probably safe to assume that his
code is not needed and can be removed.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Signed-off-by: NMark Brown <broonie@linaro.org>
      b74f7be9
  43. 08 5月, 2014 1 次提交
  45. 02 5月, 2014 1 次提交
  47. 10 3月, 2014 1 次提交
  49. 07 3月, 2014 1 次提交
  51. 13 2月, 2014 1 次提交
  53. 07 1月, 2014 1 次提交
  55. 31 12月, 2013 1 次提交
  57. 13 12月, 2013 1 次提交
  59. 04 12月, 2013 2 次提交