public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Shengjiu Wang <shengjiu.wang@nxp.com>
Cc: abelvesa@kernel.org, peng.fan@nxp.com, mturquette@baylibre.com,
	sboyd@kernel.org, Frank.Li@nxp.com, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com,
	linux-clk@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, stefan.eichenberger@toradex.com
Subject: Re: [PATCH RESEND] clk: imx: imx8-acm: fix flags for acm clocks
Date: Wed, 25 Feb 2026 16:18:56 +0800	[thread overview]
Message-ID: <aZ6wcGntUQmwt8yk@shlinux89> (raw)
In-Reply-To: <20260212085750.3253187-1-shengjiu.wang@nxp.com>

On Thu, Feb 12, 2026 at 04:57:50PM +0800, Shengjiu Wang wrote:
>From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
>
>Currently, the flags for the ACM clocks are set to 0. This configuration
>causes the fsl-sai audio driver to fail when attempting to set the
>sysclk, returning an EINVAL error. The following error messages
>highlight the issue:
>fsl-sai 59090000.sai: ASoC: error at snd_soc_dai_set_sysclk on 59090000.sai: -22
>imx-hdmi sound-hdmi: failed to set cpu sysclk: -22
>
>By setting the flag CLK_SET_RATE_NO_REPARENT, we signal that the ACM
>driver does not support reparenting and instead relies on the clock tree
>as defined in the device tree. This change resolves the issue with the
>fsl-sai audio driver.
>
>CC: stable@vger.kernel.org
>Fixes: d3a0946d7ac9 ("clk: imx: imx8: add audio clock mux driver")
>Signed-off-by: Stefan Eichenberger <stefan.eichenberger@toradex.com>
>Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>

Reviewed-by: Peng Fan <peng.fan@nxp.com>

  reply	other threads:[~2026-02-25  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12  8:57 [PATCH RESEND] clk: imx: imx8-acm: fix flags for acm clocks Shengjiu Wang
2026-02-25  8:18 ` Peng Fan [this message]
2026-03-18 15:39 ` Abel Vesa

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=aZ6wcGntUQmwt8yk@shlinux89 \
    --to=peng.fan@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=abelvesa@kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=shengjiu.wang@nxp.com \
    --cc=stefan.eichenberger@toradex.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