Hello,

Based on the preinstalled 3.8 based ChromeOS kernel and previous 3.15 
based attempts by Stephan and me that broke for 3.16, I've prepared a 
device tree for the HP Chromebook 11 aka Google Spring.

v2 reuses the new cros-ec-keyboard.dtsi and retires exynos5250-cros-common.dtsi.
It drops the timings subnode from dp-controller in expectation of the new
drm eDP bridge framework, which needs it under a different node.
The built-in MMC is now usable, its node had been inherited as "disabled".

Not yet enabled are trackpad, Wifi and sound.

Now depends on a Tegra branch (pull pending):
http://git.kernel.org/cgit/linux/kernel/git/tegra/linux.git/log/?h=for-3.17/dt-cros-ec-kbd
Cc: linux-te...@vger.kernel.org

My rebasing branch for testing is here:
https://github.com/afaerber/linux/commits/spring-next

Regards,
Andreas

v1 -> v2:
* Dropped 3 documentation patches from series:
  2 picked up,
  https://patchwork.kernel.org/patch/4397271/
  https://patchwork.kernel.org/patch/4397291/
  1 already sent separately as v2, pending.
  https://patchwork.kernel.org/patch/4424881/
* Minimized and beautified Spring device tree and to some degree Snow as well.
  See individual patches.

Andreas Färber (4):
  ARM: dts: exynos5250: max77686 is Snow only
  ARM: dts: exynos5250: cypress,cyapa trackpad is Snow only
  ARM: dts: exynos5250: Fold common ChromeOS parts into Snow
  ARM: dts: exynos5250: Add Spring device tree

 arch/arm/boot/dts/Makefile                    |   1 +
 arch/arm/boot/dts/exynos5250-cros-common.dtsi | 323 -----------------
 arch/arm/boot/dts/exynos5250-snow.dts         | 334 ++++++++++++++++--
 arch/arm/boot/dts/exynos5250-spring.dts       | 485 ++++++++++++++++++++++++++
 4 files changed, 799 insertions(+), 344 deletions(-)
 delete mode 100644 arch/arm/boot/dts/exynos5250-cros-common.dtsi
 create mode 100644 arch/arm/boot/dts/exynos5250-spring.dts

-- 
1.9.3

--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to