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/ARM/VExpress: refine the check for DVI support
Date: Mon, 29 Jan 2018 16:13:40 +0000 [thread overview]
Message-ID: <CAKv+Gu8hsB8jrtRZPu80MDs5QsUBR79-x_DL0vZksSOYA8K3Mg@mail.gmail.com> (raw)
In-Reply-To: <HE1PR08MB2923B395C8BB1A6A5235EEEE9DE50@HE1PR08MB2923.eurprd08.prod.outlook.com>
On 29 January 2018 at 16:01, Thomas Abraham <thomas.abraham@arm.com> wrote:
> Hi Leif,
>
>> On Mon, Jan 29, 2018 at 8:21 PM, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>> On Fri, Jan 26, 2018 at 10:34:59PM +0530, Thomas Abraham wrote:
>> > The base models could have different values for the revision ID field
>> > in the System ID register. Base models do not have support for DVI and
>> > so the revision ID field should also be masked out when checking for
>> > the presence of DVI support.
>> >
>> > Contributed-under: TianoCore Contribution Agreement 1.1
>> > Signed-off-by: Thomas Abraham <thomas.abraham@arm.com>
>> > ---
>> > .../VExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmVExpress.c |
>> 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git
>> >
>> a/Platform/ARM/VExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmV
>> > Express.c
>> >
>> b/Platform/ARM/VExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmV
>> > Express.c
>> > index 3f3ceb3..89ba130 100644
>> > ---
>> >
>> a/Platform/ARM/VExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmV
>> > Express.c
>> > +++
>> b/Platform/ARM/VExpressPkg/Library/PL111LcdArmVExpressLib/PL111Lcd
>> > +++ ArmVExpress.c
>> > @@ -264,7 +264,7 @@ LcdPlatformSetMode (
>> > SysId = MmioRead32 (ARM_VE_SYS_ID_REG);
>> > if (SysId != ARM_RTSM_SYS_ID) {
>> > // Take out the FVP GIC variant to reduce the permutations.
>> > - SysId &= ~ARM_FVP_SYS_ID_VARIANT_MASK;
>> > + SysId &= ~(ARM_FVP_SYS_ID_VARIANT_MASK |
>> > + ARM_FVP_SYS_ID_REV_MASK);
>> > if (SysId != ARM_FVP_BASE_BOARD_SYS_ID) {
>> > // Set the DVI into the new mode
>> > Status = ArmPlatformSysConfigSet (SYS_CFG_DVIMODE,
>> > mResolutions[ModeNumber].Mode);
>>
>> I think this change makes sense (and should arguably have been there from the
>> start). But I also think it highlights that the surrounding comments are incorrect,
>> and get increasingly confusing with this modification.
>>
>> I would suggest that
>> // On the FVP models the GIC variant in encoded in bits [15:12].
>> is replaced by
>> // On the FVP models, the build variant is encoded in bits [15:12].
>>
>> and that
>> // Take out the FVP GIC variant to reduce the permutations.
>> is replaced by
>> // Ignore build variant and revision.
>>
>> If you're happy with that, I can fold these changes to the surrounding comments
>> in and commit.
>
> Yes, happy to have these changes folded in. Thank you!.
>
Likewise
Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
next prev parent reply other threads:[~2018-01-29 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 17:04 [PATCH] Platform/ARM/VExpress: refine the check for DVI support Thomas Abraham
2018-01-29 13:12 ` Thomas Abraham
2018-01-29 15:35 ` Leif Lindholm
2018-01-29 14:51 ` Leif Lindholm
2018-01-29 16:01 ` Thomas Abraham
2018-01-29 16:13 ` Ard Biesheuvel [this message]
2018-01-29 16:28 ` Leif Lindholm
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+Gu8hsB8jrtRZPu80MDs5QsUBR79-x_DL0vZksSOYA8K3Mg@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