From: Lars-Peter Clausen <lars@metafoo.de>
To: Nicolin Chen <b42378@freescale.com>
Cc: alsa-devel@alsa-project.org, devicetree-discuss@lists.ozlabs.org,
timur@tabi.org, rob.herring@calxeda.com, broonie@kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/3] ASoC: fsl: Add S/PDIF CPU DAI driver
Date: Wed, 31 Jul 2013 14:16:27 +0200 [thread overview]
Message-ID: <51F9001B.6070203@metafoo.de> (raw)
In-Reply-To: <30e7b0fec9e813b8765514e48296ebecc6ca1039.1375271745.git.b42378@freescale.com>
[...]
a/Documentation/devicetree/bindings/sound/fsl,spdif.txt
b/Documentation/devicetree/bindings/sound/fsl,spdif.txt
> new file mode 100644
> index 0000000..a655800
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/fsl,spdif.txt
> @@ -0,0 +1,63 @@
> +Freescale Sony/Philips Digital Interface Format (S/PDIF) Controller
> +
> +The Freescale S/PDIF audio block is a stereo transceiver that allows the
> +processor to receive and transmit digital audio via an coaxial cable or
> +a fibre cable.
> +
> +Required properties:
> +
> + - compatible : Compatible list, contains "fsl,spdif".
That's not what the driver says though.
> +
> + - reg : Offset and length of the register set for the device.
> +
> + - interrupts : <a b> where a is the interrupt number and b is a field that
> + represents an encoding of the sense and level information for the interrupt.
> + This should be encoded based on the information in section 2) depending on
> + the type of interrupt controller you have.
The exact layout of the cell depends on the parent interrupt controller, so
you probably shouldn't describe it here.
> +
> + - clocks : The phandle for the clock ID number registered in clock tree.
> +
> + - fsl,spdif-dma-events: The dma event ID numbers for Tx and Rx.
> +
Use the generic DMA bindings.
> +Optional properties:
> +
> + - rx-clk-source : The clock cource for Rx. Need to set this source according
> + to the SoC datasheet in SPDIF_SRPC section. If absent, the default source is
> + value 0x0 - if (DPLL Locked) SPDIF_RxClk else extal.
> +
> + - tx-clk-source : The clock cources for Tx. There're three sources, each for
> + different supported sample rate, sequentially 32000Hz, 44100Hz and 48000Hz.
> + Need to set this source according to the SoC datasheet in SPDIF_STC section.
> + If absent, the default source is value 0x1 - CCM spdif0_clk_root input.
> +
> + - tx-clk-div : The clock divider factor for Tx clock. There're three values,
> + each for different supported sample rate, sequentially 32000Hz 44100Hz 48000Hz.
> + Need to set this source according to the clock rate from the clock source.
> + If absent, the default divider factor is <37 23 37> by using spdif0_clk source.
Can't the driver figure out the divider values on its own based on the input
clock rate?
- Lars
next prev parent reply other threads:[~2013-07-31 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 12:07 [PATCH 0/3] ASoC: Add Freescale i.MX S/PDIF controller driver Nicolin Chen
2013-07-31 12:07 ` [PATCH 1/3] ASoC: codec: spdif: Add S20_3LE and S24_LE support for dummy codec drivers Nicolin Chen
2013-07-31 13:28 ` Mark Brown
2013-07-31 12:07 ` [PATCH 2/3] ASoC: fsl: Add S/PDIF CPU DAI driver Nicolin Chen
2013-07-31 12:16 ` Lars-Peter Clausen [this message]
2013-07-31 14:12 ` Chen Guangyu-B42378
2013-07-31 12:07 ` [PATCH 3/3] ASoC: fsl: Add S/PDIF machine driver Nicolin Chen
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=51F9001B.6070203@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rob.herring@calxeda.com \
--cc=timur@tabi.org \
/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).