Message ID | 48408534.cOKhDiQbmB@phil (mailing list archive) |
---|---|
State | Accepted, archived |
Headers | show |
Series | [GIT,PULL] Rockchip clock updates for 5.1 | expand |
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.
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