From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFT 1/2] drivers: bus: check cci device tree node status
Date: Wed, 10 Dec 2014 10:46:22 +0530 [thread overview]
Message-ID: <5487D726.6000603@arm.com> (raw)
In-Reply-To: <CAM4voa=TQeOMTHmM2iBquDRwoEFPAgUFeMwJ73H4qdcSmR1Lug@mail.gmail.com>
On Wednesday 10 December 2014 09:55 AM, Abhilash Kesavan wrote:
> Hi Sudeep,
>
> On Wed, Dec 10, 2014 at 9:44 AM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>> Hi Abhilash,
>>
>> On Wednesday 10 December 2014 09:31 AM, Abhilash Kesavan wrote:
>>>
>>> Hi,
>>>
>>> On Fri, Nov 28, 2014 at 8:20 PM, Abhilash Kesavan <a.kesavan@samsung.com>
>>> wrote:
>>>>
>>>> The arm-cci driver completes the probe sequence even if the cci node is
>>>> marked as disabled. Add a check in the driver to honour the cci status
>>>> in the device tree.
>>>>
>>>> Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
>>>
>>>
>>> This patch helps disable CCI on the Arndale Octa board thus resolving
>>> some imprecise aborts seen on that board. Kindly review.
>>>
>>> Regards,
>>> Abhilash
>>>>
>>>> ---
>>>> drivers/bus/arm-cci.c | 3 +++
>>>> 1 file changed, 3 insertions(+)
>>>>
>>>> diff --git a/drivers/bus/arm-cci.c b/drivers/bus/arm-cci.c
>>>> index 860da40..0ce5e2d 100644
>>>> --- a/drivers/bus/arm-cci.c
>>>> +++ b/drivers/bus/arm-cci.c
>>>> @@ -1312,6 +1312,9 @@ static int cci_probe(void)
>>>> if (!np)
>>>> return -ENODEV;
>>>>
>>>> + if (!of_device_is_available(np))
>>>> + return -ENODEV;
>>>> +
>>
>>
>> IIUC, by this change you are disabling the MCPM boot protocol here.
>> Is there any alternative boot protocol that works on this platform
>> to boot all 8 cores ? Sorry by quick grep couldn't find one, hence
>> so I am asking.
>
> Thanks for the reply.
> On disabling MCPM, we will default to platsmp.c/firmware.c which boots
> 4 cores as per Kevin's comment here[1]. This was the original behavior
> before MCPM was enabled for all 5420 based SoCs.
>
Thanks for pointing that out. I assume the firmware can handle the
alternate boot protocol and no more workarounds are needed especially
when getting CPUIdle working in this mode.
Anyways the patch makes sense irrespective how it works on exynos, so
you can add,
Acked-by: Sudeep Holla <sudeep.holla@arm.com>
Regards,
Sudeep
next prev parent reply other threads:[~2014-12-10 5:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 14:50 [PATCH RFT 1/2] drivers: bus: check cci device tree node status Abhilash Kesavan
2014-11-28 14:50 ` [PATCH RFT 2/2] arm: dts: disable CCI on exynos420 based arndale-octa Abhilash Kesavan
2014-11-28 15:19 ` Krzysztof Kozlowski
2014-11-28 15:39 ` Abhilash Kesavan
2014-12-01 9:03 ` Krzysztof Kozlowski
2014-12-01 11:09 ` Russell King - ARM Linux
2014-12-01 11:19 ` Krzysztof Kozlowski
2014-12-01 18:50 ` Kevin Hilman
2014-12-01 19:52 ` Tyler Baker
2014-12-10 4:01 ` [PATCH RFT 1/2] drivers: bus: check cci device tree node status Abhilash Kesavan
2014-12-10 4:14 ` Sudeep Holla
2014-12-10 4:25 ` Abhilash Kesavan
2014-12-10 5:16 ` Sudeep Holla [this message]
2015-01-08 6:45 ` Sudeep Holla
2015-01-08 15:27 ` Abhilash Kesavan
2015-01-09 5:10 ` Sudeep Holla
2015-01-09 16:28 ` Abhilash Kesavan
2015-01-09 21:09 ` Kevin Hilman
2015-01-10 3:21 ` Abhilash Kesavan
2014-12-10 18:29 ` Nicolas Pitre
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=5487D726.6000603@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).