Re: [GIT PULL] ARM: EXYNOS: Improvements for 4.2, second try

From: Krzysztof Kozlowski
Date: Sun May 17 2015 - 04:52:33 EST


2015-05-11 12:14 GMT+09:00 Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>:
> Dear Kukjin,
>
> Updated pull request, replacing also the usage of soc_is_exynos4()
> with of_machine_is_compatible(). You requested this in comments
> for "ARM: EXYNOS: Fix failed second suspend on Exynos4".
>
> This adds coupled cpuidle for Exynos3250 and improves the Exynos
> code in few places. Everything for upcoming 4.2 merge window.
> Description along with a tag.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit b82f3a05ff0b5eaf2c9900eeb34e58a6624db8d9:
>
> ARM: EXYNOS: Fix failed second suspend on Exynos4 (2015-05-11 11:03:09 +0900)
>
> are available in the git repository at:
>
> https://github.com/krzk/linux.git tags/samsung-for-next-4.2-2
>
> for you to fetch changes up to c91889378098ff0bb5fe6f422a3c0eb554b34930:
>
> ARM: plat-samsung: Constify platform_device_id (2015-05-11 11:05:31 +0900)
>
> ----------------------------------------------------------------
> Extending cpuidle driver and improvements for Exynos based boards:
> 1. Replace soc_is_exynos4() with of_machine_is_compatible().
> 2. Add missing return-value checks and of_node_put() for power domain
> driver.
> 3. Fix missing clk_prepare in S3C24XX ADC driver.
> 4. Rework clock handling when switching power domains on/off. Instead
> of settting fixed parent in DTS we grab the parent clock before
> turning the domain off.
> 5. Add coupled cpuidle support for Exynos3250 to an existing
> cpuidle-exynos driver. As a result it enables AFTR mode
> (ARM-Off Top-Running) to be used by default on Exynos3250
> without the need to hot unplug CPU1 first.
> 6. Constify irq_domain_ops and platform_device_id.

Dear Kukjin,

Just humbly reminding - this stuff still waits for you :).

Best regards,
Krzysztof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/