From: Tony Lindgren <tony@atomide.com>
To: Suman Anna <s-anna@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: dra7xx-clocks: Fixup IPU1 mux clock parent source
Date: Thu, 20 Feb 2020 09:52:51 -0800 [thread overview]
Message-ID: <20200220175251.GO37466@atomide.com> (raw)
In-Reply-To: <20200211155103.23973-1-s-anna@ti.com>
* Suman Anna <s-anna@ti.com> [200211 07:52]:
> The IPU1 functional clock is the output of a mux clock (represented
> by ipu1_gfclk_mux previously) and the clock source for this has been
> updated to be sourced from dpll_core_h22x2_ck in commit 39879c7d963e
> ("ARM: dts: dra7xx-clocks: Source IPU1 functional clock from CORE DPLL").
> ipu1_gfclk_mux is an obsolete clock now with the clkctrl conversion,
> and this clock source parenting is lost during the new clkctrl layout
> conversion.
>
> Remove this stale clock and fix up the clock source for this mux
> clock using the latest equivalent clkctrl clock. This restores the
> previous logic and ensures that the IPU1 continues to run at the
> same frequency of IPU2 and independent of the ABE DPLL.
>
> Fixes: b5f8ffbb6fad ("ARM: dts: dra7: convert to use new clkctrl layout")
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> Hi Tony,
>
> Patch on top of 5.6-rc1. Appreciate it if you can include it for the 5.6-rc
> cycle.
OK applying into fixes thanks.
Tony
prev parent reply other threads:[~2020-02-20 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 15:51 [PATCH] ARM: dts: dra7xx-clocks: Fixup IPU1 mux clock parent source Suman Anna
2020-02-11 15:51 ` Suman Anna
2020-02-20 17:52 ` Tony Lindgren [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=20200220175251.GO37466@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.