* [GIT PULL] Rockchip clock updates for 5.1
@ 2019-02-01 11:17 Heiko Stuebner
2019-02-05 22:08 ` Stephen Boyd
0 siblings, 1 reply; 3+ messages in thread
From: Heiko Stuebner @ 2019-02-01 11:17 UTC (permalink / raw)
To: Stephen Boyd, mturquette; +Cc: linux-clk, linux-rockchip
Hi Mike, Stephen,
looks I can re-use my introduction from 4.20 and 5.0 - no big changes
again this time.
A rate_parent flag and some fixup for the fractional part of a PLL
So please pull.
Thanks
Heiko
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.1-rockchip-clk1
for you to fetch changes up to 491b00ff699356a8dab10eb517a1b44205514c9e:
clk: rockchip: add CLK_SET_RATE_PARENT for rk3066 lcdc dclks (2019-01-07 09:17:15 +0100)
----------------------------------------------------------------
Fix for PLL rate calculation on rk3328 and SET_RATE_PARENT flag
for the display clock on rk3066.
----------------------------------------------------------------
Finley Xiao (1):
clk: rockchip: add CLK_SET_RATE_PARENT for rk3066 lcdc dclks
Katsuhiro Suzuki (1):
clk: rockchip: fix frac settings of GPLL clock for rk3328
drivers/clk/rockchip/clk-rk3188.c | 4 ++--
drivers/clk/rockchip/clk-rk3328.c | 12 ++++++------
2 files changed, 8 insertions(+), 8 deletions(-)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [GIT PULL] Rockchip clock updates for 5.1
2019-02-01 11:17 [GIT PULL] Rockchip clock updates for 5.1 Heiko Stuebner
@ 2019-02-05 22:08 ` Stephen Boyd
2019-02-15 10:32 ` Heiko Stübner
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Boyd @ 2019-02-05 22:08 UTC (permalink / raw)
To: Heiko Stuebner, Stephen Boyd, mturquette; +Cc: linux-clk, linux-rockchip
Quoting Heiko Stuebner (2019-02-01 03:17:47)
> Hi Mike, Stephen,
>
> looks I can re-use my introduction from 4.20 and 5.0 - no big changes
> again this time.
>
> A rate_parent flag and some fixup for the fractional part of a PLL
>
> So please pull.
Thanks. Pulled into clk-next. If you like I can pick patches directly
from list if you send out a reviewed-by tag on the patches. I'm happy
either way.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [GIT PULL] Rockchip clock updates for 5.1
2019-02-05 22:08 ` Stephen Boyd
@ 2019-02-15 10:32 ` Heiko Stübner
0 siblings, 0 replies; 3+ messages in thread
From: Heiko Stübner @ 2019-02-15 10:32 UTC (permalink / raw)
To: Stephen Boyd; +Cc: Stephen Boyd, mturquette, linux-clk, linux-rockchip
Am Dienstag, 5. Februar 2019, 23:08:23 CET schrieb Stephen Boyd:
> Quoting Heiko Stuebner (2019-02-01 03:17:47)
>
> > Hi Mike, Stephen,
> >
> > looks I can re-use my introduction from 4.20 and 5.0 - no big changes
> > again this time.
> >
> > A rate_parent flag and some fixup for the fractional part of a PLL
> >
> > So please pull.
>
> Thanks. Pulled into clk-next. If you like I can pick patches directly
> from list if you send out a reviewed-by tag on the patches. I'm happy
> either way.
It's hard to determine that before each cycle :-) .
The upside right now is, that handling clock-ids gets very easy.
Shared branches between trees for dt-binding ids are not favored,
instead the way to go seems to be doing numbers first and replacing
them in the next cycle when the ids got merged.
Right now I'm also in control of the shared id-branch, merging it myself
into both clock and dts branches, which somehow seems to still be ok,
and hence I save a bit of work :-D .
But of course we can merge the real easy things directly into the clock
tree ... I'll keep that in mind for the next clock patches.
Heiko
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-02-15 10:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-01 11:17 [GIT PULL] Rockchip clock updates for 5.1 Heiko Stuebner
2019-02-05 22:08 ` Stephen Boyd
2019-02-15 10:32 ` Heiko Stübner
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).