From: Keerthy <a0393675@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] ARM: Introduce function to switch to hypervisor mode
Date: Fri, 29 Jul 2016 11:51:34 +0530 [thread overview]
Message-ID: <579AF5EE.8010603@ti.com> (raw)
In-Reply-To: <20160728134405.GJ5926@bill-the-cat>
On Thursday 28 July 2016 07:14 PM, Tom Rini wrote:
> On Thu, Jul 28, 2016 at 02:08:10PM +0200, Marek Vasut wrote:
>> On 07/27/2016 05:37 AM, Keerthy wrote:
>>>
>>>
>>> On Wednesday 27 July 2016 09:05 AM, Keerthy wrote:
>>>> On SoCs like DRA7, OMAP5 one cannot enable hypervisor mode directly
>>>> from the
>>>> u-boot because the ROM code puts the chip to supervisor mode after it
>>>> jumps to boot loader.
>>>>
>>>> Patch 1: Introduces a weak function which can be overridden specific to
>>>> SoCs to switch to hypervisor mode.
>>>>
>>>> Patch 2: overrides weak function in patch 1 switch cpu to hypervisor
>>>> mode using the available ROM code hook early in the boot phase before
>>>> the boot loader checks for hypervisor mode on OMAP5 based SoCs.
>>>>
>>>> Based on top of http://patchwork.dal.design.ti.com/patch/24937/.
>>>
>>> Please ignore the above link.
>>>
>>> Based on:
>>>
>>> http://lists.denx.de/pipermail/u-boot/2016-June/258300.html
>>
>> Please resubmit fixed patch.
>
> That's just a bad link in 0/2, nothing to resubmit.
Thanks for reviewing Tom!
The series generated a compile error on a bunch of other defconfigs. I
have fixed that and send a v2 with your Reviewed-by.
>
prev parent reply other threads:[~2016-07-29 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 3:35 [U-Boot] [PATCH 0/2] ARM: Introduce function to switch to hypervisor mode Keerthy
2016-07-27 3:35 ` [U-Boot] [PATCH 1/2] " Keerthy
2016-07-28 13:44 ` Tom Rini
2016-07-27 3:35 ` [U-Boot] [PATCH 2/2] ARM: OMAP5+: Override switch_to_hypervisor function Keerthy
2016-07-28 13:44 ` Tom Rini
2016-07-27 3:37 ` [U-Boot] [PATCH 0/2] ARM: Introduce function to switch to hypervisor mode Keerthy
2016-07-28 12:08 ` Marek Vasut
2016-07-28 12:42 ` Keerthy
2016-07-28 13:44 ` Tom Rini
2016-07-29 6:21 ` Keerthy [this message]
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=579AF5EE.8010603@ti.com \
--to=a0393675@ti.com \
--cc=u-boot@lists.denx.de \
/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