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 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver
Date: Mon, 19 Aug 2013 19:34:08 +0800 [thread overview]
Message-ID: <20130819113407.GA11489@MrMyself> (raw)
In-Reply-To: <20130819111349.GJ3719@e106331-lin.cambridge.arm.com>
On Mon, Aug 19, 2013 at 12:13:49PM +0100, Mark Rutland wrote:
> > > > > > + "rxtx<0-7>" Clock source list for tx and rx clock.
> > > > > > + This clock list should be identical to
> > > > > > + the source list connecting to the spdif
> > > > > > + clock mux in "SPDIF Transceiver Clock
> > > > > > + Diagram" of SoC reference manual. It
> > > > > > + can also be referred to TxClk_Source
> > > > > > + bit of register SPDIF_STC.
> > Actually there's a clock mux for TxClk and it's connecting with 8 clock
> > sources. So the TxClk_Source bit show the connection between its value
> > with the correspond source on the clock mux:
> >
> > TxClk_Source 000 XTAL clk input
> > 001 CCM spdif0_clk_root input
> > 010 asrc_clk input
> > 011 spdif_extclk input, from pads
> > 100 esai_hckt input
> > 101 frequency divided ipg_clk input
> > 110 mlb_clk input
> > 111 mlb phy clk input
>
> Ah. So are these the actual input names on the mux, or the names of the
> outputs that are wired up to the mux? If the former, these may be better
> clock-names than rxtx<0-7>.
The clock names are actually different with different SoC. The list above
is only for i.MX6Q. So we can't specify these names here, because the driver
then would need to maintain a clock names list for different SoC as well.
> Is there a similar Rx mux?
Both Tx and RX clocks can be derived from the Tx mux.
> Given the "rxtx<0-7>" names you've given these clocks, are there 8 clock
> inputs that get duplicated within the spdif block and fed into both
> muxes, or are there 16 external inputs that happen to be two groups of 8
> identical sets of clocks in systems so far?
I think you can refer to the RM, since you just got it. The diagram doesn't
show which one you mentioned is true. But I think we can understand in both
ways.
I'm going to send a v8. So I think I don't need to modify the description
right?
Thank you
Nicolin Chen
next prev parent reply other threads:[~2013-08-19 11:34 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 [this message]
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
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=20130819113407.GA11489@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).