From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bin Meng <bmeng.cn@gmail.com>
Date: Mon, 28 Oct 2019 15:12:45 +0800
Subject: [U-Boot] [PATCH v3 022/108] x86: timer: Use a separate flag for
 whether timer is inited
In-Reply-To: <20191021033913.220758-22-sjg@chromium.org>
References: <20191021033913.220758-22-sjg@chromium.org>
Message-ID: <CAEUhbmUax156SRtSsNa0ZoY=kyLY+aDz-jUFUCR3SXKSctG6xQ@mail.gmail.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 Mon, Oct 21, 2019 at 11:39 AM Simon Glass <sjg@chromium.org> wrote:
>
> At present the value of the timer base is used to determine whether the
> timer has been set up or not. It is true that the timer is essentially
> never exactly 0 when it is read. However 'time 0' may indicate the time
> that the machine was reset so it is useful to be able to denote that.
>
> Update the code to use a separate flag instead.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Changes in v3: None
> Changes in v2: None
>
>  arch/x86/include/asm/global_data.h | 1 +
>  drivers/timer/tsc_timer.c          | 3 ++-
>  2 files changed, 3 insertions(+), 1 deletion(-)
>

Reviewed-by: Bin Meng <bmeng.cn@gmail.com>