- Mar 30, 2022
-
-
Sean Anderson authored
This converts most CCF drivers to use generic ops. imx6q is the only outlier, where we retain the existing functionality by moving the check to request(). Signed-off-by:
Sean Anderson <seanga2@gmail.com> Reviewed-by:
Claudiu Beznea <claudiu.beznea@microchip.com> Reviewed-by:
Peng Fan <peng.fan@nxp.com> Link: https://lore.kernel.org/r/20220320203446.740178-2-seanga2@gmail.com [ fixed missing include for at91 ] Signed-off-by:
-
Sean Anderson authored
Most CCF drivers follow a common pattern where their clock ops defer the actual operation to the backing CCF clock. Add some generic implementations of these functions to reduce duplication of code. Signed-off-by:
-
Sean Anderson authored
These functions are exactly the same as their "nodev" varients, except they accept a device and not an ofnode. Rewrite them to just call the other function. Signed-off-by:
-
Sean Anderson authored
Most callers of this function do not check the return value, and it is unclear what action they should take if it fails. If a function is freeing multiple clocks, it should not stop just because the first one failed. Since the callbacks can no longer fail, just convert the return type to void. Signed-off-by:
-
Sean Anderson authored
This function always succeeds, so don't check its return value. Signed-off-by:
-
Sean Anderson authored
This function always succeeds, so don't check its return value. Signed-off-by:
-
Sean Anderson authored
This function always succeeds, so don't check its return value. Signed-off-by:
-
Sean Anderson authored
This function always succeeds, so don't check its return value. Signed-off-by:
-
Sean Anderson authored
This function always succeeds, so don't check its return value. Signed-off-by:
-
Sean Anderson authored
When freeing a clock there is not much we can do if there is an error, and most callers do not actually check the return value. Even e.g. checking to make sure that clk->id is valid should have been done in request() in the first place (unless someone is messing with the driver behind our back). Just return void and don't bother returning an error. Signed-off-by:
Simon Glass <sjg@chromium.org> Link: https://lore.kernel.org/r/20220115222504.617013-2-seanga2@gmail.com
-
- Mar 28, 2022
-
-
https://source.denx.de/u-boot/custodians/u-boot-videoTom Rini authored
- drop old CFB code - drop CONFIG_LCD_BMP_RLE8
-
This is not defined by any board. Even sandbox doesn't actually use it since it has migrated to DM_VIDEO. Drop this option. Remove the dead code also, for completeness, even though the whole lcd.c file will be dropped soon. Signed-off-by:
Anatolij Gustschin <agust@denx.de>
-
This is not used. Drop it. Signed-off-by: -
This converts the following to Kconfig: CONFIG_VIDEO_BCM2835 This is the final ad-hoc CONFIG_VIDEO_... to convert. Signed-off-by:
Matthias Brugger <mbrugger@suse.com>
-
This is no-longer used and is the last reference to video_hw_init(). Drop it. Signed-off-by: -
This does not use driver model and is more than two years past the migration date. Drop it. It can be added back later if needed. Signed-off-by: -
This does not use driver model and is more than two years past the migration date. Drop it. It can be added back later if needed. Signed-off-by: -
This is not used in U-Boot anymore. Drop it. Signed-off-by: -
Drop the unnecessary cruft from this header and update the title. Signed-off-by: -
Drop the Kconfigs which are not used and all references to them. In particular, this drops CONFIG_VIDEO to avoid confusion and allow us to eventually rename CONFIG_DM_VIDEO to CONFIG_VIDEO. Also drop the prototype for video_get_info_str() which is no-longer used. Signed-off-by:
Jason Liu <jason.hui.liu@nxp.com>
-
This option is not implemented anymore. Drop it. Signed-off-by: -
This is not used now. Drop it. Signed-off-by: -
Unfortunately this driver uses the old video structure to store things. This is not supported with driver model. Drop the old code and comment out the other pieces, so the maintainer can take a look. Signed-off-by: -
Drop this old code which is not built anymore, as it depends on CONFIG_VIDEO which has been removed. Signed-off-by: -
The non-driver model video support was removed two years ago. Drop this driver, which is only used by nokia_rx51. Signed-off-by: -
Tom Rini authored
Prepare v2022.04-rc5
-
Tom Rini authored
Signed-off-by:Tom Rini <trini@konsulko.com>
-
Tom Rini authored
Rsync all defconfig files using moveconfig.py Signed-off-by: -
Tom Rini authored
- A zstd, two Apple M1 and an MXS NAND critical bugfix - Clean up another file that wasn't being removed and update some external documentation links.
-
Previous u-boot code changed the default bch setting behavior and caused backward compatible issue. This fix choose the legacy bch geometry back again as the default option. If the minimum ecc strength that NAND chips required need to be chosen, it can be enabled by either adding DT flag "fsl,use-minimum-ecc" or CONFIG_NAND_MXS_USE_MINIMUM_ECC in configs. The unused flag "fsl,legacy-bch-geometry" get removed. Fixes: 51cdf83e (mtd: gpmi: provide the option to use legacy bch geometry) Fixes: 616f03da (mtd: gpmi: change the BCH layout setting for large oob NAND) Tested-by:
Tim Harvey <tharvey@gateworks.com> Tested-by:
Sean Nyekjaer <sean@geanix.com> Signed-off-by:
Han Xu <han.xu@nxp.com> Reviewed-by:
Miquel Raynal <miquel.raynal@bootlin.com>
-
The code was mistakenly initializing the input buffer twice. Tested to be working on BeagleBone by adjusting CONFIG_SYS_BOOTM_LEN to 64MiB (probably works with less) and preparing uImage with: cat arch/arm/boot/Image \ | zstd --ultra -22 --zstd=windowLog=22 \ > linux.bin.zst mkimage -A arm -T kernel uImage -C zstd -d linux.bin.zst \ -a 0x80008000 -e 0x80008000 Without the windowLog restriction, bootm fails with a zstd decompression error 7 (window too large), which I haven't troubleshooted. There should be a bit more documentation on the feature... Reviewed-by:
-
Freescale git repos are now on source.codeaurora.org. Signed-off-by:Pali Rohár <pali@kernel.org>
-
make sandbox_defconfig make mrproper make tests fails with ../drivers/video/u_boot_logo.S: Assembler messages: ../drivers/video/u_boot_logo.S:5: Error: file not found: drivers/video/u_boot_logo.bmp We have to delete the generated file. Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
-
The current approach for setting the environment variables that describe the memory layout runs the risk of overlapping with reserved memory regions. Use the lmb code to derive the addresses for these variables instead. Signed-off-by:
Mark Kettenis <kettenis@openbsd.org> Reviewed-by:
-
The firmware on larger NVMe drives needs more than 100ms to come up. Change the timeout to 1s. Signed-off-by:
Hector Martin <marcan@marcan.st> Signed-off-by:
-
- Mar 27, 2022
-
-
https://source.denx.de/u-boot/custodians/u-boot-efiTom Rini authored
Pull request for efi-2022-04-rc5-2 Documentation: * man-page for the wdt command UEFI: * Unit test for boot manager
-
- Mar 26, 2022
-
-
Heinrich Schuchardt authored
When calling efi_dp_from_name() we are not interested in the device part. Just pass NULL as an argument. Suggested-by:
AKASHI Takahiro <takahiro.akashi@linaro.org> Signed-off-by:
-
Heinrich Schuchardt authored
Provide a unit test for * efidebug boot add * efidebug boot order * bootefi bootmgr * initrd via EFI_LOAD_FILE2_PROTOCOL Signed-off-by: -
Heinrich Schuchardt authored
Up to now the initrddump.efi application has drained the input after showing the prompt. This works for humans but leads to problems when automating testing. If the input is drained, this should be done before showing the prompt. Signed-off-by:
Ilias Apalodimas <ilias.apalodimas@linaro.org>
-
Heinrich Schuchardt authored
initrddump.efi uses colored output and clear the screen. This is not helpful for integration into Python tests. Allow specifying 'nocolor' in the load option data to suppress color output and clearing the screen. Signed-off-by:
-
