From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH v6 1/4] x86: qemu: move QFW to its own uclass
Date: Thu, 11 Mar 2021 21:45:23 -0700 [thread overview]
Message-ID: <CAPnjgZ3CMwcXC--T+NBo_oXeXgAtXatKUrr50r0b+NJhE5YSTg@mail.gmail.com> (raw)
In-Reply-To: <20210307035958.25969-2-ashe@kivikakk.ee>
On Sat, 6 Mar 2021 at 21:01, Asherah Connor <ashe@kivikakk.ee> wrote:
>
> We move qfw into its own uclass and split the PIO functions into a
> specific driver for that uclass. The PIO driver is selected in the
> qemu-x86 board config (this covers x86 and x86_64).
>
> include/qfw.h is cleaned up and documentation added.
>
> Signed-off-by: Asherah Connor <ashe@kivikakk.ee>
>
> ---
>
> Changes in v6:
> * Sandbox driver and tests are split into own commit.
>
> Changes in v5:
> * Split conversion of existing x86-only QFW to DM into its own patch.
> * Fix qfw_get_dev() so it actually returns -ENODEV when device is
> missing.
> * Add CONFIG_QFW_PIO.
> * Choose CONFIG_QFW_PIO in board/emulation/qemu-x86/Kconfig.
> * QFW sandbox driver no longer inserts itself from device tree; wasn't
> relevant to implementation and the ``compatible'' string was too
> made-up. Use U_BOOT_DRVINFO like the other QFW driver in this patch.
> * Relevant documentation and sandbox/qemu tests are now here.
>
> arch/x86/cpu/qemu/cpu.c | 9 +-
> arch/x86/cpu/qemu/qemu.c | 49 +------
> arch/x86/cpu/qfw_cpu.c | 11 +-
> board/emulation/qemu-x86/Kconfig | 1 +
> cmd/qfw.c | 56 ++++---
> common/Makefile | 2 +
> common/qfw.c | 105 +++++++++++++
> drivers/misc/Kconfig | 11 +-
> drivers/misc/Makefile | 5 +-
> drivers/misc/qfw.c | 243 +++++++++++--------------------
> drivers/misc/qfw_pio.c | 69 +++++++++
> include/dm/uclass-id.h | 1 +
> include/qfw.h | 200 +++++++++++++++++++++----
> 13 files changed, 490 insertions(+), 272 deletions(-)
> create mode 100644 common/qfw.c
> create mode 100644 drivers/misc/qfw_pio.c
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2021-03-12 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 3:59 [PATCH v6 0/4] Move qfw to DM, add Arm support Asherah Connor
2021-03-07 3:59 ` [PATCH v6 1/4] x86: qemu: move QFW to its own uclass Asherah Connor
2021-03-12 4:45 ` Simon Glass [this message]
2021-03-07 3:59 ` [PATCH v6 2/4] test: qemu: add qfw sandbox driver, dm tests, qemu tests Asherah Connor
2021-03-14 20:22 ` Tom Rini
2021-03-19 2:57 ` Asherah Connor
2021-03-07 3:59 ` [PATCH v6 3/4] qemu: add MMIO driver for QFW Asherah Connor
2021-03-12 4:45 ` Simon Glass
2021-03-07 3:59 ` [PATCH v6 4/4] qemu: arm: select QFW, MMIO on qemu-arm Asherah Connor
2021-03-12 4:45 ` Simon Glass
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=CAPnjgZ3CMwcXC--T+NBo_oXeXgAtXatKUrr50r0b+NJhE5YSTg@mail.gmail.com \
--to=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.