From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] dt-bindings: sound: Add DT bindings for Broadcom Cygnus audio
Date: Fri, 6 Nov 2015 10:31:47 +0000 [thread overview]
Message-ID: <20151106103147.GZ18409@sirena.org.uk> (raw)
In-Reply-To: <563BB5B0.5040501@broadcom.com>
On Thu, Nov 05, 2015 at 12:01:52PM -0800, Simran Rai wrote:
> On 11/4/2015 6:07 AM, Mark Brown wrote:
> >On Mon, Nov 02, 2015 at 02:11:23PM -0800, Simran Rai wrote:
> >>+ Interfaces grouping of serial port. In multi-channel stereo, use
> >>+ "2_0", in 3.1 multi-channel grouping, use "3_1" and in 5.1
> >>+ multi-channel grouping, use "5_1".
> >I don't really understand what this means or why this is not runtime
> >configured.
> By runtime configured, do you mean passing the channel grouping through
> machine file? Is there any specific callback that I can use?
No, this appears to just be setting the number of channels which is
normally configured depending on how many channels userspace is playing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151106/7d51feb6/attachment.sig>
next prev parent reply other threads:[~2015-11-06 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 22:11 [PATCH v2 0/2] Add audio support for Broadcom Cygnus SoC Simran Rai
2015-11-02 22:11 ` [PATCH v2 1/2] dt-bindings: sound: Add DT bindings for Broadcom Cygnus audio Simran Rai
2015-11-04 14:07 ` Mark Brown
2015-11-05 20:01 ` Simran Rai
2015-11-06 10:31 ` Mark Brown [this message]
2015-11-06 22:10 ` Simran Rai
2015-11-02 22:11 ` [PATCH v2 2/2] sound: soc: Add Cygnus audio driver Simran Rai
2015-11-04 14:28 ` Mark Brown
2015-11-04 14:06 ` [PATCH v2 0/2] Add audio support for Broadcom Cygnus SoC 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=20151106103147.GZ18409@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).