From: Mark Brown <broonie@kernel.org>
To: Sugar Zhang <sugar.zhang@rock-chips.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
heiko@sntech.de, alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: DT bindings: rockchip-i2s: add capture and lrck-mode
Date: Wed, 23 Sep 2015 09:20:26 -0700 [thread overview]
Message-ID: <20150923162026.GP30445@sirena.org.uk> (raw)
In-Reply-To: <1442979683-9441-3-git-send-email-sugar.zhang@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
On Wed, Sep 23, 2015 at 11:41:23AM +0800, Sugar Zhang wrote:
> rockchip,lrck-mode: 0: rxtx separate, 1: tx share, 2: rx share.
> default use 'rxtx separate' mode.
I'm slightly confused about this property - is this covering differences
in the IP deployed on different SoCs or is it covering how the SoC is
wired into the board? If it's for how the SoC is wired into the board
(ie, Rx and Tx wired together) then this should already be covered by
either the machine driver or the device at the other end of the link.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Sugar Zhang <sugar.zhang@rock-chips.com>
Cc: alsa-devel@alsa-project.org, heiko@sntech.de,
linux-kernel@vger.kernel.org, tiwai@suse.com,
lgirdwood@gmail.com, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] Documentation: DT bindings: rockchip-i2s: add capture and lrck-mode
Date: Wed, 23 Sep 2015 09:20:26 -0700 [thread overview]
Message-ID: <20150923162026.GP30445@sirena.org.uk> (raw)
In-Reply-To: <1442979683-9441-3-git-send-email-sugar.zhang@rock-chips.com>
[-- Attachment #1.1: Type: text/plain, Size: 519 bytes --]
On Wed, Sep 23, 2015 at 11:41:23AM +0800, Sugar Zhang wrote:
> rockchip,lrck-mode: 0: rxtx separate, 1: tx share, 2: rx share.
> default use 'rxtx separate' mode.
I'm slightly confused about this property - is this covering differences
in the IP deployed on different SoCs or is it covering how the SoC is
wired into the board? If it's for how the SoC is wired into the board
(ie, Rx and Tx wired together) then this should already be covered by
either the machine driver or the device at the other end of the link.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] Documentation: DT bindings: rockchip-i2s: add capture and lrck-mode
Date: Wed, 23 Sep 2015 09:20:26 -0700 [thread overview]
Message-ID: <20150923162026.GP30445@sirena.org.uk> (raw)
In-Reply-To: <1442979683-9441-3-git-send-email-sugar.zhang@rock-chips.com>
On Wed, Sep 23, 2015 at 11:41:23AM +0800, Sugar Zhang wrote:
> rockchip,lrck-mode: 0: rxtx separate, 1: tx share, 2: rx share.
> default use 'rxtx separate' mode.
I'm slightly confused about this property - is this covering differences
in the IP deployed on different SoCs or is it covering how the SoC is
wired into the board? If it's for how the SoC is wired into the board
(ie, Rx and Tx wired together) then this should already be covered by
either the machine driver or the device at the other end of the link.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150923/d4a638b3/attachment.sig>
next prev parent reply other threads:[~2015-09-23 16:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 3:41 [PATCH 0/2] ASoC: rockchip: i2s: add 8 channels capture and lrck-mode Sugar Zhang
2015-09-23 3:41 ` Sugar Zhang
2015-09-23 3:41 ` [PATCH 1/2] ASoC: rockchip: i2s: add 8 channels capture and lrck-mode support Sugar Zhang
2015-09-23 3:41 ` Sugar Zhang
2015-09-23 16:24 ` Mark Brown
2015-09-23 16:24 ` Mark Brown
2015-09-28 8:16 ` sugar
2015-09-28 8:16 ` sugar
2015-09-28 8:16 ` sugar
2015-09-30 18:46 ` Mark Brown
2015-09-30 18:46 ` Mark Brown
2015-10-07 8:01 ` sugar
2015-10-07 8:01 ` sugar
2015-10-07 8:01 ` sugar
2015-10-07 9:27 ` Mark Brown
2015-10-07 9:27 ` Mark Brown
2015-10-07 9:39 ` Mark Brown
2015-10-07 9:39 ` Mark Brown
2015-10-07 9:39 ` Mark Brown
2015-10-07 10:01 ` sugar
2015-10-07 10:01 ` sugar
2015-10-07 10:01 ` sugar
2015-10-07 13:04 ` [alsa-devel] " Caleb Crome
2015-10-07 13:04 ` Caleb Crome
2015-10-08 1:47 ` sugar
2015-10-08 1:47 ` sugar
2015-10-08 1:47 ` sugar
2015-10-08 2:36 ` [alsa-devel] " Caleb Crome
2015-10-08 2:36 ` Caleb Crome
2015-10-08 2:44 ` sugar
2015-10-08 2:44 ` sugar
2015-10-08 3:19 ` Caleb Crome
2015-10-08 3:19 ` Caleb Crome
2015-10-08 3:59 ` sugar
2015-10-08 3:59 ` sugar
2015-10-08 3:59 ` sugar
2015-09-23 3:41 ` [PATCH 2/2] Documentation: DT bindings: rockchip-i2s: add capture and lrck-mode Sugar Zhang
2015-09-23 3:41 ` Sugar Zhang
2015-09-23 16:20 ` Mark Brown [this message]
2015-09-23 16:20 ` Mark Brown
2015-09-23 16:20 ` 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=20150923162026.GP30445@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.