From: Ard Biesheuvel <ardb@kernel.org>
To: linux-efi@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, atish.patra@wdc.com,
leif@nuviainc.com, Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 0/3] efi/arm: refactor DT EFI param parsing
Date: Wed, 19 Feb 2020 16:24:37 +0100 [thread overview]
Message-ID: <20200219152440.11561-1-ardb@kernel.org> (raw)
In preparation for another arrival (RISC-V), do some janitorial work on
the FDT param parsing code for EFI as well. The code sits in an #ifdef
block in efi.c, which is usually a good indicator that it should be moved
into its own source file. Then, we simplify the DT handling, by switching
to the FDT library, instead of going through the more high level early OF
enumeration code, which in our case will be doing libfdt calls under the
hood as well, as EFI on ARM specifically uses *flattened* DT. (note that
the EFI stub for ARM uses libfdt as well to populate the DT properties
that we read back here)
Ard Biesheuvel (3):
efi/arm: move FDT param discovery code out of efi.c
efi/arm: move FDT specific definitions into fdtparams.c
efi/arm: rewrite FDT param discovery routines
drivers/firmware/efi/Makefile | 1 +
drivers/firmware/efi/arm-init.c | 17 +--
drivers/firmware/efi/efi.c | 135 --------------------
drivers/firmware/efi/fdtparams.c | 125 ++++++++++++++++++
include/linux/efi.h | 10 +-
5 files changed, 133 insertions(+), 155 deletions(-)
create mode 100644 drivers/firmware/efi/fdtparams.c
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Ard Biesheuvel <ardb@kernel.org>
To: linux-efi@vger.kernel.org
Cc: atish.patra@wdc.com, leif@nuviainc.com,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] efi/arm: refactor DT EFI param parsing
Date: Wed, 19 Feb 2020 16:24:37 +0100 [thread overview]
Message-ID: <20200219152440.11561-1-ardb@kernel.org> (raw)
In preparation for another arrival (RISC-V), do some janitorial work on
the FDT param parsing code for EFI as well. The code sits in an #ifdef
block in efi.c, which is usually a good indicator that it should be moved
into its own source file. Then, we simplify the DT handling, by switching
to the FDT library, instead of going through the more high level early OF
enumeration code, which in our case will be doing libfdt calls under the
hood as well, as EFI on ARM specifically uses *flattened* DT. (note that
the EFI stub for ARM uses libfdt as well to populate the DT properties
that we read back here)
Ard Biesheuvel (3):
efi/arm: move FDT param discovery code out of efi.c
efi/arm: move FDT specific definitions into fdtparams.c
efi/arm: rewrite FDT param discovery routines
drivers/firmware/efi/Makefile | 1 +
drivers/firmware/efi/arm-init.c | 17 +--
drivers/firmware/efi/efi.c | 135 --------------------
drivers/firmware/efi/fdtparams.c | 125 ++++++++++++++++++
include/linux/efi.h | 10 +-
5 files changed, 133 insertions(+), 155 deletions(-)
create mode 100644 drivers/firmware/efi/fdtparams.c
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-02-19 15:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:24 Ard Biesheuvel [this message]
2020-02-19 15:24 ` [PATCH 0/3] efi/arm: refactor DT EFI param parsing Ard Biesheuvel
2020-02-19 15:24 ` [PATCH 1/3] efi/arm: move FDT param discovery code out of efi.c Ard Biesheuvel
2020-02-19 15:24 ` Ard Biesheuvel
2020-02-19 15:24 ` [PATCH 2/3] efi/arm: move FDT specific definitions into fdtparams.c Ard Biesheuvel
2020-02-19 15:24 ` Ard Biesheuvel
2020-02-19 15:24 ` [PATCH 3/3] efi/arm: rewrite FDT param discovery routines Ard Biesheuvel
2020-02-19 15:24 ` Ard Biesheuvel
2020-02-20 18:30 ` Leif Lindholm
2020-02-20 18:30 ` Leif Lindholm
2020-02-20 19:20 ` Ard Biesheuvel
2020-02-20 19:20 ` 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-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=20200219152440.11561-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=atish.patra@wdc.com \
--cc=leif@nuviainc.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.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 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.