From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 0/9] efi: add PCI controller driver
Date: Wed, 4 Dec 2019 13:56:50 +0100 [thread overview]
Message-ID: <20191204125659.22506-1-a.fatoum@pengutronix.de> (raw)
This series adds support for reusing existing barebox PCI drivers under
EFI. This means implementation of the EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL_GUID,
instead of EFI_PCI_IO_PROTOCOL_GUID, which abstracts the devices and
handles enumeration.
This was tested with the default QEMU x86_64 machine and OVMF (Tianocore)
as UEFI firmware and an emulated 8250_pci (driver included in this
series):
qemu-system-x86_64 -pflash OVMF.fd -device pci-serial,chardev=cdev0 \
-chardev file,id=cdev0,path=COM -nographic /dev/sdb
Driver is written against UEFI Specification 2.1D. This is my first
dabble with PCI controllers, so please take a more thorough look.
Thanks!
Ahmad
Ahmad Fatoum (9):
efi: add and use new efi_device_has_guid helper
driver: add missing parentheses around macro argument
efi: fix off-by-one in mem_malloc_init(..., end)
x86: efi: lds: don't discard any relocation sections
PCI: add driver_data member to struct pci_device_id
PCI: copy over some Linux PCI helpers
efi: turn set of defines into enumerations
pci: add EFI PCI root bridge IO protocol driver
serial: add support for PCI NS16550 UARTs
arch/x86/mach-efi/elf_x86_64_efi.lds.S | 7 +-
common/efi/efi.c | 2 +-
drivers/block/efi-block-io.c | 11 +-
drivers/efi/Kconfig | 1 +
drivers/efi/efi-device.c | 11 +-
drivers/pci/Kconfig | 5 +
drivers/pci/Makefile | 1 +
drivers/pci/bus.c | 26 +
drivers/pci/pci-efi.c | 311 ++
drivers/pci/pci-efi.h | 331 ++
drivers/serial/Kconfig | 8 +
drivers/serial/Makefile | 1 +
drivers/serial/serial_ns16550_pci.c | 5311 ++++++++++++++++++++++++
include/driver.h | 4 +-
include/efi.h | 42 +-
include/efi/efi-device.h | 12 +
include/linux/mod_devicetable.h | 1 +
include/linux/pci.h | 34 +
18 files changed, 6073 insertions(+), 46 deletions(-)
create mode 100644 drivers/pci/pci-efi.c
create mode 100644 drivers/pci/pci-efi.h
create mode 100644 drivers/serial/serial_ns16550_pci.c
--
2.24.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-12-04 12:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 12:56 Ahmad Fatoum [this message]
2019-12-04 12:56 ` [PATCH 1/9] efi: add and use new efi_device_has_guid helper Ahmad Fatoum
2019-12-04 12:56 ` [PATCH 2/9] driver: add missing parentheses around macro argument Ahmad Fatoum
2019-12-04 12:56 ` [PATCH 3/9] efi: fix off-by-one in mem_malloc_init(..., end) Ahmad Fatoum
2019-12-04 12:56 ` [PATCH 4/9] x86: efi: lds: don't discard any relocation sections Ahmad Fatoum
2019-12-04 12:56 ` [PATCH 5/9] PCI: add driver_data member to struct pci_device_id Ahmad Fatoum
2019-12-04 12:56 ` [PATCH 6/9] PCI: copy over some Linux PCI helpers Ahmad Fatoum
2019-12-04 12:56 ` [PATCH 7/9] efi: turn set of defines into enumerations Ahmad Fatoum
2019-12-04 12:56 ` [PATCH 8/9] pci: add EFI PCI root bridge IO protocol driver Ahmad Fatoum
2019-12-09 10:39 ` Ahmad Fatoum
2019-12-04 12:56 ` [PATCH 9/9] serial: add support for PCI NS16550 UARTs Ahmad Fatoum
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-all 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=20191204125659.22506-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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