- Mar 10, 2022
-
-
For debugging and dicoverability it is useful to be able to see a list of each event spy in a U-Boot ELF file. Add a script which shows this, along with the event type and the source location. This makes events a little easier to use than weak functions, for example. Add a basic sandbox test as well. We could provide a test for other boards, but for now, few use events. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Add a command to show the available events. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Instead of a special function, send an event after driver model is inited and adjust the boards which use this function. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This hook can be implmented using events, for the three boards that actually use it. Add the event type and event handlers. Drop CONFIG_MISC_INIT_F since we can just use CONFIG_EVENT to control this. Since sandbox always enables CONFIG_EVENT, we can drop the defconfig lines there too. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Generate events when devices are probed or removed, allowing hooks to be added for these situations. This is controlled by the DM_EVENT config option. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Call event_init() before relocation to get the event system running. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Add a test for event registration and activation. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Add a way to create and dispatch events without needing to allocate memory. Also add a way to 'spy' on events, thus allowing 'hooks' to be created. Use a linker list for static events, which we can use to replace functions like arch_cpu_init_f(). Allow an EVENT_DEBUG option which makes it easier to see what is going on at runtime, but uses more code space. Dynamic events allow the creation of a spy at runtime. This is not always necessary, but can be enabled with EVENT_DYNAMIC if needed. A 'test' event is the only option for now. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Allow finding a symbol by its address. Also export the function to get the file offset of a particular address, so it can be used by a script to be added. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
These header files don't follow the correct order. Fix this. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Mar 07, 2022
-
-
Tom Rini authored
- bcm6753 support - Aspeed GPIO driver - AM33xx DT-related MMC updates
-
Build in the driver for the Aspeed GPIO controller and turn on the `gpio` shell command. Signed-off-by:
Andrew Jeffery <andrew@aj.id.au>
-
Populate gpio_count in the gpio subsystem for the AST2500. Signed-off-by:
Andrew Jeffery <andrew@aj.id.au>
-
The Aspeed GPIO driver supports the GPIO controllers found in the AST2400, AST2500 and AST2600 BMC SoCs. The implementation is a cut-down copy of the upstream Linux kernel driver, adapted for u-boot. Signed-off-by:
Andrew Jeffery <andrew@aj.id.au>
-
This code has been ported from Linux v5.16.9 arch/arm/boot/dts/am33xx.dtsi file to allow correct usage of MMC2 controller in U-Boot. This IP block is a bit specific as it is connected to L3 interconnect bus, whereas mmc[01] are connected to L4. Proper configuration of this block (including providing clock) is handled in ti-sysc.c driver. Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
This change provides similar aliases definitions as now present in Linux kernel v5.16.9 for am33xx.dtsi file. Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
In the Linux kernel (v5.16) for this SoC there are two separate drivers - namely sdhci-omap.c and omap_hsmmc.c which have separate set of compatibles. The U-Boot's drivers/mmc/omap_hsmmc.c driver supports both eMMC and SD devices - hence the compatible for SDHCI can be added. After this change the am335x DTS description can be easier ported from Linux kernel. Signed-off-by:
Lukasz Majewski <lukma@denx.de> Reviewed-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Enable the led support on the refboard bcm96753ref. Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
Enable the led in the device tree of the refboard bcm96753ref. It also defines two leds (led_red ad led_green). Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
Add a node leds to support the LED IP in the device tree of the bcm6753. Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
Add the support of the LED IP for bcm6357. This LED IP supports blinking, fading and pulsating, but for the moment, only blinking is supported. Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
This add the initial support of the broadcom reference board bcm96753ref with a bcm6753 SoC. This board has 1 GB of RAM, 256 MB of flash (nand), 2 USB port, 1 UART, and 4 ethernet ports. Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
This IP is also used on some arm SoC, so we allow to use it on arm bcm6753 too. Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
This adds the nand support for chipset bcm6753. Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
This IP is also used on some arm SoC, so we allow to use it on arm bcm6753 too. Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
This add the initial support of the broadcom bcm6753 SoC family. Signed-off-by:
Philippe Reynes <philippe.reynes@softathome.com>
-
- Mar 03, 2022
-
-
Tom Rini authored
- Assorted Kconfig migrations and related cleanups.
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_CHIP_SELECTS_PER_CTRL Cc: Alison Wang <alison.wang@nxp.com> Cc: Pramod Kumar <pramod.kumar_1@nxp.com> Cc: Priyanka Jain <priyanka.jain@nxp.com> Cc: Rajesh Bhagat <rajesh.bhagat@nxp.com> Cc: Vladimir Oltean <olteanv@gmail.com> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_CFI_FLASH_USE_WEAK_ACCESSORS Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
This option is not in use anywhere and the documentation implies it's for some very old and unlikely to be seen currently issues. Rather than update the code so the CONFIG symbol could be easily in Kconfig, remove the code. Cc: Ramon Fried <rfried.dev@gmail.com> Signed-off-by:
Tom Rini <trini@konsulko.com> Acked-by:
Ramon Fried <rfried.dev@gmail.com>
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_BOOTP_MAY_FAIL CONFIG_BOOTP_VENDOREX CONFIG_BOOTP_BOOTFILESIZE CONFIG_BOOTP_NISDOMAIN CONFIG_BOOTP_TIMEOFFSET Cc: Ramon Fried <rfried.dev@gmail.com> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
This slight environment modification shouldn't be in the CONFIG namespace, change it. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_BOOTFILE Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_BOARD_POSTCLK_INIT Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_BOARD_ECC_SUPPORT Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_BIOSEMU Cc: Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_BOARD_COMMON Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
These particular values are not configurable and today we always set CONFIG_SECURE_BL1_ONLY. Move these to where they're used in the code, and drop from the CONFIG namespace. Cc: Minkyu Kang <mk7.kang@samsung.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Jaehoon Chung <jh80.chung@samsung.com> Reviewed-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Tom Rini authored
This converts the following to Kconfig: CONFIG_BTB Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
Remove some code, primarily CPM2 related, that is now unused since the removal of MPC8540/60ADS. Fixes 3913191c ("powerpc: mpc8540ads: mpc8560ads: Drop support for MPC8540/60ADS") Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-