linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: Dove: Add the audio device to the Cubox DT
Date: Thu, 3 Oct 2013 18:17:16 +0200	[thread overview]
Message-ID: <20131003181716.6d03d576@armhf> (raw)
In-Reply-To: <5246E747.6020103@gmail.com>

On Sat, 28 Sep 2013 16:27:19 +0200
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:

> Jean-Francois,
> 
> I can confirm the following for CuBox:
> 
> AU1_EXTCLK is connected to si5351 clkout 2. For the _current_
> (v3.12-rc1) dove-cubox.dts that means that you'll have to exchange
> the properties for &i2c0/si5351/clkout[12]. If you leave it the way
> it is, clkout2 is not allowed to change the pll inside si5351 and
> only try to get close to the requested clk rate by using output
> dividers. Would be great if you can provide a corresponding patch
> for v3.12 (no need to Cc stable).
> 
> Also, as you seem to push kirkwood-i2s DT forward, please get back
> to clkout2 (<&si5351 2>) for the audio node as you did correctly in
> the first place.
> 
> With above changes, SPDIF_EN, and forcing kirkwood-i2s to always use
> extclk, I can play SPDIF audio with 44k1 and 48k. Other rates could
> also work, but my audio equipment ignores anything else.

Sebastian,

Thanks for your change. I can now get audio at 44.1, 32 and 22.05 kHz
on HDMI with the external clock (via i2s, but s/pdif and other rates
should work too).

	[snip]
> What I am wondering here is, why you want to use i2s at all? On CuBox,
> HDMI transmitter is connected to both i2s and spdif. IIRC, for the
> transmitter it makes no difference if you provide i2s or spdif audio,
> _but_ what you are loosing for sure is pass-through, i.e. sending
> compressed AC3 directly.
	[snip]

It seems that my patch about adding s/pdif to the kirkwood audio driver
has not been accepted yet...

-- 
Ken ar c'henta?	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/

  reply	other threads:[~2013-10-03 16:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  9:35 [PATCH 2/2] ARM: Dove: Add the audio device to the Cubox DT Jean-Francois Moine
2013-08-28 10:14 ` Sebastian Hesselbarth
2013-08-31 10:51   ` Jean-Francois Moine
2013-08-31 11:24     ` Russell King - ARM Linux
2013-08-31 11:55       ` Jean-Francois Moine
2013-08-31 12:17         ` Russell King - ARM Linux
2013-09-01  7:04       ` Jean-Francois Moine
2013-09-01  9:26     ` Sebastian Hesselbarth
2013-09-01 11:23       ` Jean-Francois Moine
2013-09-26  8:11       ` Jean-Francois Moine
2013-09-26  8:31         ` Sebastian Hesselbarth
2013-09-26 11:28           ` Jean-Francois Moine
2013-09-26 12:42             ` Sebastian Hesselbarth
2013-09-28 14:27             ` Sebastian Hesselbarth
2013-10-03 16:17               ` Jean-Francois Moine [this message]
2013-10-08 16:11                 ` Jason Cooper
2013-10-08 17:59                   ` Jean-Francois Moine
2013-10-08 18:00                     ` Jason Cooper

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=20131003181716.6d03d576@armhf \
    --to=moinejf@free.fr \
    --cc=linux-arm-kernel@lists.infradead.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).