public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Sameer Pujar <spujar@nvidia.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	thierry.reding@gmail.com, jonathanh@nvidia.com,
	oder_chiou@realtek.com, broonie@kernel.org, perex@perex.cz,
	tiwai@suse.com, lgirdwood@gmail.com, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ASoC: rt5640: Update MCLK rate in set_sysclk()
Date: Fri, 10 Feb 2023 14:00:55 +0530	[thread overview]
Message-ID: <4a45f084-7d33-59d2-8ef9-cb95e29866a3@nvidia.com> (raw)
In-Reply-To: <87lel61k3h.wl-kuninori.morimoto.gx@renesas.com>

Hi Morimoto-san,

On 10-02-2023 05:12, Kuninori Morimoto wrote:
>
>> Simple-card/audio-graph-card drivers do not handle MCLK clock when it
>> is specified in the codec device node. The expectation here is that,
>> the codec should actually own up the MCLK clock and do necessary setup
>> in the driver.
> I have no objection about this patch, but have interesting about this comment.
>
> Simple-card/audio-graph-card both are using asoc_simple_hw_params,
> and it calls clk_set_rate() for Codec/CPU if it has mclk.
> But am I misunderstanding ?
> If it was simple-card-utils side miss, I'm happy to fix it.

The simple-card-utils driver does not populate the clock handle whenever 
the MCLK clock is parsed from CODEC device node. So 
asoc_simple_set_clk_rate() will not update the rate and clock 
enable/disable won't happen either.Initially I had tried to fix this in 
the simple-card-utils itself and it did break few things on other HW.
Please see [0] for relevant discussion.

Later [1] was pushed to address the issue I was facing that time.

In summary, the suggestion was, clock property should be associated with 
only devices and device driver should own up the clock handling for it. 
The machine driver can just pass the required configuration for it.


[0] 
https://patchwork.ozlabs.org/project/linux-tegra/patch/1612939421-19900-2-git-send-email-spujar@nvidia.com/#2647112
[1] 
https://lore.kernel.org/lkml/1615829492-8972-3-git-send-email-spujar@nvidia.com/

  reply	other threads:[~2023-02-10  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 14:36 [PATCH 0/2] Codec support on Jetson AGX Orin Sameer Pujar
2023-02-09 14:36 ` [PATCH 1/2] ASoC: rt5640: Update MCLK rate in set_sysclk() Sameer Pujar
2023-02-09 23:42   ` Kuninori Morimoto
2023-02-10  8:30     ` Sameer Pujar [this message]
2023-02-12 23:56       ` Kuninori Morimoto
2023-02-09 14:36 ` [PATCH 2/2] arm64: tegra: Audio codec support on Jetson AGX Orin Sameer Pujar
2023-02-10  8:45   ` Krzysztof Kozlowski
2023-02-10  9:02     ` Sameer Pujar
2023-02-09 18:36 ` (subset) [PATCH 0/2] Codec " 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=4a45f084-7d33-59d2-8ef9-cb95e29866a3@nvidia.com \
    --to=spujar@nvidia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=oder_chiou@realtek.com \
    --cc=perex@perex.cz \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    --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