From: "Leif Lindholm" <leif@nuviainc.com>
To: Ard Biesheuvel <ard.biesheuvel@arm.com>
Cc: devel@edk2.groups.io
Subject: Re: [PATCH edk2-platforms 1/3] Platform/96Boards/96BoardsI2cDxe: connect I2C controllers at EndOfDxe
Date: Mon, 18 May 2020 18:26:24 +0100 [thread overview]
Message-ID: <20200518172624.GF10467@vanye> (raw)
In-Reply-To: <20200516175934.31148-2-ard.biesheuvel@arm.com>
On Sat, May 16, 2020 at 19:59:32 +0200, Ard Biesheuvel wrote:
> The 96boards I2C driver currently relies on the platform to connect
> all controllers, or I2C peripherals will not be exposed if they are
> not the active boot target. Since I2C peripherals are not boot targets
> in the first place, but are used to expose things like random number
> generators, let's connect the I2C controllers specifically at EndOfDxe
> so that the devices living on it will be available regardless of the
> boot policy.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> ---
> Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.inf | 5 ++++-
> Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.c | 18 ++++++++++++++++++
> 2 files changed, 22 insertions(+), 1 deletion(-)
>
> diff --git a/Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.inf b/Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.inf
> index ae69f0933e93..3d9ca559e60b 100644
> --- a/Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.inf
> +++ b/Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.inf
> @@ -36,10 +36,13 @@ [Protocols]
> [Guids]
> g96BoardsI2c0MasterGuid
> g96BoardsI2c1MasterGuid
> + gEfiEndOfDxeEventGroupGuid
>
> [FixedPcd]
> g96BoardsTokenSpaceGuid.PcdI2c0BusFrequencyHz
> g96BoardsTokenSpaceGuid.PcdI2c1BusFrequencyHz
>
> [Depex]
> - g96BoardsMezzanineProtocolGuid AND g96BoardsI2c0MasterGuid OR g96BoardsI2c1MasterGuid
> + g96BoardsMezzanineProtocolGuid AND (
> + g96BoardsI2c0MasterGuid OR g96BoardsI2c1MasterGuid
> + )
Is this change actually a bugfix?
It appears unrelated to the patch description as such, although
clearly an improvement.
/
Leif
> diff --git a/Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.c b/Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.c
> index e4ecbca62c0c..a751769cf691 100644
> --- a/Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.c
> +++ b/Platform/96Boards/96BoardsI2cDxe/96BoardsI2cDxe.c
> @@ -179,6 +179,19 @@ RegisterI2cBus (
> ASSERT_EFI_ERROR (Status);
> }
>
> +STATIC
> +VOID
> +EFIAPI
> +OnEndOfDxe (
> + IN EFI_EVENT Event,
> + IN VOID *Context
> + )
> +{
> + gBS->CloseEvent (Event);
> + gBS->ConnectController (mI2cBus0.I2cMasterHandle, NULL, NULL, TRUE);
> + gBS->ConnectController (mI2cBus1.I2cMasterHandle, NULL, NULL, TRUE);
> +}
> +
> EFI_STATUS
> EFIAPI
> EntryPoint (
> @@ -187,6 +200,7 @@ EntryPoint (
> )
> {
> EFI_STATUS Status;
> + EFI_EVENT EndOfDxeEvent;
>
> Status = gBS->LocateProtocol (&g96BoardsMezzanineProtocolGuid, NULL,
> (VOID **)&mMezzanine);
> @@ -197,5 +211,9 @@ EntryPoint (
> RegisterI2cBus (&g96BoardsI2c1MasterGuid, &mI2cBus1,
> mMezzanine->I2c1NumDevices, mMezzanine->I2c1DeviceArray);
>
> + Status = gBS->CreateEventEx (EVT_NOTIFY_SIGNAL, TPL_CALLBACK, OnEndOfDxe,
> + NULL, &gEfiEndOfDxeEventGroupGuid, &EndOfDxeEvent);
> + ASSERT_EFI_ERROR (Status);
> +
> return EFI_SUCCESS;
> }
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-05-18 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 17:59 [PATCH edk2-platforms 0/3] Silicon/SynQuacer: preparatory ConnectAll fixes Ard Biesheuvel
2020-05-16 17:59 ` [PATCH edk2-platforms 1/3] Platform/96Boards/96BoardsI2cDxe: connect I2C controllers at EndOfDxe Ard Biesheuvel
2020-05-18 17:26 ` Leif Lindholm [this message]
2020-05-19 10:23 ` Ard Biesheuvel
2020-05-19 10:46 ` Leif Lindholm
2020-05-16 17:59 ` [PATCH edk2-platforms 2/3] Silicon/SynQuacer/NetsecDxe: drop false dependency on device path protocol Ard Biesheuvel
2020-05-16 17:59 ` [PATCH edk2-platforms 3/3] Silicon/SynQuacer/NetsecDxe: avoid media detection delay at boot Ard Biesheuvel
2020-05-19 12:32 ` [PATCH edk2-platforms 0/3] Silicon/SynQuacer: preparatory ConnectAll fixes 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=20200518172624.GF10467@vanye \
--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