From: Mark Brown <broonie@kernel.org>
To: Caleb Crome <caleb@crome.org>
Cc: "Sugar Zhang" <sugar.zhang@rock-chips.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
perex@perex.cz, tiwai@suse.com, "Heiko Stübner" <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [alsa-devel] [PATCH v2 1/3] ASoC: rockchip: i2s: add 8 channels capture support
Date: Mon, 19 Oct 2015 16:15:25 +0100 [thread overview]
Message-ID: <20151019151525.GA32054@sirena.org.uk> (raw)
In-Reply-To: <CAG5mAdzfoK_rnQhu=NGMzto2K49uKT4eOotRh3uGX=D6KOB5gQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
On Thu, Oct 08, 2015 at 07:30:43AM -0700, Caleb Crome wrote:
> Is it possible to allow channels > 8 if certain requirements are met? If
> the rockchip supports 8 channels @ 32-bits/sample, that means 256
> bits/frame. Can those 256 bits be sliced into 16 channels of 16-bit
> samples?
Please don't top post.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-19 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 12:40 [PATCH v2 0/3] ASoC: rockchip: i2s: add 8 channels capture support and share lrck Sugar Zhang
2015-10-08 12:40 ` [PATCH v2 1/3] ASoC: rockchip: i2s: add 8 channels capture support Sugar Zhang
[not found] ` <CAG5mAdzfoK_rnQhu=NGMzto2K49uKT4eOotRh3uGX=D6KOB5gQ@mail.gmail.com>
2015-10-19 15:15 ` Mark Brown [this message]
2015-10-08 12:40 ` [PATCH v2 2/3] Documentation: DT bindings: rockchip-i2s: add capture property Sugar Zhang
2015-10-22 16:50 ` Mark Brown
2015-10-08 12:40 ` [PATCH v2 3/3] ASoC: rockchip: i2s: share tx/rx lrck when symmetric_rates enabled Sugar Zhang
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=20151019151525.GA32054@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=caleb@crome.org \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=perex@perex.cz \
--cc=sugar.zhang@rock-chips.com \
--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
all inboxes | Powered by JetHome®