From: Tomasz Figa <t.figa@samsung.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Vikas Sajjan <sajjan.linux@gmail.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Tushar Behera <tushar.behera@linaro.org>,
sunil joshi <joshi@samsung.com>,
Chander Kashyap <chander.kashyap@linaro.org>
Subject: Re: AFTR does not work on arndale 5250
Date: Tue, 08 Apr 2014 18:13:47 +0200 [thread overview]
Message-ID: <5344203B.6080702@samsung.com> (raw)
In-Reply-To: <5344075D.2030203@linaro.org>
Hi Daniel, Vikas, Chander,
On 08.04.2014 16:27, Daniel Lezcano wrote:
> On 04/08/2014 03:32 PM, Vikas Sajjan wrote:
>> Hi Daniel,
>>
>> I checked AFTR on v3.14 (
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs/tags/v3.14)
>>
>> on exynos5250 based chromebook (exynos5250-snow.dtb)
>>
>> I am able to hotplug CPU1 (echo 0 >
>> /sys/devices/system/cpu/cpu1/online).
>> I can see, it enters exynos4_enter_core0_aftr() when I hotplug CPU1.
>
> Hi,
>
> thanks a lot for your help.
>
> I reproduced it on my arndale board with linux-samsung/for-next and on
> v3.14.
>
> Used the exynos_defconfig, enabled cpuidle and used exynos5250-arndale.dtb.
>
You should compare your bootloader versions as this is one of the
aspects that can break AFTR support as it relies on kind of ABI between
bootloader and kernel.
Bets regards,
Tomasz
next prev parent reply other threads:[~2014-04-08 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 13:06 AFTR does not work on arndale 5250 Daniel Lezcano
2014-04-08 11:01 ` Tomasz Figa
2014-04-08 13:32 ` Vikas Sajjan
2014-04-08 14:27 ` Daniel Lezcano
2014-04-08 16:13 ` Tomasz Figa [this message]
2014-04-08 16:47 ` Daniel Lezcano
2014-04-08 13:59 ` Chander Kashyap
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=5344203B.6080702@samsung.com \
--to=t.figa@samsung.com \
--cc=chander.kashyap@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sajjan.linux@gmail.com \
--cc=tushar.behera@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.