From: Abel Vesa <abel.vesa@nxp.com>
To: Philippe Schenker <philippe.schenker@toradex.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"peng.fan@nxp.com" <peng.fan@nxp.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: Broken Audio on Stable Kernels for i.MX 7 based Boards
Date: Fri, 20 May 2022 16:48:43 +0300 [thread overview]
Message-ID: <YoecO1jxbh3nVJGF@abelvesa> (raw)
In-Reply-To: <536ad55a36d88364299f22782f7c12a6c70c5c11.camel@toradex.com>
On 22-05-20 13:25:29, Philippe Schenker wrote:
> Hello
>
> I noticed today, that commit eccac77ede394 ("clk: imx7d: Remove
> audio_mclk_root_clk") was backported to stable kernels. This commit by
> itself does break audio functionality on i.MX 7 based boards. [1]
>
> For this to work commit 4cb7df64c73 ("ARM: dts: imx7: Use
> audio_mclk_post_div instead audio_mclk_root_clk") is also needed but is
> lacking a Fixes: tag, hence it is missing in stable kernels. [2]
>
> I noticed this while merging stable-patches into our downstream-
> branches.
>
> @Abel can you confirm my finding?
Hi Philippe,
Yes. Sorry about it. I should've added the Fixes tag
to the first patch (of that series) too. My bad.
Lets hope Greg pick it up.
> @Greg could you pull patch [2] into kernels where [1] got merged?
>
> Thanks,
> Philippe
>
>
> [1]
> https://lore.kernel.org/all/20220127141052.1900174-2-abel.vesa@nxp.com/
> [2]
> https://lore.kernel.org/all/20220127141052.1900174-1-abel.vesa@nxp.com/
next prev parent reply other threads:[~2022-05-20 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 13:25 Broken Audio on Stable Kernels for i.MX 7 based Boards Philippe Schenker
2022-05-20 13:48 ` Abel Vesa [this message]
2022-05-20 20:24 ` gregkh
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=YoecO1jxbh3nVJGF@abelvesa \
--to=abel.vesa@nxp.com \
--cc=francesco.dolcini@toradex.com \
--cc=gregkh@linuxfoundation.org \
--cc=peng.fan@nxp.com \
--cc=philippe.schenker@toradex.com \
--cc=stable@vger.kernel.org \
/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