[alsa-devel] ASOC snd_soc_dai_ops for clock mux control
Hi all,
I'm working on the driver of an audio CPU DAI IP providing - Internal clocks which can be used for master clock generation by TX as well as RX section - One oversampling clock available to RX section - One oversampling clock available to TX section.
Kernel version is 3.5.7
I want to add support to the CPU DAI driver to - Specify the rate of the input clocks - Select which of the clock inputs shall be used by RX and which shall be used by TX section
I'm currently wondering how to map this to existing snd_soc_dai_ops functions. Currently I see only set_sysclk, set_pll, set_clkdiv for clock control.
I plan to use set_sysclk to specify the rate as well as the direction of each clock.
What is currently missing for me is a way to specify the clock to be used by RX or TX section.
I can't really add this in set_sysclk. In case I switch to clock X when set_sysclk is called with clock ID of X, I need a way to distinguish if RX or TX section or both need to switch to this clock. But I can't really double the internal clock X in virtual clocks X_TX, X_RX (one time for TX and one time for RX section) as the internal clock X has only one rate for both sections and this would not represent the hardware correctly.
Do you have any recommendation how to implement ?
What do you think about adding a new function pointer to snd_soc_dai_ops ? int (*set_clkmux)(struct snd_soc_dai *dai, int mux_id, int source_id); I think this would be the cleanest solution as it models the features of the hardware (the clock multiplexers for RX or TX sections)
It might be possible to use set_pll or set_clkdiv to realize. I could use set_pll and ignore the freq_in and freq_out I could use set_clkdiv and interpret div (divider integer value) as a source_id But this is not a 100% clean solution in my opinion.
Best regards
Christoph
On 04/03/2013 09:22 AM, Gellner, Christoph (ADITG/SW1) wrote:
Hi all,
I'm working on the driver of an audio CPU DAI IP providing
Internal clocks which can be used for master clock generation by TX as well as RX sectionOne oversampling clock available to RX sectionOne oversampling clock available to TX section.Kernel version is 3.5.7
I want to add support to the CPU DAI driver to
Specify the rate of the input clocksSelect which of the clock inputs shall be used by RX and which shall be used by TX sectionI'm currently wondering how to map this to existing snd_soc_dai_ops functions. Currently I see only set_sysclk, set_pll, set_clkdiv for clock control.
I plan to use set_sysclk to specify the rate as well as the direction of each clock.
What is currently missing for me is a way to specify the clock to be used by RX or TX section.
Do you have any recommendation how to implement ?
Let's say your CPU DAI IP has 3 clocks which we'll call MCLK (master clock), FLL1, and FLL2 (the two oversampling clocks).
Are you wanting a way to say: "RX should use FLL1 and TX should use FLL2" ??
If so, there's a couple options I can think of. (A) You could call a codec-specific API in your machine driver that expresses this intent. (B) you could create "virtual" clock ID's that express the mapping (e.g. FLL1_TX, FLL1_RX, FLL2_TX, FLL2_RX). I think (A) is a cleaner solution that clearly communicates what is happening.
-gabriel
On Wed, Apr 03, 2013 at 10:55:05PM -0700, Gabriel M. Beddingfield wrote:
If so, there's a couple options I can think of. (A) You could call a codec-specific API in your machine driver that expresses this intent. (B) you could create "virtual" clock ID's that express the mapping (e.g. FLL1_TX, FLL1_RX, FLL2_TX, FLL2_RX). I think (A) is a cleaner solution that clearly communicates what is happening.
Or just extend snd_soc_dai_set_sysclk() to have an extra paremeter for source like we did with snd_soc_dai_set_pll() (for pretty much the same reason).
Hi,
Thank you for your feedback. Basically I want to specify clocks for RX section and TX section independently.
If this is "RX should use FLL1 and TX should use FLL2" or "RX should use FLL1 and TX should use MCLK" should not make any difference in my opinion.
As you state, solution A is cleaner as it clearly communicates what is happening below.
My target is to use ASOC architecture. Therefore I do not want to bypass it.
As I understand the ASOC architecture target to provide interfaces to all DAI configurations and handles the linking. Therefore I would prefer to add the missing set_clkmux to ASOC architecture. Is something like clock multiplexers really that special ? What is your opinion, would set_clkmux be beneficial for ASOC architecture ?
I understand that in case there is only one section for RX and TX this can be implicitly handled by set_sysclk. I'm currently wondering what shall be configured by set_sysclk. Is it only the clock, rate and direction of the clock or does it implies that the clock is to be used in all cases ?
What happens in case the oversampling clock FLL1 can be output, too (generated from MCLK). Is it allowed to call set_sysclk two times 1) specify MCLK to be input and the rate 2) specify FLL1 to be output at a rate derived from MCLK
I believe in this case using set_sysclk for selecting the clock can be really difficult. What is your opinion ?
Best regards
Christoph
-----Original Message----- From: Gabriel M. Beddingfield [mailto:gabrbedd@gmail.com] Sent: Donnerstag, 4. April 2013 07:55 To: Gellner, Christoph (ADITG/SW1) Cc: alsa-devel@alsa-project.org Subject: Re: [alsa-devel] ASOC snd_soc_dai_ops for clock mux control
On 04/03/2013 09:22 AM, Gellner, Christoph (ADITG/SW1) wrote:
Hi all,
I'm working on the driver of an audio CPU DAI IP providing
Internal clocks which can be used for master clock generation by TX as well as RX sectionOne oversampling clock available to RX sectionOne oversampling clock available to TX section.Kernel version is 3.5.7
I want to add support to the CPU DAI driver to
Specify the rate of the input clocksSelect which of the clock inputs shall be used by RX and which shall be used by TX sectionI'm currently wondering how to map this to existing snd_soc_dai_ops functions. Currently I see only set_sysclk, set_pll, set_clkdiv for clock control.
I plan to use set_sysclk to specify the rate as well as the direction of each clock.
What is currently missing for me is a way to specify the clock to be used by RX or TX section.
Do you have any recommendation how to implement ?
Let's say your CPU DAI IP has 3 clocks which we'll call MCLK (master clock), FLL1, and FLL2 (the two oversampling clocks).
Are you wanting a way to say: "RX should use FLL1 and TX should use FLL2" ??
If so, there's a couple options I can think of. (A) You could call a codec-specific API in your machine driver that expresses this intent. (B) you could create "virtual" clock ID's that express the mapping (e.g. FLL1_TX, FLL1_RX, FLL2_TX, FLL2_RX). I think (A) is a cleaner solution that clearly communicates what is happening.
-gabriel
participants (3)
-
Gabriel M. Beddingfield -
Gellner, Christoph (ADITG/SW1) -
Mark Brown