Bug-fixes for a few boards
Subsystems (3)
v3 cover Bug-fixes for a few boards
This series includes fixes to get some rockchip and nvidia boards working again. It also drops the broken Beaglebone Black config and provides a devicetree fix for coral (x86).
Changes in v3:
- Use BLOBLIST instead of OF_BLOBLIST
- Cut the patch down to bare bones
- Split out the refactoring into a separate patch
- Drop the non-dcache optimisation, since the cache should normally be on
Changes in v2:
- Put the conditions under EFI_TCG2_PROTOCOL
- Consider MEASURED_BOOT too
- Remove the superfluous if() and drop the debug() as well
- Use 'phase' instead of 'stage'
- Add new patch to correct memory size in SPL
- Drop patch "regulator: rk8xx: Fix incorrect parameter"
- Rewrite boneblack patch to onstead drop the target and update docs
Simon Glass (18):
binman: Support an assumed size for missing binaries
binman: Make Intel ME default to position 0x1000
mkeficapsule: Add a --version argument
binman: Collect the version number for mkeficapsule
binman: Deal with mkeficapsule being missing
binman: Return failure when a usage() message is generated
binman: Keep the efi_capsule input file
x86: Set up some assumed sizes for binary blobs
nvidia: nyan-big: Disable debug UART
tpm: Avoid code bloat when not using EFI_TCG2_PROTOCOL
rockchip: veyron: Add logging for power init
power: regulator: Handle autoset in regulators_enable_boot_on()
fdt: Correct condition for bloblist existing
spl: Allow ATF to work when dcache is disabled
rockchip: Ensure memory size is available in RK3399 SPL
rockchip: Avoid #ifdefs in RK3399 SPL
rockchip: bob: kevin: Disable dcache in SPL
Drop the special am335x_boneblack_vboot target
arch/x86/dts/u-boot.dtsi | 5 ++ board/google/veyron/veyron.c | 30 +++---- board/ti/am335x/MAINTAINERS | 1 - boot/Kconfig | 4 + common/spl/spl_atf.c | 3 +- configs/am335x_boneblack_vboot_defconfig | 94 ---------------------- configs/am335x_evm_defconfig | 3 +- configs/chromebook_bob_defconfig | 1 + configs/chromebook_kevin_defconfig | 1 + configs/nyan-big_defconfig | 1 - doc/mkeficapsule.1 | 4 + doc/usage/fit/beaglebone_vboot.rst | 21 +++-- drivers/power/regulator/regulator-uclass.c | 2 +- drivers/ram/rockchip/sdram_rk3399.c | 49 ++++++----- lib/Kconfig | 4 - lib/fdtdec.c | 12 ++- tools/binman/binman.rst | 7 ++ tools/binman/btool/mkeficapsule.py | 3 +- tools/binman/entry.py | 1 + tools/binman/etype/blob.py | 7 +- tools/binman/etype/efi_capsule.py | 5 +- tools/binman/etype/intel_descriptor.py | 2 +- tools/binman/ftest.py | 28 +++++++ tools/binman/test/326_assume_size.dts | 16 ++++ tools/binman/test/327_assume_size_ok.dts | 16 ++++ tools/mkeficapsule.c | 10 ++- 26 files changed, 168 insertions(+), 162 deletions(-) delete mode 100644 configs/am335x_boneblack_vboot_defconfig create mode 100644 tools/binman/test/326_assume_size.dts create mode 100644 tools/binman/test/327_assume_size_ok.dts
Signature · 1 line
2.34.1
PATCH v3 1/18 binman: Support an assumed size for missing binaries
Binman has a the useful feature of handling missing external blobs gracefully, including allowing them to be missing, deciding whether the resulting image is functional or not and faking blobs when this is necessary for particular tools (e.g. mkimage).
This feature is widely used in CI. One drawback is that if U-Boot grows too large to fit along with the required blobs, then this is not discovered until someone does a 'real' build which includes the blobs.
Add a 'assume-size' property to entries to allow Binman to reserve a given size for missing external blobs.
---
(no changes since v1)
tools/binman/binman.rst | 7 ++++++ tools/binman/entry.py | 1 + tools/binman/etype/blob.py | 7 +++++- tools/binman/ftest.py | 28 ++++++++++++++++++++++++ tools/binman/test/326_assume_size.dts | 16 ++++++++++++++ tools/binman/test/327_assume_size_ok.dts | 16 ++++++++++++++ 6 files changed, 74 insertions(+), 1 deletion(-) create mode 100644 tools/binman/test/326_assume_size.dts create mode 100644 tools/binman/test/327_assume_size_ok.dts
tools/binman/binman.rst +7 -0
@@ -711,6 +711,13 @@ missing-msg: information about what needs to be fixed. See missing-blob-help for the message for each tag. +assume-size: + Sets the assumed size of a blob entry if it is missing. This allows for a + check that the rest of the image fits into the available space, even when + the contents are not available. If the entry is missing, Binman will use + this assumed size for the entry size, including creating a fake file of that + size if requested. + no-expanded: By default binman substitutes entries with expanded versions if available, so that a `u-boot` entry type turns into `u-boot-expanded`, for example. The
tools/binman/entry.py +1 -0
@@ -315,6 +315,7 @@ class Entry(object): self.overlap = fdt_util.GetBool(self._node, 'overlap') if self.overlap: self.required_props += ['offset', 'size'] + self.assume_size = fdt_util.GetInt(self._node, 'assume-size', 0) # This is only supported by blobs and sections at present self.compress = fdt_util.GetString(self._node, 'compress', 'none')
tools/binman/etype/blob.py +6 -1
@@ -48,11 +48,16 @@ class Entry_blob(Entry): self.external and (self.optional or self.section.GetAllowMissing())) # Allow the file to be missing if not self._pathname: + if not fake_size and self.assume_size: + fake_size = self.assume_size self._pathname, faked = self.check_fake_fname(self._filename, fake_size) self.missing = True if not faked: - self.SetContents(b'') + content_size = 0 + if self.assume_size: # Ensure we get test coverage on next line + content_size = self.assume_size + self.SetContents(tools.get_bytes(0, content_size)) return True self.ReadBlobContents()
tools/binman/ftest.py +28 -0
@@ -7460,5 +7460,33 @@ fdt fdtmap Extract the devicetree blob from the fdtmap with self.assertRaises(ValueError) as e: self._DoReadFile('323_capsule_accept_revert_missing.dts') + def test_assume_size(self): + """Test handling of the assume-size property for external blob""" + with self.assertRaises(ValueError) as e: + self._DoTestFile('326_assume_size.dts', allow_missing=True, + allow_fake_blobs=True) + self.assertIn("contents size 0xa (10) exceeds section size 0x9 (9)", + str(e.exception)) + + def test_assume_size_ok(self): + """Test handling of the assume-size where it fits OK""" + with test_util.capture_sys_output() as (stdout, stderr): + self._DoTestFile('327_assume_size_ok.dts', allow_missing=True, + allow_fake_blobs=True) + err = stderr.getvalue() + self.assertRegex( + err, + "Image '.*' has faked external blobs and is non-functional: .*") + + def test_assume_size_no_fake(self): + """Test handling of the assume-size where it fits OK""" + with test_util.capture_sys_output() as (stdout, stderr): + self._DoTestFile('327_assume_size_ok.dts', allow_missing=True) + err = stderr.getvalue() + self.assertRegex( + err, + "Image '.*' is missing external blobs and is non-functional: .*") + + if __name__ == "__main__": unittest.main()
tools/binman/test/326_assume_size.dts new file +16 -0
@@ -0,0 +1,16 @@ +// SPDX-License-Identifier: GPL-2.0+ + +/dts-v1/; + +/ { + #address-cells = <1>; + #size-cells = <1>; + + binman { + size = <9>; + blob-ext { + filename = "assume_blob"; + assume-size = <10>; + }; + }; +};
tools/binman/test/327_assume_size_ok.dts new file +16 -0
@@ -0,0 +1,16 @@ +// SPDX-License-Identifier: GPL-2.0+ + +/dts-v1/; + +/ { + #address-cells = <1>; + #size-cells = <1>; + + binman { + size = <10>; + blob-ext { + filename = "assume_blob"; + assume-size = <10>; + }; + }; +};
Signature · 1 line
2.34.1
PATCH v3 2/18 binman: Make Intel ME default to position 0x1000
In reply to Simon GlassThis cannot ever go at offset 0 since the descriptor is there. Use a better offset for the ME, as used by link and coral, for example.
This matters when we start using assumed sizes for missing blobs.
---
(no changes since v1)
tools/binman/etype/intel_descriptor.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/binman/etype/intel_descriptor.py +1 -1
@@ -59,7 +59,7 @@ class Entry_intel_descriptor(Entry_blob_ext): if self.missing: # Return zero offsets so that these entries get placed somewhere if self.HasSibling('intel-me'): - info['intel-me'] = [0, None] + info['intel-me'] = [0x1000, None] return info offset = self.data.find(FD_SIGNATURE) if offset == -1:
Signature · 1 line
2.34.1
PATCH v3 3/18 mkeficapsule: Add a --version argument
In reply to Simon GlassTools should have an option to obtain the version, so add this to the mkeficapsule tool.
---
(no changes since v1)
doc/mkeficapsule.1 | 4 ++++ tools/mkeficapsule.c | 8 +++++++- 2 files changed, 11 insertions(+), 1 deletion(-)
doc/mkeficapsule.1 +4 -0
@@ -87,6 +87,10 @@ Generate a firmware revert empty capsule .BI "-o\fR,\fB --capoemflag " Capsule OEM flag, value between 0x0000 to 0xffff +.TP +.BR -V ", " --version +Print version information and exit. + .TP .BR -h ", " --help Print a help message
tools/mkeficapsule.c +7 -1
@@ -21,6 +21,8 @@#include <gnutls/pkcs7.h> #include <gnutls/abstract.h> +#include <version.h> +#include "eficapsule.h" static const char *tool_name ="mkeficapsule" ;
@@ -28,7 +30,7 @@ static const char *tool_name = "mkeficapsule";efi_guid_t efi_guid_fm_capsule =EFI_FIRMWARE_MANAGEMENT_CAPSULE_ID_GUID ;efi_guid_t efi_guid_cert_type_pkcs7 =EFI_CERT_TYPE_PKCS7_GUID ; -static const char *opts_short ="g:i:I:v:p:c:m:o:dhARD" ; +static const char *opts_short ="g:i:I:v:p:c:m:o:dhARDV" ;enum {CAPSULE_NORMAL_BLOB =0 ,
@@ -70,6 +72,7 @@ static void print_usage(void)"\t-R, --fw-revert firmware revert capsule, takes no GUID, no image blob\n" "\t-o, --capoemflag Capsule OEM Flag, an integer between 0x0000 and 0xffff\n" "\t-D, --dump-capsule dump the contents of the capsule headers\n" +"\t-V, --version show version number\n" "\t-h, --help print a help message\n" , tool_name); }
@@ -969,6 +972,9 @@ int main(int argc, char **argv)case 'D' : capsule_dump = true;break ; +case 'V' : +printf ("mkeficapsule version %s\n" ,PLAIN_VERSION ); +exit (EXIT_SUCCESS );default :print_usage ();exit (EXIT_SUCCESS );
Signature · 1 line
2.34.1
Re: [PATCH v3 03/18] mkeficapsule: Add a --version argument
Quoted 69 lines · Simon Glass
Tools should have an option to obtain the version, so add this to the mkeficapsule tool.
Signed-off-by Simon Glass <[email protected]>---
(no changes since v1)
doc/mkeficapsule.1 | 4 ++++ tools/mkeficapsule.c | 8 +++++++- 2 files changed, 11 insertions(+), 1 deletion(-)doc/mkeficapsule.1 +4
-0@@ -87,6 +87,10 @@ Generate a firmware revert empty capsule .BI "-o\fR,\fB --capoemflag " Capsule OEM flag, value between 0x0000 to 0xffff +.TP +.BR -V ", " --version +Print version information and exit. + .TP .BR -h ", " --help Print a help messagetools/mkeficapsule.c +7
-2@@ -21,6 +21,8 @@#include <gnutls/pkcs7.h> #include <gnutls/abstract.h> +#include <version.h> +#include "eficapsule.h" static const char *tool_name ="mkeficapsule" ;@@ -28,7 +30,7 @@ static const char *tool_name = "mkeficapsule";efi_guid_t efi_guid_fm_capsule =EFI_FIRMWARE_MANAGEMENT_CAPSULE_ID_GUID ;efi_guid_t efi_guid_cert_type_pkcs7 =EFI_CERT_TYPE_PKCS7_GUID ; -static const char *opts_short ="g:i:I:v:p:c:m:o:dhARD" ; +static const char *opts_short ="g:i:I:v:p:c:m:o:dhARDV" ;enum {CAPSULE_NORMAL_BLOB =0 ,@@ -70,6 +72,7 @@ static void print_usage(void)"\t-R, --fw-revert firmware revert capsule, takes no GUID, no image blob\n" "\t-o, --capoemflag Capsule OEM Flag, an integer between 0x0000 and 0xffff\n" "\t-D, --dump-capsule dump the contents of the capsule headers\n" +"\t-V, --version show version number\n" "\t-h, --help print a help message\n" , tool_name); }@@ -969,6 +972,9 @@ int main(int argc, char **argv)case 'D' : capsule_dump = true;break ; +case 'V' : +printf ("mkeficapsule version %s\n" ,PLAIN_VERSION ); +exit (EXIT_SUCCESS );default :print_usage ();exit (EXIT_SUCCESS ); --
Quoted 2 lines
2.34.1
PATCH v3 4/18 binman: Collect the version number for mkeficapsule
In reply to Simon GlassNow that this tool has a version number, collect it.
---
(no changes since v1)
tools/binman/btool/mkeficapsule.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
tools/binman/btool/mkeficapsule.py +2 -1
@@ -33,7 +33,8 @@ class Bintoolmkeficapsule(bintool.Bintool): commandline, or through a config file. """ def __init__(self, name): - super().__init__(name, 'mkeficapsule tool for generating capsules') + super().__init__(name, 'mkeficapsule tool for generating capsules', + r'mkeficapsule version (.*)') def generate_capsule(self, image_index, image_guid, hardware_instance, payload, output_fname, priv_key, pub_key,
Signature · 1 line
2.34.1
PATCH v3 5/18 binman: Deal with mkeficapsule being missing
In reply to Simon GlassTools cannot be assumed to be present. Add a check for this with the mkeficpasule tool.
---
(no changes since v1)
tools/binman/etype/efi_capsule.py | 4 ++++ 1 file changed, 4 insertions(+)
tools/binman/etype/efi_capsule.py +4 -0
@@ -150,6 +150,10 @@ class Entry_efi_capsule(Entry_section): if ret is not None: os.remove(payload) return tools.read_file(capsule_fname) + else: + # Bintool is missing; just use the input data as the output + self.record_missing_bintool(self.mkeficapsule) + return data def AddBintools(self, btools): self.mkeficapsule = self.AddBintool(btools, 'mkeficapsule')
Signature · 1 line
2.34.1
PATCH v3 6/18 binman: Return failure when a usage() message is generated
In reply to Simon GlassThe tool must return an error code when invalid arguments are provided, otherwise binman has no way of knowing that anything went wrong.
Correct this.
---
(no changes since v1)
tools/mkeficapsule.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/mkeficapsule.c +1 -1
@@ -977,7 +977,7 @@ int main(int argc, char **argv)exit (EXIT_SUCCESS );default :print_usage (); -exit (EXIT_SUCCESS ); +exit (EXIT_FAILURE ); } }
Signature · 1 line
2.34.1
PATCH v3 7/18 binman: Keep the efi_capsule input file
In reply to Simon GlassThere is no need to remove input files. It makes it harder to diagnose failures. Keep the payload file.
There is no test for this condition, but one could be added.
---
(no changes since v1)
tools/binman/etype/efi_capsule.py | 1 - 1 file changed, 1 deletion(-)
tools/binman/etype/efi_capsule.py +0 -1
@@ -148,7 +148,6 @@ class Entry_efi_capsule(Entry_section): self.fw_version, self.oem_flags) if ret is not None: - os.remove(payload) return tools.read_file(capsule_fname) else: # Bintool is missing; just use the input data as the output
Signature · 1 line
2.34.1
Re: [PATCH v3 07/18] binman: Keep the efi_capsule input file
Quoted 9 lines · Simon Glass
There is no need to remove input files. It makes it harder to diagnose failures. Keep the payload file.
There is no test for this condition, but one could be added.
Signed-off-by Simon Glass <[email protected]>Fixes b617611b27a ("binman: capsule: Add support for generating...")---
Although I don't think this warrants a Fixes tag. It is not fixing any issue as such.
-sughosh
Quoted 21 lines
(no changes since v1)
tools/binman/etype/efi_capsule.py | 1 - 1 file changed, 1 deletion(-)tools/binman/etype/efi_capsule.py +0
-2@@ -148,7 +148,6 @@ class Entry_efi_capsule(Entry_section): self.fw_version, self.oem_flags) if ret is not None: - os.remove(payload) return tools.read_file(capsule_fname) else: # Bintool is missing; just use the input data as the output --2.34.1
Re: [PATCH v3 07/18] binman: Keep the efi_capsule input file
Hi Sughosh,
Quoted 8 lines · Sughosh Ganu
Quoted 6 lines · Simon Glass
There is no need to remove input files. It makes it harder to diagnose failures. Keep the payload file.
There is no test for this condition, but one could be added.
Quoted 8 lines
Quoted 3 lines
Signed-off-by Simon Glass <[email protected]>Fixes b617611b27a ("binman: capsule: Add support for generating...")---
Acked-by Sughosh Ganu <[email protected]>Although I don't think this warrants a Fixes tag. It is not fixing any issue as such.
I'm OK to drop it if you like. Binman is designed to keep its intermittent files in the output dir. We have talked about having a separate dir for 'intermediate' files to avoid cluttering the output dir, but have not done this yet.
Regards,
Simon
Quoted 24 lines
-sughosh
Quoted 21 lines
(no changes since v1)
tools/binman/etype/efi_capsule.py | 1 - 1 file changed, 1 deletion(-)tools/binman/etype/efi_capsule.py +0
-2@@ -148,7 +148,6 @@ class Entry_efi_capsule(Entry_section): self.fw_version, self.oem_flags) if ret is not None: - os.remove(payload) return tools.read_file(capsule_fname) else: # Bintool is missing; just use the input data as the output --2.34.1
PATCH v3 8/18 x86: Set up some assumed sizes for binary blobs
In reply to Simon GlassAdd assumed sizes so that Binman can check that the U-Boot binaries do not grow too large.
---
(no changes since v1)
arch/x86/dts/u-boot.dtsi | 5 +++++ 1 file changed, 5 insertions(+)
arch/x86/dts/u-boot.dtsi +5 -0
@@ -24,9 +24,11 @@ #ifdef CONFIG_HAVE_INTEL_ME intel-descriptor { filename = CONFIG_FLASH_DESCRIPTOR_FILE; + assume-size = <0x1000>; }; intel-me { filename = CONFIG_INTEL_ME_FILE; + assume-size = <0x1ff000>; }; #endif #ifdef CONFIG_TPL
@@ -87,6 +89,7 @@ #ifdef CONFIG_HAVE_MRC intel-mrc { offset = <CFG_X86_MRC_ADDR>; + assume-size = <0x2fc94>; }; #endif #ifdef CONFIG_FSP_VERSION1
@@ -98,6 +101,7 @@ #ifdef CONFIG_FSP_VERSION2 intel-descriptor { filename = CONFIG_FLASH_DESCRIPTOR_FILE; + assume-size = <4096>; }; intel-ifwi { filename = CONFIG_IFWI_INPUT_FILE;
@@ -139,6 +143,7 @@ intel-vga { filename = CONFIG_VGA_BIOS_FILE; offset = <CONFIG_VGA_BIOS_ADDR>; + assume-size = <0x10000>; }; #endif #ifdef CONFIG_HAVE_VBT
Signature · 1 line
2.34.1
PATCH v3 9/18 nvidia: nyan-big: Disable debug UART
In reply to Simon GlassThis cannot be enabled early in boot since some other init is needed. At this point it is unclear exactly what init is needed, so disable the debug UART to avoid a hang.
---
(no changes since v1)
configs/nyan-big_defconfig | 1 - 1 file changed, 1 deletion(-)
configs/nyan-big_defconfig +0 -1
@@ -17,7 +17,6 @@ CONFIG_TEGRA124=y CONFIG_TARGET_NYAN_BIG=y CONFIG_TEGRA_GPU=y CONFIG_SYS_LOAD_ADDR=0x82408000 -CONFIG_DEBUG_UART=y CONFIG_FIT=y CONFIG_FIT_BEST_MATCH=y CONFIG_BOOTSTAGE=y
Signature · 1 line
2.34.1
PATCH v3 10/18 tpm: Avoid code bloat when not using EFI_TCG2_PROTOCOL
In reply to Simon GlassIt does not make sense to enable all SHA algorithms unless they are needed. It bloats the code and in this case, causes chromebook_link to fail to build. That board does use the TPM, but not with measured boot, nor EFI.
Since EFI_TCG2_PROTOCOL already selects these options, we just need to add them to MEASURED_BOOT as well.
Note that the original commit combines refactoring and new features, which makes it hard to see what is going on.
---
(no changes since v2)
Changes in v2:
- Put the conditions under EFI_TCG2_PROTOCOL
- Consider MEASURED_BOOT too
boot/Kconfig | 4 ++++ lib/Kconfig | 4 ---- 2 files changed, 4 insertions(+), 4 deletions(-)
boot/Kconfig +4 -0
@@ -734,6 +734,10 @@ config LEGACY_IMAGE_FORMAT config MEASURED_BOOT bool "Measure boot images and configuration when booting without EFI" depends on HASH && TPM_V2 + select SHA1 + select SHA256 + select SHA384 + select SHA512 help This option enables measurement of the boot process when booting without UEFI . Measurement involves creating cryptographic hashes
lib/Kconfig +0 -4
@@ -438,10 +438,6 @@ config TPM bool "Trusted Platform Module (TPM) Support" depends on DM imply DM_RNG - select SHA1 - select SHA256 - select SHA384 - select SHA512 help This enables support for TPMs which can be used to provide security features for your board. The TPM can be connected via LPC or I2C
Signature · 1 line
2.34.1
Re: [PATCH v3 10/18] tpm: Avoid code bloat when not using EFI_TCG2_PROTOCOL
Hi Simon,
Quoted 12 lines · Simon Glass
It does not make sense to enable all SHA algorithms unless they are needed. It bloats the code and in this case, causes
chromebook_linkto fail to build. That board does use the TPM, but not with measured boot, nor EFI.Since
EFI_TCG2_PROTOCOLalready selects these options, we just need to add them toMEASURED_BOOTas well.Note that the original commit combines refactoring and new features, which makes it hard to see what is going on.
Quoted 6 lines
Fixes 97707f12fda tpm: Support boot measurementsReviewed-by Heinrich Schuchardt <[email protected]>Signed-off-by Simon Glass <[email protected]>---
(no changes since v2)
There was a discussion in the previous version, bout enabling these on CMD_TPM as they are required.
Thanks
/Ilias
Quoted 42 lines
Changes in v2:
- Put the conditions underEFI_TCG2_PROTOCOL
- ConsiderMEASURED_BOOTtooboot/Kconfig | 4 ++++ lib/Kconfig | 4 ---- 2 files changed, 4 insertions(+), 4 deletions(-)boot/Kconfig +4
-0@@ -734,6 +734,10 @@ config LEGACY_IMAGE_FORMAT config MEASURED_BOOT bool "Measure boot images and configuration when booting without EFI" depends on HASH && TPM_V2 + select SHA1 + select SHA256 + select SHA384 + select SHA512 help This option enables measurement of the boot process when booting without UEFI . Measurement involves creating cryptographic hasheslib/Kconfig +0
-5@@ -438,10 +438,6 @@ config TPM bool "Trusted Platform Module (TPM) Support" depends on DM imply DM_RNG - select SHA1 - select SHA256 - select SHA384 - select SHA512 help This enables support for TPMs which can be used to provide security features for your board. The TPM can be connected via LPC or I2C --2.34.1
Re: [PATCH v3 10/18] tpm: Avoid code bloat when not using EFI_TCG2_PROTOCOL
Quoted 21 lines · Ilias Apalodimas
Hi Simon,
Quoted 17 lines · Simon Glass
It does not make sense to enable all SHA algorithms unless they are needed. It bloats the code and in this case, causes
chromebook_linkto fail to build. That board does use the TPM, but not with measured boot, nor EFI.Since
EFI_TCG2_PROTOCOLalready selects these options, we just need to add them toMEASURED_BOOTas well.Note that the original commit combines refactoring and new features, which makes it hard to see what is going on.
Fixes 97707f12fda tpm: Support boot measurementsReviewed-by Heinrich Schuchardt <[email protected]>Signed-off-by Simon Glass <[email protected]>---
Quoted 4 lines
Quoted 1 line
(no changes since v2)
There was a discussion in the previous version, bout enabling these on
CMD_TPMas they are required.
Or switch this to an imply instead so you can disable it ?
Regards
/Ilias
Quoted 5 lines
Thanks
/IliasQuoted 1 line
Re: [PATCH v3 10/18] tpm: Avoid code bloat when not using EFI_TCG2_PROTOCOL
Hi Ilias,
Quoted 24 lines · Ilias Apalodimas
Quoted 21 lines · Ilias Apalodimas
Hi Simon,
Quoted 17 lines · Simon Glass
It does not make sense to enable all SHA algorithms unless they are needed. It bloats the code and in this case, causes
chromebook_linkto fail to build. That board does use the TPM, but not with measured boot, nor EFI.Since
EFI_TCG2_PROTOCOLalready selects these options, we just need to add them toMEASURED_BOOTas well.Note that the original commit combines refactoring and new features, which makes it hard to see what is going on.
Fixes 97707f12fda tpm: Support boot measurementsReviewed-by Heinrich Schuchardt <[email protected]>Signed-off-by Simon Glass <[email protected]>---
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
(no changes since v2)
There was a discussion in the previous version, bout enabling these on
CMD_TPMas they are required.
For reference [1]
Quoted 2 lines
Or switch this to an imply instead so you can disable it ?
The thing is, we need to be able to easily disable unwanted features. My reading of that thread is that U-Boot doesn't use SHA384/512 from the 'tpm2 pcr_extend' command today. Even if it did, I would think it better to allow the supported algorithms to be controlled. At worst, I would expect a separate option to disable that subcommand which would remove the implies.
Some tpm code recently added puts a table and some functions in tpm-v2.h - could someone fix that? tpm-common.c would be a better place. Also we already have a list of hash algorithms in U-Boot (common/hash.c) so should use that, and respect the fact that certain algos may not be supported.
If there is a requirement that (for a certain situation / protocol) we need to support everything, then let's have a Kconfig for that. It is what my patch was trying to work around, perhaps. For boards which don't care about extending TPM in this way, or don't use the more expensive algorithms, it avoids lots of code bloat.
One of the principles of U-Boot is to allow configurability in these situations. It shouldn't be too hard to have the best of both worlds (supports all reasonable cases by default / allow unwanted cases to be dropped).
So I'll await your reply on the above before figuring out where to go with this. For this release I'd just like to get the board working, but I understand that the TPM stuff is very-much in flux, perhaps in -next.
Regards,
Simon
[1] https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
Re: [PATCH v3 10/18] tpm: Avoid code bloat when not using EFI_TCG2_PROTOCOL
Hi Simon,
Quoted 34 lines · Simon Glass
Hi Ilias,
Quoted 24 lines · Ilias Apalodimas
Quoted 21 lines · Ilias Apalodimas
Hi Simon,
Quoted 17 lines · Simon Glass
It does not make sense to enable all SHA algorithms unless they are needed. It bloats the code and in this case, causes
chromebook_linkto fail to build. That board does use the TPM, but not with measured boot, nor EFI.Since
EFI_TCG2_PROTOCOLalready selects these options, we just need to add them toMEASURED_BOOTas well.Note that the original commit combines refactoring and new features, which makes it hard to see what is going on.
Fixes 97707f12fda tpm: Support boot measurementsReviewed-by Heinrich Schuchardt <[email protected]>Signed-off-by Simon Glass <[email protected]>---
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
(no changes since v2)
There was a discussion in the previous version, bout enabling these on
CMD_TPMas they are required.
Quoted 8 lines
For reference [1]
Quoted 2 lines
Or switch this to an imply instead so you can disable it ?
The thing is, we need to be able to easily disable unwanted features. My reading of that thread is that U-Boot doesn't use SHA384/512 from the 'tpm2
pcr_extend' command today.
It does, it was mentioned on the thread you referenced. commit 89aa8463cdf39 ("tpm-v2: allow algorithm name to be configured for pcr_read and pcr_extend")
Quoted 4 lines
Even if it did, I would think it
better to allow the supported algorithms to be controlled. At worst, I would expect a separate option to disable that subcommand which would remove the implies.
To control the algos you need to compile, you need to control the algorithms the TPM supports. Otherwise, you are leaving security holes. We don't configure the supported PCR banks today iirc.
If we need the fix for those platforms for the release so badly, why don't we just disable the TPM? It's going to be useless and potentially dangerous without SHA support. Any idea why those platforms use it for?
Quoted 4 lines
Some tpm code recently added puts a table and some functions in
tpm-v2.h- could someone fix that?tpm-common.cwould be a better place.
Do you mean commit 954b95e77ef0a8? If that's the one, I don't mind moving it there.
Those values though are described in [0], which is primarily for v2.0. Nothing prevents you from using it in v1.2 but all of the values apart from SHA1 are useless. Also, we don't support measured boot with 1.2 anyway so I didn't see the point back then.
Quoted 3 lines
Also we already have a list of hash algorithms in U-Boot (
common/hash.c) so should use that, >and respect the fact that certain algos may not be supported.
That seems tailored for a very specific reason. Do you want to fill it in with EFI internal definitions?
We could adjust some lookup functions which seems common.
Quoted 3 lines
If there is a requirement that (for a certain situation / protocol) we need to support everything, then let's have a
Kconfigfor that.
We do. The difference here is that the *TPM at runtime* dictates what you need. So you can't blindly disable stuff.
Quoted 4 lines
It is
what my patch was trying to work around, perhaps. For boards which don't care about extending TPM in this way, or don't use the more expensive algorithms, it avoids lots of code bloat.
Ok, I disagree here. That's potentially dangerous. Because someone, might need the TPM, easily misconfigure it, and end up with broken measurements.
Quoted 5 lines
One of the principles of U-Boot is to allow configurability in these situations. It shouldn't be too hard to have the best of both worlds (supports all reasonable cases by default / allow unwanted cases to be dropped).
It's not. We can have the TPM configure the supported algorithms once it starts. IMHO that's the proper way to do it. Everything else is just papering over the problem -- which even worse no one will care to fix.
Quoted 5 lines
So I'll await your reply on the above before figuring out where to go with this. For this release I'd just like to get the board working, but I understand that the TPM stuff is very-much in flux, perhaps in -next.
This is a very complex problem. Even if we configure the TPMs banks based on the supported algoriths, a previous stage loader might have enabled more. So you end up breaking that in that case...
Let me see if I can configure the TPM on boot....
Cheers
/Ilias
Quoted 5 lines
Regards,
Simon[1] https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
[0] https://trustedcomputinggroup.org/wp-content/uploads/EFI-Protocol-Specification-rev13-160330final.pdf
-- search for EFI_TCG2_BOOT_HASH_ALG_SHA512
Re: [PATCH v3 10/18] tpm: Avoid code bloat when not using EFI_TCG2_PROTOCOL
Hi Ilias,
Quoted 117 lines · Ilias Apalodimas
Hi Simon,
Quoted 34 lines · Simon Glass
Hi Ilias,
Quoted 24 lines · Ilias Apalodimas
Quoted 21 lines · Ilias Apalodimas
Hi Simon,
Quoted 17 lines · Simon Glass
It does not make sense to enable all SHA algorithms unless they are needed. It bloats the code and in this case, causes
chromebook_linkto fail to build. That board does use the TPM, but not with measured boot, nor EFI.Since
EFI_TCG2_PROTOCOLalready selects these options, we just need to add them toMEASURED_BOOTas well.Note that the original commit combines refactoring and new features, which makes it hard to see what is going on.
Fixes 97707f12fda tpm: Support boot measurementsReviewed-by Heinrich Schuchardt <[email protected]>Signed-off-by Simon Glass <[email protected]>---
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
(no changes since v2)
There was a discussion in the previous version, bout enabling these on
CMD_TPMas they are required.Quoted 8 lines
For reference [1]
Quoted 2 lines
Or switch this to an imply instead so you can disable it ?
The thing is, we need to be able to easily disable unwanted features. My reading of that thread is that U-Boot doesn't use SHA384/512 from the 'tpm2
pcr_extend' command today.It does, it was mentioned on the thread you referenced. commit
89aa8463cdf39("tpm-v2: allow algorithm name to be configured forpcr_readandpcr_extend")Quoted 4 lines
Even if it did, I would think it
better to allow the supported algorithms to be controlled. At worst, I would expect a separate option to disable that subcommand which would remove the implies.To control the algos you need to compile, you need to control the algorithms the TPM supports. Otherwise, you are leaving security holes. We don't configure the supported PCR banks today iirc.
If we need the fix for those platforms for the release so badly, why don't we just disable the TPM? It's going to be useless and potentially dangerous without SHA support. Any idea why those platforms use it for?
Quoted 4 lines
Some tpm code recently added puts a table and some functions in
tpm-v2.h- could someone fix that?tpm-common.cwould be a better place.Do you mean commit
954b95e77ef0a8? If that's the one, I don't mind moving it there.
Those values though are described in [0], which is primarily for v2.0. Nothing prevents you from using it in v1.2 but all of the values apart from SHA1 are useless. Also, we don't support measured boot with 1.2 anyway so I didn't see the point back then.Quoted 3 lines
Also we already have a list of hash algorithms in U-Boot (
common/hash.c) so should use that, >and respect the fact that certain algos may not be supported.That seems tailored for a very specific reason. Do you want to fill it in with EFI internal definitions?
We could adjust some lookup functions which seems common.Quoted 3 lines
If there is a requirement that (for a certain situation / protocol) we need to support everything, then let's have a
Kconfigfor that.We do. The difference here is that the *TPM at runtime* dictates what you need. So you can't blindly disable stuff.
Quoted 4 lines
It is
what my patch was trying to work around, perhaps. For boards which don't care about extending TPM in this way, or don't use the more expensive algorithms, it avoids lots of code bloat.Ok, I disagree here. That's potentially dangerous. Because someone, might need the TPM, easily misconfigure it, and end up with broken measurements.
Quoted 5 lines
One of the principles of U-Boot is to allow configurability in these situations. It shouldn't be too hard to have the best of both worlds (supports all reasonable cases by default / allow unwanted cases to be dropped).
It's not. We can have the TPM configure the supported algorithms once it starts. IMHO that's the proper way to do it. Everything else is just papering over the problem -- which even worse no one will care to fix.
Quoted 5 lines
So I'll await your reply on the above before figuring out where to go with this. For this release I'd just like to get the board working, but I understand that the TPM stuff is very-much in flux, perhaps in -next.
Quoted 5 lines
This is a very complex problem. Even if we configure the TPMs banks based on the supported algoriths, a previous stage loader might have enabled more. So you end up breaking that in that case...
Let me see if I can configure the TPM on boot....
I just don't understand any of this very well.
My request is, please can you find a way to allow the TPM to be enabled for a board that doesn't use the pcr_extend subcommand with SHA384/512? I just want to get that 5KB back for this board. I'm happy with the defaults being a certain way, just not wanting to require this code for boards which don't need it.
Regards,
Simon
Quoted 11 lines
Cheers
/IliasQuoted 5 lines
Regards,
Simon[1] https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
[0] https://trustedcomputinggroup.org/wp-content/uploads/EFI-Protocol-Specification-rev13-160330final.pdf
-- search forEFI_TCG2_BOOT_HASH_ALG_SHA512
PATCH v3 11/18 rockchip: veyron: Add logging for power init
In reply to Simon GlassAdd better logging for power init so that CONFIG_LOG_ERROR_RETURN can be enabled.
---
(no changes since v2)
Changes in v2:
- Remove the superfluous if() and drop the debug() as well
board/google/veyron/veyron.c | 30 ++++++++++++------------------ 1 file changed, 12 insertions(+), 18 deletions(-)
board/google/veyron/veyron.c +12 -18
@@ -29,44 +29,38 @@ static int veyron_init(void)int ret; ret =regulator_get_by_platname ("vdd_arm" , &dev); -if (ret) { -debug ("Cannot set regulator name\n" ); -return ret; - } +if (ret) +return log_msg_ret ("vdd" , ret);/* Slowly raise to max CPU voltage to prevent overshoot */ ret =regulator_set_value (dev,1200000 );if (ret) -return ret; +return log_msg_ret ("s12" , ret);udelay (175 );/* Must wait for voltage to stabilize, 2mV/us */ ret =regulator_set_value (dev,1400000 );if (ret) -return ret; +return log_msg_ret ("s14" , ret);udelay (100 );/* Must wait for voltage to stabilize, 2mV/us */ ret =rockchip_get_clk (&clk.dev);if (ret) -return ret; +return log_msg_ret ("clk" , ret); clk.id =PLL_APLL ; ret =clk_set_rate (&clk,1800000000 );if (IS_ERR_VALUE (ret)) -return ret; +return log_msg_ret ("s18" , ret); ret =regulator_get_by_platname ("vcc33_sd" , &dev); -if (ret) { -debug ("Cannot get regulator name\n" ); -return ret; - } +if (ret) +return log_msg_ret ("vcc" , ret); ret =regulator_set_value (dev,3300000 );if (ret) -return ret; +return log_msg_ret ("s33" , ret); ret =regulators_enable_boot_on (false); -if (ret) { -debug ("%s: Cannot enable boot on regulators\n" , __func__); -return ret; - } +if (ret) +return log_msg_ret ("boo" , ret);return 0 ; }
@@ -81,7 +75,7 @@ int board_early_init_r(void)if (!fdt_node_check_compatible (gd->fdt_blob,0 ,"google,veyron" )) { ret =veyron_init ();if (ret) -return ret; +return log_msg_ret ("vey" , ret); }#endif /*
Signature · 1 line
2.34.1
PATCH v3 12/18 power: regulator: Handle autoset in regulators_enable_boot_on()
In reply to Simon GlassWith a recent change, regulators_enable_boot_on() returns an error if a regulator is already set. Check for and handle this situation.
---
(no changes since v1)
drivers/power/regulator/regulator-uclass.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/power/regulator/regulator-uclass.c +1 -1
@@ -518,7 +518,7 @@ int regulators_enable_boot_on(bool verbose)dev ; uclass_next_device(&dev)) { ret =regulator_autoset (dev); -if (ret == -EMEDIUMTYPE ) { +if (ret == -EMEDIUMTYPE || ret == -EALREADY ) { ret =0 ;continue ; }
Signature · 1 line
2.34.1
PATCH v3 13/18 fdt: Correct condition for bloblist existing
In reply to Simon GlassOn some boards, the bloblist is created in SPL once SDRAM is ready. It cannot be accessed until that point, so is not available early in SPL.
Add a condition to avoid a hang in this case.
This fixes a hang in chromebook_coral
---
Changes in v3:
- Use BLOBLIST instead of OF_BLOBLIST
Changes in v2:
- Use 'phase' instead of 'stage'
lib/fdtdec.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
lib/fdtdec.c +10 -2
@@ -1669,8 +1669,16 @@ int fdtdec_setup(void) {int ret = -ENOENT ; -/* If allowing a bloblist, check that first */ -if (CONFIG_IS_ENABLED (BLOBLIST )) { +/* +* If allowing a bloblist, check that first. This would be better +* handled with an OF_BLOBLIST Kconfig, but that caused far too much +* argument, so add a hack here, used e.g. by chromebook_coral +* The necessary test is whether the previous phase passed a bloblist, +* not whether this phase creates one. +*/ +if (CONFIG_IS_ENABLED (BLOBLIST ) && + (spl_prev_phase () !=PHASE_TPL || + !IS_ENABLED (CONFIG_TPL_BLOBLIST ))) { ret =bloblist_maybe_init ();if (!ret) { gd->fdt_blob =bloblist_find (BLOBLISTT_CONTROL_FDT ,0 );
Signature · 1 line
2.34.1
PATCH v3 14/18 spl: Allow ATF to work when dcache is disabled
In reply to Simon GlassThe dcache may not be enabled in SPL. Add a check to avoid trying to use an undefined function.
---
(no changes since v1)
common/spl/spl_atf.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
common/spl/spl_atf.c +2 -1
@@ -204,7 +204,8 @@ static void __noreturn bl31_entry(uintptr_t bl31_entry, uintptr_t bl32_entry, fdt_addr);raw_write_daif (SPSR_EXCEPTION_MASK ); -dcache_disable (); +if (!CONFIG_IS_ENABLED (SYS_DCACHE_OFF )) +dcache_disable ();atf_entry (bl31_params, (void *)fdt_addr); }
Signature · 1 line
2.34.1
PATCH v3 15/18 rockchip: Ensure memory size is available in RK3399 SPL
In reply to Simon GlassAt present gd->ram_size is 0 in SPL, meaning that it is not possible to enable the cache. Correct this by always populating the RAM size correctly.
This increases code size by about 500 bytes in SPL, since it must call the rather large rockchip_sdram_size() function.
---
Changes in v3:
- Cut the patch down to bare bones
Changes in v2:
- Add new patch to correct memory size in SPL
drivers/ram/rockchip/sdram_rk3399.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/ram/rockchip/sdram_rk3399.c +4 -4
@@ -3142,19 +3142,19 @@ static int rk3399_dmc_init(struct udevice *dev)static int rk3399_dmc_probe (struct udevice *dev) { +struct dram_info *priv =dev_get_priv (dev); +#if defined(CONFIG_TPL_BUILD ) || \ (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD ))if (rk3399_dmc_init (dev))return 0 ; -#else -struct dram_info *priv =dev_get_priv (dev); - +#endif priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF );debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); priv->info.base =CFG_SYS_SDRAM_BASE ; priv->info.size =rockchip_sdram_size ((phys_addr_t)&priv->pmugrf->os_reg2); -#endif +return 0 ; }
Signature · 1 line
2.34.1
PATCH v3 16/18 rockchip: Avoid #ifdefs in RK3399 SPL
In reply to Simon GlassThe code here is confusing due to large blocks which are #ifdefed out. Add a function phase_sdram_init() which returns whether SDRAM init should happen in the current phase, using that as needed to control the code flow.
This increases code size by about 500 bytes in SPL when the cache is on, since it must call the rather large rockchip_sdram_size() function.
---
Changes in v3:
- Split out the refactoring into a separate patch
- Drop the non-dcache optimisation, since the cache should normally be on
drivers/ram/rockchip/sdram_rk3399.c | 47 ++++++++++++++++------------- 1 file changed, 26 insertions(+), 21 deletions(-)
drivers/ram/rockchip/sdram_rk3399.c +26 -21
@@ -13,6 +13,7 @@#include <log.h> #include <ram.h> #include <regmap.h> +#include <spl.h> #include <syscon.h> #include <asm/arch-rockchip/clock.h> #include <asm/arch-rockchip/cru.h>
@@ -63,8 +64,6 @@ struct chan_info { };struct dram_info { -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD ))u32 pwrup_srefresh_exit[2 ];struct chan_info chan[2 ];struct clk ddr_clk;
@@ -75,7 +74,6 @@ struct dram_info {struct rk3399_pmusgrf_regs *pmusgrf;struct rk3399_ddr_cic_regs *cic;const struct sdram_rk3399_ops *ops; -#endif struct ram_info info;struct rk3399_pmugrf_regs *pmugrf; };
@@ -92,9 +90,6 @@ struct sdram_rk3399_ops { struct rk3399_sdram_params *params); }; -#if defined(CONFIG_TPL_BUILD) || \ - (!defined(CONFIG_TPL) && defined(CONFIG_SPL_BUILD)) -struct rockchip_dmc_plat {#if CONFIG_IS_ENABLED (OF_PLATDATA )struct dtd_rockchip_rk3399_dmc dtplat;
@@ -191,6 +186,17 @@ struct io_setting { }, }; +/** +* phase_sdram_init() - Check if this is the phase where SDRAM init happens +* +* Returns: true to do SDRAM init in this phase, false to not +*/ +static bool phase_sdram_init (void ) +{ +return spl_phase () ==PHASE_TPL || + (!IS_ENABLED (CONFIG_TPL ) && !spl_in_proper ()); +} +static struct io_setting *lpddr4_get_io_settings (const struct rk3399_sdram_params *params,u32 mr5) {
@@ -3024,7 +3030,7 @@ static int rk3399_dmc_of_to_plat(struct udevice *dev)struct rockchip_dmc_plat *plat =dev_get_plat (dev);int ret; -if (!CONFIG_IS_ENABLED (OF_REAL )) +if (!CONFIG_IS_ENABLED (OF_REAL ) || !phase_sdram_init ())return 0 ; ret = dev_read_u32_array(dev, "rockchip,sdram-params",
@@ -3138,22 +3144,24 @@ static int rk3399_dmc_init(struct udevice *dev)return 0 ; } -#endif static int rk3399_dmc_probe (struct udevice *dev) {struct dram_info *priv =dev_get_priv (dev); -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD )) -if (rk3399_dmc_init (dev)) -return 0 ; -#endif - priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); -debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); - priv->info.base =CFG_SYS_SDRAM_BASE ; - priv->info.size = -rockchip_sdram_size ((phys_addr_t)&priv->pmugrf->os_reg2); +if (phase_sdram_init ()) { +if (rk3399_dmc_init (dev)) +return 0 ; + }else { + priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); +debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); + } + +if (!CONFIG_IS_ENABLED (SYS_DCACHE_OFF )) { + priv->info.base =CFG_SYS_SDRAM_BASE ; + priv->info.size = +rockchip_sdram_size ((ulong)&priv->pmugrf->os_reg2); + }return 0 ; }
@@ -3181,10 +3189,7 @@ U_BOOT_DRIVER(dmc_rk3399) = { .id = UCLASS_RAM, .of_match = rk3399_dmc_ids, .ops = &rk3399_dmc_ops, -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD )) .of_to_plat = rk3399_dmc_of_to_plat, -#endif .probe = rk3399_dmc_probe, .priv_auto = sizeof(struct dram_info), #if defined(CONFIG_TPL_BUILD) || \
Signature · 1 line
2.34.1
Re: [PATCH v3 16/18] rockchip: Avoid #ifdefs in RK3399 SPL
Hi Simon,
Quoted 103 lines · Simon Glass
The code here is confusing due to large blocks which are #ifdefed out. Add a function
phase_sdram_init()which returns whether SDRAM init should happen in the current phase, using that as needed to control the code flow.This increases code size by about 500 bytes in SPL when the cache is on, since it must call the rather large
rockchip_sdram_size()function.Signed-off-by Simon Glass <[email protected]>---
Changes in v3:
- Split out the refactoring into a separate patch
- Drop the non-dcache optimisation, since the cache should normally be ondrivers/ram/rockchip/sdram_rk3399.c | 47 ++++++++++++++++------------- 1 file changed, 26 insertions(+), 21 deletions(-)drivers/ram/rockchip/sdram_rk3399.c +13
-17@@ -13,6 +13,7 @@#include <log.h> #include <ram.h> #include <regmap.h> +#include <spl.h> #include <syscon.h> #include <asm/arch-rockchip/clock.h> #include <asm/arch-rockchip/cru.h> @@ -63,8 +64,6 @@ struct chan_info { };struct dram_info { -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD ))u32 pwrup_srefresh_exit[2 ];struct chan_info chan[2 ];struct clk ddr_clk;@@ -75,7 +74,6 @@ struct dram_info {struct rk3399_pmusgrf_regs *pmusgrf;struct rk3399_ddr_cic_regs *cic;const struct sdram_rk3399_ops *ops; -#endif struct ram_info info;struct rk3399_pmugrf_regs *pmugrf; };@@ -92,9 +90,6 @@ struct sdram_rk3399_ops { struct rk3399_sdram_params *params); }; -#if defined(CONFIG_TPL_BUILD) || \ - (!defined(CONFIG_TPL) && defined(CONFIG_SPL_BUILD)) -struct rockchip_dmc_plat {#if CONFIG_IS_ENABLED (OF_PLATDATA )struct dtd_rockchip_rk3399_dmc dtplat;@@ -191,6 +186,17 @@ struct io_setting { }, }; +/** +* phase_sdram_init() - Check if this is the phase where SDRAM init happens +* +* Returns: true to do SDRAM init in this phase, false to not +*/ +static bool phase_sdram_init (void ) +{ +return spl_phase () ==PHASE_TPL || + (!IS_ENABLED (CONFIG_TPL ) && !spl_in_proper ()); +} +static struct io_setting *lpddr4_get_io_settings (const struct rk3399_sdram_params *params,u32 mr5) {@@ -3024,7 +3030,7 @@ static int rk3399_dmc_of_to_plat(struct udevice *dev)struct rockchip_dmc_plat *plat =dev_get_plat (dev);int ret; -if (!CONFIG_IS_ENABLED (OF_REAL )) +if (!CONFIG_IS_ENABLED (OF_REAL ) || !phase_sdram_init ())return 0 ; ret = dev_read_u32_array(dev, "rockchip,sdram-params",@@ -3138,22 +3144,24 @@ static int rk3399_dmc_init(struct udevice *dev)return 0 ; } -#endif static int rk3399_dmc_probe (struct udevice *dev) {struct dram_info *priv =dev_get_priv (dev); -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD )) -if (rk3399_dmc_init (dev)) -return 0 ; -#endif - priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); -debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); - priv->info.base =CFG_SYS_SDRAM_BASE ; - priv->info.size =
drivers/ram/rockchip/sdram_rk3399.c static int rk3399_dmc_init(struct udevice *dev) · line 3160
Quoted 10 lines
drivers/ram/rockchip/sdram_rk3399.c +9
-1-rockchip_sdram_size ((phys_addr_t)&priv->pmugrf->os_reg2); +if (phase_sdram_init ()) { +if (rk3399_dmc_init (dev)) +return 0 ; + }else { + priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); +debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); + } + +if (!CONFIG_IS_ENABLED (SYS_DCACHE_OFF )) {
This check should be dropped, this driver intent is to initialize dram in first phase (normally TPL), and report the size to any other phase.
The main need for phase_sdram_init() and disable of DCACHE can probably be avoided if bob/kevin can move to use separate TPL and SPL instead of doing both dram init and everything else in SPL.
My best guess is that enabling of caches in SPL cause issue for bob and kevin because they only use SPL not TPL+SPL like (if I am not mistaken) all other Rockchip arm64 targets.
Using SPL-only was not something I tested when caches was enabled in SPL.
Maybe bob/kevin can be changed to also use TPL+SPL similar to all other RK3399 boards?
How U-Boot works on these chromebooks is still a mystery to me.
When coreboot is involved it would only load U-Boot proper and SPL or TPL+SPL would never be involved at all?
If I understand correctly SPL is only involved for bare metal boot, if this is the case then using TPL + back-to-brom to load SPL should probably work fine?, and would align all RK3399 boards to work in a similar way and reduce the need for special care/handling in the code.
Regards,
Jonas
Quoted 18 lines
drivers/ram/rockchip/sdram_rk3399.c +4
-3+ priv->info.base =CFG_SYS_SDRAM_BASE ; + priv->info.size = +rockchip_sdram_size ((ulong)&priv->pmugrf->os_reg2); + }return 0 ; }@@ -3181,10 +3189,7 @@ U_BOOT_DRIVER(dmc_rk3399) = { .id = UCLASS_RAM, .of_match = rk3399_dmc_ids, .ops = &rk3399_dmc_ops, -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD )) .of_to_plat = rk3399_dmc_of_to_plat, -#endif .probe = rk3399_dmc_probe, .priv_auto = sizeof(struct dram_info), #if defined(CONFIG_TPL_BUILD) || \
Re: [PATCH v3 16/18] rockchip: Avoid #ifdefs in RK3399 SPL
Hi Jonas,
Quoted 112 lines · Jonas Karlman
Hi Simon,
Quoted 108 lines · Simon Glass
The code here is confusing due to large blocks which are #ifdefed out. Add a function
phase_sdram_init()which returns whether SDRAM init should happen in the current phase, using that as needed to control the code flow.This increases code size by about 500 bytes in SPL when the cache is on, since it must call the rather large
rockchip_sdram_size()function.Signed-off-by Simon Glass <[email protected]>---
Changes in v3:
- Split out the refactoring into a separate patch
- Drop the non-dcache optimisation, since the cache should normally be ondrivers/ram/rockchip/sdram_rk3399.c | 47 ++++++++++++++++------------- 1 file changed, 26 insertions(+), 21 deletions(-)drivers/ram/rockchip/sdram_rk3399.c +17
-18@@ -13,6 +13,7 @@#include <log.h> #include <ram.h> #include <regmap.h> +#include <spl.h> #include <syscon.h> #include <asm/arch-rockchip/clock.h> #include <asm/arch-rockchip/cru.h> @@ -63,8 +64,6 @@ struct chan_info { };struct dram_info { -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD ))u32 pwrup_srefresh_exit[2 ];struct chan_info chan[2 ];struct clk ddr_clk;@@ -75,7 +74,6 @@ struct dram_info {struct rk3399_pmusgrf_regs *pmusgrf;struct rk3399_ddr_cic_regs *cic;const struct sdram_rk3399_ops *ops; -#endif struct ram_info info;struct rk3399_pmugrf_regs *pmugrf; };@@ -92,9 +90,6 @@ struct sdram_rk3399_ops { struct rk3399_sdram_params *params); }; -#if defined(CONFIG_TPL_BUILD) || \ - (!defined(CONFIG_TPL) && defined(CONFIG_SPL_BUILD)) -struct rockchip_dmc_plat {#if CONFIG_IS_ENABLED (OF_PLATDATA )struct dtd_rockchip_rk3399_dmc dtplat;@@ -191,6 +186,17 @@ struct io_setting { }, }; +/** +* phase_sdram_init() - Check if this is the phase where SDRAM init happens +* +* Returns: true to do SDRAM init in this phase, false to not +*/ +static bool phase_sdram_init (void ) +{ +return spl_phase () ==PHASE_TPL || + (!IS_ENABLED (CONFIG_TPL ) && !spl_in_proper ()); +} +static struct io_setting *lpddr4_get_io_settings (const struct rk3399_sdram_params *params,u32 mr5) {@@ -3024,7 +3030,7 @@ static int rk3399_dmc_of_to_plat(struct udevice *dev)struct rockchip_dmc_plat *plat =dev_get_plat (dev);int ret; -if (!CONFIG_IS_ENABLED (OF_REAL )) +if (!CONFIG_IS_ENABLED (OF_REAL ) || !phase_sdram_init ())return 0 ; ret = dev_read_u32_array(dev, "rockchip,sdram-params",@@ -3138,22 +3144,24 @@ static int rk3399_dmc_init(struct udevice *dev)return 0 ; } -#endif static int rk3399_dmc_probe (struct udevice *dev) {struct dram_info *priv =dev_get_priv (dev); -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD )) -if (rk3399_dmc_init (dev)) -return 0 ; -#endif - priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); -debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); - priv->info.base =CFG_SYS_SDRAM_BASE ; - priv->info.size = -rockchip_sdram_size ((phys_addr_t)&priv->pmugrf->os_reg2); +if (phase_sdram_init ()) { +if (rk3399_dmc_init (dev)) +return 0 ; + }else {
Quoted 8 lines
drivers/ram/rockchip/sdram_rk3399.c static int rk3399_dmc_init(struct udevice *dev) · line 3160
Quoted 5 lines
drivers/ram/rockchip/sdram_rk3399.c +5
-0+ priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); +debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); + } + +if (!CONFIG_IS_ENABLED (SYS_DCACHE_OFF )) {This check should be dropped, this driver intent is to initialize dram in first phase (normally TPL), and report the size to any other phase.
This whole patch can be dropped :-) Here I am just trying to avoid code-size growth when the cache is off. But yes, it is not needed.
Quoted 16 lines
The main need for
phase_sdram_init()and disable of DCACHE can probably be avoided if bob/kevin can move to use separate TPL and SPL instead of doing both dram init and everything else in SPL.My best guess is that enabling of caches in SPL cause issue for bob and kevin because they only use SPL not TPL+SPL like (if I am not mistaken) all other Rockchip arm64 targets.
Using SPL-only was not something I tested when caches was enabled in SPL.
Maybe bob/kevin can be changed to also use TPL+SPL similar to all other RK3399 boards?
How U-Boot works on these chromebooks is still a mystery to me.
Quoted 7 lines
When coreboot is involved it would only load U-Boot proper and SPL or TPL+SPL would never be involved at all?
If I understand correctly SPL is only involved for bare metal boot, if this is the case then using TPL + back-to-brom to load SPL should probably work fine?, and would align all RK3399 boards to work in a similar way and reduce the need for special care/handling in the code.
These boards were the first rk3399 support we had in mainline, I believe. Everything else came later but conversions were not done for these existing boards.
I actually intensely dislike the back-to-brom stuff. If the ROM had an actual API (mmc_read(), etc.) then that would be fine. But just jumping back makes it hard to control what is going on.
It is interesting to hear that SPL-only is causing a problem. Do you have any inkling of what that might be? I could take a look at converting the boards to use TPL, but it does seem a bit sideways to the issue here. Is the bootrom doing some magic, perhaps? Is there decent documentation for the boot ROM these days?
Regards,
Simon
Re: [PATCH v3 16/18] rockchip: Avoid #ifdefs in RK3399 SPL
Hi Simon,
Quoted 146 lines · Simon Glass
Hi Jonas,
Quoted 110 lines · Jonas Karlman
Hi Simon,
Quoted 107 lines · Simon Glass
The code here is confusing due to large blocks which are #ifdefed out. Add a function
phase_sdram_init()which returns whether SDRAM init should happen in the current phase, using that as needed to control the code flow.This increases code size by about 500 bytes in SPL when the cache is on, since it must call the rather large
rockchip_sdram_size()function.Signed-off-by Simon Glass <[email protected]>---
Changes in v3:
- Split out the refactoring into a separate patch
- Drop the non-dcache optimisation, since the cache should normally be ondrivers/ram/rockchip/sdram_rk3399.c | 47 ++++++++++++++++------------- 1 file changed, 26 insertions(+), 21 deletions(-)drivers/ram/rockchip/sdram_rk3399.c +16
-18@@ -13,6 +13,7 @@#include <log.h> #include <ram.h> #include <regmap.h> +#include <spl.h> #include <syscon.h> #include <asm/arch-rockchip/clock.h> #include <asm/arch-rockchip/cru.h> @@ -63,8 +64,6 @@ struct chan_info { };struct dram_info { -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD ))u32 pwrup_srefresh_exit[2 ];struct chan_info chan[2 ];struct clk ddr_clk;@@ -75,7 +74,6 @@ struct dram_info {struct rk3399_pmusgrf_regs *pmusgrf;struct rk3399_ddr_cic_regs *cic;const struct sdram_rk3399_ops *ops; -#endif struct ram_info info;struct rk3399_pmugrf_regs *pmugrf; };@@ -92,9 +90,6 @@ struct sdram_rk3399_ops { struct rk3399_sdram_params *params); }; -#if defined(CONFIG_TPL_BUILD) || \ - (!defined(CONFIG_TPL) && defined(CONFIG_SPL_BUILD)) -struct rockchip_dmc_plat {#if CONFIG_IS_ENABLED (OF_PLATDATA )struct dtd_rockchip_rk3399_dmc dtplat;@@ -191,6 +186,17 @@ struct io_setting { }, }; +/** +* phase_sdram_init() - Check if this is the phase where SDRAM init happens +* +* Returns: true to do SDRAM init in this phase, false to not +*/ +static bool phase_sdram_init (void ) +{ +return spl_phase () ==PHASE_TPL || + (!IS_ENABLED (CONFIG_TPL ) && !spl_in_proper ()); +} +static struct io_setting *lpddr4_get_io_settings (const struct rk3399_sdram_params *params,u32 mr5) {@@ -3024,7 +3030,7 @@ static int rk3399_dmc_of_to_plat(struct udevice *dev)struct rockchip_dmc_plat *plat =dev_get_plat (dev);int ret; -if (!CONFIG_IS_ENABLED (OF_REAL )) +if (!CONFIG_IS_ENABLED (OF_REAL ) || !phase_sdram_init ())return 0 ; ret = dev_read_u32_array(dev, "rockchip,sdram-params",@@ -3138,22 +3144,24 @@ static int rk3399_dmc_init(struct udevice *dev)return 0 ; } -#endif static int rk3399_dmc_probe (struct udevice *dev) {struct dram_info *priv =dev_get_priv (dev); -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD )) -if (rk3399_dmc_init (dev)) -return 0 ; -#endif - priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); -debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); - priv->info.base =CFG_SYS_SDRAM_BASE ; - priv->info.size = -rockchip_sdram_size ((phys_addr_t)&priv->pmugrf->os_reg2); +if (phase_sdram_init ()) { +if (rk3399_dmc_init (dev)) +return 0 ;Quoted 8 lines
drivers/ram/rockchip/sdram_rk3399.c static int rk3399_dmc_init(struct udevice *dev) · line 3160
Quoted 6 lines
drivers/ram/rockchip/sdram_rk3399.c +6
-0+ }else { + priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); +debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); + } + +if (!CONFIG_IS_ENABLED (SYS_DCACHE_OFF )) {This check should be dropped, this driver intent is to initialize dram in first phase (normally TPL), and report the size to any other phase.
This whole patch can be dropped :-) Here I am just trying to avoid code-size growth when the cache is off. But yes, it is not needed.
Quoted 15 lines
The main need for
phase_sdram_init()and disable of DCACHE can probably be avoided if bob/kevin can move to use separate TPL and SPL instead of doing both dram init and everything else in SPL.My best guess is that enabling of caches in SPL cause issue for bob and kevin because they only use SPL not TPL+SPL like (if I am not mistaken) all other Rockchip arm64 targets.
Using SPL-only was not something I tested when caches was enabled in SPL.
Maybe bob/kevin can be changed to also use TPL+SPL similar to all other RK3399 boards?
How U-Boot works on these chromebooks is still a mystery to me.
Quoted 7 lines
When coreboot is involved it would only load U-Boot proper and SPL or TPL+SPL would never be involved at all?
If I understand correctly SPL is only involved for bare metal boot, if this is the case then using TPL + back-to-brom to load SPL should probably work fine?, and would align all RK3399 boards to work in a similar way and reduce the need for special care/handling in the code.
Quoted 7 lines
These boards were the first rk3399 support we had in mainline, I believe. Everything else came later but conversions were not done for these existing boards.
I actually intensely dislike the back-to-brom stuff. If the ROM had an actual API (
mmc_read(), etc.) then that would be fine. But just jumping back makes it hard to control what is going on.
The logic of BootRom is very simple and very clear:
- Read image from boot medium and check the availability(format of rockchip IDB,
which is packed by the mkimage rksd/rkspi);
- Load TPL/dram init blob to the internal SRAM(size limit by the sram), and jump to the entry;
- Back to bootRom with '0' return means the dram init success, bootRom will get next image for dram;
- Read SPL image from boot medium to DDR start address(no size limit), and jump to the ddr entry;
- The signature verify will be done for all the firmware load by bootRom if the secure boot feature is enabled; This model works for all Rockchip SoCs, although some SoCs have very limit SRAM size(only available for DRAM init) and some other SoCs like rk3399 have bigger SRAM size.
Thanks,
- Kever
Quoted 8 lines
It is interesting to hear that SPL-only is causing a problem. Do you have any inkling of what that might be? I could take a look at converting the boards to use TPL, but it does seem a bit sideways to the issue here. Is the bootrom doing some magic, perhaps? Is there decent documentation for the boot ROM these days?
Regards,
Simon
Re: [PATCH v3 16/18] rockchip: Avoid #ifdefs in RK3399 SPL
Hi Kever,
Quoted 161 lines · Kever Yang
Hi Simon,
Quoted 146 lines · Simon Glass
Hi Jonas,
Quoted 110 lines · Jonas Karlman
Hi Simon,
Quoted 107 lines · Simon Glass
The code here is confusing due to large blocks which are #ifdefed out. Add a function
phase_sdram_init()which returns whether SDRAM init should happen in the current phase, using that as needed to control the code flow.This increases code size by about 500 bytes in SPL when the cache is on, since it must call the rather large
rockchip_sdram_size()function.Signed-off-by Simon Glass <[email protected]>---
Changes in v3:
- Split out the refactoring into a separate patch
- Drop the non-dcache optimisation, since the cache should normally be ondrivers/ram/rockchip/sdram_rk3399.c | 47 ++++++++++++++++------------- 1 file changed, 26 insertions(+), 21 deletions(-)drivers/ram/rockchip/sdram_rk3399.c +16
-18@@ -13,6 +13,7 @@#include <log.h> #include <ram.h> #include <regmap.h> +#include <spl.h> #include <syscon.h> #include <asm/arch-rockchip/clock.h> #include <asm/arch-rockchip/cru.h> @@ -63,8 +64,6 @@ struct chan_info { };struct dram_info { -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD ))u32 pwrup_srefresh_exit[2 ];struct chan_info chan[2 ];struct clk ddr_clk;@@ -75,7 +74,6 @@ struct dram_info {struct rk3399_pmusgrf_regs *pmusgrf;struct rk3399_ddr_cic_regs *cic;const struct sdram_rk3399_ops *ops; -#endif struct ram_info info;struct rk3399_pmugrf_regs *pmugrf; };@@ -92,9 +90,6 @@ struct sdram_rk3399_ops { struct rk3399_sdram_params *params); }; -#if defined(CONFIG_TPL_BUILD) || \ - (!defined(CONFIG_TPL) && defined(CONFIG_SPL_BUILD)) -struct rockchip_dmc_plat {#if CONFIG_IS_ENABLED (OF_PLATDATA )struct dtd_rockchip_rk3399_dmc dtplat;@@ -191,6 +186,17 @@ struct io_setting { }, }; +/** +* phase_sdram_init() - Check if this is the phase where SDRAM init happens +* +* Returns: true to do SDRAM init in this phase, false to not +*/ +static bool phase_sdram_init (void ) +{ +return spl_phase () ==PHASE_TPL || + (!IS_ENABLED (CONFIG_TPL ) && !spl_in_proper ()); +} +static struct io_setting *lpddr4_get_io_settings (const struct rk3399_sdram_params *params,u32 mr5) {@@ -3024,7 +3030,7 @@ static int rk3399_dmc_of_to_plat(struct udevice *dev)struct rockchip_dmc_plat *plat =dev_get_plat (dev);int ret; -if (!CONFIG_IS_ENABLED (OF_REAL )) +if (!CONFIG_IS_ENABLED (OF_REAL ) || !phase_sdram_init ())return 0 ; ret = dev_read_u32_array(dev, "rockchip,sdram-params",@@ -3138,22 +3144,24 @@ static int rk3399_dmc_init(struct udevice *dev)return 0 ; } -#endif static int rk3399_dmc_probe (struct udevice *dev) {struct dram_info *priv =dev_get_priv (dev); -#if defined(CONFIG_TPL_BUILD ) || \ - (!defined(CONFIG_TPL ) && defined(CONFIG_SPL_BUILD )) -if (rk3399_dmc_init (dev)) -return 0 ; -#endif - priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); -debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); - priv->info.base =CFG_SYS_SDRAM_BASE ; - priv->info.size = -rockchip_sdram_size ((phys_addr_t)&priv->pmugrf->os_reg2); +if (phase_sdram_init ()) { +if (rk3399_dmc_init (dev)) +return 0 ;Quoted 8 lines
drivers/ram/rockchip/sdram_rk3399.c static int rk3399_dmc_init(struct udevice *dev) · line 3160
Quoted 6 lines
drivers/ram/rockchip/sdram_rk3399.c +6
-0+ }else { + priv->pmugrf =syscon_get_first_range (ROCKCHIP_SYSCON_PMUGRF ); +debug ("%s: pmugrf = %p\n" , __func__, priv->pmugrf); + } + +if (!CONFIG_IS_ENABLED (SYS_DCACHE_OFF )) {This check should be dropped, this driver intent is to initialize dram in first phase (normally TPL), and report the size to any other phase.
This whole patch can be dropped :-) Here I am just trying to avoid code-size growth when the cache is off. But yes, it is not needed.
Quoted 15 lines
The main need for
phase_sdram_init()and disable of DCACHE can probably be avoided if bob/kevin can move to use separate TPL and SPL instead of doing both dram init and everything else in SPL.My best guess is that enabling of caches in SPL cause issue for bob and kevin because they only use SPL not TPL+SPL like (if I am not mistaken) all other Rockchip arm64 targets.
Using SPL-only was not something I tested when caches was enabled in SPL.
Maybe bob/kevin can be changed to also use TPL+SPL similar to all other RK3399 boards?
How U-Boot works on these chromebooks is still a mystery to me.
Quoted 7 lines
When coreboot is involved it would only load U-Boot proper and SPL or TPL+SPL would never be involved at all?
If I understand correctly SPL is only involved for bare metal boot, if this is the case then using TPL + back-to-brom to load SPL should probably work fine?, and would align all RK3399 boards to work in a similar way and reduce the need for special care/handling in the code.
Quoted 7 lines
These boards were the first rk3399 support we had in mainline, I believe. Everything else came later but conversions were not done for these existing boards.
I actually intensely dislike the back-to-brom stuff. If the ROM had an actual API (
mmc_read(), etc.) then that would be fine. But just jumping back makes it hard to control what is going on.The logic of BootRom is very simple and very clear:
- Read image from boot medium and check the availability(format of rockchip IDB,which is packed by the mkimage rksd/rkspi);
Quoted 11 lines
- Load TPL/dram init blob to the internal SRAM(size limit by the sram), and jump to the entry;
- Back to bootRom with '0' return means the dram init success, bootRom will get next image for dram;
- Read SPL image from boot medium to DDR start address(no size limit), and jump to the ddr entry;
- The signature verify will be done for all the firmware load by bootRom if the secure boot feature is enabled;
This model works for all Rockchip SoCs, although some SoCs have very limit SRAM size(only available
for DRAM init) and some other SoCs like rk3399 have bigger SRAM size.
Thanks for the info. Is there a document that describes this exactly? Some questions it should cover:
- What is the signature verification?
- What offsets are used?
- What memory addresses are things loaded to?
- What other values of 'back to bootRom' are supported?
- Is there a jump table listing available functions for U-Boot to call?
- How to call the ROM functions to read blocks from mmc, SPI, etc.
Quoted 11 lines
Thanks,
- KeverQuoted 8 lines
It is interesting to hear that SPL-only is causing a problem. Do you have any inkling of what that might be? I could take a look at converting the boards to use TPL, but it does seem a bit sideways to the issue here. Is the bootrom doing some magic, perhaps? Is there decent documentation for the boot ROM these days?
Regards,
Simon
Regards,
Simon
PATCH v3 17/18 rockchip: bob: kevin: Disable dcache in SPL
In reply to Simon GlassThis causes a hang, so disable it. Unfortunately the RAM-size fix does not resolve the problem and I am unsure what is wrong. As soon as the cache is enabled the board appears to hang.
---
(no changes since v1)
configs/chromebook_bob_defconfig | 1 + configs/chromebook_kevin_defconfig | 1 + 2 files changed, 2 insertions(+)
configs/chromebook_bob_defconfig +1 -0
@@ -1,5 +1,6 @@ CONFIG_ARM=y CONFIG_SKIP_LOWLEVEL_INIT=y +CONFIG_SPL_SYS_DCACHE_OFF=y CONFIG_COUNTER_FREQUENCY=24000000 CONFIG_ARCH_ROCKCHIP=y CONFIG_TEXT_BASE=0x00200000
configs/chromebook_kevin_defconfig +1 -0
@@ -2,6 +2,7 @@ CONFIG_ARM=y CONFIG_SKIP_LOWLEVEL_INIT=y CONFIG_COUNTER_FREQUENCY=24000000 CONFIG_ARCH_ROCKCHIP=y +CONFIG_SPL_SYS_DCACHE_OFF=y CONFIG_TEXT_BASE=0x00200000 CONFIG_SPL_GPIO=y CONFIG_NR_DRAM_BANKS=1
Signature · 1 line
2.34.1
PATCH v3 18/18 Drop the special am335x_boneblack_vboot target
In reply to Simon GlassNow that am335x_evm boots OK on the Beaglebone black, drop the latter and update the docs to cover the change.
Also add a few updates about 'make fit' and drop the note about the security review, as U-Boot's verified boot has had quite extensive review now.
---
(no changes since v2)
Changes in v2:
- Drop patch "regulator: rk8xx: Fix incorrect parameter"
- Rewrite boneblack patch to onstead drop the target and update docs
board/ti/am335x/MAINTAINERS | 1 - configs/am335x_boneblack_vboot_defconfig | 94 ------------------------ configs/am335x_evm_defconfig | 3 +- doc/usage/fit/beaglebone_vboot.rst | 21 +++--- 4 files changed, 12 insertions(+), 107 deletions(-) delete mode 100644 configs/am335x_boneblack_vboot_defconfig
board/ti/am335x/MAINTAINERS +0 -1
@@ -3,6 +3,5 @@ M: Tom Rini <[email protected]> S: Maintained F: board/ti/am335x/ F: include/configs/am335x_evm.h -F: configs/am335x_boneblack_vboot_defconfig F: configs/am335x_evm_defconfig F: configs/am335x_evm_spiboot_defconfig
configs/am335x_boneblack_vboot_defconfig deleted +0 -94
94 lines not on this page · raw message
configs/am335x_evm_defconfig +2 -1
@@ -13,6 +13,8 @@ CONFIG_AM335X_USB0_PERIPHERAL=y CONFIG_AM335X_USB1=y CONFIG_SPL=y CONFIG_TIMESTAMP=y +CONFIG_FIT_SIGNATURE=y +CONFIG_FIT_VERBOSE=y CONFIG_SPL_LOAD_FIT=y CONFIG_SYS_BOOTM_LEN=0x1000000 CONFIG_DISTRO_DEFAULTS=y
@@ -119,5 +121,4 @@ CONFIG_SPL_USB_ETHER=y CONFIG_WDT=y # CONFIG_SPL_WDT is not set CONFIG_DYNAMIC_CRC_TABLE=y -CONFIG_RSA=y CONFIG_LZO=y
doc/usage/fit/beaglebone_vboot.rst +10 -11
@@ -67,18 +67,20 @@ a. Set up the environment variable to point to your toolchain. You will need export CROSS_COMPILE=arm-linux-gnueabi- -b. Configure and build U-Boot with verified boot enabled:: +b. Configure and build U-Boot with verified boot enabled. Note that we use the +am335x_evm target since it covers all boards based on the AM335x evaluation +board:: export UBOOT=/path/to/u-boot cd $UBOOT # You can add -j10 if you have 10 CPUs to make it faster - make O=b/am335x_boneblack_vboot am335x_boneblack_vboot_config all - export UOUT=$UBOOT/b/am335x_boneblack_vboot + make O=b/am335x_evm am335x_evm_config all + export UOUT=$UBOOT/b/am335x_evm c. You will now have a U-Boot image:: - file b/am335x_boneblack_vboot/u-boot-dtb.img - b/am335x_boneblack_vboot/u-boot-dtb.img: u-boot legacy uImage, + file b/am335x_evm/u-boot-dtb.img + b/am335x_evm/u-boot-dtb.img: u-boot legacy uImage, U-Boot 2014.07-rc2-00065-g2f69f8, Firmware/ARM, Firmware Image (Not compressed), 395375 bytes, Sat May 31 16:19:04 2014, Load Address: 0x80800000, Entry Point: 0x00000000,
@@ -466,7 +468,7 @@ the private key that you signed with so that it can verify any kernels that you sign:: cd $UBOOT - make O=b/am335x_boneblack_vboot EXT_DTB=${WORK}/am335x-boneblack-pubkey.dtb + make O=b/am335x_evm EXT_DTB=${WORK}/am335x-boneblack-pubkey.dtb Here we are overriding the normal device tree file with our one, which contains the public key.
@@ -597,14 +599,11 @@ Further Improvements Several of the steps here can be easily automated. In particular it would be capital if signing and packaging a kernel were easy, perhaps a simple make -target in the kernel. +target in the kernel. A stating point for this is the 'make image.fit' target +for ARM64 in Linux from v6.9 onwards. Some mention of how to use multiple .dtb files in a FIT might be useful. -U-Boot's verified boot mechanism has not had a robust and independent security -review. Such a review should look at the implementation and its resistance to -attacks. - Perhaps the verified boot feature could be integrated into the Amstrom distribution.
Signature · 1 line
2.34.1