Hello, This series adds HDMI support for Exynos5420/5422/5800 machines by adding a node for the DISP1 power domain which is used by the HDMI and MIXER modules. It also adds IDs for the attached devices parent and input clocks that are used by the Exynos power domain driver to re-parent the devices input clocks when the DISP1 power domain is powered off and on. Thanks a lot to Joonyoung Shim and Krzysztof Kozlowski for point me in the right direction. The series is based on Marek Szyprowski's patch 'ARM: DTS: Exynos: convert to generic power domain bindings' (http://www.spinics.net/lists/linux-samsung-soc/msg40584.html) The patches were tested on an Exynos5420 Peach Pit and Exynos5800 Peach Pi Chromebooks and an Exynos5422 Odroid XU3. NOTE: There is an issue noticed with these patches and is that if the kconfig CONFIG_DRM_EXYNOS_DP symbol is disabled and only CONFIG_DRM_EXYNOS_HDMI is enabled, then disabling the framebuffer and enabling it again with: # echo 0 > /sys/devices/platform/exynos-drm/graphics/fb0/blank # echo 1 > /sys/devices/platform/exynos-drm/graphics/fb0/blank makes the system to crash due the exynos_mixer driver needing clocks enabled by the exynos_hdmi driver that are gated on hdmi_poweroff(). The same issue has been reported on other Exynos platforms so it's orthogonal to this series and needs to be fixed for all platforms. Javier Martinez Canillas (2): clk: exynos5420: Add IDs for clocks used in DISP1 power domain ARM: dts: Add DISP1 power domain for exynos5420 arch/arm/boot/dts/exynos5420.dtsi | 17 +++++++++++++++++ drivers/clk/samsung/clk-exynos5420.c | 23 ++++++++++++----------- include/dt-bindings/clock/exynos5420.h | 6 ++++++ 3 files changed, 35 insertions(+), 11 deletions(-) Patches 1 and 2 depend on each other so they have to either be merged through the same tree or patch 1 has to be merged through clock tree and create a topic branch to be pulled by the linux-samsung tree. Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |