From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: Kukjin Kim <kgene@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Anand Moon <linux.amoon@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
linux-samsung-soc@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Lukasz Majewski <l.majewski@samsung.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: exynos_defconfig: Enable big.LITTLE CPUidle support
Date: Fri, 28 Aug 2015 10:51:42 +0200 [thread overview]
Message-ID: <1440751902.13118.6.camel@collabora.co.uk> (raw)
In-Reply-To: <1440749769-10135-1-git-send-email-javier@osg.samsung.com>
On Fri, 2015-08-28 at 10:16 +0200, Javier Martinez Canillas wrote:
> Some Exynos big.LITTLE boards (i.e: Exynos5420 and Exynos5800 based
> Chromebooks) have proper firmware that allow the big.LITTLE CPUidle
> driver to work correctly, so enable support for this.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>
> ---
> Kukjin and Krzysztof,
>
> As you know there are other boards like the Exynos5422 based Odroid
> XU{3,4}
> whose firmware is broken due leaving CCI in secure mode which means
> that the
> kernel MCPM support can't properly manage CCI.
>
> So if you pick this patch, it should be tested in kernelci before
> appearing
> in linux-next to prevent any boot issues.
I've pushed this patch into Collabora's for-next branch, which should
get picked up by kernelci soonish.
--
Sjoerd Simons
Collabora Ltd.
next prev parent reply other threads:[~2015-08-28 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 8:16 [PATCH] ARM: exynos_defconfig: Enable big.LITTLE CPUidle support Javier Martinez Canillas
2015-08-28 8:51 ` Sjoerd Simons [this message]
2015-08-28 9:30 ` Javier Martinez Canillas
2015-08-29 9:01 ` Krzysztof Kozlowski
2015-08-29 9:33 ` Javier Martinez Canillas
2015-08-29 9:55 ` Krzysztof Kozlowski
2015-08-29 10:07 ` Javier Martinez Canillas
2015-08-29 10:22 ` Krzysztof Kozlowski
2015-08-29 10:31 ` Javier Martinez Canillas
2015-08-29 10:39 ` Krzysztof Kozlowski
2015-08-29 10:47 ` Javier Martinez Canillas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1440751902.13118.6.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=linux@arm.linux.org.uk \
--cc=treding@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox