public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: Ard Biesheuvel <ardb+git@google.com>, <devel@edk2.groups.io>
Cc: <jeremy.linton@arm.com>, <abner.chang@amd.com>,
	Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [edk2-devel] [PATCH 1/1] EmbeddedPkg/NonCoherentIoMmuDxe: Make SetAttributes always succeed
Date: Tue, 12 Mar 2024 09:38:14 -0700	[thread overview]
Message-ID: <74a4fb99-5d29-44ac-93bd-caea7367d08e@quicinc.com> (raw)
In-Reply-To: <20240312151716.2154180-1-ardb+git@google.com>

On 2024-03-12 08:17, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
> 
> NonCoherentIoMmuSetAttribute() does nothing except return
> EFI_UNSUPPORTED. This was fine when it was introduced, but now, the PCI
> bus driver will fail a PCI I/O Map() operation if the SetAttributes
> fails.
> 
> So return EFI_SUCCESS instead.

It's unclear to me why this change is safe (looking forward).
Does NonCoherentIoMmuDxe also imply no IoMmu actually exists?

/
     Leif

> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> This fixes a regression on Raspberry Pi4, which no longer boots.
> 
>   EmbeddedPkg/Drivers/NonCoherentIoMmuDxe/NonCoherentIoMmuDxe.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/EmbeddedPkg/Drivers/NonCoherentIoMmuDxe/NonCoherentIoMmuDxe.c b/EmbeddedPkg/Drivers/NonCoherentIoMmuDxe/NonCoherentIoMmuDxe.c
> index 4e7a5698c162..f02a76a62ea8 100644
> --- a/EmbeddedPkg/Drivers/NonCoherentIoMmuDxe/NonCoherentIoMmuDxe.c
> +++ b/EmbeddedPkg/Drivers/NonCoherentIoMmuDxe/NonCoherentIoMmuDxe.c
> @@ -70,7 +70,7 @@ NonCoherentIoMmuSetAttribute (
>     IN UINT64                IoMmuAccess
>     )
>   {
> -  return EFI_UNSUPPORTED;
> +  return EFI_SUCCESS;
>   }
>   
>   /**



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116691): https://edk2.groups.io/g/devel/message/116691
Mute This Topic: https://groups.io/mt/104886877/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-03-12 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 15:17 [edk2-devel] [PATCH 1/1] EmbeddedPkg/NonCoherentIoMmuDxe: Make SetAttributes always succeed Ard Biesheuvel via groups.io
2024-03-12 16:38 ` Leif Lindholm [this message]
2024-03-12 16:50   ` Ard Biesheuvel
2024-03-12 16:56     ` Leif Lindholm
2024-03-12 16:58       ` Ard Biesheuvel
2024-03-12 17:14         ` 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=74a4fb99-5d29-44ac-93bd-caea7367d08e@quicinc.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