From: Daniil Egranov <Daniil.Egranov@arm.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
Evan Lloyd <Evan.Lloyd@arm.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Matteo Carlini <Matteo.Carlini@arm.com>, nd <nd@arm.com>,
Arvind Chauhan <Arvind.Chauhan@arm.com>,
"Thomas Panakamattam Abraham" <thomas.abraham@arm.com>
Subject: Re: [PATCH 0/2] Use PCD for Watchdog count
Date: Thu, 21 Sep 2017 01:44:12 +0000 [thread overview]
Message-ID: <DB6PR0801MB2054C0C115A424A232F77C9A84660@DB6PR0801MB2054.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20170920162154.fgvexlzrhfowk5m5@bivouac.eciton.net>
Hi Leif,
I tested it on Juno R2. I see a one EFI SBSA watchdog test failure but I see the same failure without the patches so it's not a patch issue.
It looks good for me.
Thanks,
Daniil
-----Original Message-----
From: Leif Lindholm [mailto:leif.lindholm@linaro.org]
Sent: Wednesday, September 20, 2017 11:22 AM
To: Evan Lloyd
Cc: edk2-devel@lists.01.org; Ard Biesheuvel; Matteo Carlini; nd; Arvind Chauhan; Daniil Egranov; Thomas Panakamattam Abraham
Subject: Re: [PATCH 0/2] Use PCD for Watchdog count
Arvind, Daniil, Thomas - any comments?
I have no objections to this changeset.
/
Leif
On Mon, Sep 18, 2017 at 03:53:42PM +0100, evan.lloyd@arm.com wrote:
> From: EvanLloyd <evan.lloyd@arm.com>
>
> Paired patches for edk2 and edk2-platforms that add and use a PCD
> indicating the number of SBSA Watchdog timers present. This makes
> things more configurable, and is consistent with other examples of
> platform characteristics. It may also help with debates over GTDT
> inclusion (or not) of secure timers.
>
> Sami Mujawar (1):
> ArmPlatformPkg: Add PCD for SBSA Watchdog Count
>
> ArmPlatformPkg/ArmPlatformPkg.dec | 4 +++-
> ArmPlatformPkg/ArmJunoPkg/Include/ArmPlatform.h | 4 ++--
> 2 files changed, 5 insertions(+), 3 deletions(-)
>
> Sami Mujawar (1):
> Platforms/ARM: SBSA Watchdog PCD and build option
>
> Platform/ARM/JunoPkg/ArmJuno.dsc | 7 ++++++-
> Platform/ARM/VExpressPkg/ArmVExpress-FVP-AArch64.dsc | 7 ++++++-
> Platform/ARM/JunoPkg/AcpiTables/AcpiTables.inf | 4 +++-
> Platform/ARM/VExpressPkg/AcpiTables/AcpiTables.inf | 4 +++-
> Platform/ARM/JunoPkg/AcpiTables/Gtdt.aslc | 6 +++++-
> Platform/ARM/VExpressPkg/AcpiTables/Gtdt.aslc | 14 +++++++++++---
> 6 files changed, 34 insertions(+), 8 deletions(-)
>
> --
> Guid("CE165669-3EF3-493F-B85D-6190EE5B9759")
>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
prev parent reply other threads:[~2017-09-21 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 14:53 [PATCH 0/2] Use PCD for Watchdog count evan.lloyd
2017-09-18 14:53 ` [PATCH 1/2] ArmPlatformPkg: Add PCD for SBSA Watchdog Count evan.lloyd
2017-09-18 14:53 ` [PATCH 2/2] [edk2-platforms] Platforms/ARM: SBSA Watchdog PCD and build option evan.lloyd
2017-09-20 16:21 ` [PATCH 0/2] Use PCD for Watchdog count Leif Lindholm
2017-09-21 1:44 ` Daniil Egranov [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=DB6PR0801MB2054C0C115A424A232F77C9A84660@DB6PR0801MB2054.eurprd08.prod.outlook.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