The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Matthias Reichl <hias@horus.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Lee Jones <lee@kernel.org>,
	Martin Sperl <kernel@martin.sperl.org>,
	Luis de Bethencourt <luis@debethencourt.com>,
	alsa-devel@alsa-project.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: bcm2835: Add S16_LE support via packed DMA transfers
Date: Wed, 27 Apr 2016 11:54:04 -0700	[thread overview]
Message-ID: <878tzyublf.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1461763613-28714-2-git-send-email-hias@horus.com>

[-- Attachment #1: Type: text/plain, Size: 257 bytes --]

Matthias Reichl <hias@horus.com> writes:

> The bcm2835-i2s driver already has support for the S16_LE format but
> that format hasn't been made available because dmaengine_pcm didn't
> support packed data transfers.

Acked-by: Eric Anholt <eric@anholt.net>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  parent reply	other threads:[~2016-04-27 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 13:26 [PATCH 1/2] ASoC: dmaengine_pcm: Add support for packed transfers Matthias Reichl
2016-04-27 13:26 ` [PATCH 2/2] ASoC: bcm2835: Add S16_LE support via packed DMA transfers Matthias Reichl
2016-04-27 14:33   ` Martin Sperl
2016-04-27 16:36   ` Applied "ASoC: bcm2835: Add S16_LE support via packed DMA transfers" to the asoc tree Mark Brown
2016-04-27 18:54   ` Eric Anholt [this message]
2016-04-27 14:14 ` [PATCH 1/2] ASoC: dmaengine_pcm: Add support for packed transfers Lars-Peter Clausen
2016-04-27 14:33 ` Martin Sperl
2016-04-27 16:34 ` Applied "ASoC: dmaengine_pcm: Add support for packed transfers" 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=878tzyublf.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=hias@horus.com \
    --cc=kernel@martin.sperl.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=luis@debethencourt.com \
    --cc=perex@perex.cz \
    --cc=swarren@wwwdotorg.org \
    --cc=tiwai@suse.com \
    /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