Re: renesas-drivers-2015-10-13-v4.3-rc5

[Simon Horman <horms@verge.net.au>]

On Wed, Oct 14, 2015 at 09:04:43AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Wed, Oct 14, 2015 at 2:39 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Tue, Oct 13, 2015 at 12:28:45PM +0200, Geert Uytterhoeven wrote:
> >> I've pushed renesas-drivers-2015-10-13-v4.3-rc5 to
> >> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
> >> This tree is meant to ease development of platform support and drivers for
> >> Renesas ARM ("shmobile") SoCs. It's created by merging (a) the for-next
> >> branches of various subsystem trees and (b) branches with driver code
> >> submitted or planned for submission to maintainers into the development
> >> branch of Simon Horman's renesas.git tree.
> >>
> >> Today's version is based on renesas-devel-20151013v2-v4.3-rc5.
> >>
> >> Notes:
> >>   - As topic/gen3-cpg-v8+fix and topic/arm64-rcar-gen3-v10.1 started
> >>     using the cpg-mssr driver instead of the cpg-mstp driver, while
> >>     later integration topic branches still used cpg-mstp bindings,
> >>     several drivers (e.g. gpio, but that should affect wake-up-by-gpio
> >>     only) cannot get their module clocks, or their module clocks are not
> >>     managed correctly (e.g. ravb, which still works despite this).
> >>     There are 3 ways to fix this:
> >>       - Convert your dtsi blocks to the cpg-mssr bindings (best),
> >>       - Re-add clk-mstp.o for CONFIG_ARCH_R8A7795 in
> >>       drivers/clk/shmobile/Makefile, and make sure CONFIG_PM=n
> >>       (untested),
> >>       - Use renesas-drivers-2015-09-29-v4.3-rc3 (for the lazy consumer).
> >>     However, in the light of "[PATCH/RFC v3 0/3] clk: shmobile: Add new
> >>     Renesas CPG/MSSR DT bindings"
> >>     (http://www.spinics.net/lists/devicetree/msg97237.html), all of the
> >>     above are temporary solutions.
> >
> > I would like to update topic/arm64-rcar-gen3-v10.1 and post
> > as v11 for further review both here and in the broader Linux ARM community
> > at linux-arm-kernel@lists.infradead.org.
> >
> > Do you recommend updating that patchset for the above? If so in
> > which way do you recommend updating it?
> 
> I'm afraid there's not much you can do before I have a new CPG/MSSR
> driver that works.
> 
> You can start updating the dtsi, but you can't test it, and I had to do the same
> updates to test my driver anyway.

My motivation for posting v11 is to get more eyes on the code.
I think its fine to state that the CPG bindings are expected to
change. With that in mind I think it would be best not to make any changes
to topic/arm64-rcar-gen3-v10.1 in that regard for v11. Does that sound
sensible?