From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: renesas-drivers-2015-10-13-v4.3-rc5
Date: Wed, 14 Oct 2015 00:39:46 +0000 [thread overview]
Message-ID: <20151014003946.GD24693@verge.net.au> (raw)
In-Reply-To: <1444732125-12741-1-git-send-email-geert+renesas@glider.be>
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?
[snip]
next prev parent reply other threads:[~2015-10-14 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 10:28 renesas-drivers-2015-10-13-v4.3-rc5 Geert Uytterhoeven
2015-10-14 0:39 ` Simon Horman [this message]
2015-10-14 7:04 ` renesas-drivers-2015-10-13-v4.3-rc5 Geert Uytterhoeven
2015-10-14 7:09 ` renesas-drivers-2015-10-13-v4.3-rc5 Simon Horman
2015-10-14 7:12 ` renesas-drivers-2015-10-13-v4.3-rc5 Geert Uytterhoeven
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=20151014003946.GD24693@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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