summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2025-01-14ram: k3-ddrss: Add k3_ddrss_ddr_bank_base_size_calc() to solve 'calculations ↵Santhosh Kumar K
restricted to 32 bits' issue As R5 is a 32 bit processor, the RAM banks' base and size calculation is restricted to 32 bits, which results in wrong values if bank's base is greater than 32 bits or bank's size is greater than or equal to 4GB. So, add k3_ddrss_ddr_bank_base_size_calc() to get the base address and size of RAM's banks from the device tree memory node, and store in a 64 bit device private data which can be used for ECC reserved memory calculation, Setting ECC range and Fixing up bank size in device tree when ECC is enabled. Signed-off-by: Santhosh Kumar K <[email protected]> Reviewed-by: Wadim Egorov <[email protected]>
2025-01-14ram: k3-ddrss: Use the DDR controller BIST engine for ECC primingGeorgi Vlaev
The 1-bit inline ECC support in TI's DDRSS bridge requires the configured memory regions to be preloaded with a pattern before use. This is done by the k3-ddrss driver from the R5 SPL in a 'for' loop. It takes around 10 seconds to fill 2GB of memory, for example. Memset can cut the time in half and using DMA currently yields a similar result. The BIST engine of DDR controller provides support for initializing any memory region with a pattern. This bypasses the DDRSS bridge, so the required inline ECC data is not computed and populated in the memory. For some values like zero, the computed ECC syndrome is also zero and we can use these values to preload the memory from the DDR controller, without the assistance of the bridge. The registers involved in the process are described in the 'DDR controller registers' topic in [1] AM62 and [2] J721E reference manuals. The patch replaces the 'for' loop memory fill function with the BIST memory initialization procedure. This cuts the time to preload the 2GB memory from 10 seconds down to 1 second. The bist preload function uses the lpddr4 APIs in the k3-ddrss, so this is compatible with devices with both 16-bit LPDDR4 and 32-bit LPDDR4 interfaces (e.g J721E). [1] AM62x: https://www.ti.com/lit/pdf/spruiv7 [2] DRA829/TDA4VM: https://www.ti.com/lit/zip/spruil1 Signed-off-by: Georgi Vlaev <[email protected]> Signed-off-by: Santhosh Kumar K <[email protected]>
2025-01-14arm: dts: k3-*-ddr: Add ss_cfg reg entrySanthosh Kumar K
Add ss_cfg memory region which maps the DDRSS configuration region for the memory controller node. Signed-off-by: Santhosh Kumar K <[email protected]> Signed-off-by: Neha Malcom Francis <[email protected]> Tested-by: Neha Malcom Francis <[email protected]>
2025-01-14Merge patch series "fdt_support: improve board_fdt_chosen_bootargs() for ↵Tom Rini
flexibility" Dmitry Rokosov <[email protected]> says: This series consists of three patches. The first patch modifies the function documentation style in the include/fdt_support.h file to comply with kernel-doc requirements. The second patch modifies the board_fdt_chosen_bootargs() function to return a const char* type. This change clarifies to the caller that the returned string should neither be freed nor modified. It aligns with the existing fdt_setprop() function, which already utilizes a const char* parameter. This promotes consistency within the codebase and enhances code safety by preventing unintended modifications to the returned string. The third patch addresses the need for flexibility in providing kernel command line arguments (bootargs) for different kernel images within the same U-Boot environment. It introduces a read-only (RO) fdt_property argument to the board_fdt_chosen_bootargs() function, allowing access to the original chosen/bootargs data. This is crucial for scenarios where different kernel versions require distinct console setups (e.g., ttyS0 for vendor kernels and ttyAML0 for upstream kernels). By enabling board developers to either merge or replace the original bootargs, this patch enhances the configurability of U-Boot for various kernel images without relying on outdated configurations like CMDLINE_EXTEND. CI/CD results: https://github.com/u-boot/u-boot/pull/716/checks Link: https://lore.kernel.org/r/20241220-board_fdt_chosen_bootargs_improvements-v1-0-f6a7181787c5@salutedevices.com
2025-01-14common: fdt: hand over original fdt bootargs into board chosen handlerDmitry Rokosov
Sometimes, it is necessary to provide an additional bootargs string to the kernel command line. We have a real scenario where one U-Boot blob needs to boot several kernel images: the vendor-patched kernel image and the latest upstream kernel image. The Amlogic (Meson architecture) tty driver has different tty suffixes in these kernels: the vendor uses 'ttySx', while the upstream implementation uses 'ttyAMLx'. The initial console setup is provided to the kernel using the kernel command line (bootargs). For the vendor kernel, we should use 'console=ttyS0,115200', while for the upstream kernel, it must be 'console=ttyAML0,115200'. This means we have to use different command line strings depending on the kernel version. To resolve this issue, we cannot use the CMDLINE_EXTEND kernel configuration because it is considered legacy and is not supported for the arm64 architecture. CMDLINE_EXTEND is outdated primarily because we can provide additional command line strings through the 'chosen/bootargs' FDT node. However, U-Boot uses this node to inject the U-Boot bootargs environment variable content, which results in U-Boot silently overriding all data in the 'chosen/bootargs' node. While we do have the board_fdt_chosen_bootargs() board hook to address such issues, this function lacks any FDT context, such as the original value of the 'chosen/bootargs' node. This patch introduces a read-only (RO) fdt_property argument to board_fdt_chosen_bootargs() to share the original 'chosen/bootargs' data with the board code. Consequently, the board developer can decide how to handle this information for their board setup: whether to drop it or merge it with the bootargs environment. Signed-off-by: Dmitry Rokosov <[email protected]> Reviewed-by: Quentin Schulz <[email protected]>
2025-01-14fdt_support: board_fdt_chosen_bootargs() should return const char*Dmitry Rokosov
It should be structured this way to demonstrate to the caller that freeing the return value is unnecessary and that the caller cannot modify it. The function fdt_setprop() includes a parameter with a const char* prototype, so it is better to use the const qualifier. Signed-off-by: Dmitry Rokosov <[email protected]> Reviewed-by: Heinrich Schuchardt <[email protected]>
2025-01-14include/fdt_support: fix docstyle to comply with kernel-doc requirementsDmitry Rokosov
No errors from kernel-doc with this patch applied: $ ./scripts/kernel-doc -v -none include/fdt_support.h include/fdt_support.h:17: info: Scanning doc for arch_fixup_fdt include/fdt_support.h:37: info: Scanning doc for fdt_root include/fdt_support.h:48: info: Scanning doc for fdt_chosen include/fdt_support.h:59: info: Scanning doc for fdt_initrd include/fdt_support.h:100: info: Scanning doc for fdt_fixup_memory include/fdt_support.h:115: info: Scanning doc for fdt_fixup_memory_banks include/fdt_support.h:148: info: Scanning doc for fdt_fixup_display include/fdt_support.h:176: info: Scanning doc for fdt_record_loadable include/fdt_support.h:205: info: Scanning doc for ft_board_setup include/fdt_support.h:218: info: Scanning doc for board_rng_seed include/fdt_support.h:231: info: Scanning doc for board_fdt_chosen_bootargs include/fdt_support.h:251: info: Scanning doc for ft_system_setup include/fdt_support.h:266: info: Scanning doc for fdt_shrink_to_minimum include/fdt_support.h:301: info: Scanning doc for fdt_copy_fixed_partitions include/fdt_support.h:314: info: Scanning doc for fdt_translate_address include/fdt_support.h:327: info: Scanning doc for fdt_translate_dma_address include/fdt_support.h:342: info: Scanning doc for fdt_get_dma_range include/fdt_support.h:464: info: Scanning doc for fdt_get_cells_len include/fdt_support.h:480: info: Scanning doc for fdtdec_get_child_count include/fdt_support.h:500: info: Scanning doc for fdt_kaslrseed Signed-off-by: Dmitry Rokosov <[email protected]> Acked-by: Heinrich Schuchardt <[email protected]>
2025-01-14chromebook_coral: Move CONFIG_BLOBLIST_ADDR to CARTom Rini
Reading doc/board/google/chromebook_coral.rst we can see that at some point it was intended to put the bloblist in CAR, rather than DRAM, at some point during development. This is fine for TPL/SPL stages where we have very minimal information stored in the bloblist and so we can set the limit there to 4KiB and then expand it to 196KiB in U-Boot proper so there's room for ACPI tables and so forth. We also update the documentation to use the same location for CONFIG_BLOBLIST_ADDR in both references. Signed-off-by: Tom Rini <[email protected]>
2025-01-14Merge patch series "SMBIOS improvements"Tom Rini
Raymond Mao <[email protected]> says: Motivations for changes: Current SMBIOS library and command-line tool is not fully matching with the requirements: 1. Missing support for other mandatory types (#7, #9, #16, #17, #19). 2. Only a few platforms support SMBIOS node from the device tree. 3. Values of some fields are hardcoded in the library other than fetching from the device hardware. 4. Embedded data with dynamic length is not supported (E.g. Contained Object Handles in Type #2 and Contained Elements in Type #3) Changes: 1. Refactor the SMBIOS library and command-line tool to better align with the SMBIOS spec. 2. Create an arch-specific driver for all aarch64-based platforms to fetch SMBIOS private data from the device hardware (processor and cache). 3. Create a sysinfo driver to poppulate platform SMBIOS private data. 4. Add generic SMBIOS DTS file for arm64 platforms for those common strings and values which cannot be retrieved from the system registers. Vendors can create their own SMBIOS node using this as an example. For those boards without SMBIOS nodes, this DTS file can be included to have a generic SMBIOS information of the system. 5. Add support for Type #7 (Cache Information) and link its handles to Type #4. 6. To minimize size-growth for those platforms which have not sufficient ROM spaces or the platforms which don't need detailed SMBIOS information, new added fields are only being built when kconfig GENERATE_SMBIOS_TABLE_VERBOSE is selected. Once this patch is acceptted, subsequent patch sets will add other missing types (#9, #16, #17, #19). Tests: To test this with QEMU arm64, please follow the guide on dt_qemu.rst to get a merged DT to run with. ``` qemu-system-aarch64 -machine virt -machine dumpdtb=qemu.dtb cat <(dtc -I dtb qemu.dtb) <(dtc -I dtb ./dts/dt.dtb | grep -v /dts-v1/) \ | dtc - -o merged.dtb qemu-system-aarch64 -machine virt -nographic -bios u-boot.bin \ -dtb merged.dtb ``` Link: https://lore.kernel.org/r/[email protected]
2025-01-14configs: Enable sysinfo for QEMU Arm64Raymond Mao
Enable sysinfo smbios by default for arm64. When SYSINFO_SMBIOS is enabled, disable QFW_SMBIOS. Signed-off-by: Raymond Mao <[email protected]> Reviewed-by: Simon Glass <[email protected]>
2025-01-14cmd: update smbios cmdRaymond Mao
Update the cmd according to the changes of the smbios library: 1. Refactor smbios cmd print functions to match the content defined by the specification. 2. Add new print functions for Type 3, 4 and 7. 3. Remove the fallback string "Not specified" from smbios_get_string, as the spec requires a NULL output for those undefined strings. 4. Update the test_cmd_smbios_sandbox pytest expected result to align with the smbios library changes and add new pytest test_cmd_smbios_sysinfo_verbose to test the verbose smbios output. Signed-off-by: Raymond Mao <[email protected]>
2025-01-14armv8: Add generic smbios information into the device treeRaymond Mao
Add common smbios information that can be used by all armv8 platforms and set it as default for qemu-arm64. >From now smbios library can load values from here for those fields doesn't exist in the sysinfo driver. To run this with QEMU arm64, we need to dump the generated DTB from QEMU first, merge it with the one we build and then re-run QEMU with the merged DTB. ``` qemu-system-aarch64 -machine virt -machine dumpdtb=qemu.dtb cat <(dtc -I dtb qemu.dtb) <(dtc -I dtb ./dts/dt.dtb | \ grep -v /dts-v1/) | dtc - -o merged.dtb qemu-system-aarch64 -machine virt -nographic -bios u-boot.bin \ -dtb merged.dtb ``` For details please take reference on dt_qemu.rst Signed-off-by: Raymond Mao <[email protected]>
2025-01-14armv8: Add arch-specific sysinfo platform driverRaymond Mao
Add sysinfo platform driver for all armv8 platforms to retrieve hardware information on processor and cache. Signed-off-by: Raymond Mao <[email protected]> Reviewed-by: Simon Glass <[email protected]>
2025-01-14smbios: add detailed smbios informationRaymond Mao
Add detailed SMBIOS information as following: 1. Missing fields in Type #3 and #4 2. Type #7 Add support to dynamic length of contained object handles and elements. As SMBIOS is a fundamental feature which is enabled for all boards, in order to avoid increasing rom size, all detailed SMBIOS information is under kconfig GENERATE_SMBIOS_TABLE_VERBOSE. Board maintainers can determine whether to select this feature. Signed-off-by: Raymond Mao <[email protected]>
2025-01-14smbios: Refactor smbios libraryRaymond Mao
Current smbios library does not fully match to the specification. It hardcodes values instead of exposing values from the device. It does not reserve the space to support dynamic length for contained object handles or elements and misses the handling of a few of fields. The refactoring of this patch includes: 1. Expose values from device via sysinfo interface. 2. Replace smbios_add_prop with smbios_add_prop_si to allow getting string values from sysinfo. 3. Add smbios_get_val_si to get values from sysinfo or device tree. 4. Use sysinfo_get_data to get data area. 5. Reserve the space of contained object handles and elements. 6. Miscellaneous fixes in smbios. Signed-off-by: Raymond Mao <[email protected]>
2025-01-14sysinfo: Add sysinfo driver and data structure for smbiosRaymond Mao
Add sysinfo driver to retrieve smbios information (Type 4 and 7). So that the smbios library can use it for getting values from the hardware platform instead of device tree. Signed-off-by: Raymond Mao <[email protected]>
2025-01-14test/dm: add sandbox test for sysinfo_get_dataRaymond Mao
Adding sysinfo_get_data into sandbox ut test dm_test_sysinfo. Signed-off-by: Raymond Mao <[email protected]>
2025-01-14sysinfo: Add sysinfo API for accessing data areaRaymond Mao
Add interface for sysinfo to access a data area from the platform. This is useful to save/read a memory region of platform-specific data. Signed-off-by: Raymond Mao <[email protected]>
2025-01-14smbios: Refactor the smbios headfileRaymond Mao
Move the smbios field definitions to a separated simple headfile, which is a prerequisite to be included by dts files. Add new definitions for cache information. This patch also includes a few of code optimizations in smbios. Signed-off-by: Raymond Mao <[email protected]> Acked-by: Heinrich Schuchardt <[email protected]>
2025-01-14Merge patch series "Adjust how autoprobe is implemented"Tom Rini
Simon Glass <[email protected]> says: This little series makes a minor change to how autoprobe is implemented, as discussed on the list. Link: https://lore.kernel.org/r/[email protected] Link: https://lore.kernel.org/r/[email protected]
2025-01-14dm: core: Simplify dm_probe_devices()Simon Glass
There is no point in checking the pre_reloc flag, since devices not marked as pre-reloc will not have been bound, so won't exist yet. There doesn't seem to be any point in checking if the device has a valid devicetree node either, so drop that too. Signed-off-by: Simon Glass <[email protected]>
2025-01-14common: Move autoprobe out to board initSimon Glass
Rather than doing autoprobe within the driver model code, move it out to the board-init code. This makes it clear that it is a separate step from binding devices. For now this is always done twice, before and after relocation, but we should discuss whether it might be possible to drop the post-relocation probe. For boards with SPL, the autoprobe is still done there as well. Note that with this change, autoprobe happens after the EVT_DM_POST_INIT_R/F events are sent, rather than before. Link: https://lore.kernel.org/u-boot/[email protected]/ Signed-off-by: Simon Glass <[email protected]>
2025-01-14common: Drop check for DM in initf_dm()Simon Glass
This is enabled by all boards, so drop the condition. Signed-off-by: Simon Glass <[email protected]> Reviewed-by: Tom Rini <[email protected]>
2025-01-14Merge tag 'xilinx-for-v2025.04-rc1-v2' of ↵Tom Rini
https://source.denx.de/u-boot/custodians/u-boot-microblaze AMD/Xilinx changes for v2025.04-rc1 v2 Versal: - Enable dfu support for SPI with multiboot ZynqMP: - Align multiboot reg description - DT syncups - Wire missing DTs in defconfig - Kria: Remove usb hub initialization via commands - Kria: Update DP reset in psu_init AMD/Xilinx: - Enable SPI_STACKED_PARALLEL configs SPI/ZYNQMP_GQSPI: - Update debug message to use log_debug() RTC: - Enable ZYNQMP_RTC for Versal SOCs
2025-01-14Merge branch 'master' of https://source.denx.de/u-boot/custodians/u-boot-pmicTom Rini
2025-01-14rtc: zynqmp: allow on Versal architecturesVincent Fazio
Allow the ZyncMP RTC driver to be enabled on Versal architectures. Also, require DM_RTC since the driver uses the RTC driver model. Signed-off-by: Vincent Fazio <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Michal Simek <[email protected]>
2025-01-14zynqmp_gqspi: update to log_debugIbai Erkiaga
Update recent parallel memory support code to move to log_debug instead of debug as per logging in U-Boot documentation Signed-off-by: Ibai Erkiaga <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Michal Simek <[email protected]>
2025-01-14board: xilinx: Add missing prototype for set_dfu_alt_infoVenkatesh Yadav Abbarapu
Add missing prototype to fix the sparse warning, warning: no previous prototype for 'set_dfu_alt_info' [-Wmissing-prototypes]. Signed-off-by: Venkatesh Yadav Abbarapu <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Michal Simek <[email protected]>
2025-01-14arm64: zynqmp: Add eeprom labels for System Controller dtsJonathan Stroud
Label all eeproms so we can open by label rather than a fixed i2c address. Signed-off-by: Jonathan Stroud <[email protected]> Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/878558c3c859599d29bc4ae2278baebf84b368e0.1736152966.git.michal.simek@amd.com
2025-01-14arm64: zynqmp: Enable iio-hwmon description only for SOMMichal Simek
Description is coming from SOM only that's why enable it only on SOM. Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/08ee4ce2fe242905dd99cea2b87373b57d8fea91.1736152939.git.michal.simek@amd.com
2025-01-14config: xilinx: Enable the SPI_STACKED_PARALLEL config optionVenkatesh Yadav Abbarapu
Enable the SPI_STACKED_PARALLEL config option for all AMD/xilinx platforms, as this is required for parallel and stacked memories. Signed-off-by: Venkatesh Yadav Abbarapu <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Michal Simek <[email protected]>
2025-01-14board: zynqmp: zynqmp-sm-k26-revA: release DP from resetNeal Frager
This releases the DP configuration from reset early on during the boot process for K26 SOM. It will also avoid the boot hang situation should any attempt be made to configure the DP registers while it is still in reset. Fixes the same issue as described by the commit 8b81010a2fe3 ("video: zynqmp: Add support for reset"). Signed-off-by: Neal Frager <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Michal Simek <[email protected]>
2025-01-14xilinx: Sort OF_LIST and add missing vpk120 and zcu670 platformsMichal Simek
Sort OF_LIST entries and also add missing vpk120 and zcu670 platforms. Compilation is failing when these DTs are exported via DEVICE_TREE because binman is not able to create a link for default configuration. Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/505996b6ef969b1b677ab921462c75c798c366e7.1734335553.git.michal.simek@amd.com
2025-01-14zynqmp: Remove usb init initialization for KriaMichal Simek
USB hub initialization is done by driver introduced by commit 09f557e106ef ("usb: onboard-hub: Add i2c initialization for usb5744 hub") that's why there is no need to do initialization via variables. Reported-by: Love Kumar <[email protected]> Acked-by: Ilias Apalodimas <[email protected]> Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/96e9c80aeeed4e9664858bf236476997d17a9914.1734522042.git.michal.simek@amd.com
2025-01-14arm64: zynqmp: Sync DTs with Linux v6.13-rc1Michal Simek
Sync zynqmp* DTS files with v6.13-rc1 Linux kernel including three patches from Sean: arm64: zynqmp: Enable AMS for all boards arm64: zynqmp: Expose AMS to userspace as HWMON arm64: zynqmp: Add thermal zones Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/06e466d64c9d8e718e2f06a76cc65d6da2a37a7b.1733996500.git.michal.simek@amd.com
2025-01-14arm64: zynqmp: add clock-output-names property in clock nodesNaman Trivedi
Replace underscores with hyphens in the clock node names as per dt-schema rule. Also, add clock-output-names property to all clock nodes, so that the resulting clock name do not change when clock node name is changed. Signed-off-by: Naman Trivedi <[email protected]> Acked-by: Senthil Nathan Thangaraj <[email protected]> Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/1080e31393c3e1b49735b77e7ddc14d570b83222.1733991159.git.michal.simek@amd.com
2025-01-14arm64: zynqmp: Do not use hardcoded address in do_zynqmp_reboot()Michal Simek
multi_boot is already the part of csu_base structure that's why use it directly instead of using register offset value. Fixes: fc001432e5b0 ("arm64: zynqmp: Add u-boot command to boot into recovery image") Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/3e5c6ea426b81cc73b90e6425764e41a98deb2a6.1733735454.git.michal.simek@amd.com
2025-01-14arm64: versal: RO multi_boot register in non JTAG bootmodeMichal Simek
The main reason for this change is that upstream QEMU has no multiboot register implemented that's why access to it fails which ends up in CI failure for our target. That's why in JTAG bootmode returns 0 which is correct behaviour because multiboot register is not used in this mode and value should be ignored and as a side effect it is also fixing CI/Qemu issue. Also move versal_get_bootmode() to avoid function declaration. Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/484b9cafc45e72308a1a29a3ab772020f96784cc.1736155238.git.michal.simek@amd.com
2025-01-14arm64: versal: Support operations around multiboot registerMichal Simek
Read multiboot register and show it's value by default. Also extend logic in dfu_alt_info string generation to support capsule update for different offsets. Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/72ba2efd0fb7b66a86b409a1521fe288a4dd3453.1733395093.git.michal.simek@amd.com
2025-01-14arm64: versal: Wire SPIs for dfu_alt_info variable generationMichal Simek
Enable automatic dfu_alt_info variable generation based on MTD partition. Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/67ff88c8c7186138353c0b74ed37a318fb4b199e.1733395093.git.michal.simek@amd.com
2025-01-14power: pmic: tps65941: Fix TI TPS65224 PMIC compatiableUdit Kumar
Fix compatiable name for TPS65224 PMIC as defined in dts/upstream/Bindings/mfd/ti,tps6594.yaml bindings. Fixes: 1468fbba6d55("power: pmic: tps65941: Add TI TPS65224 PMIC") Signed-off-by: Udit Kumar <[email protected]> Reviewed-by: Tom Rini <[email protected]> Reviewed-by: Jaehoon Chung <[email protected]>
2025-01-14power: replace magic numbers with macrosShree Ramamoorthy
Replace magic numbers in buckval2votl() & buckvolt2val() with macros to help with clarity and correlate what the numbers correspond to in the TPS65219 datasheet. Signed-off-by: Shree Ramamoorthy <[email protected]> Reviewed-by: Jaehoon Chung <[email protected]>
2025-01-14power: regulator: replace printf() with pr_err()Shree Ramamoorthy
Replace printf() with pr_err() because pr_err() has a uniform print format and takes into consideration the log levels supported. Signed-off-by: Shree Ramamoorthy <[email protected]> Reviewed-by: Jaehoon Chung <[email protected]>
2025-01-13Merge branch 'master' of https://source.denx.de/u-boot/custodians/u-boot-usbTom Rini
- ehci-mx5/ehci-mx6 driver improvements
2025-01-13usb: ehci-mx6: Add i.MX95 supportMarek Vasut
i.MX95 uses the same USB IP as i.MX8MM. It can then reuse the ehci-mx6 driver. Signed-off-by: Marek Vasut <[email protected]> Reviewed-by: Fabio Estevam <[email protected]>
2025-01-12Merge branch 'master' of https://source.denx.de/u-boot/custodians/u-boot-shTom Rini
2025-01-12arm64: renesas: Convert boards over to is_cortex_a() functionsMarek Vasut
Use generic is_cortex_a() functions instead of open-coded midr_el1 read. No functional change. Reviewed-by: Paul Barker <[email protected]> Signed-off-by: Marek Vasut <[email protected]>
2025-01-12arm64: Add MIDR entries for Cortex-A57 and Cortex-A76Marek Vasut
Add MIDR entries for Cortex-A57 and Cortex-A76 cores. Those are used on R-Car Gen3 and Gen4 SoCs respectively. Reviewed-by: Paul Barker <[email protected]> Reviewed-by: Peter Robinson <[email protected]> Signed-off-by: Marek Vasut <[email protected]>
2025-01-12arm64: Convert core type check macros into inline functionsMarek Vasut
Turn the core type check macros into inline functions to perform better type checking on them. The inline functions get optimized out in case they are not used. Indent the MIDR_PARTNUM_CORTEX_An macros in preparation for addition of future three-digit cores and use MIDR_PARTNUM_SHIFT in MIDR_PARTNUM_MASK to be consistent. Reviewed-by: Paul Barker <[email protected]> Reviewed-by: Peter Robinson <[email protected]> Signed-off-by: Marek Vasut <[email protected]>
2025-01-10Merge tag 'u-boot-rockchip-20250110' of ↵Tom Rini
https://source.denx.de/u-boot/custodians/u-boot-rockchip CI: https://source.denx.de/u-boot/custodians/u-boot-rockchip/-/pipelines/24129 - Add boards: rk3566: FriendlyARM NanoPi R3S rk3588s: Radxa ROCK 5C, rk3588: Khadas Edge2 - Migrate to OF_UPSTREAM: rk3066a/rk3188; rk3288: tinker, miqi, firefly; - Migrate to TPL: rk3399 kevin and bob;
generated by cgit v1.3.1 (git 2.54.0) at 2026-08-13 03:24:50 +0000