devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: Nicolin Chen <b42378@freescale.com>,
	ian.campbell@citrix.com, pawel.moll@arm.com,
	galak@codeaurora.org, broonie@kernel.org, lars@metafoo.de,
	p.zabel@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, swarren@wwwdotorg.org, mark.rutland@arm.com
Subject: Re: [PATCH v5 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver
Date: Sat, 17 Aug 2013 17:14:09 +0200	[thread overview]
Message-ID: <20130817151409.GW26614@pengutronix.de> (raw)
In-Reply-To: <2362958.X2QCBUPAyI@flatron>

On Sat, Aug 17, 2013 at 02:56:11PM +0200, Tomasz Figa wrote:
> Hi Nicolin,
> > First, you are right that all the properties you just commented are
> > software configurations. And I got the point that device tree now
> > can't allow any software configuration even if the actual hardware
> > connection will depend on it.
> > 
> > If so, I would like to remove those abused clocks and also drop the
> > unused clocks in src<0-7>, then just remain those needed clocks src.
> > I think that can be plausible because there'll be no more clock abuse
> > and the driver will be able to get the source index from the name
> > 'src<num>'.
> 
> OK.
> 
> > And you are right about the 9 clock inputs, just there're not only 9
> > inputs but also an extra external clock from S/PDIF transmitter via
> > coaxial cable or optical fiber -- RxCLK. Please check the following
> > list:
> > 
> > 0000 if (DPLL Locked) SPDIF_RxClk else extal
> > 0001 if (DPLL Locked) SPDIF_RxClk else spdif_clk
> > 0010 if (DPLL Locked) SPDIF_RxClk else asrc_clk
> > 0011 if (DPLL Locked) SPDIF_RxClk else spdif_extclk
> > 0100 if (DPLL Locked) SPDIF_Rxclk else esai_hckt
> > 0101 extal_clk
> > 0110 spdif_clk
> > 0111 asrc_clk
> > 1000 spdif_extclk
> > 1001 esai_hckt
> > 1010 if (DPLL Locked) SPDIF_RxClk else mlb_clk
> > 1011 if (DPLL Locked) SPDIF_RxClk else mlb_phy_clk
> > 1100 mkb_clk
> > 1101 mlb_phy_clk
> 
> Could you explain what the above values are? If they are values written to 
> a 4-bit mux that selects RX clock source, then all the 16 clocks should be 
> specified from device tree, even if they are duplicated.

The S/PDIF core can recover the clock for the tx signal from the rx
signal. So if you have an S/PDIF input signal, then the DPLL will be
locked and the SPDIF_RxClk can be used for tx. So the above are really 8
clocks and one "If DPLL locked, use it" bit.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-08-17 15:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 11:26 [PATCH v5 0/2] Add freescale S/PDIF CPU DAI and machine drivers Nicolin Chen
2013-08-15 11:26 ` [PATCH v5 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver Nicolin Chen
2013-08-15 12:18   ` Tomasz Figa
     [not found]     ` <20130816044330.GD1846@MrMyself>
2013-08-17 12:56       ` Tomasz Figa
2013-08-17 15:14         ` Sascha Hauer [this message]
2013-08-17 15:38           ` Tomasz Figa
2013-08-15 11:26 ` [PATCH v5 2/2] ASoC: fsl: Add S/PDIF machine driver Nicolin Chen
     [not found] ` <20130816080124.GE1846@MrMyself>
     [not found]   ` <20130816085632.GO26614@pengutronix.de>
2013-08-17 12:26     ` [PATCH v5 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver Tomasz Figa
2013-08-17 15:00       ` Sascha Hauer
2013-08-17 15:13         ` Tomasz Figa
2013-08-17 15:14           ` Sascha Hauer
     [not found] ` <20130816095357.GA4694@MrMyself>
     [not found]   ` <20130816101151.GQ26614@pengutronix.de>
2013-08-17 12:28     ` Tomasz Figa
2013-08-17 14:53       ` Sascha Hauer
2013-08-17 15:17         ` Tomasz Figa
2013-08-19  9:35           ` Mark Rutland
2013-08-20  0:06             ` Mike Turquette
2013-08-21  8:50               ` Mark Rutland
2013-08-21 21:34                 ` Tomasz Figa
2013-08-22  7:19                   ` Mike Turquette
2013-08-22 12:09                     ` Mark Rutland
2013-08-22 21:00                       ` Sascha Hauer
2013-08-22 22:43                         ` Mike Turquette
2013-08-22 22:49                           ` Tomasz Figa
2013-08-23  6:34                             ` Sascha Hauer
2013-08-23 12:58                               ` Mark Rutland
2013-08-23 14:01                                 ` [alsa-devel] " Sascha Hauer
2013-08-23 14:57                                   ` Mark Rutland
2013-08-23 21:41                                   ` Mike Turquette
2013-08-24  0:20                                     ` Mark Brown
2013-08-23 12:44                         ` Mark Rutland

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=20130817151409.GW26614@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=b42378@freescale.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ian.campbell@citrix.com \
    --cc=lars@metafoo.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.rutland@arm.com \
    --cc=p.zabel@pengutronix.de \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --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).