From: "Sami Mujawar" <sami.mujawar@arm.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH edk2-platforms 0/2] Platform/ARM/Juno: remove explicit PCIe enumeration
Date: Fri, 6 Dec 2019 11:41:29 +0000 [thread overview]
Message-ID: <DB6PR0802MB2375E50A878FBB213F5B860D845F0@DB6PR0802MB2375.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20191206111246.GR7359@bivouac.eciton.net>
Tested on Juno R2, the MAC address for Marvel Yukon NIC is programmed correctly.
Tested-by: Sami Mujawar <sami.mujawar@arm.com>
Regards,
Sami Mujawar
-----Original Message-----
From: Leif Lindholm <leif.lindholm@linaro.org>
Sent: 06 December 2019 11:13 AM
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: devel@edk2.groups.io; Sami Mujawar <Sami.Mujawar@arm.com>; Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH edk2-platforms 0/2] Platform/ARM/Juno: remove explicit PCIe enumeration
On Fri, Dec 06, 2019 at 11:02:17 +0000, Ard Biesheuvel wrote:
> The platform DXE driver of the Juno platform enumerates the PCIe
> explicitly by calling ConnectController on the PCIe root bridge, in
> order to ensure that all PCI I/O protocols have been instantiated when
> we try to locate the one describing the Marvel Yukon NIC, so that we can program its MAC address.
>
> Taking control of core firmware behavior like this has already caused
> confusion when reasoning about why and when PCIe option ROMs get
> dispatched, and is likely to cause more confusion down the road.
>
> So let's fix this, by triggering the MAC programming via a protocol
> notify on the PCI I/O protocol.
>
> This has been build tested only at the moment.
>
> Cc: Sami Mujawar <sami.mujawar@arm.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
This looks sensible to me (and way more can-of-wormish than I would have expected) - so:
Acked-by: Leif Lindholm <leif.lindholm@linaro.org>
*but* we need tested-by from somewhere before merging 2/2.
1/2 could go in whenever.
/
Leif
> Ard Biesheuvel (2):
> Platform/ARM/ArmJunoDxe: make mAcpiRegistration STATIC
> Platform/ARM/ArmJunoDxe: use PciIo protocol notify to program the
> MAC
>
> .../JunoPkg/Drivers/ArmJunoDxe/ArmJunoDxe.c | 163 ++++--------------
> .../JunoPkg/Drivers/ArmJunoDxe/ArmJunoDxe.inf | 1 -
> 2 files changed, 31 insertions(+), 133 deletions(-)
>
> --
> 2.17.1
>
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.
next prev parent reply other threads:[~2019-12-06 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 11:02 [PATCH edk2-platforms 0/2] Platform/ARM/Juno: remove explicit PCIe enumeration Ard Biesheuvel
2019-12-06 11:02 ` [PATCH edk2-platforms 1/2] Platform/ARM/ArmJunoDxe: make mAcpiRegistration STATIC Ard Biesheuvel
2019-12-06 12:16 ` Laszlo Ersek
2019-12-06 11:02 ` [PATCH edk2-platforms 2/2] Platform/ARM/ArmJunoDxe: use PciIo protocol notify to program the MAC Ard Biesheuvel
2019-12-06 12:12 ` Laszlo Ersek
2019-12-06 12:16 ` Ard Biesheuvel
2019-12-06 11:12 ` [PATCH edk2-platforms 0/2] Platform/ARM/Juno: remove explicit PCIe enumeration Leif Lindholm
2019-12-06 11:41 ` Sami Mujawar [this message]
2019-12-06 14:01 ` 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=DB6PR0802MB2375E50A878FBB213F5B860D845F0@DB6PR0802MB2375.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