From: Shawn Guo <shawnguo@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH] arm64: dts: imx8mp: don't initialize audio clocks from CCM node
Date: Fri, 9 Jun 2023 22:19:57 +0800 [thread overview]
Message-ID: <20230609141957.GY4199@dragon> (raw)
In-Reply-To: <20230602191013.4124840-1-l.stach@pengutronix.de>
On Fri, Jun 02, 2023 at 09:10:13PM +0200, Lucas Stach wrote:
> The audio clocks should be intitialized to the correct rate by the subsystem
> using them. There is no need to always initialize them from the CCM node
> assigned-clocks property. This way boards using the audio clocks in a non-
> standard way can change them without first duplicating the CCM clock
> setup.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Applied, thanks!
prev parent reply other threads:[~2023-06-09 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 19:10 [PATCH] arm64: dts: imx8mp: don't initialize audio clocks from CCM node Lucas Stach
2023-06-09 14:19 ` Shawn Guo [this message]
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=20230609141957.GY4199@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=patchwork-lst@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).