From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
alsa-devel@alsa-project.org, lars@metafoo.de, festevam@gmail.com,
s.hauer@pengutronix.de, Nicolin Chen <b42378@freescale.com>,
timur@tabi.org, rob.herring@calxeda.com, tomasz.figa@gmail.com,
p.zabel@pengutronix.de, R65777@freescale.com,
shawn.guo@linaro.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v8 2/2] ASoC: fsl: Add S/PDIF machine driver
Date: Tue, 20 Aug 2013 13:53:49 -0600 [thread overview]
Message-ID: <5213C94D.7050304@wwwdotorg.org> (raw)
In-Reply-To: <20130820190701.GR30073@sirena.org.uk>
On 08/20/2013 01:07 PM, Mark Brown wrote:
> On Tue, Aug 20, 2013 at 09:48:46AM -0600, Stephen Warren wrote:
>> On 08/19/2013 06:18 PM, Mark Brown wrote:
>
>>> S/PDIF is also sometimes used as an interconnect between
>>> devices - some CODECs have S/PDIF I/O (more normally used as an
>>> external connector on the box). This is most frequently seen
>>> as a way to
>
>> That's not a good argument for an incorrect binding.
>
> The point is that it might turn into a more correct binding
> depending on what the S/PDIF device actually is.
There's *never* an object on the board called a "dummy codec".
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@kernel.org>
Cc: Nicolin Chen <b42378@freescale.com>,
lars@metafoo.de, p.zabel@pengutronix.de, s.hauer@pengutronix.de,
linuxppc-dev@lists.ozlabs.org, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, timur@tabi.org,
rob.herring@calxeda.com, shawn.guo@linaro.org,
festevam@gmail.com, tomasz.figa@gmail.com, mark.rutland@arm.com,
R65777@freescale.com
Subject: Re: [PATCH v8 2/2] ASoC: fsl: Add S/PDIF machine driver
Date: Tue, 20 Aug 2013 13:53:49 -0600 [thread overview]
Message-ID: <5213C94D.7050304@wwwdotorg.org> (raw)
In-Reply-To: <20130820190701.GR30073@sirena.org.uk>
On 08/20/2013 01:07 PM, Mark Brown wrote:
> On Tue, Aug 20, 2013 at 09:48:46AM -0600, Stephen Warren wrote:
>> On 08/19/2013 06:18 PM, Mark Brown wrote:
>
>>> S/PDIF is also sometimes used as an interconnect between
>>> devices - some CODECs have S/PDIF I/O (more normally used as an
>>> external connector on the box). This is most frequently seen
>>> as a way to
>
>> That's not a good argument for an incorrect binding.
>
> The point is that it might turn into a more correct binding
> depending on what the S/PDIF device actually is.
There's *never* an object on the board called a "dummy codec".
next prev parent reply other threads:[~2013-08-20 19:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 12:08 [PATCH v8 0/2] Add freescale S/PDIF CPU DAI and machine drivers Nicolin Chen
2013-08-19 12:08 ` Nicolin Chen
2013-08-19 12:08 ` Nicolin Chen
2013-08-19 12:08 ` [PATCH v8 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver Nicolin Chen
2013-08-19 12:08 ` Nicolin Chen
2013-08-19 12:08 ` Nicolin Chen
2013-08-19 12:34 ` Sascha Hauer
2013-08-19 12:34 ` Sascha Hauer
2013-08-20 2:21 ` Nicolin Chen
2013-08-20 2:21 ` Nicolin Chen
2013-08-19 21:35 ` Stephen Warren
2013-08-19 21:35 ` Stephen Warren
2013-08-20 2:28 ` Nicolin Chen
2013-08-20 2:28 ` Nicolin Chen
2013-08-20 15:49 ` Stephen Warren
2013-08-20 15:49 ` Stephen Warren
2013-08-19 12:08 ` [PATCH v8 2/2] ASoC: fsl: Add S/PDIF machine driver Nicolin Chen
2013-08-19 12:08 ` Nicolin Chen
2013-08-19 12:08 ` Nicolin Chen
2013-08-19 21:39 ` Stephen Warren
2013-08-19 21:39 ` Stephen Warren
2013-08-20 0:18 ` Mark Brown
2013-08-20 0:18 ` Mark Brown
2013-08-20 0:18 ` Mark Brown
2013-08-20 15:48 ` Stephen Warren
2013-08-20 15:48 ` Stephen Warren
2013-08-20 19:07 ` Mark Brown
2013-08-20 19:07 ` Mark Brown
2013-08-20 19:07 ` Mark Brown
2013-08-20 19:53 ` Stephen Warren [this message]
2013-08-20 19:53 ` Stephen Warren
2013-08-20 22:28 ` Mark Brown
2013-08-20 22:28 ` Mark Brown
2013-08-20 22:28 ` Mark Brown
2013-08-21 2:18 ` Nicolin Chen
2013-08-21 2:18 ` [alsa-devel] " Nicolin Chen
2013-08-21 2:18 ` Nicolin Chen
2013-08-21 16:08 ` Stephen Warren
2013-08-21 16:08 ` [alsa-devel] " Stephen Warren
2013-08-21 16:08 ` Stephen Warren
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=5213C94D.7050304@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=R65777@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=lars@metafoo.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=rob.herring@calxeda.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=timur@tabi.org \
--cc=tomasz.figa@gmail.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.