From mboxrd@z Thu Jan  1 00:00:00 1970
From: Diana Craciun <diana.craciun@freescale.com>
Date: Fri, 4 Jul 2014 14:39:34 +0300
Subject: [U-Boot] [PATCH 0/4] Add LS1021A-QDS/TWR Non-secure and HYP
	support.
In-Reply-To: <128388bd235241899c7cadc2a2c510db@BY2PR03MB505.namprd03.prod.outlook.com>
References: <1404381072-42875-1-git-send-email-Li.Xiubo@freescale.com>
	<53B53B00.6060606@freescale.com>
	<128388bd235241899c7cadc2a2c510db@BY2PR03MB505.namprd03.prod.outlook.com>
Message-ID: <53B69276.5000909@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 07/04/2014 04:31 AM, Xiubo Li-B47053 wrote:
>>> This patch series depends on the following patch:
>>>
>>> [U-Boot,v4,03/10] ARM: non-sec: reset CNTVOFF to zero
>>>
>>> Before switching to non-secure, make sure that CNTVOFF is set
>>> to zero on all CPUs. Otherwise, kernel running in non-secure
>>> without HYP enabled (hence using virtual timers) may observe
>> But we have HYP enabled. In this case why are the series dependent on
>> this patch?
>>
> Well, if the HYP is enabled, the host OS will use the Physical timer,
> and these CNTVOFFs could be cleared in kernel too.
>
> When and where to clear them is better ? In uboot or in kernel when needed?

If HYP mode is available CNTVOFF is cleared in Linux. What I am trying 
to say is that it will work also without the patch you mentioned.

Diana