From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Vitaly Andrianov <vitalya@ti.com>, Mark Rutland <mark.rutland@arm.com>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"ssantosh@kernel.org" <ssantosh@kernel.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
"grygorii.strashko@ti.com" <grygorii.strashko@ti.com>
Subject: Re: [PATCH] keystone: adds cpu_die implementation
Date: Mon, 29 Jun 2015 14:12:48 -0700 [thread overview]
Message-ID: <5591B4D0.8090204@oracle.com> (raw)
In-Reply-To: <559191E0.4080808@ti.com>
On 6/29/15 11:43 AM, Vitaly Andrianov wrote:
>
>
> On 06/29/2015 01:52 PM, Mark Rutland wrote:
>> On Mon, Jun 29, 2015 at 06:52:32PM +0100, Vitaly Andrianov wrote:
>>> This commit add cpu_die implementation
>>>
>>> Signed-off-by: Vitaly Andrianov <vitalya@ti.com>
>>> ---
>>>
>>> The discussion of the "keystone: psci: adds cpu_die implementation"
>>> commit
>>> shows that if PCSI is enabled platform code doesn't need that
>>> implementation
>>> at all. Having PSCI commands in DTB should be sufficient. Unfortunately
>>> Keystone with LPAE enable requires some additional development.
>>
>> I don't follow.
>>
>> What do you need to implement for LPAE?
> Hi Mark,
>
> The Keystone platform needs to set ttbr1 when it boots secondary core.
> It is done in the keystone_smp_secondary_initmem(), which is
> .smp_secondary_init member of the keystone_smp_ops. I couldn't find a
> way how I can add similar function to psci_smp_ops.
>
> Do you have any idea?
>
>>
>> Why not implement that rather than adding more platform code that you'll
>> likely want to remove later anyway?
>
> If I can solve the above problem, I will not add this code.
>
This problem is already solved. :-)
After [1], there is no longer need to fiddle with TTBR1 setup
for secondary bringup. I believe its already in RMK's queue and it
should show up in linus's tree after 4.2 merge window.
Regards,
Santosh
[1] http://www.spinics.net/lists/arm-kernel/msg416129.html
next prev parent reply other threads:[~2015-06-29 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 17:52 [PATCH] keystone: adds cpu_die implementation Vitaly Andrianov
2015-06-29 17:52 ` Mark Rutland
2015-06-29 18:43 ` Vitaly Andrianov
2015-06-29 21:12 ` santosh.shilimkar [this message]
2015-06-29 21:28 ` Russell King - ARM Linux
2015-06-29 21:37 ` Russell King - ARM Linux
2015-06-30 13:47 ` Vitaly Andrianov
2015-06-30 14:54 ` Russell King - ARM Linux
2015-06-30 16:38 ` Vitaly Andrianov
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=5591B4D0.8090204@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=ssantosh@kernel.org \
--cc=vitalya@ti.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