Simplify efi_sigstore_parse_sigdb() by using existing functions.
Signed-off-by: Heinrich Schuchardt
---
v3:
Keep error handling in efi_sigstore_parse_sigdb()
v2:
remove a superfluous check
---
lib/efi_loader/efi_signature.c | 11 ++-
1 file changed, 2 insertions(+), 9 del
Don't duplicate GUIDs.
Signed-off-by: Heinrich Schuchardt
---
v3:
no change
v2:
no change
---
lib/efi_loader/efi_tcg2.c | 29 +
1 file changed, 13 insertions(+), 16 deletions(-)
diff --git a/lib/efi_loader/efi_tcg2.c b/lib/efi_loader/efi_tcg2.c
index
In multiple places we need the default GUID matching a variable name.
The patch provides a library function. For secure boot related variables
like 'PK', 'KEK', 'db' a lookup table is used. For all other variable
names EFI_GLOBAL_VARIABLE is returned.
Signed-off-by: Heinrich Schuchardt
---
v3:
The UEFI specification defines which vendor GUIDs should be used for
predefined variables like 'PK'. Currently we have multiple places
where this relationship is stored.
With this patch series a function for retrieving the GUID is provided
and existing code is adjusted to used it.
v3:
Kee
UEFI variable names are typically constants and hence should be defined as
const. Unfortunately some of our API functions do not define the parameters
for UEFI variable names as const. This requires unnecessary conversions.
Adjust parameters of several internal functions to tre UEFI variable names
Hi Tom,
On 01.10.21 14:59, Tom Rini wrote:
On Fri, Oct 01, 2021 at 01:01:37PM +0200, Stefan Roese wrote:
Added to Tom to Cc
On 01.10.21 12:43, Stefan Roese wrote:
On 01.10.21 12:39, Pali Rohár wrote:
Hello!
On Friday 01 October 2021 12:28:34 Stefan Roese wrote:
First the test on "next" wit
Select SPL_SKIP_LOWLEVEL_INIT on 32bit Armada platforms via Kconfig,
as this was removed from mach/config.h in a2ac2b96 ("Convert
CONFIG_SKIP_LOWLEVEL_INIT et al to Kconfig").
Signed-off-by: Stefan Roese
Fixes: a2ac2b96 ("Convert CONFIG_SKIP_LOWLEVEL_INIT et al to Kconfig")
Cc: Tom Rini
Cc: Mare
The macro called MUX_VAL generates a writel instruction with
semicolon at the end. This table was written to use semicolons,
however one was missed:
MUX_VAL(CP(SYS_BOOT2), (IEN | PTD | DIS | M4))/* GPIO_4 */
Since the extra semicolon is unnecessary with the use of the macro,
remove
This adds support for the NanoPi R1S H5 board.
Allwinner H5 SoC
512MB DDR3 RAM
10/100/1000M Ethernet x 2
RTL8189ETV WiFi 802.11b/g/n
USB 2.0 host port (A)
MicroSD Slot
Reset button
Serial Debug Port
WAN - LAN - SYS LED
The dts file is taken from Linux 5.14 tag, and includes the
change to the eepr
> Benefit is, besides host mode, now user can choose device mode with
> setting of dr_mode = ?peripheral?;
>
> Signed-off-by: Ran Wang
> ---
> Change in v2:
> - Remove property 'snps,dis_rxdet_inp3_quirk' due to its side effect to Linux
>kernel (USB device no detected)
>
> arch/arm/dts/fs
This series adds basic support for Apple's M1 SoC to U-Boot.
This builds a basic U-Boot that can be used as a payload
for the m1n1 boot loader being developed by the Asahi Linux
project.
The goal here is to privide an UEFI interface on these machines that
allows booting various open source OSes.
This uclass is intended to manage IOMMUs on systems where the
IOMMUs are not in bypass mode by default. In that case U-Boot
cannot ignore the IOMMUs if it wants to use devices that need
to do DMA and sit behind such an IOMMU.
This initial IOMMU uclass implementation does not implement and
device
Add a set of tests for the IOMMU uclass.
Signed-off-by: Mark Kettenis
---
arch/sandbox/dts/test.dts | 6 ++
configs/sandbox64_defconfig| 1 +
configs/sandbox_defconfig | 1 +
configs/sandbox_flattree_defconfig | 1 +
configs/sandbox_noinst_defconfig | 1 +
co
Add support for Apple's M1 SoC that is used in "Apple Silicon"
Macs. This builds a basic U-Boot that can be used as a payload
for the m1n1 boot loader being developed by the Asahi Linux
project.
Signed-off-by: Mark Kettenis
---
arch/arm/Kconfig| 21
arch/arm/Makefile
Apple M1 SoCs include an S5L UART which is a variant of the S5P
UART. Add support for this variant and enable it by default
on Apple SoCs.
Signed-off-by: Mark Kettenis
---
arch/arm/Kconfig| 1 +
arch/arm/include/asm/arch-m1/uart.h | 41 +++
configs/apple_m1_defcon
The DART is an IOMMU that is used on Apple's M1 SoC. This driver
configures the DART such that it operates in bypass mode which is
enough to support DMA for the USB3 ports integrated on the SoC.
Signed-off-by: Mark Kettenis
---
arch/arm/Kconfig | 1 +
drivers/iommu/Kconfig | 10
Add preliminary device trees for the Apple M1 mini (2020) and
Apple M1 Macbook Pro 13" (2020). Device tree bindings for
the Apple M1 SoC are still being formalized and these device
trees will be synchronized with the Linux kernel as needed.
These device trees are provided as a reference only as U
Provide preliminary instructions on how to get U-Boot to run on
Apple Silicon Macs.
Signed-off-by: Mark Kettenis
---
doc/board/apple/index.rst | 9 +++
doc/board/apple/m1.rst| 56 +++
doc/board/index.rst | 1 +
3 files changed, 66 insertions(+)
On Thu, Sep 16, 2021 at 04:52:19PM +0800, Chia-Wei Wang wrote:
> Enable SPL FIT image load and verification support.
> The HW accelerated SHA is also available with the
> newly added support of the HACE HW hash engine.
>
> The SPL thumb build is also enabled to keep the binary
> less than 64KB to
On Sat, Sep 18, 2021 at 08:17:54AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Add the DT entry for a watchdog based on RTI1. It requires additional
> firmware on the MCU R5F cores to handle the expiry, e.g.
> https://github.com/siemens/k3-rti-wdt. As this firmware will also lock
> the power
Add missing hyphens and reword one sentence for clarity.
Signed-off-by: Simon Glass
---
.../devicetree/bindings/example-schema.yaml | 14 -
.../devicetree/bindings/writing-bindings.rst | 2 +-
.../devicetree/bindings/writing-schema.rst| 29 ++-
3 files changed, 2
U-Boot makes use of the devicetree for its driver model. Devices are bound
based on the hardware description in the devicetree.
Since U-Boot is not an operating system, it has no command line or user
space to provide configuration and policy information. This must be made
available in some other w
On 10/3/21 11:50 AM, Simon Glass wrote:
Add missing hyphens and reword one sentence for clarity.
Signed-off-by: Simon Glass
---
.../devicetree/bindings/example-schema.yaml | 14 -
.../devicetree/bindings/writing-bindings.rst | 2 +-
.../devicetree/bindings/writing-schema.rst
On Tue, Aug 31, 2021 at 01:12:24PM -0500, Nishanth Menon wrote:
> Synchronize with the upstream version as of v5.14 kernel tag
>
> Signed-off-by: Nishanth Menon
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Fri, Sep 10, 2021 at 05:37:43PM -0400, Tom Rini wrote:
> This resyncs the dts files for all of the currently in-tree K3
> platforms, along with relevant bindings, with the v5.14 Linux Kernel
> release. Of note are that the main-navss/mcu-navss nodes were renamed
> to main_navss / mcu_navss and
On Thu, Sep 16, 2021 at 02:10:09PM +0800, Chia-Wei Wang wrote:
> The WDT devices described in the general .dtsi file
> should be marked as "disabled" by default.
>
> A WDT should be then enabled in the board specific
> .dts file on demands.
>
> Signed-off-by: Chia-Wei Wang
> Reviewed-by: Ryan C
On Fri, Sep 17, 2021 at 06:46:01AM +, Mathew McBride wrote:
> A search of the tree showed there is only one user
> of this driver (soon to be two) - board/socrates
>
> The second user will be the Traverse Ten64 board.
>
> Both these boards have DM_RTC.
>
> Signed-off-by: Mathew McBride
Ap
On Fri, Sep 17, 2021 at 06:46:02AM +, Mathew McBride wrote:
> The RX8035 is a newer model from EPSON which is
> very similar in operation to the RX8025.
>
> The changes mirror similar ones that will be
> in Linux 5.15:
> https://lore.kernel.org/all/20210709044518.28769-2-m...@traverse.com.au/
On Fri, Sep 17, 2021 at 06:46:03AM +, Mathew McBride wrote:
> The RX8025/RX8035 does not like having it's time registers
> set byte-by-byte in separate I2C transactions.
>
> From the note at the top of the file, it appears
> target-dependent workarounds have been used in the
> past for this.
On Fri, Sep 17, 2021 at 06:46:04AM +, Mathew McBride wrote:
> Writing of individual registers was not functioning
> correctly as a 0 'offset' byte under DM-managed
> I2C was being appended in front of register we
> wanted to access.
>
> Signed-off-by: Mathew McBride
Applied to u-boot/next,
On Fri, Sep 17, 2021 at 03:11:20PM +0300, Vladimir Oltean wrote:
> The weak definition of pci_skip_dev from drivers/pci/pci_common.c is not
> under CONFIG_DM_PCI_COMPAT, and that definition needs a previous
> function prototype declaration to avoid W=1 build warnings.
>
> That prototype is not av
On Fri, Sep 17, 2021 at 03:11:21PM +0300, Vladimir Oltean wrote:
> To avoid a build warning with W=1, provide a function prototype for
> dm_pciauto_prescan_setup_bridge, which is a non-static function whose
> definition is inside pci_auto.c.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin
On Fri, Sep 17, 2021 at 03:11:22PM +0300, Vladimir Oltean wrote:
> To avoid W=1 build warnings, declare this function as static, since it
> is not used outside of this translation module.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
sign
On Fri, Sep 17, 2021 at 03:11:23PM +0300, Vladimir Oltean wrote:
> To avoid W=1 build warnings, declare this function as static, since it
> is not used outside of this translation module.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
sign
On Fri, Sep 17, 2021 at 03:11:24PM +0300, Vladimir Oltean wrote:
> To avoid W=1 build warnings, declare this function as static, since it
> is not used outside of this translation module.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
sign
On Fri, Sep 17, 2021 at 03:11:25PM +0300, Vladimir Oltean wrote:
> To avoid W=1 build warnings, declare this function as static, since it
> is not used outside of this translation module.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
sign
On Fri, Sep 17, 2021 at 03:11:26PM +0300, Vladimir Oltean wrote:
> To avoid W=1 build warnings, declare this function as static, since it
> is not used outside of this translation module.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
sign
On Fri, Sep 17, 2021 at 03:11:28PM +0300, Vladimir Oltean wrote:
> To avoid W=1 build warnings, declare this function as static, since it
> is not used outside of this translation module.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
sign
On Fri, Sep 17, 2021 at 03:11:27PM +0300, Vladimir Oltean wrote:
> To avoid W=1 build warnings, declare this function as static, since it
> is not used outside of this translation module.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
sign
On Fri, Sep 17, 2021 at 03:11:29PM +0300, Vladimir Oltean wrote:
> The function prototype for ft_pci_setup is inside fdt_support.h, we need
> to include that header.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description:
On Fri, Sep 17, 2021 at 03:11:30PM +0300, Vladimir Oltean wrote:
> To avoid W=1 build warnings, declare this function as static, since it
> is not used outside of this translation module.
>
> Signed-off-by: Vladimir Oltean
> Reviewed-by: Bin Meng
Applied to u-boot/next, thanks!
--
Tom
sign
On Sat, Sep 18, 2021 at 08:17:52AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Prepares for the addition of the IOT2050 board which is based on the TI
> AM65x. The board comes in four variants, Basic and Advanced, each as
> product generation 1 (SR1.0) and 2 (SR2.x), so there are separate dt
On Sat, Sep 18, 2021 at 08:17:53AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This adds support for the IOT2050 Basic and Advanced devices. The Basic
> used the dual-core AM6528 GP processor, the Advanced one the AM6548 HS
> quad-core version.
>
> Both variants are booted via a Siemens-pro
On Sat, Sep 18, 2021 at 08:17:55AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> To avoid the need of extra boot scripting on AM65x for loading a
> watchdog firmware, add the required rproc init and loading logic for the
> first R5F core to the watchdog start handler. In case the R5F cluster i
On Sat, Sep 18, 2021 at 08:17:56AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This allows to use the watchdog in custom scripts but does not enforce
> that the OS has to support it as well.
>
> Signed-off-by: Jan Kiszka
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description
Since it's expected that DM_USB is enabled by now, remove some dead
code and the checks for DM_USB.
Signed-off-by: Adam Ford
diff --git a/arch/arm/include/asm/ehci-omap.h b/arch/arm/include/asm/ehci-omap.h
index f970bba937..2b51b5eb99 100644
--- a/arch/arm/include/asm/ehci-omap.h
+++ b/arch/arm/
Some usb-nop-xceiv devices use a gpio to put them
in reset. Add a reset function to put them into that
state, and have the init function take them out of reset
Signed-off-by: Adam Ford
diff --git a/drivers/phy/nop-phy.c b/drivers/phy/nop-phy.c
index 9f12ebc062..be993a764f 100644
--- a/drivers/p
Several omap boards use CONFIG_OMAP_EHCI_PHYx_RESET_GPIO to pull
the phy out of reset, when this should really be done inside the
phy driver. Add functions to determine which phys are associated
the EHCI driver, hold them in reset before EHCI is initialized,
initialize the EHCI, then release the p
Hi Tom,
> From: Tom Rini
> Sent: Monday, October 4, 2021 2:41 AM
>
> On Thu, Sep 16, 2021 at 04:52:19PM +0800, Chia-Wei Wang wrote:
>
> > Enable SPL FIT image load and verification support.
> > The HW accelerated SHA is also available with the newly added support
> > of the HACE HW hash engine.
Fix inconsistent function parameter name of the hash algorithm.
Signed-off-by: Chia-Wei Wang
Fixes: 92055e138f2 ("image: Drop if/elseif hash selection in calculate_hash()")
---
common/image-fit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/image-fit.c b/common/imag
The AST2600 SRAM has been extended to 88KB since A1
chip revision. This patch updates the SRAM size to
offer more space for early stack/heap use.
Signed-off-by: Chia-Wei Wang
---
arch/arm/include/asm/arch-aspeed/platform.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/
This patch series intends to provide a secure boot chain from SPL to Linux
kernel
based on the hash and signature verification of FIT image paradigm.
To improve the performance and save code size (SPL is limited to 64KB due to
HW-RoT),
the drviers of two HW crypto engine HACE and ACRY are also a
From: Joel Stanley
Add HACE DTS node and enable it for AST2600 EVB.
Signed-off-by: Joel Stanley
Signed-off-by: Chia-Wei Wang
---
arch/arm/dts/ast2600-evb.dts | 5 +
arch/arm/dts/ast2600.dtsi| 8
2 files changed, 13 insertions(+)
diff --git a/arch/arm/dts/ast2600-evb.dts b/ar
Add RSACLK enable for ACRY, the HW RSA/ECC crypto engine
of ASPEED AST2600 SoCs.
As ACRY and HACE share the same reset control bit, we do not
perform the reset-hold-n-release operation during their clock
ungating process. Instead, only reset release is conducted to
prevent mutual interference.
Si
ACRY is deisnged to accerlerate ECC/RSA digital signature
generation and verification.
Signed-off-by: Chia-Wei Wang
---
drivers/crypto/aspeed/Kconfig | 10 ++
drivers/crypto/aspeed/Makefile | 1 +
drivers/crypto/aspeed/aspeed_acry.c | 182
lib/rsa/Kconf
Add ACRY DTS node and enable it for AST2600 EVB.
Signed-off-by: Chia-Wei Wang
---
arch/arm/dts/ast2600-evb.dts | 5 +
arch/arm/dts/ast2600.dtsi| 9 +
2 files changed, 14 insertions(+)
diff --git a/arch/arm/dts/ast2600-evb.dts b/arch/arm/dts/ast2600-evb.dts
index adb80a30ef..0536
Return CONFIG_SYS_LOAD_ADDR pointing to DRAM space for
spl_get_load_buffer() to allow generic SPL image loading
code (e.g. FIT and Ymodem) to store data in DRAM.
Signed-off-by: Chia-Wei Wang
---
arch/arm/mach-aspeed/ast2600/spl.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
dif
From: Joel Stanley
Add YCLK enable for HACE, the HW hash engine of
ASPEED AST2600 SoCs.
Signed-off-by: Joel Stanley
Signed-off-by: Chia-Wei Wang
---
.../arm/include/asm/arch-aspeed/scu_ast2600.h | 5 +++--
drivers/clk/aspeed/clk_ast2600.c | 20 +++
2 files change
From: Johnny Huang
Hash and Crypto Engine (HACE) is designed to accelerate the
throughput of hash data digest, and symmetric-key encryption.
Signed-off-by: Johnny Huang
Signed-off-by: Chia-Wei Wang
---
drivers/crypto/Kconfig | 2 +
drivers/crypto/Makefile | 1 +
d
AST2600 leverages the FIT hash/signature verification to fulfill
secure boot trust chain. To improve the performance and save SW
code size for those crypto operations, the two HW crypto engine,
HACE and ACRY, are enabled.
However, both of the engines can only access to data stored in
DRAM space. T
Enable SPL FIT image load and verification support.
The HW accelerated SHA is also available with the
newly added support of the HACE HW hash engine.
The SPL thumb build is also enabled to keep the binary
less than 64KB to fit into the Aspeed secure boot design.
Signed-off-by: Chia-Wei Wang
---
Move CONFIG_EXTRA_ENV_SETTINGS to board-specific
configuration headers.
Signed-off-by: Chia-Wei Wang
---
include/configs/aspeed-common.h | 9 -
include/configs/evb_ast2500.h | 9 +
include/configs/evb_ast2600.h | 9 +
3 files changed, 18 insertions(+), 9 deletions(-)
On Sat, 2 Oct 2021 at 01:43, Heinrich Schuchardt wrote:
>
>
>
> On 10/1/21 13:18, Masahisa Kojima wrote:
> > This commit adds the DeployedMode and AuditMode variable
> > measurement required in TCG PC Client PFP Spec.
> >
> > Signed-off-by: Masahisa Kojima
> > ---
> >
> > Changes in v3:
> > - rea
On Sat, 2 Oct 2021 at 01:28, Heinrich Schuchardt wrote:
>
>
>
> On 10/1/21 13:18, Masahisa Kojima wrote:
> > This commit adds the UEFI GPT disk partition topology
> > measurement required in TCG PC Client PFP Spec.
> >
> > Signed-off-by: Masahisa Kojima
> > ---
> >
> > Changes in v3:
> > - EV_EFI
Heinrich,
On Fri, Oct 01, 2021 at 08:41:52AM +0200, Heinrich Schuchardt wrote:
>
>
> On 10/1/21 7:01 AM, AKASHI Takahiro wrote:
> > In blk_get_device_by_str(), the comment says: "Updates the partition table
> > for the specified hw partition."
> > Since hw partition is supported only on MMC, it
Hi Peter,
On Fri, Oct 01, 2021 at 12:48:24PM +0100, Peter Robinson wrote:
> On Fri, Oct 1, 2021 at 6:03 AM AKASHI Takahiro
> wrote:
> >
> > In blk_get_device_by_str(), the comment says: "Updates the partition table
> > for the specified hw partition."
> > Since hw partition is supported only on M
On Fri, Oct 01, 2021 at 11:30:37AM +0200, Heinrich Schuchardt wrote:
>
>
> On 10/1/21 07:01, AKASHI Takahiro wrote:
> > UCLASS_PARTITION device will be created as a child node of
> > UCLASS_BLK device.
> >
> > Signed-off-by: AKASHI Takahiro
> > ---
> > drivers/block/blk-uclass.c | 111 +++
# Resending the RFC as some of patches were deplicately submitted.
# See also
https://git.linaro.org/people/takahiro.akashi/u-boot.git efi/dm_disk
The purpose of this RPC is to reignite the discussion about how UEFI
subystem would best be integrated into U-Boot device model.
In the past, I popos
In blk_get_device_by_str(), the comment says: "Updates the partition table
for the specified hw partition."
Since hw partition is supported only on MMC, it makes no sense to do so
for other devices.
Signed-off-by: AKASHI Takahiro
---
disk/part.c | 3 ++-
1 file changed, 2 insertions(+), 1 deleti
Every time a scsi bus/port is scanned and a new block device is detected,
we want to call device_probe() as it will give us a chance to run additional
post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
---
Every time a usb bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run additional
post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
---
common
Every time a mmc bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run additional
post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
---
driver
Every time a nvme bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run additional
post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
---
drive
Every time a sata bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run additional
post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
---
drive
Every time an ide bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run additional
post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
---
drive
UCLASS_PARTITION device will be created as a child node of
UCLASS_BLK device.
Signed-off-by: AKASHI Takahiro
---
drivers/block/blk-uclass.c | 111 +
include/blk.h | 9 +++
include/dm/uclass-id.h | 1 +
3 files changed, 121 insertions(+)
d
Now that all the block device drivers have enable a probe hook, we will
call blk_create_partitions() to enumerate all the partitions and create
associated udevices when a block device is detected.
Signed-off-by: AKASHI Takahiro
---
drivers/block/blk-uclass.c | 15 +++
1 file changed,
In include/blk.h, Simon suggested:
===>
/*
* These functions should take struct udevice instead of struct blk_desc,
* but this is convenient for migration to driver model. Add a 'd' prefix
* to the function operations, so that blk_read(), etc. can be reserved for
* functions with the correct ar
In most of all usages, we can avoid using blk_desc which is expected
to be data private to the device not be accessed outside device drivers.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_disk.c | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git
This member field in udevice will be used to dereference from udevice
to efi_object (or efi_handle).
Signed-off-by: AKASHI Takahiro
---
include/dm/device.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/dm/device.h b/include/dm/device.h
index 0a9718a5b81a..33b09a836f06 100644
--
The change in this patch will probably have been covered by other guy's patch.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_disk.c | 49 ---
1 file changed, 49 deletions(-)
diff --git a/lib/efi_loader/efi_disk.c b/lib/efi_loader/efi_disk.c
index dfa6
Adding this callback function, efi_disk_create() in block devices's
post_probe hook will allows for automatically creating efi_disk objects
per block device.
This will end up not only eliminating efi_disk_register() called in UEFI
initialization, but also enabling detections of new block devices e
Add efi_disk_create() function.
Any UEFI handle created by efi_disk_create() can be treated as a efi_disk
object, the udevice is either a UCLASS_BLK (a whole raw disk) or
UCLASS_PARTITION (a disk partition).
So this function is expected to be called every time such an udevice
is detected and acti
efi_disk_register() will be no longer needed now that all efi_disks are
set to be created with device model thanks to efi_disk-dm integration.
Signed-off-by: AKASHI Takahiro
---
include/efi_loader.h | 2 -
lib/efi_loader/efi_disk.c | 102 -
lib/efi_lo
This function is a counterpart of efi_add_handle() and will be used
in order to remove an efi_disk object in a later patch.
Signed-off-by: AKASHI Takahiro
---
include/efi_loader.h | 2 ++
lib/efi_loader/efi_boottime.c | 8
2 files changed, 10 insertions(+)
diff --git a/include
This function is expected to be called, in particular from dm's pre_remove
hook, when associated block devices no longer exist.
Signed-off-by: AKASHI Takahiro
---
include/efi_loader.h | 2 ++
lib/efi_loader/efi_disk.c | 54 +++
2 files changed, 56 insert
Adding the callback function, efi_disk_delete(), in block devices's
pre_remove hook will allows for automatically deleting efi_disk objects
per block device.
This will eliminate any improper efi_disk objects which hold a link to
non-existing udevice structures when associated block devices are phy
Signed-off-by: AKASHI Takahiro
---
lib/efi_driver/efi_block_device.c | 6 ++
lib/efi_loader/efi_device_path.c | 29 +
lib/efi_loader/efi_disk.c | 12 +++-
3 files changed, 46 insertions(+), 1 deletion(-)
diff --git a/lib/efi_driver/efi_block_devi
efi_driver-specific binding will be no longer needed now that efi_disk-
dm integration takes care of efi_driver case as well.
Signed-off-by: AKASHI Takahiro
---
lib/efi_driver/efi_block_device.c | 24
1 file changed, 24 deletions(-)
diff --git a/lib/efi_driver/efi_block
Due to efi_disk-dm integration, the resultant device path for a test disk
got slightly changed, with efi_root contained as the first component.
Signed-off-by: AKASHI Takahiro
---
lib/efi_selftest/efi_selftest_block_device.c | 26 ++--
1 file changed, 24 insertions(+), 2 deletions
Hi Heinrich,
What is the current status of this patch series?
Could you give me any comments?
Thank you,
2021年9月17日(金) 13:47 Masami Hiramatsu :
>
> Hi Heinrich,
>
> 2021年9月17日(金) 12:54 Heinrich Schuchardt :
> >
> > On 9/16/21 10:53 AM, Masami Hiramatsu wrote:
> > > Hello Heinrich,
> > >
> > > He
91 matches
Mail list logo
