summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'next' of ↵WIP/31Aug2021-nextTom Rini2021-08-3112-61/+349
|\ | | | | | | | | | | https://gitlab.denx.de/u-boot/custodians/u-boot-marvell into next - Handling all DM watchdogs in watchdog_reset() (Rasmus)
| * sandbox: add test of wdt-uclass' watchdog_reset()Rasmus Villemoes2021-08-312-0/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | Check that the watchdog_reset() implementation in wdt-uclass behaves as expected: - resets all activated watchdog devices - leaves unactivated/stopped devices alone - that the rate-limiting works, with a per-device threshold Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * sandbox: add test of wdt_gpio driverRasmus Villemoes2021-08-314-1/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | It seems that no other test has claimed gpio_a:7 yet, so use that. The only small wrinkle is modifying the existing wdt test to use uclass_get_device_by_driver() since we now have two UCLASS_WDT instances in play, so it's a little more robust to fetch the device by driver and not merely uclass+index. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * watchdog: add gpio watchdog driverRasmus Villemoes2021-08-314-0/+97
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A rather common kind of external watchdog circuit is one that is kept alive by toggling a gpio. Add a driver for handling such a watchdog. The corresponding linux driver apparently has support for some watchdog circuits which can be disabled by tri-stating the gpio, but I have never actually encountered such a chip in the wild; the whole point of adding an external watchdog is usually that it is not in any way under software control. For forward-compatibility, and to make DT describe the hardware, the current driver only supports devices that have the always-running property. I went a little back and forth on whether I should fail ->probe or only ->start, and ended up deciding ->start was the right place. The compatible string is probably a little odd as it has nothing to do with linux per se - however, I chose that to make .dts snippets reusable between device trees used with U-Boot and linux, and this is the (only) compatible string that linux' corresponding driver and DT binding accepts. I have asked whether one should/could add "wdt-gpio" to that binding, but the answer was no: https://lore.kernel.org/lkml/CAL_JsqKEGaFpiFV_oAtE+S_bnHkg4qry+bhx2EDs=NSbVf_giA@mail.gmail.com/ If someone feels strongly about this, I can certainly remove the "linux," part from the string - it probably wouldn't the only place where one can't reuse a DT snippet as-is between linux and U-Boot. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * watchdog: wdt-uclass.c: handle all DM watchdogs in watchdog_reset()Rasmus Villemoes2021-08-312-26/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A board can have and make use of more than one watchdog device, say one built into the SOC and an external gpio-petted one. Having wdt-uclass only handle the first is both a little arbitrary and unexpected. So change initr_watchdog() so we visit (probe) all DM watchdog devices, and call the init_watchdog_dev helper for each. Similarly let watchdog_reset() loop over the whole uclass - each having their own ratelimiting metadata, and a separate "is this device running" flag. This gets rid of the watchdog_dev member of struct global_data. We do, however, still need the GD_FLG_WDT_READY set in initr_watchdog(). This is because watchdog_reset() can get called before DM is ready, and I don't think we can call uclass_get() that early. The current code just returns 0 if "getting" the first device fails - that can of course happen because there are no devices, but it could also happen if its ->probe call failed. In keeping with that, continue with the handling of the remaining devices even if one fails to probe. This is also why we cannot use uclass_probe_all(). If desired, it's possible to later add a per-device "u-boot,autostart" boolean property, so that one can do CONFIG_WATCHDOG_AUTOSTART per-device. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * board: x530: switch to wdt_stop_all()Rasmus Villemoes2021-08-311-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the gd->watchdog_dev member is going away, switch to using the new wdt_stop_all() helper. While here, clean up the preprocessor conditional: The ->watchdog_dev member is actually guarded by CONFIG_WDT [disabling that in x530_defconfig while keeping CONFIG_WATCHDOG breaks the build], and in the new world order so is the existence of the wdt_stop_all() function. Actually, existence of wdt_stop_all() depends on CONFIG_${SPL_}WDT, so really spell the condition using CONFIG_IS_ENABLED, and make it a C rather than cpp if. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * watchdog: wdt-uclass.c: add wdt_stop_all() helperRasmus Villemoes2021-08-312-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the watchdog_dev member of struct global_data is going away in favor of the wdt-uclass handling all watchdog devices, prepare for that by adding a helper to call wdt_stop() on all known devices. If an error is encountered, still do wdt_stop() on remaining devices, but remember and return the first error seen. Initially, this will only be used in one single place (board/alliedtelesis/x530/x530.c). Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * sandbox: disable CONFIG_WATCHDOG_AUTOSTARTRasmus Villemoes2021-08-312-0/+2
| | | | | | | | | | | | | | | | | | | | For the unit tests, it is more convenient if the tests are in charge of when the watchdog devices are started and stopped, so prevent wdt-uclass from doing it automatically. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * watchdog: wdt-uclass.c: keep track of each device's running stateRasmus Villemoes2021-08-311-4/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | As a step towards handling all DM watchdogs in watchdog_reset(), use a per-device flag to keep track of whether the device has been started instead of a bit in gd->flags. We will still need that bit to know whether we are past initr_watchdog() and hence have populated gd->watchdog_dev - incidentally, that is how it was used prior to commit 9c44ff1c5f3c. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * watchdog: wdt-uclass.c: refactor initr_watchdog()Rasmus Villemoes2021-08-311-16/+21
| | | | | | | | | | | | | | | | | | | | | | | | In preparation for handling all DM watchdogs in watchdog_reset(), pull out the code which handles starting (or not) the gd->watchdog_dev device. Include the device name in various printfs. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * watchdog: wdt-uclass.c: neaten UCLASS_DRIVER definitionRasmus Villemoes2021-08-311-4/+4
| | | | | | | | | | | | | | | | | | The addition of .pre_probe and .per_device_auto made this look bad. Fix it. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * watchdog: wdt-uclass.c: introduce struct wdt_privRasmus Villemoes2021-08-311-20/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | As preparation for having the wdt-uclass provided watchdog_reset() function handle all DM watchdog devices, and not just the first such, introduce a uclass-owned struct to hold the reset_period and next_reset, so these become per-device instead of being static variables. No functional change intended. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * watchdog: wdt-uclass.c: use wdt_start() in wdt_expire_now()Rasmus Villemoes2021-08-311-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | wdt_start() does the "no ->start? return -ENOSYS" check, don't open-code that in wdt_expire_now(). Also, wdt_start() maintains some global (and later some per-device) state, which would get out of sync with this direct method call - not that it matters much here since the board is supposed to reset very soon. Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
* | Merge branch '2021-08-31-kconfig-migrations-part2' into nextTom Rini2021-08-311568-3018/+2880
|\ \ | |/ |/| | | | | | | | | | | | | | | | | - Further CONFIG to Kconfig migrations - Some DDR related symbols - CONFIG_SYS_LOAD_ADDR moved, loadaddr always set in environment now. - Finish MX7D, convert IMX_CONFIG - Some RAMBOOT related options - L1 cache size converted and named consistently for all arches. A further follow-up to rename things for even better clarity is welcome. - CONFIG_SKIP_LOWLEVEL_INIT, CONFIG_SYS_MALLOC_LEN
| * Kconfig: Remove all default n/no optionsMichal Simek2021-08-3165-224/+1
| | | | | | | | | | | | | | | | default n/no doesn't need to be specified. It is default option anyway. Signed-off-by: Michal Simek <michal.simek@xilinx.com> [trini: Rework FSP_USE_UPD portion] Signed-off-by: Tom Rini <trini@konsulko.com>
| * Convert CONFIG_SYS_MALLOC_LEN to KconfigTom Rini2021-08-31953-740/+690
| | | | | | | | | | | | | | | | | | This converts the following to Kconfig: CONFIG_SYS_MALLOC_LEN Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Sean Anderson <seanga2@gmail.com> Reviewed-by: Rick Chen <rick@andestech.com>
| * Convert CONFIG_SKIP_LOWLEVEL_INIT et al to KconfigTom Rini2021-08-31457-310/+512
| | | | | | | | | | | | | | | | | | | | | | | | This converts the following to Kconfig: CONFIG_SKIP_LOWLEVEL_INIT CONFIG_SKIP_LOWLEVEL_INIT_ONLY In order to do this, we need to introduce SPL and TPL variants of these options so that we can clearly disable these options only in SPL in some cases, and both instances in other cases. Signed-off-by: Tom Rini <trini@konsulko.com>
| * Finish converting CONFIG_SYS_CACHELINE_SIZE to KconfigTom Rini2021-08-3135-103/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We move the SYS_CACHE_SHIFT_N options from arch/arm/Kconfig to arch/Kconfig, and introduce SYS_CACHE_SHIFT_4 to provide a size of 16. Introduce select statements for other architectures based on current usage. For MIPS, we take the existing arch-specific symbol and migrate to the generic symbol. This lets us remove a little bit of otherwise unused code. Cc: Alexey Brodkin <alexey.brodkin@synopsys.com> Cc: Anup Patel <anup.patel@wdc.com> Cc: Atish Patra <atish.patra@wdc.com> Cc: Bin Meng <bmeng.cn@gmail.com> Cc: Leo <ycliang@andestech.com> Cc: Palmer Dabbelt <palmer@dabbelt.com> Cc: Paul Walmsley <paul.walmsley@sifive.com> Cc: Sean Anderson <seanga2@gmail.com> Cc: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Sean Anderson <seanga2@gmail.com> Reviewed-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Reviewed-by: Rick Chen <rick@andestech.com>
| * ls1046ardb_qspi*: Enable RAMBOOT_PBLTom Rini2021-08-313-0/+9
| | | | | | | | | | | | | | | | | | | | Based on include/configs/ls1046ardb.h it seems that CONFIG_RAMBOOT_PBL should have been enabled, but was not. Enable and migrate the values to Kconfig. Cc: Mingkai Hu <mingkai.hu@nxp.com> Cc: Rajesh Bhagat <rajesh.bhagat@nxp.com> Signed-off-by: Tom Rini <trini@konsulko.com>
| * Convert CONFIG_RAMBOOT_PBL et al to KconfigTom Rini2021-08-3166-274/+201
| | | | | | | | | | | | | | | | | | This converts the following to Kconfig: CONFIG_RAMBOOT_PBL CONFIG_SYS_FSL_PBL_PBI CONFIG_SYS_FSL_PBL_RCW Signed-off-by: Tom Rini <trini@konsulko.com>
| * Convert CONFIG_QSPI_BOOT to KconfigTom Rini2021-08-3118-18/+6
| | | | | | | | | | | | | | This converts the following to Kconfig: CONFIG_QSPI_BOOT Signed-off-by: Tom Rini <trini@konsulko.com>
| * Convert CONFIG_SYS_FSL_DDR4 to KconfigTom Rini2021-08-3111-14/+4
| | | | | | | | | | | | | | This converts the following to Kconfig: CONFIG_SYS_FSL_DDR4 Signed-off-by: Tom Rini <trini@konsulko.com>
| * configs: Remove unused IMX_NAND symbolTom Rini2021-08-312-2/+0
| | | | | | | | | | | | The symbol CONFIG_IMX_NAND is not referenced in the code, remove it. Signed-off-by: Tom Rini <trini@konsulko.com>
| * nitrogen6x: Populate FDTFILE at build-time for all platformsTom Rini2021-08-312-10/+1
| | | | | | | | | | | | | | | | | | | | Rather than using CONFIG_SABRELITE to set FDTFILE for only that platform, switch to always setting this based on CONFIG_DEFAULT_DEVICE_TREE as this should always match the kernel device tree name anyhow. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Troy Kisky <troy.kisky@boundarydevices.com>
| * nitrogen6x: Migrate DDR_MB to KconfigTom Rini2021-08-3110-9/+11
| | | | | | | | | | | | | | | | | | Move the CONFIG_DDR_MB symbol to Kconfig. A later clean-up would be to make dynamic memory size detection work based on how this is done on other i.MX6 platforms. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Troy Kisky <troy.kisky@boundarydevices.com>
| * Convert CONFIG_SPL to KconfigTom Rini2021-08-312-2/+1
| | | | | | | | | | | | | | This converts the following to Kconfig: CONFIG_SPL Signed-off-by: Tom Rini <trini@konsulko.com>
| * imx: Finish migration of IMX_CONFIG to KconfigTom Rini2021-08-31193-137/+198
| | | | | | | | | | | | | | | | | | - Provide a default Kconfig value of the default script - Largely continue to define this via the board Kconfig file - For the boards that select a script based on defconfig rather than TARGET, keep this within the defconfig. Signed-off-by: Tom Rini <trini@konsulko.com>
| * imx: Introduce CONFIG_MACH_IMXTom Rini2021-08-312-0/+16
| | | | | | | | | | | | | | | | | | Currently, there is no over-arching symbol for access to arch/arm/mach-imx nor the CONFIG symbols that are common over all of these related platforms. This new CONFIG symbol will allow us to start down this path. Signed-off-by: Tom Rini <trini@konsulko.com>
| * Convert CONFIG_MX7D to KconfigTom Rini2021-08-313-2/+3
| | | | | | | | | | | | | | | | This converts the following to Kconfig: CONFIG_MX7D Cc: Oleksandr Suvorov <oleksandr.suvorov@toradex.com> Signed-off-by: Tom Rini <trini@konsulko.com>
| * Convert CONFIG_SYS_LOAD_ADDR to KconfigTom Rini2021-08-31935-564/+636
| | | | | | | | | | | | | | Now that we have consistent usage, migrate this symbol to Kconfig. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Rick Chen <rick@andestech.com>
| * global: Convert CONFIG_LOADADDR to CONFIG_SYS_LOADADDRTom Rini2021-08-31166-355/+141
| | | | | | | | | | | | | | | | | | - In most of the codebase, we reference CONFIG_SYS_LOAD_ADDR and not CONFIG_LOADADDR. - Generally, CONFIG_SYS_LOADADDR is set to CONFIG_LOADADDR and then as noted, we use CONFIG_SYS_LOADADDR. Signed-off-by: Tom Rini <trini@konsulko.com>
| * qfw: Switch to CONFIG_SYS_LOAD_ADDR from CONFIG_LOADADDRTom Rini2021-08-312-6/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | All platforms define CONFIG_SYS_LOAD_ADDR, but only some define CONFIG_LOADADDR. Very very rarely are these not the same address, and qemu-ppce500 is one such case. However, based on reading the history of the code, this mismatched value was simply a copy-paste from other PowerPC platforms where it is this unused currently. Switch the code to use CONFIG_SYS_LOAD_ADDR and update the documentation. Cc: Bin Meng <bmeng.cn@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
| * Convert CONFIG_SPL_MPC8XXX_INIT_DDR_SUPPORT to KconfigTom Rini2021-08-314-2/+2
| | | | | | | | | | | | | | This converts the following to Kconfig: CONFIG_SPL_MPC8XXX_INIT_DDR_SUPPORT Signed-off-by: Tom Rini <trini@konsulko.com>
| * nxp: Migrate a number of DDR related symbols to KconfigTom Rini2021-08-31159-91/+262
| | | | | | | | | | | | | | | | | | | | - Guard most of the options in drivers/ddr/fsl/Kconfig with SYS_FSL_DDR || SYS_FSL_MMDC. - Migrate FSL_DMA, DDR_ECC, DDR_ECC_CMD, and ECC_INIT_VIA_DDRCONTROLLER to Kconfig. - Clean up the logic for including the DDR_ECC_CMD code. Signed-off-by: Tom Rini <trini@konsulko.com>
| * nxp: Migrate CONFIG_DDR_CLK_FREQ to KconfigTom Rini2021-08-31152-89/+166
| | | | | | | | | | | | | | | | | | | | | | | | As this symbol can either be a fixed value or the function get_board_ddr_clk, migration is tricky. Introduce a choice of DYNAMIC or STATIC_DDR_CLK_FREQ. If DYNAMIC, we continue to use the board defined get_board_ddr_clk function. If STATIC, set CONFIG_DDR_CLK_FREQ to that value and now include/clock_legacy.h contains the function prototype or defines get_board_ddr_clk() to that static value. Update callers to test for DYNAMIC or STATIC. Signed-off-by: Tom Rini <trini@konsulko.com>
| * ddr: Migrate DDR_SPD to KconfigTom Rini2021-08-313-0/+11
| | | | | | | | | | | | | | | | | | Move the symbol that controls building some JEDEC SPD support functions to Kconfig. This is required on the TI keystone 2 platforms and very frequently (but not always) used on large number of Freescale/NXP platforms, so use imply there. Signed-off-by: Tom Rini <trini@konsulko.com>
| * mvebe: Migrate CONFIG_DDR_LOG_LEVEL to KconfigTom Rini2021-08-312-4/+14
| | | | | | | | | | | | Move this specific option to Kconfig. Signed-off-by: Tom Rini <trini@konsulko.com>
| * mvebu: ddr: Rename CONFIG_DDR_FIXED_SIZE to CONFIG_SYS_SDRAM_SIZETom Rini2021-08-313-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | We have a number of CONFIG symbols to express the fixed size of system memory. For now, rename CONFIG_DDR_FIXED_SIZE to CONFIG_SYS_SDRAM_SIZE and adjust usage to match that CONFIG_SYS_SDRAM_SIZE expects the entire size rather than MiB. Cc: Marek Behún <marek.behun@nic.cz> Cc: Stefan Roese <sr@denx.de> Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Marek Behún <marek.behun@nic.cz>
| * mvebu: Migrate CONFIG_DDR_32BIT/64BIT to KconfigTom Rini2021-08-313-3/+14
| | | | | | | | | | | | | | | | | | Move CONFIG_DDR_32BIT/64BIT to Kconfig as a choice for Armada XP platforms. Make 64bit the default as this mirrors the current code. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Marek Behún <marek.behun@nic.cz> Reviewed-by: Stefan Roese <sr@denx.de>
| * global: Remove unused or unnecessary CONFIG symbols related to DDRTom Rini2021-08-3011-134/+2
|/ | | | | | | | These symbols are now either unused or were only used within the config file to determine other logic, which could be done in a way that doesn't further pollute the CONFIG namespace. Signed-off-by: Tom Rini <trini@konsulko.com>
* Merge branch '2021-08-30-kconfig-migrations-part1' into nextTom Rini2021-08-30789-7086/+2834
|\ | | | | | | | | | | | | | | | | | | | | | | - Begin merging some Kconfig migration, and CONFIG namespace cleanup series in. This gives us: - A number of I2C symbols migrated over - DWC2, i8042, altera_spi and a few other areas updated to use CFG not CONFIG for the concept of "configuration space" defines. - Rename CONFIG_EXTRA_ENV_BOARD_SETTINGS to EXTRA_ENV_BOARD_SETTINGS - Some dead code removal. - Rename a number of CONFIG symbols that were only referenced within the config header to not use CONFIG as a prefix.
| * Kconfig: Use spaces not tabs in Kconfig entiresWIP/2021-08-30-kconfig-migrations-part1-nextTom Rini2021-08-302-3/+3
| | | | | | | | | | | | | | While the Kconfig language seems to accept either form of whitespace, we use a space throughout the project, except in these spots. Signed-off-by: Tom Rini <trini@konsulko.com>
| * astro_mcf5373l: Rework ASTRO_ID logicTom Rini2021-08-301-7/+7
| | | | | | | | | | | | | | | | | | Rather than using CONFIG namespace for logic internal to include/configs/astro_mcf5373l.h to select ASTRO_ID (and populate the default environment), strip CONFIG from the various options used and set. Signed-off-by: Tom Rini <trini@konsulko.com>
| * mpc83xx: Update commentTom Rini2021-08-301-1/+1
| | | | | | | | | | | | | | | | Update the comment here to refer to PCI_CONFIG_ADDRESS rather than CONFIG_ADDRESS. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
| * spi: altera_spi: Do not abuse CONFIG namespaceTom Rini2021-08-301-4/+2
| | | | | | | | | | | | | | | | The value CONFIG_ALTERA_SPI_IDLE_VAL is never re-defined by a board. Rename this to ALTERA_SPI_IDLE_VAL. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
| * video: Remove ati_radeon_fbTom Rini2021-08-305-3243/+0
| | | | | | | | | | | | | | This driver is currently unused. Remove. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
| * global: Remove dead code that starts with CONFIG_[0-9A]Tom Rini2021-08-3014-253/+3
| | | | | | | | | | | | | | This removes a number of spots of dead code based on symbols that start with CONFIG_[0-9] or CONFIG_A. Signed-off-by: Tom Rini <trini@konsulko.com>
| * i8042: Do not abuse CONFIG namespaceTom Rini2021-08-302-8/+8
| | | | | | | | | | | | | | | | | | | | This driver uses the CONFIG namespace to set the chips internal CONFIG namespace related bits. However, CONFIG is reserved for the top-level Kconfig based configuration system. Use CFG as the namespace here instead to avoid pollution. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
| * ppc: Rework some hard-coded BOOTCOMMANDSTom Rini2021-08-3023-76/+76
| | | | | | | | | | | | | | | | There are an assortment of hard-coded CONFIG_BOOTCOMMAND options in some board headers. Rework these so that they do not add to the CONFIG namespace. Signed-off-by: Tom Rini <trini@konsulko.com>
| * arm: Migrate GICV2 / GICV3 to KconfigTom Rini2021-08-3018-30/+36
| | | | | | | | | | | | | | | | Migrate CONFIG_GICV2 and CONFIG_GICV3 to Kconfig. We still have the GIC related registers that need to be handled more cleanly but start by moving this symbol to Kconfig. Signed-off-by: Tom Rini <trini@konsulko.com>
View Lorry Controller Status