Re: [U-Boot] [PATCH] mmc: Poll for broken card detection case

On 01/23/2018 12:25 PM, Jaehoon Chung wrote: > On 01/23/2018 12:10 PM, Jun Nie wrote: >> 2018-01-23 10:00 GMT+08:00 Jaehoon Chung : >>> On 01/22/2018 09:21 PM, Jun Nie wrote: 2018-01-22 13:03 GMT+08:00 Jaehoon Chung : > Hi, > > On

Re: [U-Boot] [PATCH 1/8] mtd: nand: sunxi: Fix strength minimum value

On Wed, 24 Jan 2018 01:44:47 +0100 Miquel Raynal wrote: > When no requirement in Device Tree is given about the ECC strength and > step size, the engine should fallback on the minimal working case for > this engine (16b/1024B) instead of the NAND chip

Re: [U-Boot] [PATCH 4/8] spl: nand: sunxi: Enhancements and cleaning

Hi, On Wed, Jan 24, 2018 at 01:44:50AM +0100, Miquel Raynal wrote: > Do some cleaning in sunxi NAND SPL driver like adding helpers and > clearing flags at the right spot > > Signed-off-by: Miquel Raynal I'm not really fond of these kind of wildcard patches,

Re: [U-Boot] [PATCH 3/8] sunxi: Allow SPL to be compiled for sun8i platforms

Hi, On Wed, Jan 24, 2018 at 01:44:49AM +0100, Miquel Raynal wrote: > Add some clocks/PLL definitions and the dependency on MACH_SUN8I in > Kconfig so the SPL could be compiled to boards using A33 SoCs. > > Signed-off-by: Miquel Raynal The SPL can already be

Re: [U-Boot] [PATCH 2/8] spl: nand: sunxi: Fix second case of modulo by zero error

On Wed, Jan 24, 2018 at 01:44:48AM +0100, Miquel Raynal wrote: > In the nand_read_buffer() step, the seed is calculated by doing a modulo > by conf->nseeds which is always zero when not using the randomizer (most > of SLC NANDs). > > This situation turns out to lead to a run time freeze. > >

Re: [U-Boot] [PATCH 1/8] mtd: nand: sunxi: Fix strength minimum value

Hi, On Wed, Jan 24, 2018 at 01:44:47AM +0100, Miquel Raynal wrote: > When no requirement in Device Tree is given about the ECC strength and > step size, the engine should fallback on the minimal working case for > this engine (16b/1024B) instead of the NAND chip requirement which might > be

Re: [U-Boot] [PATCH 3/3] configs: odroid-xu3: enable the configs relevant to regulator

On 01/24/2018 01:04 AM, Anand Moon wrote: > Hi Jaehoon Chung, > > On 16 January 2018 at 12:03, Jaehoon Chung wrote: >> Enable the CONFIG_CMD_REGULATOR and CONFIG_DM_REGULATOR_S2MPS11. >> >> Signed-off-by: Jaehoon Chung >> --- >>

Re: [U-Boot] [PATCH 2/3] power: pmic: s2mps11: probe the regulator driver

On 01/24/2018 01:02 AM, Anand Moon wrote: > Hi JaeHoon Chung, > > On 16 January 2018 at 12:03, Jaehoon Chung wrote: >> Add the probe function to support the s2mps11 regulator driver. >> >> Signed-off-by: Jaehoon Chung >> --- >>

[U-Boot] [GIT PULL] Please pull u-boot-mmc master

Dear Tom, Could you pull these patches to u-boot/master? If there is a problem, let me know, plz. The following changes since commit 557767ed29968af0294e3aae48433e5d5a298e0b: Merge git://git.denx.de/u-boot-marvell (2018-01-20 08:39:47 -0500) are available in the Git repository at:

Re: [U-Boot] [PATCH] mmc: fix to assign to corret clock value when clock is enabling

On 01/24/2018 04:01 AM, Stephen Warren wrote: > On 01/22/2018 10:04 PM, Jaehoon Chung wrote: >> When clock is enabling, it's assigned to 0 as mmc->clock. >> Then it can't initialize any card. >> Fix to assign to correct clock value as mmc->cfg->f_min or f_max. > > Tested-by: Stephen Warren

Re: [U-Boot] [PATCH 1/3] power: regulator: s2mps11: add a regulator driver for s2mps11

On 01/24/2018 01:01 AM, Anand Moon wrote: > Hi JaeHoon Chung, > > On 16 January 2018 at 12:03, Jaehoon Chung wrote: >> exynos5422 has the s2mps11 PMIC. >> s2mps11 pmic has the 10-BUCK and 38-LDO regulators. >> Each IP and devices in exynos5422 can be controlled by each

Re: [U-Boot] Pull request: u-boot-spi/master

On Tue, Jan 23, 2018 at 3:58 PM, Daniel Schwierzeck wrote: > > > On 22.01.2018 21:55, Álvaro Fernández Rojas wrote: >> Hi Daniel, >> >> >> El 22/01/2018 a las 21:26, Daniel Schwierzeck escribió: >>> >>> On 22.01.2018 18:14, Tom Rini wrote: On Mon, Jan 22, 2018

Re: [U-Boot] [PATCH v6 2/2] common: Generic firmware loader for file system

On 24.01.2018 06:13, Chee, Tien Fong wrote: On Tue, 2018-01-23 at 10:13 +0100, Simon Goldschmidt wrote: On 23.01.2018 09:31, Chee, Tien Fong wrote: On Tue, 2018-01-23 at 08:58 +0100, Simon Goldschmidt wrote: On 27.12.2017 06:04, tien.fong.c...@intel.com wrote: From: Tien Fong Chee

[U-Boot] [PATCH v3 0/3] cadence-quadspi: Fix issues with non 32bit aligned accesses

This series reverts use of bounce_buf.c for non-DMA related alignment restriction and replaces it with local bounce buffer to handle problems with non 32 bit aligned writes on TI platforms. Based on top of Jason's series: [PATCH v6 0/4] spi: cadence_spi: Adopt Linux DT bindings Tested on K2G EVM.

[U-Boot] [PATCH v3 1/3] Revert "spi: cadence_qspi_apb: Use 32 bit indirect read transaction when possible"

From: Goldschmidt Simon This reverts commit b63b46313ed29e9b0c36b3d6b9407f6eade40c8f. This commit changed cadence_qspi_apb to use bouncebuf.c, which invalidates the data cache after reading. This is meant for dma transfers only and breaks the cadence_qspi

[U-Boot] [PATCH v3 3/3] spi: cadence_qspi_apb: Make flash writes 32 bit aligned

Make flash writes 32 bit aligned by using bounce buffers to deal with non 32 bit aligned buffers. This is required because as per TI K2G TRM[1], the external master is only permitted to issue 32-bit data interface writes until the last word of an indirect transfer. Otherwise indirect writes is

[U-Boot] [PATCH v3 2/3] Revert "spi: cadence_qspi_apb: Use 32 bit indirect write transaction when possible"

This reverts commit 57897c13de03ac0136d64641a3eab526c6810387. Using bounce_buf.c to handle non-DMA alignment problems is bad as bounce_buf.c does cache manipulations which is not required. Therefore revert this patch in favour of local bounce buffer solution in the next patch. Signed-off-by:

Re: [U-Boot] [PATCH v6 2/2] common: Generic firmware loader for file system

On Tue, 2018-01-23 at 10:13 +0100, Simon Goldschmidt wrote: > On 23.01.2018 09:31, Chee, Tien Fong wrote: > > > > On Tue, 2018-01-23 at 08:58 +0100, Simon Goldschmidt wrote: > > > > > > On 27.12.2017 06:04, tien.fong.c...@intel.com wrote: > > > > > > > > From: Tien Fong Chee

Re: [U-Boot] [PATCH V2] Convert CONFIG_CMD_NAND to Kconfig

On Tue, Jan 23, 2018 at 8:09 PM, Adam Ford wrote: > This converts the following to Kconfig: >CONFIG_CMD_NAND > > Signed-off-by: Adam Ford > --- > V2: Remove SUNXI default since this is selected when NAND_SUNXI is > Since they cannot both

[U-Boot] [PATCH V2] Convert CONFIG_CMD_NAND to Kconfig

This converts the following to Kconfig: CONFIG_CMD_NAND Signed-off-by: Adam Ford --- V2: Remove SUNXI default since this is selected when NAND_SUNXI is Since they cannot both recursively check each other. This was causing some trouble. V1: Several boards

[U-Boot] Please pull u-boot-fsl-qoriq master

Tom, The following changes since commit 485c13c7536731991c59f7b3432bc33c9dafb0f0: Merge git://git.denx.de/u-boot-dm (2018-01-21 20:13:29 -0500) are available in the git repository at: git://git.denx.de/u-boot-fsl-qoriq.git 6c8945ec41cb7bff27fbacc88316e3e557c20240 for you to fetch changes

Re: [U-Boot] [PATCH] cmd: Kconfig: Make CMD_NAND select NAND

On Tue, Jan 23, 2018 at 12:10 PM, Andrew F. Davis wrote: > On 01/23/2018 12:01 PM, Adam Ford wrote: >> On Tue, Jan 23, 2018 at 11:15 AM, Andrew F. Davis wrote: >>> On 01/23/2018 04:40 AM, Adam Ford wrote: Many boards check for CONFIG_CMD_NAND instead of

[U-Boot] [PATCH 7/8] sunxi: dts: Add NAND node to sun8i DTSI

Add the NAND controller node, as well as the definition of the missing pins and clock. Signed-off-by: Miquel Raynal --- arch/arm/dts/sun8i-a23-a33.dtsi | 31 +++ arch/arm/dts/sun8i-a33.dtsi | 8 2 files changed, 39

[U-Boot] [PATCH 6/8] configs: Add NAND support for NES Classic

Add NAND parameters to the Nintendo NES Classic configuration file. Signed-off-by: Miquel Raynal --- configs/Nintendo_NES_Classic_Edition_defconfig | 4 1 file changed, 4 insertions(+) diff --git a/configs/Nintendo_NES_Classic_Edition_defconfig

[U-Boot] [PATCH 5/8] spl: nand: sunxi: use PIO instead of DMA

Because using DMA implementation is not generic and was not developped to work on SoCs like A33, migrate the SPL to use PIO. Signed-off-by: Miquel Raynal --- board/sunxi/board.c | 4 +- drivers/mtd/nand/sunxi_nand_spl.c | 167

[U-Boot] [PATCH 3/8] sunxi: Allow SPL to be compiled for sun8i platforms

Add some clocks/PLL definitions and the dependency on MACH_SUN8I in Kconfig so the SPL could be compiled to boards using A33 SoCs. Signed-off-by: Miquel Raynal --- arch/arm/include/asm/arch-sunxi/clock_sun6i.h | 6 ++ drivers/mtd/nand/Kconfig

[U-Boot] [PATCH 8/8] sunxi: dts: Enable NAND on NES classic

Let the Nintendo NES Classic use the Macronix NAND chip on it. Signed-off-by: Miquel Raynal --- arch/arm/dts/sun8i-r16-nintendo-nes-classic-edition.dts | 14 ++ 1 file changed, 14 insertions(+) diff --git

[U-Boot] [PATCH 4/8] spl: nand: sunxi: Enhancements and cleaning

Do some cleaning in sunxi NAND SPL driver like adding helpers and clearing flags at the right spot Signed-off-by: Miquel Raynal --- drivers/mtd/nand/sunxi_nand_spl.c | 64 +-- 1 file changed, 41 insertions(+), 23 deletions(-)

[U-Boot] [PATCH 2/8] spl: nand: sunxi: Fix second case of modulo by zero error

In the nand_read_buffer() step, the seed is calculated by doing a modulo by conf->nseeds which is always zero when not using the randomizer (most of SLC NANDs). This situation turns out to lead to a run time freeze. Derive this seed only when the randomizer is enabled (and conf->nseeds logically

[U-Boot] [PATCH 1/8] mtd: nand: sunxi: Fix strength minimum value

When no requirement in Device Tree is given about the ECC strength and step size, the engine should fallback on the minimal working case for this engine (16b/1024B) instead of the NAND chip requirement which might be simply unreachable. Signed-off-by: Miquel Raynal

[U-Boot] [PATCH 0/8] Bring NAND support to Nintendo NES Classic

Hello, This series adds fixes to sunxi NAND drivers (SPL and U-Boot), in order to later migrate the SPL driver to use PIO instead of DMA to have more generic code (working also on a A33). Finally, NAND support is added to Nintendo NES Classic through Kconfig and DT additions. Thanks, Miquèl

Re: [U-Boot] [PATCH 1/1] efi_loader: always call Exit after an image returns.

> Am 24.01.2018 um 01:05 schrieb Heinrich Schuchardt : > >> On 01/24/2018 12:31 AM, Alexander Graf wrote: >> >> >>> On 23.01.18 23:46, Heinrich Schuchardt wrote: >>> If an application or driver started via StartImage returns without >>> calling Exit, StartImage has to call

Re: [U-Boot] [PATCH 1/1] efi_loader: always call Exit after an image returns.

On 01/24/2018 12:31 AM, Alexander Graf wrote: > > > On 23.01.18 23:46, Heinrich Schuchardt wrote: >> If an application or driver started via StartImage returns without >> calling Exit, StartImage has to call Exit. This is mandated by the >> UEFI spec and we do the same in efi_do_enter(). >> >>

[U-Boot] Please pull u-boot-coldfire/master

The following changes since commit c761a7e29d703d60208585bb7d8415e00aa22556: Revert "travis-ci: Add qemu-x86_64 target" (2018-01-22 21:06:41 -0500) are available in the Git repository at: git://git.denx.de/u-boot-coldfire.git master for you to fetch changes up to

Re: [U-Boot] [PATCH 1/1] efi_loader: always call Exit after an image returns.

On 23.01.18 23:46, Heinrich Schuchardt wrote: > If an application or driver started via StartImage returns without > calling Exit, StartImage has to call Exit. This is mandated by the > UEFI spec and we do the same in efi_do_enter(). > > The patch looks bigger than it is. To avoid a forward

Re: [U-Boot] [PATCH v4 13/18] efi_loader: fix StartImage bootservice

On 24.01.18 00:16, Heinrich Schuchardt wrote: > On 01/24/2018 12:04 AM, Alexander Graf wrote: >> >> >> On 23.01.18 22:35, Heinrich Schuchardt wrote: >>> On 01/19/2018 09:16 PM, xypron.g...@gmx.de wrote: From: Heinrich Schuchardt The calling convention for the

Re: [U-Boot] [PATCH v4 13/18] efi_loader: fix StartImage bootservice

On 01/24/2018 12:04 AM, Alexander Graf wrote: > > > On 23.01.18 22:35, Heinrich Schuchardt wrote: >> On 01/19/2018 09:16 PM, xypron.g...@gmx.de wrote: >>> From: Heinrich Schuchardt >>> >>> The calling convention for the entry point of an EFI image >>> is always 'asmlinkage'.

[U-Boot] [PATCH v6 2/4] dts: cadence_spi: Sync DT bindings with Linux

Adopt the Linux DT bindings and clean-up duplicate and unused values. Fix indentation of the QSPI node in the keystone k2g device tree. Tested on TI K2G platform: Tested-by: Vignesh R Tested on a socfpga-cyclonev board: Tested-by: Simon Goldschmidt

[U-Boot] [PATCH v6 4/4] dts: cadence_spi: Update documentation for DT bindings

Update documentation to reflect adopting the Linux DT bindings. Tested on TI K2G platform: Tested-by: Vignesh R Tested on a socfpga-cyclonev board: Tested-by: Simon Goldschmidt Signed-off-by: Jason Rush Reviewed-by: Jagan

[U-Boot] [PATCH v6 1/4] spi: cadence_spi: Sync DT bindings with Linux

Adopt the Linux DT bindings. This also fixes an issue with the indaddrtrig register on the Cadence QSPI device being programmed with the wrong value for the socfpga arch. Tested on TI K2G platform: Tested-by: Vignesh R Tested on a socfpga-cyclonev board: Tested-by: Simon

[U-Boot] [PATCH v6 3/4] config: cadence_spi: Remove defines read from DT

Cleanup unused #define values that are read from the DT. Tested on TI K2G platform: Tested-by: Vignesh R Tested on a socfpga-cyclonev board: Tested-by: Simon Goldschmidt Signed-off-by: Jason Rush Reviewed-by: Jagan Teki

[U-Boot] [PATCH v6 0/4] spi: cadence_spi: Adopt Linux DT bindings

Adopt the Linux DT bindings. This also fixes an issue with the indaddrtrig register on the Cadence QSPI device being programmed with the wrong value for the socfpga arch. Tested on TI K2G platform: Tested-by: Vignesh R Tested on a socfpga-cyclonev board: Tested-by: Simon

Re: [U-Boot] [PATCH v4 13/18] efi_loader: fix StartImage bootservice

On 23.01.18 22:35, Heinrich Schuchardt wrote: > On 01/19/2018 09:16 PM, xypron.g...@gmx.de wrote: >> From: Heinrich Schuchardt >> >> The calling convention for the entry point of an EFI image >> is always 'asmlinkage'. >> >> Signed-off-by: Heinrich Schuchardt

Re: [U-Boot] extract size of FIT image

On Tue, 23 Jan 2018 22:25:04 + Bishop, Mark (STRT) mbis...@smithsinterconnectinc.com wrote: > Is there an easy way or an existing mechanism to look inside of a FIT > image and get the size of the complete image? => fdt addr => fdt header 'totalsize' is the complete image size. -- Anatolij

[U-Boot] [PATCH 1/1] efi_loader: always call Exit after an image returns.

If an application or driver started via StartImage returns without calling Exit, StartImage has to call Exit. This is mandated by the UEFI spec and we do the same in efi_do_enter(). The patch looks bigger than it is. To avoid a forward declaration function efi_exit() was moved up. Only one

[U-Boot] [PATCH 5/7] sun50i: h5: Clean up OrangePi PC 2 device tree

Sort nodes alphabetically, and remove the ethernet alias duplicated from the SoC device tree. Signed-off-by: Samuel Holland --- arch/arm/dts/sun50i-h5-orangepi-pc2.dts | 41 - 1 file changed, 20 insertions(+), 21 deletions(-) diff --git

[U-Boot] [PATCH 7/7] sun50i: h5: Add support for the Orange Pi Zero Plus

The Orange Pi Zero Plus is a single board computer based on the Allwinner H5 SoC. It has 512MiB RAM, gigabit Ethernet, and one USB 2.0 port, with headers for two additional ports. Signed-off-by: Samuel Holland --- arch/arm/dts/Makefile | 1 +

[U-Boot] [PATCH 3/7] sun50i: a64: Move ethernet nodes to SoC DTS

These nodes were previously in an unused file specific to the Pine64. Move them to the base SoC device tree for use by other boards. Require individual boards to enable the emac and provide a pin configuration. Signed-off-by: Samuel Holland ---

[U-Boot] [PATCH 4/7] sun50i: a64: Update OrangePi Win defconfig and DTS

Enable Ethernet support in the device tree and add the necessary MACPWR configuration. Also fix spacing in USB device tree nodes and add the relevant configuration options. Signed-off-by: Samuel Holland --- arch/arm/dts/sun50i-a64-orangepi-win.dts | 18 +++---

[U-Boot] [PATCH 6/7] sun50i: h5: Enable remaining USB ports on OrangePi PC2

The OrangePi PC 2 has three USB type A ports, with one connected to each EHCI/OHCI controller. Enable the controllers for the other two ports. Signed-off-by: Samuel Holland --- arch/arm/dts/sun50i-h5-orangepi-pc2.dts | 16 1 file changed, 16 insertions(+)

[U-Boot] [PATCH 2/7] sun50i: a64: Fix USB clock/reset properties

Move the CLK_USB_OHCI0/1 clocks to the OHCI nodes where they belong, and make the format consistent with the H3/H5 nodes. While here, also remove leading zeros from the USB nodes' unit addresses. Signed-off-by: Samuel Holland --- arch/arm/dts/sun50i-a64.dtsi | 34

[U-Boot] [PATCH 1/7] sunxi: binman: Fix U-Boot binary size check

If raw mode is disabled, CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR is not defined, which breaks compiling the device trees. Only enable the size check when it actually matters--that is, when MMC raw mode is enabled. Signed-off-by: Samuel Holland ---

[U-Boot] [PATCH 0/7] sun50i device tree changes

These patches fix one general build issue, improve support for two existing boards, and add support for the Orange Pi Zero Plus. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH] gpio: sunxi: Add compatible string for H5 PIO

On Tue, Jan 23, 2018 at 1:15 PM, Jagan Teki wrote: > On Wed, Jan 24, 2018 at 12:42 AM, Chris Blake wrote: >> On Tue, Jan 23, 2018 at 1:09 PM, Jagan Teki wrote: >>> On Tue, Jan 16, 2018 at 3:58 AM, Chris Blake

Re: [U-Boot] [PATCH] gpio: sunxi: Add compatible string for H5 PIO

On Tue, Jan 23, 2018 at 1:09 PM, Jagan Teki wrote: > On Tue, Jan 16, 2018 at 3:58 AM, Chris Blake wrote: >> Due to the changes in >> https://github.com/linux-sunxi/u-boot-sunxi/commit/8faac0941cd409c6ff3738fbf658de2296f48e9a, >>

[U-Boot] extract size of FIT image

Is there an easy way or an existing mechanism to look inside of a FIT image and get the size of the complete image? Mark Bishop Sr. Firmware/Software Engineer - Microwave Subsystems [cid:image001.png@01D281ED.A45F0A90] 4726 Eisenhower Blvd. Tampa, FL 33634 USA T +1 813 901 7293

Re: [U-Boot] [PATCH v4 13/18] efi_loader: fix StartImage bootservice

On 01/19/2018 09:16 PM, xypron.g...@gmx.de wrote: > From: Heinrich Schuchardt > > The calling convention for the entry point of an EFI image > is always 'asmlinkage'. > > Signed-off-by: Heinrich Schuchardt > --- > v4 > rebase according to

[U-Boot] [PATCH 2/2] warp7 : run sec_init for CAAM RNG

This patch adds a sec_init call into board_init. Doing so in conjunction with the patch "drivers/crypto/fsl: assign job-rings to non-TrustZone" enables use of the CAAM in Linux when OPTEE/TrustZone is active. u-boot will initialise the RNG and assign ownership of the job-ring registers to a

[U-Boot] [PATCH 1/2] drivers/crypto/fsl: assign job-rings to non-TrustZone

After enabling TrustZone various parts of the CAAM silicon become inaccessible to non TrustZone contexts. The job-ring registers are designed to allow non TrustZone contexts like Linux to still submit jobs to CAAM even after TrustZone has been enabled. The default job-ring permissions after the

[U-Boot] [PATCH 0/2] Fix CAAM for TrustZone enable for warp7

This series is the u-boot fix to a problem we encountered when enabling OPTEE/TrustZone on the WaRP7. The symptom is once TrustZone is activated the first page of CAAM registers becomes read-only, read-zero from the perspective of Linux and other non TrustZone contexts. Offlining the problem with

[U-Boot] [PATCH v3 9/9] bootm: optee: Add mechanism to validate an OPTEE image before boot

This patch makes it possible to verify the contents and location of an OPTEE image in DRAM prior to handing off control to that image. If image verification fails we won't try to boot any further. Signed-off-by: Bryan O'Donoghue Cc: Harinarayan Bhatta

[U-Boot] [PATCH v3 5/9] optee: Add optee_image_get_load_addr()

This patch adds optee_image_get_load_addr() a helper function used to calculate the load-address of an OPTEE image based on the lower entry-point address given in the OPTEE header. Signed-off-by: Bryan O'Donoghue Cc: Harinarayan Bhatta Cc: Andrew

Re: [U-Boot] [PATCH] arm64 :show_regs: show the real hardware register even after relocation

On Tue, Jan 23, 2018 at 10:47:11AM +0800, Peng Fan wrote: > Not only show the calculated value after relocation, also show > the real hardware register value. > > Signed-off-by: Peng Fan > Reported-by: Karl Beldan > --- > arch/arm/lib/interrupts_64.c |

[U-Boot] [PATCH v3 7/9] optee: Add optee_verify_bootm_image()

This patch adds optee_verify_bootm_image() which will be subsequently used to verify the parameters encoded in the OPTEE header match the memory allocated to the OPTEE region, OPTEE header magic and version prior to handing off control to the OPTEE image. Signed-off-by: Bryan O'Donoghue

[U-Boot] [PATCH v3 8/9] optee: Add error printout

When encountering an error in OPTEE verification print out various details of the OPTEE header to aid in further debugging of encountered errors. Signed-off-by: Bryan O'Donoghue Cc: Harinarayan Bhatta Cc: Andrew F. Davis Cc: Tom Rini

[U-Boot] [PATCH v3 6/9] tools: mkimage: add optee image type

This patch adds support for bootable OPTEE images to mkimage. Currently there is a (Trusted Execution Environment) TEE image type, the TEE image type is installed to a memory location control is passed to the TEE and then the TEE returns to u-boot. flow #0: BootROM -> u-boot -> tee -> u-boot ->

[U-Boot] [PATCH v3 4/9] optee: Add optee_image_get_entry_point()

Add a helper function for extracting the least significant 32 bits from the OPTEE entry point address, which will be good enough to load OPTEE binaries up to (2^32)-1 bytes. We may need to extend this out later on but for now (2^32)-1 should be fine. Signed-off-by: Bryan O'Donoghue

[U-Boot] [PATCH v3 2/9] optee: Add CONFIG_OPTEE_TZDRAM_SIZE

OPTEE is currently linked to a specific area of memory called the TrustZone DRAM. This patch adds a CONFIG entry for the default size of TrustZone DRAM that a board-port can over-ride. The region that U-Boot sets aside for the OPTEE run-time should be verified before attempting to hand off to the

[U-Boot] [PATCH v3 3/9] optee: Add CONFIG_OPTEE_TZDRAM_BASE

OPTEE is currently linked to a specific area of memory called the TrustZone DRAM. This patch adds a CONFIG entry for the default address of TrustZone DRAM that a board-port can over-ride. The region that U-Boot sets aside for the OPTEE run-time should be verified before attempting to hand off to

[U-Boot] [PATCH v3 1/9] optee: Add lib entries for sharing OPTEE code across ports

This patch adds code to lib to enable sharing of useful OPTEE code between board-ports and architectures. The code on lib/optee/optee.c comes from the TI omap2 port. Eventually the OMAP2 code will be patched to include the shared code. The intention here is to add more useful OPTEE specific code

[U-Boot] [PATCH v3 0/9] Add new OPTEE bootm support to u-boot

v3: - Rework printout to be added at the end as opposed to churn over three separate patches - Andrew - Reword patch 006 to better explain the thinking behind new image type - Andrew v2: - Added CONFIG_OPTEE_TZDRAM_BASE instead of #ifndef OPTEE_TZDRAM_BASE as an error. - Tom Rini - Added

[U-Boot] [PATCH v3 11/15] env: mmc: depends on the MMC framework

The raw MMC environment directly calls into the MMC framework. Make sure it's enabled before we can select it. Reviewed-by: Simon Glass Signed-off-by: Maxime Ripard --- env/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[U-Boot] [PATCH v3 09/15] env: Support multiple environments

Now that we have everything in place to support multiple environment, let's make sure the current code can use it. The priority used between the various environment is the same one that was used in the code previously. At read / init times, the highest priority environment is going to be

[U-Boot] [PATCH v3 05/15] env: Make it explicit where we're loading our environment from

Since we can have multiple environments now, it's better to provide a decent indication on what environments were tried and which were the one to fail and succeed. Reviewed-by: Simon Glass Signed-off-by: Maxime Ripard --- env/env.c | 18

[U-Boot] [PATCH v3 07/15] env: mmc: Make the debug messages play a little nicer

Since we have global messages to indicate what's going on, the custom messages in the environment drivers only make the output less readable. Make MMC play a little nicer by removing all the extra \n and formatting that is redundant with the global output. Reviewed-by: Andre Przywara

[U-Boot] [PATCH v3 14/15] sunxi: Transition from the MMC to a FAT-based environment

The current environment has been hardcoded to an offset that starts to be an issue given the current size of our main U-Boot binary. By implementing a custom environment location routine, we can always favor the FAT-based environment, and fallback to the MMC if we don't find something in the FAT

[U-Boot] [PATCH v3 15/15] env: sunxi: Enable FAT-based environment support by default

Now that we have everything in place to implement the transition scheme, let's enable it by default. Reviewed-by: Andre Przywara Reviewed-by: Lukasz Majewski Signed-off-by: Maxime Ripard --- env/Kconfig | 4 1 file

[U-Boot] [PATCH v3 08/15] env: common: Make the debug messages play a little nicer

Since we have global messages to indicate what's going on, the custom messages in the environment drivers only make the output less readable. Make the common code play a little nicer by removing all the extra output in the standard case. Reviewed-by: Andre Przywara

[U-Boot] [PATCH v3 10/15] env: Initialise all the environments

Since we want to have multiple environments, we will need to initialise all the environments since we don't know at init time what drivers might fail when calling load. Let's init all of them, and only consider for further operations the ones that have not reported any errors at init time.

[U-Boot] [PATCH v3 06/15] env: fat: Make the debug messages play a little nicer

Since we have global messages to indicate what's going on, the custom messages in the environment drivers only make the output less readable. Make FAT play a little nicer by removing all the extra \n and formatting that is redundant with the global output. Reviewed-by: Andre Przywara

[U-Boot] [PATCH v3 01/15] cmd: nvedit: Get rid of the env lookup

The nvedit command is the only user of env_driver_lookup_default outside of the environment code itself, and it uses it only to print the environment it's about to save to during env save. As we're about to rework the environment to be able to handle multiple environment sources, we might not

[U-Boot] [PATCH v3 13/15] env: Mark env_get_location as weak

Allow boards and architectures to override the default environment lookup code by overriding env_get_location. Reviewed-by: Andre Przywara Reviewed-by: Lukasz Majewski Reviewed-by: Simon Glass Signed-off-by: Maxime Ripard

[U-Boot] [PATCH v3 04/15] env: Make the env save message a bit more explicit

Since we'll soon have support for multiple environments, the environment saving message might end up being printed multiple times if the higher priority environment cannot be used. That might confuse the user, so let's make it explicit if the operation failed or not. Reviewed-by: Andre Przywara

[U-Boot] [PATCH v3 12/15] env: Allow to build multiple environments in Kconfig

Now that we have everything in place in the code, let's allow to build multiple environments backend through Kconfig. Reviewed-by: Andre Przywara Reviewed-by: Lukasz Majewski Reviewed-by: Simon Glass Signed-off-by: Maxime Ripard

[U-Boot] [PATCH v3 03/15] env: Pass additional parameters to the env lookup function

In preparation for the multiple environment support, let's introduce two new parameters to the environment driver lookup function: the priority and operation. The operation parameter is meant to identify, obviously, the operation you might want to perform on the environment. The priority is a

[U-Boot] [PATCH v3 02/15] env: Rename env_driver_lookup_default and env_get_default_location

The env_driver_lookup_default and env_get_default_location functions are about to get refactored to support loading from multiple environment. The name is therefore not really well suited anymore. Drop the default part to be a bit more relevant. Reviewed-by: Andre Przywara

[U-Boot] [PATCH v3 00/15] env: Multiple env support and env transition for sunxi

Hi, Here is a second attempt at transitioning away from the MMC raw environment to a FAT-based one for Allwinner SoCs. Since the RFC was quite well received, I actually tested it and fixed a few rough edges. You'll find the first RFC here for reference:

Re: [U-Boot] List of architectures no longer printed

Dear Nathan, In message you wrote: > > "mkimage -A -h" no longer prints architectures. Is there another way to get > a list of architectures? I confirm this is a regression. Old versions of U-=Boot used to

[U-Boot] List of architectures no longer printed

Hi, "mkimage -A -h" no longer prints architectures. Is there another way to get a list of architectures? Reference: http://manpages.ubuntu.com/manpages/xenial/man1/mkimage.1.html https://linux.die.net/man/1/mkimage "-A [architecture] Set architecture. Pass -h as the architecture to see the

Re: [U-Boot] [PATCH] gpio: sunxi: Add compatible string for H5 PIO

On Wed, Jan 24, 2018 at 12:42 AM, Chris Blake wrote: > On Tue, Jan 23, 2018 at 1:09 PM, Jagan Teki wrote: >> On Tue, Jan 16, 2018 at 3:58 AM, Chris Blake wrote: >>> Due to the changes in >>>

Re: [U-Boot] [PATCH] gpio: sunxi: Add compatible string for H5 PIO

On Tue, Jan 16, 2018 at 3:58 AM, Chris Blake wrote: > Due to the changes in > https://github.com/linux-sunxi/u-boot-sunxi/commit/8faac0941cd409c6ff3738fbf658de2296f48e9a, > allwinner,sun50i-h5-pinctrl needs to be defined otherwise PIO does not work > on H5 based

Re: [U-Boot] [PATCH] mmc: fix to assign to corret clock value when clock is enabling

On 01/22/2018 10:04 PM, Jaehoon Chung wrote: When clock is enabling, it's assigned to 0 as mmc->clock. Then it can't initialize any card. Fix to assign to correct clock value as mmc->cfg->f_min or f_max. Tested-by: Stephen Warren Thanks! Fixes: 9546eb92cb6 ("mmc: fix the

Re: [U-Boot] [PATCH] cmd: Kconfig: Make CMD_NAND select NAND

On 01/23/2018 12:01 PM, Adam Ford wrote: > On Tue, Jan 23, 2018 at 11:15 AM, Andrew F. Davis wrote: >> On 01/23/2018 04:40 AM, Adam Ford wrote: >>> Many boards check for CONFIG_CMD_NAND instead of CONFIG_NAND, so >>> let's make CMD_NAND select NAND to make some Kconfig migration >>>

Re: [U-Boot] [PATCH] cmd: Kconfig: Make CMD_NAND select NAND

On Tue, Jan 23, 2018 at 11:15 AM, Andrew F. Davis wrote: > On 01/23/2018 04:40 AM, Adam Ford wrote: >> Many boards check for CONFIG_CMD_NAND instead of CONFIG_NAND, so >> let's make CMD_NAND select NAND to make some Kconfig migration >> easier >> >> Signed-off-by: Adam Ford

[U-Boot] [PATCH v4] arm: add support for PDU001

This patch adds support for the PDU001 board. Signed-off-by: Felix Brack --- Changes in v4: - move remaining U-Boot specific parts from DTS to DTSI file Changes in v3: - revert to deprecated SPDX license identifier GPL-2.0+ - maintain alphabetical order in Kconfig files - move

Re: [U-Boot] [PATCH] cmd: Kconfig: Make CMD_NAND select NAND

On 01/23/2018 04:40 AM, Adam Ford wrote: > Many boards check for CONFIG_CMD_NAND instead of CONFIG_NAND, so > let's make CMD_NAND select NAND to make some Kconfig migration > easier > > Signed-off-by: Adam Ford > > diff --git a/cmd/Kconfig b/cmd/Kconfig > index

Re: [U-Boot] [PATCH v2 1/2] spi: zynqmp_qspi: Add support for ZynqMP qspi driver

On Thu, Jan 4, 2018 at 1:07 PM, Siva Durga Prasad Paladugu wrote: > This patch adds qspi driver support for ZynqMP SoC. This > driver is responsible for communicating with qspi flash > devices. > > Signed-off-by: Siva Durga Prasad Paladugu >

[U-Boot] [PATCH v3 2/2] mmc: Add bcm2835 sdhost controller

The BCM2835 family of SoCs has 2 different SD controllers: One based on the SDHCI spec and a custom, home-grown one. This patch implements a driver for the latter based on the Linux driver. This is needed so that we can make use of device trees that assume driver presence of both SD controllers.

[U-Boot] [PATCH v3 1/2] bcm283x: Add pinctrl driver

The bcm283x family of SoCs have a GPIO controller that also acts as pinctrl controller. This patch introduces a new pinctrl driver that can actually properly mux devices into their device tree defined pin states and is now the primary owner of the gpio device. The previous GPIO driver gets moved

[U-Boot] [PATCH v3 0/2] Rpi: Add support for second sd host controller

The Raspberry Pi (bcm283x SoC) family contains 2 IP blocks to drive SD peripherals: A pretty standard SDHCI one called iProc and a home grown one called "sdhost". When driving U-Boot by the same device tree that we use for Linux, we end up in situations where only the "sdhost" device is available

  1   2   >