From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Thomas Abraham <thomas.abraham@arm.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] Platform/FVP-AArch64: switch to the SBSA watchdog
Date: Thu, 20 Dec 2018 12:09:04 +0100 [thread overview]
Message-ID: <CAKv+Gu_-X3MQfhH_2pWZTkZEZ6QfAJXXFzJZoBKiLE8X1_CjhA@mail.gmail.com> (raw)
In-Reply-To: <CAJuA9ajwt80aHzn=cfdvhMSBtjC3Hj0F4GmvjCd=eWiL=tvUBg@mail.gmail.com>
On Thu, 20 Dec 2018 at 11:03, Thomas Abraham <thomas.abraham@arm.com> wrote:
>
> On Wed, Dec 19, 2018 at 10:04 PM Leif Lindholm <leif.lindholm@linaro.org> wrote:
> >
> > On Tue, Dec 18, 2018 at 05:46:21PM +0100, Ard Biesheuvel wrote:
> > > On the FVP Foundation model, the SP805 watchdog appears to be 'wired'
> > > incorrectly, resulting in a watchdog counter that decrements at the
> > > APB clock rate of 24 MHz instead of the usual 32 kHz. Since the
> > > timer start value is only 32-bits wide, this makes the watchdog
> > > unusable in UEFI, since the default timeout set by the DXE core is
> > > 5 minutes, which is not representable in 32-bit at this clock rate.
> > >
> > > So switch to the SBSA watchdog instead, which is wired up to the
> > > generic timer, and ticks at the correct rate.
> > >
> > > Contributed-under: TianoCore Contribution Agreement 1.1
> > > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >
> > From my point of view:
> > Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
> >
> > But I'd like a nod from Sami or Thomas (added to cc) as well.
>
> I have not been able test this patch yet but the changes looks fine.
>
> - Thomas.
>
Thanks all
Pushed as dc6b5ef8a6c2..88e5de1a2346
prev parent reply other threads:[~2018-12-20 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 16:46 [PATCH] Platform/FVP-AArch64: switch to the SBSA watchdog Ard Biesheuvel
2018-12-19 16:25 ` Leif Lindholm
2018-12-20 10:02 ` Thomas Abraham
2018-12-20 11:09 ` Ard Biesheuvel [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-list 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=CAKv+Gu_-X3MQfhH_2pWZTkZEZ6QfAJXXFzJZoBKiLE8X1_CjhA@mail.gmail.com \
--to=devel@edk2.groups.io \
/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