From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/4] rockchip: fix serial output on rk3036
Date: Tue, 28 Feb 2017 18:25:50 +0100 [thread overview]
Message-ID: <1641374.43nVGhYm9v@phil> (raw)
In-Reply-To: <20170228073240.GJ25384-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Am Montag, 27. Februar 2017, 23:32:40 CET schrieb Stephen Boyd:
> On 02/28, Heiko Stuebner wrote:
> > Recent changes to the 8250-dw variant revealed issues concerning
> > how the clock rates are handled on the rk3036 uart.
> >
> > For one, there was an error in the clock declaration, but also the
> > shared uart-pll-select-mux also as default got supplied from the apll
> > that also supplies the cpu and thus gets frequency scaled.
> >
> > The patches in this series remedy this and make the debug uart
> > function again on 4.10 + current merge window.
>
> What's the merge path? The last patch is sort of questionable
> because it fixes a regression by changing assigned clocks in DT,
> which doesn't really make sense from a DT perspective (it should
> have been right already or can be configured from the clk driver
> itself in software).
yeah, I was (and somewhat still am) debating on the dt vs. clk driver
positioning. As you can see, there are multiple sources, most of them are
somewhat questionable. I.e. apll and dpll are the cpu + ddr supplies and we
will want to do ddr-scaling at some point too.
So the gpll really is the only really sane option and I guess simply doing it
in the driver (similar to what rk3188 does) might be better.
If some boards really want to select a different source, they then can do that
via assigned-clocks in the board-dts.
prev parent reply other threads:[~2017-02-28 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 5:14 [PATCH 0/4] rockchip: fix serial output on rk3036 Heiko Stuebner
[not found] ` <20170228051420.7214-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2017-02-28 5:14 ` [PATCH 1/4] clk: rockchip: add ", " to mux_pll_src_apll_dpll_gpll_usb480m_p " Heiko Stuebner
2017-02-28 7:33 ` [PATCH 1/4] clk: rockchip: add "," " Stephen Boyd
2017-02-28 5:14 ` [PATCH 2/4] clk: rockchip: add SCLK_UARTPLL to rk3036 clock ids Heiko Stuebner
2017-02-28 5:14 ` [PATCH 3/4] clk: rockchip: assign the SCLK_UARTPLL clock id on rk3036 Heiko Stuebner
2017-02-28 5:14 ` [PATCH 4/4] ARM: dts: rockchip: Make uartpll a child of the gpll " Heiko Stuebner
2017-02-28 7:32 ` [PATCH 0/4] rockchip: fix serial output " Stephen Boyd
[not found] ` <20170228073240.GJ25384-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-02-28 17:25 ` Heiko Stuebner [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=1641374.43nVGhYm9v@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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).