- 10 2月, 2019 13 次提交
-
-
由 Lokesh Vutla 提交于
Use regulator_set_enable_if_allowed() api instead of regulator_set_enable() while enabling io regulators. This way the driver doesn't see an error when disabling an always-on regulator and when enabling is not supported. Reviewed-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
regulator_set_enable() api throws an error in the following three cases: - when requested to disable an always-on regulator - when set_enable() ops not provided by regulator driver - when enabling is actually failed.(Error returned by the regulator driver) Sometimes consumer drivers doesn't want to track the first two scenarios and just need to worry about the case where enabling is actually failed. But it is also a good practice to have an error value returned in the first two cases. So introduce an api regulator_set_enable_if_allowed() which ignores the first two error cases and returns an error as given by regulator driver. Consumer drivers can use this api need not worry about the first two error conditions. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Lokesh Vutla 提交于
This reverts commit e17e0ceb. It is advised to return an error when trying to disable an always-on regulator and let the consumer driver handle the error if needed. Reviewed-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Simon Glass 提交于
This is no-longer used. Drop it. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de>
-
由 Simon Glass 提交于
This enum still exists but we can shrink it a little based on recent driver-model conversions with samsung. Update it to remove unused items. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de>
-
由 Simon Glass 提交于
Now that these boards use driver model we can drop the old code. At present s5p_mmc_init() is still used by goni and smdkv310 so cannot be removed unless we remove those boards. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NMinkyu Kang <mk7.kang@samsung.com>
-
由 Simon Glass 提交于
This function is not needed now since the audio codecs have been converted to proper drivers. The codec-enable GPIO is handled there. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NMinkyu Kang <mk7.kang@samsung.com>
-
由 Simon Glass 提交于
Update the flashmap so that this board can be started over USB A-A. It is slightly different from snow. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de>
-
由 Simon Glass 提交于
Update the spring settings to use this codec, which is what it actually shipped with. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de>
-
由 Simon Glass 提交于
This chip is used by spring. Add a driver for it and update the samsung_sound driver to pick it up. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Move all exynos boards over to use CONFIG_BLK. This converts s5p_goni also, but adding dummy functions for pinmux and peripheral ID. This will not function correctly, but gives the maintainer more time to convert the board if desired. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NMinkyu Kang <mk7.kang@samsung.com>
-
由 Simon Glass 提交于
At present the model is shown twice, once in the generic code and once in the exynos code. Drop the latter. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NMinkyu Kang <mk7.kang@samsung.com>
-
由 Simon Glass 提交于
This converts the following to Kconfig: CONFIG_BOARD_TYPES Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLukasz Majewski <lukma@denx.de> Acked-by: NAlexey Brodkin <abrodkin@synopsys.com> Reviewed-by: NMinkyu Kang <mk7.kang@samsung.com>
-
- 08 2月, 2019 3 次提交
-
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
Rsync all defconfig files using moveconfig.py Signed-off-by: NTom Rini <trini@konsulko.com>
-
-
- 07 2月, 2019 21 次提交
-
-
由 Vignesh R 提交于
Add myself as co-maintainer for U-Boot SPI NOR subsystem. Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NJagan Teki <jagan@openedev.com> [jagan: drop mtd/spi file from SPI entry] Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Vignesh R 提交于
Now that new SPI NOR layer uses stateless 4 byte opcodes by default, don't enable SPI_FLASH_BAR. For SPI controllers that cannot support 4-byte addressing, (stm32_qspi.c, fsl_qspi.c, mtk_qspi.c, ich.c, renesas_rpc_spi.c) add an imply clause to enable SPI_FLASH_BAR so as to not break functionality. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
SF_DUAL_FLASH claims to enable support for SF_DUAL_STACKED_FLASH and SF_DUAL_PARALLEL_FLASH. But, in current U-Boot code, grepping for above enums yield no user and therefore support seems to be incomplete. Remove these configs so as to avoid confusion. Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
SPL only needs to be able to read from SPI Flash to load next stage and does not really need write/erase etc. Therefore in order to reduce SPI Flash code size in SPL, enable SPI_FLASH_TINY, that only supports reading from SPI flash, as default. Note: Since, SPI_FLASH_TINY does not support SPI_FLASH_BAR, SPI_FLASH_TINY is not enabled for boards with SPI controllers that cannot support 4 byte addressing. Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Add a tiny SPI flash stack that just supports reading data/images from SPI flash. This is useful for boards that have SPL size constraints and would need to use SPI flash framework just to read images/data from flash. There is approximately 1.5 to 2KB savings with this. Based on prior work of reducing spi flash id table by Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
spi_flash and spi_flash_ids are no longer needed after SPI NOR migration. Remove them. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Switch spi_flash_* interfaces to call into new SPI NOR framework via MTD layer. Fix up sf_dataflash to work in legacy way. And update sandbox to use new interfaces/definitions Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Linux uses "jedec,spi-nor" as compatible string for JEDEC compatible SPI Flash device nodes. Therefore make U-Boot also to look for the same compatible string so that we can use Linux DTS files as is. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: Horatiu Vultur <horatiu.vultur@microchip.com Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
For legacy reasons, we will have to keep around U-Boot specific SPI_FLASH_BAR and SPI_TX_BYTE. Add them back to the new framework Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Sync Serial Flash Discoverable Parameters (SFDP) parsing support from Linux. This allows auto detection and configuration of Flash parameters. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Sync changes from Linux SPI NOR framework to add 4 byte addressing support. This is required in order to support flashes like MT35x that no longer support legacy Bank Address Register(BAR) way of accessing >16MB region. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Many SPI controllers have special MMIO interfaces which provide accelerated read/write access but require knowledge of flash parameters to make use of it. Recent spi-mem layer provides a way to support such controllers. Therefore, add spi-mem support to spi-nor-core as a way to support SPI controllers with MMIO interface. SPI MEM layer takes care of translating spi_mem_ops to spi_xfer()s in case of legacy SPI controllers. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Current U-Boot SPI NOR support (sf layer) is quite outdated as it does not support 4 byte addressing opcodes, SFDP table parsing and different types of quad mode enable sequences. Many newer flashes no longer support BANK registers used by sf layer to a access >16MB of flash address space. So, sync SPI NOR framework from Linux v4.19 that supports all the above features. Start with basic sync up that brings in basic framework subsequent commits will bring in more features. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Add hweight*() macros required for moving to new SF layer Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NJagan Teki <jagan@openedev.com>
-
由 Vignesh R 提交于
Add non DM version of SPI_MEM to support easy migration to new SPI NOR framework. This can be removed once DM_SPI conversion is complete. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
It is necessary to call spi_claim_bus() before starting any SPI transactions and this restriction would also apply when calling spi-mem operations. Therefore claim and release bus before requesting transfer via exec_op. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
Extend spi_mem_adjust_op_size() to take spi->max_write_size and spi->max_read_size into account. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
SPI controllers support all types of SPI modes including dual/quad bus widths. Therefore remove constraint wrt SPI mode from spi-mem layer. Signed-off-by: NVignesh R <vigneshr@ti.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Tested-by: NStefan Roese <sr@denx.de> Tested-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Vignesh R 提交于
In arch/sandbox/include/asm/types.h we have Therefore for 32 bit Sandbox build BITS_PER_LONG turns out to be 32 as CONFIG_PHYS64 is not set This messes up the current logic of GENMASK macro due to mismatch b/w size of unsigned long (64 bit) and that of BITS_PER_LONG. Fix this by using CONFIG_SANDBOX_BITS_PER_LONG which is set to 64/32 based on the host machine on which its being compiled. Without this patch: GENMASK(14,0) => 0x7fffffffffff After this patch: GENMASK(14,0) => 0x7fff Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Vignesh R 提交于
Completely move CONFIG_SPI_FLASH from remaining board header files to defconfigs Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
-
由 Hannes Schmelzer 提交于
commit fdce9d35 ("arm: dts: am33xx: Sync dts with Linux 4.20.0") did remove the "u-boot,dm-spl" flag from the 'ocp' bus which was introduced with commit 19aa4ac0 ("dts: am33xx: add u-boot, dm-spl to ocp bus") Due to this all boards having CONFIG_SPL_OF_CONTROL enabled are broken because they cannot bind/probe the boot-media interface during SPL stage. This commit introduces the 'am33xx-u-boot.dtsi' which is included with the auto include mechanism. The am33xx-u-boot-dtsi adds the important "u-boot,dm-pre-reloc" to the 'ocp bus' (the root bus of almost all peripherals, at least the bootable ones). The peripherials (mmc, spi, ...) needed during SPL stage need to be equipped with the 'u-boot,dm-pre-reloc' in their responsible dts file. Signed-off-by: NHannes Schmelzer <hannes.schmelzer@br-automation.com>
-
- 06 2月, 2019 3 次提交
-
-
由 Eugen Hristev 提交于
Update Atmel AT91 maintainership Signed-off-by: NEugen Hristev <eugen.hristev@microchip.com> Acked-by: NNicolas Ferre <nicolas.ferre@microchip.com>
-
由 York Sun 提交于
Change maintainers to Prabhakar Kushwaha for fsl-qoriq, mpc85xx and mpc86xx. Signed-off-by: NYork Sun <york.sun@nxp.com> Reviewed-by: NTom Rini <trini@konsulko.com> Acked-by: NPrabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
-
git://git.denx.de/u-boot-marvell由 Tom Rini 提交于
- Move Armada XP / 38x PCIe driver to DM_PCI from me - Move Armada XP / 38x LCD driver to DM_VIDEO from me - Add uDPU board (Armada-3720) from Vladimir [trini: Fix warning in pci-uclass.c by removing ret from pci_uclass_child_post_bind as it no longer calls functions with a return code to catch.] Signed-off-by: Tom Rini <trini@konsulko.com>II
-