From: Shawn Guo <shawnguo2@yeah.net>
To: Liu Ying <victor.liu@nxp.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com
Subject: Re: [PATCH] arm64: dts: imx8mp-skov-revb-mi1010ait-1cp1: Assign "media_isp" clock rate
Date: Thu, 17 Oct 2024 16:43:51 +0800 [thread overview]
Message-ID: <ZxDOR9VL0u6OB+jX@dragon> (raw)
In-Reply-To: <20240924071218.3578402-1-victor.liu@nxp.com>
On Tue, Sep 24, 2024 at 03:12:18PM +0800, Liu Ying wrote:
> Commit 2d39b78e5716 ("arm64: dts: imx8mp: Add DT nodes for the two ISPs")
> added a new phandle to the "assigned-clocks" property of media_blk_ctrl
> node just before the phandle for "video_pll1" clock in i.MX8MP SoC device
> tree so that "media_isp" clock rate is assigned to 500MHz by default.
> However, it missed updating this relevant board device tree where the
> relevant "assigned-clock-rates" property is changed to set a new rate
> for "video_pll1" clock. This causes the "media_isp" clock rate being
> wrongly set to the "video_pll1" clock rate and the "video_pll1" clock
> rate being untouched. Fix this by assigning "media_isp" clock rate
> explicitly to 500MHz in this board device tree.
>
> Fixes: 2d39b78e5716 ("arm64: dts: imx8mp: Add DT nodes for the two ISPs")
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
Applied, thanks!
prev parent reply other threads:[~2024-10-17 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 7:12 [PATCH] arm64: dts: imx8mp-skov-revb-mi1010ait-1cp1: Assign "media_isp" clock rate Liu Ying
2024-10-17 8:43 ` 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=ZxDOR9VL0u6OB+jX@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=victor.liu@nxp.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;
as well as URLs for NNTP newsgroup(s).