From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] clk: rockchip: leave npll for DCLK_VOP0(HDMI) only
Date: Thu, 08 Jan 2015 23:30:01 +0100 [thread overview]
Message-ID: <3353483.Eif0pChkY5@phil> (raw)
In-Reply-To: <1416236138-11010-1-git-send-email-kever.yang@rock-chips.com>
Hi Kever,
Am Montag, 17. November 2014, 22:55:36 schrieb Kever Yang:
> To support all kinds of frequency requirement for HDMI on rk3288,
> we need a PLL that can change rate at run time.
>
> There are some discussion before at [0], I think we can just leave
> the npll for HDMI(DCLK_VOP0) used to make it simple.
>
> Comments are welcome.
I think I said it in private somewhere already, but just so it's also
available publically:
I don't think customizing/limiting the clock usage like this will fly,
especially as this would require each and every rk3288 board to use vop0 for
hdmi and vop1 for other stuff.
With the new rk3288 Firefly devboard this concern already becomes reality.
There a vga converter is connected to VOP0, which leaves only vop1 for hdmi if
one wants to support the vga connection.
>From our discussion about this problem I remember that the missing clock
frequencies only affected more esotheric screen resolutions, so personally I'm
not this much concerned an would like to wait till we find a better solution to
the problem.
Heiko
next prev parent reply other threads:[~2015-01-08 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 14:55 [RFC PATCH 0/2] clk: rockchip: leave npll for DCLK_VOP0(HDMI) only Kever Yang
2014-11-17 14:55 ` [RFC PATCH 1/2] clk: rockchip: leave npll for VOP0 only Kever Yang
2014-11-17 14:55 ` [RFC PATCH 2/2] arm: dts: rockchip: select npll as parent of DCLK_VOP0 Kever Yang
2015-01-08 22:30 ` Heiko Stübner [this message]
2015-01-14 22:16 ` [RFC PATCH 0/2] clk: rockchip: leave npll for DCLK_VOP0(HDMI) only Mike Turquette
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=3353483.Eif0pChkY5@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).