Clock support for rk3066,rk3188 and rk3288
Get series with b4
b4 am 14804456.X61YuWlsJQ@diegoVersions newest first · linked by author and title
- v5 Latest posting 3/30 of 14 patches 0 repliesNew
- v5 posting 2/30 of 14 patches 0 repliesSuperseded
- v5 posting 1/314 patches 0 repliesSuperseded
Earlier versions · 4
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v4 | 13 patches | 0 replies | Superseded | |
| v3 | 11 patches | 0 replies | Superseded | |
| v2 | 11 patches | 0 replies | Superseded | |
| v1 | 11 patches | 0 replies | Superseded |
Patches in v5 posting 3/3 No applies recorded yet
None of the 14 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.
Cover letter [PATCH v5 00/14] Clock support for rk3066,rk3188 and rk3288
Hi Mike,
Am Montag, 14. Juli 2014, 10:07:01 schrieb Heiko St?bner:
Quoted 46 lines
Hi Olof,
Am Sonntag, 13. Juli 2014, 20:12:07 schrieb Olof Johansson:
Quoted 3 lines
Hi,
On Sun, Jul 13, 2014 at 12:46 PM, Mike Turquette <[email protected]>
Quoted 32 lines · wrote:
Quoted 20 lines
Quoting Heiko St?bner (2014-07-02 16:53:24)
Quoted 9 lines
This series adds a clock driver infrastructure for Rockchip SoCs in general and clock-definitions for the RK3188 and RK3288 in particular.
Apart from the
arch/armpatches included here, there are some more in the waiting line, like adding the i2c nodes and possibly the pwm, i2s
and spi nodes if the relevant drivers get accepted, where the ids defined in the dt-binding headers are needed.Quoted 3 lines
So if the whole thing is acceptable could we either offer a branch from the clk-tree that can get merged or take the whole series through the arm tree?
Heiko,
This version looks good. I've pushed a branch with all 14 of these patches based on 3.16-rc3 to the clk tree. See:
Quoted 6 lines
git://git.linaro.org/people/mike.turquette/linux.gitclk-rockchipIf everyone is OK to merge that stable branch then I will merge clk-rockchip into clk-next and we're all good. If the arm-soc guys want to carve it up a bit further or handle it in a different way then we can do that. I've Cc'd arm-soc for clarification.
Traditionally we usually take the DT changes through arm-soc, but as long as we share the branch we might be ok. We tend to stick them in different branches in our tree though, so rockchip will be a little mis-sorted this release. Not a big deal, and we can deal with it.
Quoted 5 lines
So, I'll leave it to Heiko to choose here, he knows best what other DT changes are coming this release. If he wants to carry the DT changes separately, then patches 1-10 would be for the clk tree, so it should be easy to reset the branch back a bit (and 11-14 would be for arm-soc).
Quoted 8 lines
hmm, there are essentially two changeset/branches upcoming:
- the collected dts changes for rk3066 and rk3188 I posted saturday These essentially extend patches 12-14
- rk3288 support which would start off patch 11 (the reset controller)So if we were to separate the series I would say patches 1-11 in the shared branch and patch 12-14 as the first ones for a rk3066/rk3188 specific branch.
are you ok with simply resetting the clk-rockchip branch to
"ARM: rockchip: Select ARCH_HAS_RESET_CONTROLLER"
being the last commit and the last 3 patches going through arm-soc?
As we're already at -rc6 now, it would be very cool if we could get this sorted soon.
Thanks
Heiko