Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Reichl <hias-vtPv7MOkFPkAvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>,
	Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>
Cc: alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
	linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: [PATCH 0/4] ASoC: bcm2835: Additional modes and constraint updates
Date: Wed,  8 Nov 2017 21:03:28 +0100	[thread overview]
Message-ID: <20171108200332.28949-1-hias@horus.com> (raw)

Main point of this series is support for justified and DSP modes and
implementation of the set_tdm_slot interface in the bcm2835 I2S driver.

I've also updated the constraints: The switch from discrete rates to
RATE_CONTINUOUS and bump of maximum rates to 384kHz has been tested
with various cards. Enforcement of full symmetry fixes issues with
split-codec setups (eg separate ADC and DAC).

This series brings the bcm2835-i2s driver in line with the downstream
rpi tree where we've carried these patches for several months.

             reply	other threads:[~2017-11-08 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 20:03 Matthias Reichl [this message]
2017-11-08 20:03 ` [PATCH 2/4] ASoC: bcm2835: Support left/right justified and DSP modes Matthias Reichl
2017-11-08 20:03 ` [PATCH 3/4] ASoC: bcm2835: Support additional samplerates up to 384kHz Matthias Reichl
2017-11-08 20:26   ` Eric Anholt
     [not found] ` <20171108200332.28949-1-hias-vtPv7MOkFPkAvxtiuMwx3w@public.gmane.org>
2017-11-08 20:03   ` [PATCH 1/4] ASoC: bcm2835: Add support for TDM modes Matthias Reichl
2017-11-10 21:29     ` Applied "ASoC: bcm2835: Add support for TDM modes" to the asoc tree Mark Brown
2017-11-08 20:03   ` [PATCH 4/4] ASoC: bcm2835: Enforce full symmetry Matthias Reichl
2017-11-10 21:28     ` Applied "ASoC: bcm2835: Enforce full symmetry" to the asoc tree Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171108200332.28949-1-hias@horus.com \
    --to=hias-vtpv7mokfpkavxtiumwx3w@public.gmane.org \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org \
    --cc=linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=stefan.wahren-eS4NqCHxEME@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox