mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olivier MOYSAN <olivier.moysan@foss.st.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	<linux-sound@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: stm32: sai: manage context in set_sysclk callback
Date: Wed, 24 Sep 2025 11:48:58 +0200	[thread overview]
Message-ID: <a4950a0d-32a2-4cdd-8c8a-8f451181b0d6@foss.st.com> (raw)
In-Reply-To: <875xdgpmq6.wl-kuninori.morimoto.gx@renesas.com>

Hi Kuninori,

On 9/18/25 03:34, Kuninori Morimoto wrote:
> 
> Hi Olivier
> 
> Thank you for clarify the situation
> 
>> Looking at the traces (see below), initially, we had one call with the
>> 'in' direction (kernel clock frequency) and one call with the 'out'
>> direction.
> (snip)
>> Now, both calls have the 'out' direction when the property
>> 'system-clock-direction-out' is set. This seems more consistent with the
>> changes from commit 5725bce709db1.
> 
> Ah.. simple-card-utils calls snd_soc_dai_set_sysclk() from 3 functions
> 
> 	- simple_init_dai()
> 	- simple_util_hw_params()
> 	- simple_util_shutdown()
> 
> but its "direction" is...
> 
> Step0:
> 	Before
> 	a728f56094e7cf60a1dc0642fe86901d1a4dfb4e
> 	 ("ASoC: make clock direction configurable in asoc-simple")
> 
> 	- simple_init_dai()		fixed: 0
> 	- simple_util_hw_params()	fixed: SND_SOC_CLOCK_xx
> 	- simple_util_shutdown()	fixed: SND_SOC_CLOCK_xx
> 
> Step1:
> 	After
> 	a728f56094e7cf60a1dc0642fe86901d1a4dfb4e
> 	 ("ASoC: make clock direction configurable in asoc-simple")
> 
> 	and before
> 
> 	5725bce709db1c001140d79398581e067e28c031
> 	("ASoC: simple-card-utils: Unify clock direction by clk_direction")
> 
> 
> 	- simple_init_dai()		dai->clk_direction
> 	- simple_util_hw_params()	fixed: SND_SOC_CLOCK_xx
> 	- simple_util_shutdown()	fixed: SND_SOC_CLOCK_xx
> 
> Step2:
> 	After
> 	5725bce709db1c001140d79398581e067e28c031
> 	("ASoC: simple-card-utils: Unify clock direction by clk_direction")
> 
> 	- simple_init_dai()		dai->clk_direction
> 	- simple_util_hw_params()	dai->clk_direction
> 	- simple_util_shutdown()	dai->clk_direction
> 
> In Step0 and Step1, your dirver is called with both dir IN/OUT ?
> 

Yes, based on the trace, this appears to be the case.

>> In my setup, the kernel clock is an input clock. Maybe it should be
>> tagged as an input clock. However, we have no
>> 'system-clock-direction-in' property yet.
>> Anyway, the patch in the STM32 SAI driver is still valid.
> 
> OK
> 
> Or maybe reset simple_dai->sysclk somehow (not sure...) ?
> (simple_init_dai() will call snd_soc_dai_set_sysclk() if it has
> simple_dai->sysclk)
> 

Yes, resetting simple_dai->sysclk may also be an option, but I could not 
find a way to do it in practice. Requesting a reset of 
simple_dai->sysclk from the CPU DAI .probe callback might be the right 
time I think, but there is no service that allows this.
Another way would be to set "system-clock-frequency = <0>" in the CPU DT 
node. However, this is not possible, as it conflicts with the following 
check in the simple_set_clk_rate() function:
if (simple_dai->clk_fixed && rate != simple_dai->sysclk) {
    dev_err(...)
}

So, the current patch still seems like the better option to me.

Best regards
Olivier

> Thank you for your help !!
> 
> Best regards
> ---
> Kuninori Morimoto

  reply	other threads:[~2025-09-24  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16 12:31 Olivier Moysan
2025-09-17  0:32 ` Kuninori Morimoto
2025-09-17 14:20   ` Olivier MOYSAN
2025-09-18  1:34     ` Kuninori Morimoto
2025-09-24  9:48       ` Olivier MOYSAN [this message]
2025-09-24 23:26         ` Kuninori Morimoto
2025-09-26 12:50 ` Mark Brown

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=a4950a0d-32a2-4cdd-8c8a-8f451181b0d6@foss.st.com \
    --to=olivier.moysan@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®