Skip to contentSkip to conversation

Clock generators in ASoC setups

DISCUSSION Daniel Mack 2 participants 4 messages Jul 25, 2012 – Aug 4, 2012

lore
Share & tools
lore
#0 lore raw

Hi Mark and Liam,

some board I'm working on feature chips (connected via I2C) that are in charge of generating clocks for both the CPU DAI and the codecs. Previously, I configured them manually in platform specific code, but I wonder if there's a better, more generic way to get the job done, especially with regards to DT driven boards?

Thanks,
Daniel

#1 lore raw
Quoted 5 lines · Daniel Mack

some board I'm working on feature chips (connected via I2C) that are in charge of generating clocks for both the CPU DAI and the codecs. Previously, I configured them manually in platform specific code, but I wonder if there's a better, more generic way to get the job done, especially with regards to DT driven boards?

The problem here is that we don't have a usable clock API to work with.

#2 lore raw
Quoted 10 lines · Mark Brown
Quoted 5 lines · Daniel Mack

some board I'm working on feature chips (connected via I2C) that are in charge of generating clocks for both the CPU DAI and the codecs. Previously, I configured them manually in platform specific code, but I wonder if there's a better, more generic way to get the job done, especially with regards to DT driven boards?

The problem here is that we don't have a usable clock API to work with.

Hmm, could you elaborate a bit about the background here? So the idea is to have the clock framework that handles all system clocks also take care for clocks related to audio?

What would such a framework need to accomplish, and what missing in - for example - the common clock framework in that regard?

If there's a discussion thread about that topic, a pointer to that would suffice.

Thanks,
Daniel

#3 lore raw
Quoted 8 lines · Daniel Mack
Quoted 3 lines · Mark Brown

On Wed, Jul 25, 2012 at 10:18:24AM +0200, Daniel Mack wrote:

The problem here is that we don't have a usable clock API to work with.

Hmm, could you elaborate a bit about the background here? So the idea is to have the clock framework that handles all system clocks also take care for clocks related to audio?

Yes, since many of them are the same clocks - we certainly have massive overlap here and clocks can go in both directions.

Quoted 2 lines

What would such a framework need to accomplish, and what missing in - for example - the common clock framework in that regard?

Well, for a start it'd need to be deployed on a useful set of platforms. Right now we've not got any clock API at all on most platforms and only a vanishingly small set are using the generic API. I'm hopefully going to persuade Arnd to unblock the one issue preventing me fixing the first problem and obviously there's some progress on the second.

As things stand there just isn't a non-specific clock API that anything that generates clocks can realistically use.