Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Kulhavy <petr@barix.com>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: DT soundcard driver with special clock routing
Date: Mon, 14 Dec 2015 12:32:01 +0100	[thread overview]
Message-ID: <566EA8B1.2020908@barix.com> (raw)
In-Reply-To: <5669B2BD.6010100@samsung.com>

Hi Sylwester,

thank you for the explanation. I can follow the clock description in the 
DT and it looks like a reasonable approach.
However neither the codec or I2S seem to implement any clock provider.
How is the implementation side done? I mean someone needs to set the 
PLLs, etc.

Thanks
Petr

On 10.12.2015 18:13, Sylwester Nawrocki wrote:
> On 10/12/15 17:31, Petr Kulhavy wrote:
>> Hi,
>>
>> I'm developing a DT-based driver for an ARM SoC device with the
>> following special clock routing:
>>
>> - WM8758 codec attached to the CPU DAI via I2S
>> - the codec is I2S clock master
>> - the CPU feeds the codec with 12MHz clock (outside of the I2S)
>> - the codec converts the 12MHz  internally to 48kHz*256 or 44.1kHz *256
>> clock and provides it to I2S as MCLK
>>
>> So the special set-up needed here is that the codec needs to be
>> configured to:
>> a) generate the proper MCLK
>> b) enable the respective GPIO pin as clock output
>>
>> What is the best way of representing this set-up using device tree?
>> I'm wondering if this can be done by adding a specific option in the
>> codec DT binding for enabling the clock output and then use the simple
>> audio card.
>> Or do I need to write a specific soundcard driver that sets up the codec
>> registers? I would like to avoid that if possible and use existing code...
>>
>> What would you recommend?
> I assume when the clock enable/disable code is not there it could
> be added to the codec driver, e.g. like in case of max98090.
> The clock source just needs to be exposed as a common clock object.
>
> As an example of similar setup you could take a look at
> arch/arm/boot/dts/exynos4412-odroid-common.dts. The difference
> was that in case of Odroid the clock was generated by a PLL inside
> a SoC, then it was routed to I2S which fed the clock to the codec
> through the SoC's io pin. The codec was I2S master and the I2S
> IP block was actually a source of its main ("mclk") clock.
> I hope this helps.
>

  reply	other threads:[~2015-12-14 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 16:31 DT soundcard driver with special clock routing Petr Kulhavy
2015-12-10 17:13 ` Sylwester Nawrocki
2015-12-14 11:32   ` Petr Kulhavy [this message]
2015-12-14 12:28     ` Sylwester Nawrocki
2015-12-16  7:54       ` Petr Kulhavy
2015-12-23 12:43         ` Sylwester Nawrocki

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=566EA8B1.2020908@barix.com \
    --to=petr@barix.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=s.nawrocki@samsung.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