From: Kevin Hilman <khilman@kernel.org>
To: Abhilash Kesavan <kesavan.abhilash@gmail.com>
Cc: Abhijeet Dev <abhijeet@abhijeet-dev.net>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Mauro Ribeiro <mdrjr0@gmail.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Chander Kashyap <k.chander@samsung.com>,
Mauro Ribeiro <mauro.ribeiro@hardkernel.com>,
Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: exynos5422-odroid-xu3: MCPM: only 6 of 8 CPUs coming online
Date: Fri, 24 Oct 2014 09:00:40 -0700 [thread overview]
Message-ID: <7hk33p8nkn.fsf@deeprootsystems.com> (raw)
In-Reply-To: <CAM4voakn128LmppJeVbtibwJcwa-TQL8KWhsEDb_DXTZECs48Q@mail.gmail.com> (Abhilash Kesavan's message of "Fri, 24 Oct 2014 20:03:23 +0530")
Abhilash Kesavan <kesavan.abhilash@gmail.com> writes:
> On Thu, Oct 23, 2014 at 9:26 PM, Kevin Hilman <khilman@kernel.org> wrote:
>> Abhilash Kesavan <a.kesavan@samsung.com> writes:
>>
>>> The change was based on my reading of the platsmp file of the
>>> Odroid-xu3 3.10 kernel and issues experienced previously. From what I
>>> understand, the platsmp code in 3.10 kernel is trying to reset the A7s
>>> and my change just bypasses the check (no magic here ). The change was
>>> only suggested as a workaround to get 8 cores up using MCPM and not an
>>> actual fix. I had explained this in my mail to Kevin. So, if this
>>> were to be mainlined we would probably need to use something like
>>> exynos_core_restart in mcpm along with the workaround. But, this is
>>> all guesswork on my part and someone with knowledge of the 3.10
>>> kernel/bootloader needs to comment.
>>
>> Unfortunately, the harkernel tree git repo doesn't help understand where
>> the change came from because an entire v3.10.y based Samsung BSP is
>> checked into the tree on top of a v3.8.y kernel in a single commit !!!
>>
>> Abhilash, in the absence of the original author, could write up a patch
>> with your change?
>>
>> Or, if you can help me with a detailed changelog, I can work on the patch.
>> I don't have any exynos docs, so it would be good to have a description
>> of what reading/writing to that register are actually doing.
>
> I could post a patch with an explanation of how I think the workaround
> works, but there are a few issues:
> - I am not completely confident that this is the best/right change.
Maybe post as RFC.
> - We are adding code to the exynos mcpm back-end to work-around a
> bootloader setting for Odroid-xu3. We would have to make it specific
> to odroid somehow as we do not require it for 5420/5800 chromebooks.
Hmm, if you have an idea how/where to fix it in u-boot, I'd be glad to
give that a try. I'm using the hardkernel u-boot repo:
https://github.com/hardkernel/u-boot.git, branch odroidxu3-v2012.07, and
would be happy to test any fixes there.
> - This might solve the 8 core boot-up issue but other scenarios might
> still fail like the one Joonyoung has already reported.
I replied yesterday to that report, and the one Joonyoung reported
exists with or without your proposed fix, so I don't think they're
directly related.
>>
>> Also, can you explain what you meant by using exynos_core_restart? I
>> don't see that function in mainline.
>
> It is present in linux-next and kgene's for-next branch as part of
> this commit "ARM: EXYNOS: SWRESET is needed to boot secondary CPU on
> exynos3250".
OK, I see it now.
Kevin
next prev parent reply other threads:[~2014-10-24 16:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 3:06 exynos5422-odroid-xu3: MCPM: only 6 of 8 CPUs coming online Abhilash Kesavan
2014-10-09 21:58 ` Kevin Hilman
2014-10-15 11:35 ` Joonyoung Shim
2014-10-17 12:06 ` Kevin Hilman
2014-10-23 1:04 ` Joonyoung Shim
2014-10-23 1:17 ` Joonyoung Shim
2014-10-23 1:25 ` Mauro Ribeiro
2014-10-23 1:36 ` Joonyoung Shim
2014-10-23 1:42 ` Mauro Ribeiro
2014-10-23 1:49 ` Joonyoung Shim
2014-10-23 1:54 ` Joonyoung Shim
2014-10-23 8:36 ` Abhijeet Dev
[not found] ` <CAG30XQJ29cM6=OFh=TTbR2rfWGt3AK1o2=PMqdoq6ejUJtUwGA@mail.gmail.com>
[not found] ` <A804D1798D614199AFA7AEDC00248EA9@sisodomain.com>
2014-10-23 15:56 ` Kevin Hilman
2014-10-24 14:33 ` Abhilash Kesavan
2014-10-24 16:00 ` Kevin Hilman [this message]
2014-10-25 12:47 ` Mauro Ribeiro
2014-10-27 19:00 ` Kevin Hilman
2014-10-23 18:01 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 18:58 Kevin Hilman
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=7hk33p8nkn.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=abhijeet@abhijeet-dev.net \
--cc=jy0922.shim@samsung.com \
--cc=k.chander@samsung.com \
--cc=kesavan.abhilash@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mauro.ribeiro@hardkernel.com \
--cc=mdrjr0@gmail.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