[GIT PULL 3/5] Samsung exynos cpuidle update for v3.17

[Kukjin Kim]

Kevin Hilman wrote:
> 
> Hello,
> 
Hi,

> On Fri, Jul 18, 2014 at 5:52 PM, Kukjin Kim <kgene.kim at samsung.com> wrote:
> > The following changes since commit 1795cd9b3a91d4b5473c97f491d63892442212ab:
> >
> >   Linux 3.16-rc5 (2014-07-13 14:04:33 -0700)
> >
> > are available in the git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > tags/exynos-cpuidle
> >
> > for you to fetch changes up to fc2cac41ebbfb16da8b036cba6ec6714ab780a6d:
> >
> >   ARM: EXYNOS: populate suspend and powered_up callbacks for mcpm
> > (2014-07-19 03:36:00 +0900)
> >
> > ----------------------------------------------------------------
> > exynos cpuidle update for v3.17
> >
> > - add callbacks exynos_suspend() and exynos_powered_up()
> >   for support cpuidle through mcpm
> > - skip exynos_cpuidle for exynos5420 because is uses
> >   cpuidle-big-liggle generic cpuidle driver
> > - add generic functions to calculate cpu number is used
> >   for pmu and this is required for exynos5420 multi-cluster
> > - add of_device_id structure for big.LITTLE cpuidle and
> >   add "samsung,exynos5420" compatible string for exynos5420
> 
> I'm curious what platforms this is expected to work on, and where it's
> been tested.
> 
exynos5420 and its reference board, smdk5420.

> I tried it on exynos5800-peach-pi (chromebook2) and it hangs up (no
> kernel messages) shortly after the driver loads, and never finishes to
> boot.
> 
Oh, sorry about that, if so, it should be fixed before -rc1. Just note that I
thought since exynos5800 is very similar with exynos5420 so I didn't ask
Chander to test the series on exynos5800 based board...Just asked to test with
Nico's mcpm series. BTW, unfortunately I have no exynos5800-peach-pi...

> I needed an extra compatible entry for the 5800 in the driver for the
> driver to load, which suggests it hasn't been tested on 5800, but at
> least in theory, this should be compatible with the 542x, right?
> 
Yes I think so. As you can see in exynos5800.dtsi, it is including exynos5420.

> For testing, I tried today's linux-next and arm-soc/for-next.
> 
Hmm...why is the problem happened at last? Not at that time? :(

I need to figure it out...

Thanks,
Kukjin