[GIT PULL 8/9] ARM: tegra: Devicetree changes for v4.3-rc1

[olof@lixom.net (Olof Johansson)]

On Fri, Aug 21, 2015 at 05:27:51PM +0100, Jon Hunter wrote:
> 
> On 21/08/15 17:09, Olof Johansson wrote:
> > On Thu, Aug 20, 2015 at 06:58:48PM -0700, Olof Johansson wrote:
> >> On Fri, Aug 14, 2015 at 04:48:39PM +0200, Thierry Reding wrote:
> >>> Hi ARM SoC maintainers,
> >>>
> >>> The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
> >>>
> >>>   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
> >>>
> >>> are available in the git repository at:
> >>>
> >>>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.3-dt
> >>>
> >>> for you to fetch changes up to 6909c6632fdbea441b5077b4f882c0bf4b71997e:
> >>>
> >>>   ARM: tegra: Add gpio-ranges property (2015-08-13 16:31:53 +0200)
> >>>
> >>> Thanks,
> >>> Thierry
> >>>
> >>> ----------------------------------------------------------------
> >>> ARM: tegra: Devicetree changes for v4.3-rc1
> >>>
> >>> Enables CPU frequency scaling on Jetson TK1 and enables the GK20A GPU on
> >>> Venice2 and Jetson TK1. This also enables support for the PMU hardware
> >>> found on Tegra124, which among other things, can be used for performance
> >>> measurements.
> >>
> >> Merged, thanks.
> > 
> > This caused build failures due to missing tegra124-car.h:
> 
> Should be included by Paul's patch, "clk: tegra: Add DFLL DVCO reset
> control for Tegra124", which is part of the clk series pull request [0].
> 
> > http://arm-soc.lixom.net/buildlogs/arm-soc/v4.2-rc2-954-g5825349/buildall.arm.tegra_defconfig.log.failed
> > 
> > I've dropped this branch again.
> 
> It is building ok on linux-next today.

Yeah, it builds when the dependent changes from the clk tree are included, but
this breaks bisectability potentially for quite a bit of code, and requires
that we merge after the clk branch goes in or mainline will be busted.

As mentioned just now on IRC too, it might make most sense to rebase on top
of the clk branch to avoid this breakage. Either that or drop the patch in
question for 4.3.


-Olof