From: "Pete Batard" <pete@akeo.ie>
To: Ard Biesheuvel <ard.biesheuvel@arm.com>,
Jeremy Linton <jeremy.linton@arm.com>,
devel@edk2.groups.io
Cc: Leif Lindholm <leif@nuviainc.com>,
Andrei Warkentin <awarkentin@vmware.com>,
Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [PATCH v4 6/6] Platform/RaspberryPi: Trivial whitespace cleanup
Date: Tue, 1 Sep 2020 12:46:30 +0100 [thread overview]
Message-ID: <c5151d3b-b0dc-5f34-94c0-82ea8923393e@akeo.ie> (raw)
In-Reply-To: <7d6c81cb-8d2e-2991-d585-300df9f00a13@arm.com>
Hi Ard,
On 2020.09.01 12:39, Ard Biesheuvel wrote:
> On 8/31/20 7:25 PM, Jeremy Linton wrote:
>> Pete's review pointed out some whitespace issues in the
>> context of a previous patch. Since there are a number of
>> similar errors in the file lets fix them separately.
>>
>> Cc: Leif Lindholm <leif@nuviainc.com>
>> Cc: Pete Batard <pete@akeo.ie>
>> Cc: Andrei Warkentin <awarkentin@vmware.com>
>> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
>> Cc: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
>> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
>> Reviewed-by: Pete Batard <@pbatard>
>> ---
>> Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c | 24
>> +++++++++++-----------
>> 1 file changed, 12 insertions(+), 12 deletions(-)
>>
>> diff --git a/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
>> b/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
>> index e8f964a329..4ed294cdfe 100644
>> --- a/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
>> +++ b/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
>> @@ -209,9 +209,9 @@ SetupVariables (
>> }
>> Size = sizeof (UINT32);
>> - Status = gRT->GetVariable(L"CustomCpuClock",
>> - &gConfigDxeFormSetGuid,
>> - NULL, &Size, &Var32);
>> + Status = gRT->GetVariable (L"CustomCpuClock",
>> + &gConfigDxeFormSetGuid,
>> + NULL, &Size, &Var32);
>> if (EFI_ERROR (Status)) {
>> Status = PcdSet32S (PcdCustomCpuClock, PcdGet32
>> (PcdCustomCpuClock));
>> ASSERT_EFI_ERROR (Status);
>> @@ -266,7 +266,7 @@ SetupVariables (
>> Size = sizeof (AssetTagVar);
>> - Status = gRT->GetVariable(L"AssetTag",
>> + Status = gRT->GetVariable (L"AssetTag",
>> &gConfigDxeFormSetGuid,
>> NULL, &Size, AssetTagVar);
>> @@ -275,7 +275,7 @@ SetupVariables (
>> L"AssetTag",
>> &gConfigDxeFormSetGuid,
>> EFI_VARIABLE_NON_VOLATILE |
>> EFI_VARIABLE_BOOTSERVICE_ACCESS | EFI_VARIABLE_RUNTIME_ACCESS,
>> - sizeof(AssetTagVar),
>> + sizeof (AssetTagVar),
>> AssetTagVar
>> );
>> }
>> @@ -441,9 +441,9 @@ ApplyVariables (
>> * spaces. SystemMemorySizeBelow4GB tracks the maximum memory
>> below 4GB
>> * line, factoring in the limit imposed by the SoC register range.
>> */
>> - SystemMemorySizeBelow4GB = MIN(SystemMemorySize, 4UL * SIZE_1GB);
>> - SystemMemorySizeBelow4GB = MIN(SystemMemorySizeBelow4GB,
>> BCM2836_SOC_REGISTERS);
>> - SystemMemorySizeBelow4GB = MIN(SystemMemorySizeBelow4GB,
>> BCM2711_SOC_REGISTERS);
>> + SystemMemorySizeBelow4GB = MIN (SystemMemorySize, 4UL * SIZE_1GB);
>> + SystemMemorySizeBelow4GB = MIN (SystemMemorySizeBelow4GB,
>> BCM2836_SOC_REGISTERS);
>> + SystemMemorySizeBelow4GB = MIN (SystemMemorySizeBelow4GB,
>> BCM2711_SOC_REGISTERS);
>> ASSERT (SystemMemorySizeBelow4GB > 3UL * SIZE_1GB);
>> @@ -536,14 +536,14 @@ ApplyVariables (
>> /*
>> * SD card pins go to Arasan.
>> */
>> - MmioWrite32((GPIO_BASE_ADDRESS + 0xD0),
>> - MmioRead32(GPIO_BASE_ADDRESS + 0xD0) | 0x2);
>> + MmioWrite32 ((GPIO_BASE_ADDRESS + 0xD0),
>> + MmioRead32 (GPIO_BASE_ADDRESS + 0xD0) | 0x2);
>> } else {
>> /*
>> * SD card pins back to eMMC2.
>> */
>> - MmioWrite32((GPIO_BASE_ADDRESS + 0xD0),
>> - MmioRead32(GPIO_BASE_ADDRESS + 0xD0) & ~0x2);
>> + MmioWrite32 ((GPIO_BASE_ADDRESS + 0xD0),
>> + MmioRead32 (GPIO_BASE_ADDRESS + 0xD0) & ~0x2);
>
> Anyone mind if I replace these with MmioOr32 / MmioAnd32 ?
No objection from me. This should indeed make the code cleaner.
Thanks,
/Pete
>
>
>> /*
>> * WiFi back to Arasan.
>> */
>>
>
next prev parent reply other threads:[~2020-09-01 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 17:25 [PATCH v4 0/6] Platform/RasberryPi: Thermal zone Jeremy Linton
2020-08-31 17:25 ` [PATCH v4 1/6] Platform/RaspberryPi4: Add a basic thermal zone Jeremy Linton
2020-08-31 17:25 ` [PATCH v4 2/6] Platform/RaspberryPi: Monitor ACPI Table installs Jeremy Linton
2020-08-31 17:32 ` Andrei Warkentin
2020-08-31 17:25 ` [PATCH v4 3/6] Platform/RaspberryPi: Add entry for user fan control Jeremy Linton
2020-08-31 17:25 ` [PATCH v4 4/6] Platform/RaspberryPi4: Create ACPI fan object Jeremy Linton
2020-08-31 17:25 ` [PATCH v4 5/6] Platform/RaspberryPi4: Allow the user to set Temp Jeremy Linton
2020-08-31 18:57 ` Pete Batard
2020-08-31 19:05 ` Ard Biesheuvel
2020-08-31 17:25 ` [PATCH v4 6/6] Platform/RaspberryPi: Trivial whitespace cleanup Jeremy Linton
2020-09-01 11:39 ` Ard Biesheuvel
2020-09-01 11:46 ` Pete Batard [this message]
2020-09-01 12:23 ` [PATCH v4 0/6] Platform/RasberryPi: Thermal zone Ard Biesheuvel
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=c5151d3b-b0dc-5f34-94c0-82ea8923393e@akeo.ie \
--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