From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Jernej Skrabec <jernej.skrabec@siol.net>
Cc: sboyd@kernel.org, mturquette@baylibre.com,
linux-kernel@vger.kernel.org, wens@csie.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] clk: sunxi-ng: h6: Allow video & vpu clocks to change parent rate
Date: Wed, 3 Apr 2019 09:54:30 +0200 [thread overview]
Message-ID: <20190403075430.4j7sw5vxqop6ptkj@flea> (raw)
In-Reply-To: <20190402210623.14988-4-jernej.skrabec@siol.net>
[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]
On Tue, Apr 02, 2019 at 11:06:23PM +0200, Jernej Skrabec wrote:
> Video related clocks need to set rate as close as possible to the
> requested one, so they should be able to change parent clock rate.
>
> VPU clock sometimes has to be set to higher than default parent clock
> rate. This is requ
>
> Add CLK_SET_RATE_PARENT flag to tcon-lcd0, tcon-tv0 and ve.
>
> Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-03 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 21:06 [PATCH 0/3] clk: sunxi-ng: H6 related clock fixes Jernej Skrabec
2019-04-02 21:06 ` [PATCH 1/3] clk: sunxi-ng: nkmp: Avoid GENMASK(-1, 0) Jernej Skrabec
2019-04-03 7:52 ` Maxime Ripard
2019-04-02 21:06 ` [PATCH 2/3] clk: sunxi-ng: h6: Preset hdmi-cec clock parent Jernej Skrabec
2019-04-03 7:54 ` Maxime Ripard
2019-04-02 21:06 ` [PATCH 3/3] clk: sunxi-ng: h6: Allow video & vpu clocks to change parent rate Jernej Skrabec
2019-04-03 7:54 ` Maxime Ripard [this message]
2019-04-03 13:22 ` Chen-Yu Tsai
2019-04-03 14:42 ` Jernej Škrabec
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=20190403075430.4j7sw5vxqop6ptkj@flea \
--to=maxime.ripard@bootlin.com \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=wens@csie.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