From: Nicolin Chen <b42378@freescale.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"timur@tabi.org" <timur@tabi.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"festevam@gmail.com" <festevam@gmail.com>,
"tomasz.figa@gmail.com" <tomasz.figa@gmail.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"R65777@freescale.com" <R65777@freescale.com>
Subject: Re: [PATCH v7 2/2] ASoC: fsl: Add S/PDIF machine driver
Date: Mon, 19 Aug 2013 18:21:06 +0800 [thread overview]
Message-ID: <20130819102105.GC11402@MrMyself> (raw)
In-Reply-To: <20130819100143.GH3719@e106331-lin.cambridge.arm.com>
On Mon, Aug 19, 2013 at 11:01:43AM +0100, Mark Rutland wrote:
> > At least they are separate drivers as I mentioned in the commit comments.
>
> I'm not sure that the boundary of Linux drivers should necessarily
> determine the way we carve up the description of IP blocks, though
> presumably it's a pretty sensible way of carving it up or we wouldn't
> have done it.
I'm not sure if I understand your point correctly. But in fact the IP driver
is not being carved up. The spdif-transmitter and spdif-receiver are basically
dummy codec drivers. All the IP-related codes are implemented in fsl_spdif.c,
the PATCH 1/2 you just reviewed.
> Is there any public documentation on the i.MX S/PDIF hardware block(s)?
http://cache.freescale.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf
Thank you,
Nicolin
next prev parent reply other threads:[~2013-08-19 10:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 8:35 [PATCH v7 0/2] Add freescale S/PDIF CPU DAI and machine drivers Nicolin Chen
2013-08-19 8:35 ` [PATCH v7 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver Nicolin Chen
2013-08-19 9:18 ` Mark Rutland
2013-08-19 9:34 ` Nicolin Chen
2013-08-19 9:54 ` Mark Rutland
2013-08-19 10:13 ` Nicolin Chen
2013-08-19 11:13 ` Mark Rutland
2013-08-19 11:34 ` Nicolin Chen
2013-08-20 8:47 ` Mark Rutland
2013-08-20 5:19 ` Shawn Guo
2013-08-20 8:54 ` Mark Rutland
2013-08-20 16:28 ` Stephen Warren
2013-08-19 8:35 ` [PATCH v7 2/2] ASoC: fsl: Add S/PDIF machine driver Nicolin Chen
2013-08-19 9:24 ` Mark Rutland
2013-08-19 9:50 ` Nicolin Chen
2013-08-19 10:01 ` Mark Rutland
2013-08-19 10:21 ` Nicolin Chen [this message]
2013-08-19 11:15 ` Mark Rutland
2013-08-19 10:27 ` Philipp Zabel
2013-08-19 10:52 ` Mark Brown
2013-08-19 11:31 ` Mark Rutland
2013-08-19 11:45 ` 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=20130819102105.GC11402@MrMyself \
--to=b42378@freescale.com \
--cc=R65777@freescale.com \
--cc=alsa-devel@alsa-project.org \
--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=swarren@wwwdotorg.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 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).