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: Wed, 16 Dec 2015 07:54:19 +0000	[thread overview]
Message-ID: <567118AB.5060302@barix.com> (raw)
In-Reply-To: <566EB5FD.2000803@samsung.com>

Hi Sylwester,

Currently I'm struggling with the clocks on the DaVinci platform as the 
clock tree is defined in the platform driver and not in DT.
Is there a way to reference the clocks by names from DT, or does the 
DaVinci clock driver need to be rewritten for DT support?

There is one more thing I came across using the simple soundcard driver. 
The codec needs to be set to generate the clock via PLL.
Unfortunately the simple soundcard always passes clock ID 0 to 
snd_soc_dai_set_sysclk() - I need a different value for the internal PLL.

What is the preferred approach here? On one hand the simple soundcard 
driver could be extended with a DT parameter "clock ID".
Or does a dedicated soundcard driver need to be written?

Thanks
Petr

On 14.12.2015 13:28, Sylwester Nawrocki wrote:
> Yes, you need the clock provider somewhere. In my case it was the I2S 
> driver that registered a clock provider. Probably you can add your 
> output clock provider to your SoC's main clock controller driver, and 
> perhaps use pinctrl API for the pin function mux setup. You can place 
> assigned-clock* DT properties in the clock provider node and the PLL's 
> will be configured by the kernel's clk subsystem. Grep for 
> of_clk_set_defaults or see last chapter of 
> Documentation/devicetree/bindings/clock/clock-bindings.txt. 

  reply	other threads:[~2015-12-16  7:54 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
2015-12-14 12:28     ` Sylwester Nawrocki
2015-12-16  7:54       ` Petr Kulhavy [this message]
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=567118AB.5060302@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