Even though we expect only master core to execute U-Boot code
let's make sure even if for some reason slave cores attempt to
execute U-Boot in parallel with master they get halted very early.
If platform wants it may kick-start slave cores before passing control
to say Linux kernel or any other
Even though from software developer PoV not much has changed in v1.1 firmware
for axs103 board still there's an important modification introduced by
SNPS hardware team: slave cores kick-start procedure now differs and we need
to accommodate this change in U-Boot.
Alexey Brodkin (2):
axs103:
Tiny printf doesn't support %pM, so when CONFIG_USE_TINY_PRINTF is
enabled use %x to manually print MAC address.
Signed-off-by: Vignesh R
---
net/eth_common.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/net/eth_common.c b/net/eth_common.c
index
From: Lee Jones
Signed-off-by: Lee Jones
---
include/configs/stih410-b2260.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/stih410-b2260.h b/include/configs/stih410-b2260.h
index ccbbf32..b83bef5 100644
---
From: Patrice Chotard
Update the CONFIG_EXTRA_ENV_SETTINGS, BOOT_TARGET_DEVICES and CONFIG_BOOTARGS
Fix SDRAM size
This series depends on series "[PATCH v3 00/13] STiH410-B2260: add reset,
usb and fastboot support" [1]. Hence this series must be applied when [1]
will be
From: Nicolas Le Bayon
32MB are reserved for Trusted Zone purpose
Signed-off-by: Nicolas Le Bayon
---
include/configs/stih410-b2260.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/configs/stih410-b2260.h
From: Patrice Chotard
Signed-off-by: Patrice Chotard
---
include/configs/stih410-b2260.h | 31 +--
1 file changed, 25 insertions(+), 6 deletions(-)
diff --git a/include/configs/stih410-b2260.h
* Rely on default pulse polarity value
* Don't mess with "multicore" value as it doesn't affect execution
In essence we now do a bare minimal stuff:
1) Select HS38x2_1 with CORE_SEL=1 bits
2) Select "manual" core start (via CREG) with START_MODE=0
3) Generate cpu_start pulse with START=1
In axs103 v1.1 procedure to kick-start slave cores has changed quite a bit
compared t previous implementation.
In particular:
* We used to have a generic START bit for all cores selected by CORE_SEL
mask. But now we don't touch CORE_SEL at all because we have a dedicated
START bit for each
Checking 'is_zimage' at this time will always fail and therefore booting
a FIT style image will always lead to this error message:
"## Kernel loading failed (missing x86 kernel setup) ..."
This change now removes this check and booting of FIT images works just
fine.
Signed-off-by: Stefan Roese
On 03/30/2017 03:08 PM, Ley Foon Tan wrote:
> Add clock driver support for Arria 10.
>
> Signed-off-by: Tien Fong Chee
> Signed-off-by: Ley Foon Tan
>
> Conflicts:
> arch/arm/mach-socfpga/clock_manager.c
^ what's this "conflicts" about ?
On 03/30/2017 03:08 PM, Ley Foon Tan wrote:
> Convert Altera DDR SDRAM driver to use Kconfig method.
> Enable ALTERA_SDRAM by default if it is on Gen5 target.
> Arria 10 will have different driver.
>
> Signed-off-by: Tien Fong Chee
> Signed-off-by: Ley Foon Tan
On 03/30/2017 03:22 AM, chee skywind wrote:
> On Wed, Mar 29, 2017 at 5:03 PM, Marek Vasut wrote:
>
>> On 03/29/2017 05:49 AM, tien.fong.c...@intel.com wrote:
>>> From: "Chee, Tien Fong"
>>>
>>> Commit ce62e57fc571 ("ARM: boot0 hook: remove macro,
On 03/29/2017 05:49 AM, tien.fong.c...@intel.com wrote:
> From: "Chee, Tien Fong"
>
> Commit ce62e57fc571 ("ARM: boot0 hook: remove macro, include whole
> header file") miss out cleaning macro in this header file, and this
> has broken implementation of a boot header
On 03/30/2017 03:08 PM, Ley Foon Tan wrote:
> Add SPL support for Arria 10.
>
> Signed-off-by: Tien Fong Chee
> Signed-off-by: Ley Foon Tan
> ---
> arch/arm/mach-socfpga/spl.c | 74
> ++---
> 1 file
These structures are normally named with 'uc' instead of 'uclass'. Change
this one for consistency.
Signed-off-by: Simon Glass
---
drivers/led/led-uclass.c | 4 ++--
drivers/led/led_gpio.c | 4 ++--
include/led.h| 4 ++--
3 files changed, 6 insertions(+), 6
At present this is very simple, supporting only on and off. We want to
also support toggling and blinking. As a first step, change the name of
the main method and use an enum to indicate the state.
Signed-off-by: Simon Glass
---
drivers/led/led-uclass.c | 6 +++---
When driver model is used for LEDs, provide a command to allow LED access.
Signed-off-by: Simon Glass
---
cmd/Kconfig | 9
cmd/Makefile | 1 +
cmd/led.c| 133 +++
3 files changed, 143 insertions(+)
create
Allow LEDs to be blinked if the driver supports it.
Signed-off-by: Simon Glass
---
drivers/led/led-uclass.c | 10 ++
include/led.h| 22 ++
test/dm/led.c| 22 ++
3 files changed, 54 insertions(+)
diff
The existing 'led' command does not support driver model. Rename it to
indicate that it is legacy code.
Signed-off-by: Simon Glass
---
cmd/Makefile | 2 +-
cmd/legacy_led.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/cmd/Makefile
Add support for toggling an LED into the uclass interface. This can be
efficiently implemented by the driver.
Signed-off-by: Simon Glass
---
drivers/led/led_gpio.c | 7 +++
include/led.h | 1 +
test/dm/led.c | 25 +
3 files
It is useful to be able to read the LED as well as write it. Add this to
the uclass and update the GPIO driver.
Signed-off-by: Simon Glass
---
drivers/led/led-uclass.c | 10 ++
drivers/led/led_gpio.c | 15 +++
include/led.h| 16
The LED interface for driver model is a little primitive. This series
expands it to match the legacy interface and adds a command to match.
Simon Glass (8):
sandbox: Add some test LEDs
dm: led: Rename struct led_uclass_plat
dm: led: Adjust the LED uclass
dm: led: Add support for getting
Add some LEDs to the standard sandbox device tree.
Signed-off-by: Simon Glass
---
arch/sandbox/dts/sandbox.dts | 14 ++
cmd/{led.c => legacy_led.c} | 0
2 files changed, 14 insertions(+)
rename cmd/{led.c => legacy_led.c} (100%)
diff --git
Hi Tom,
In this patch-set we add support of new AXS103 firmware as well
as troubleshoot unexpected execution by multiple cores simultaneously.
The following changes since commit 5cf618ee60a752d058a767372ca1ecb8d9c09b16:
Merge git://git.denx.de/u-boot-arc (2017-03-24 08:19:30 -0400)
are
On 03/29/2017 07:21 AM, Ruchika Gupta wrote:
> From: Vinitha Pillai-B57223
>
> - Add SD secure boot target for ls1046ardb.
> - Implement board specific spl_board_init() to setup CAAM stream ID and
> corresponding stream ID in SMMU.
> - Change the u-boot size defined by a
On 03/29/2017 07:21 AM, Ruchika Gupta wrote:
> From: Vinitha Pillai-B57223
>
> - Add SD secure boot target for ls1046ardb.
> - Implement board specific spl_board_init() to setup CAAM stream ID and
> corresponding stream ID in SMMU.
> - Change the u-boot size defined by a
The default value with distro_bootcmd is 2 seconds, which is
reasonably fast, and provides a consistent experience across platforms
supporting distro_bootcmd.
The current bootdelay value of 0 seconds is a bit challenging to
interrupt when desired.
Signed-off-by: Vagrant Cascadian
The Allwinner SoCs with 64-bit cores use an ARM Trusted Firmware binary,
which needs to be loaded alongside U-Boot proper.
Set the respective Kconfig options to let them select this feature and
also automatically build the FIT image.
Signed-off-by: Andre Przywara
---
The sunxi SPL was holding the detected RAM size in some local variable
only, so it wasn't accessible for other functions.
Store the value in gd->ram_size instead, so it can be used later on.
Signed-off-by: Andre Przywara
Reviewed-by: Simon Glass
---
For a board or platform to support FIT loading in the SPL, it has to
provide a board_fit_config_name_match() routine, which helps to select
one of possibly multiple DTBs contained in a FIT image.
Provide a simple function which chooses the DT name U-Boot was
configured with.
If the DT name is one
Some platforms require more complex U-Boot images than we can easily
generate via the mkimage command line, for instance to load additional
image files.
Introduce a CONFIG_SPL_FIT_SOURCE and CONFIG_SPL_FIT_GENERATOR symbol,
which can either hold an .its source file describing the image layout,
or,
By default, u-boot itself outputs on the serial console at 115200, so
it may as well pass the same value to the booted operating system as
well.
Signed-off-by: Vagrant Cascadian
---
include/configs/mx6cuboxi.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Fri, Mar 31, 2017 at 5:48 PM, Vagrant Cascadian wrote:
> By default, u-boot itself outputs on the serial console at 115200, so
> it may as well pass the same value to the booted operating system as
> well.
>
> Signed-off-by: Vagrant Cascadian
The default value with distro_bootcmd is 2 seconds, which is
reasonably fast, and provides a consistent experience across platforms
supporting distro_bootcmd.
The current bootdelay value of 0 seconds is a bit challenging to
interrupt when desired.
Signed-off-by: Vagrant Cascadian
Signed-off-by: Vagrant Cascadian
---
include/configs/odroid.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/configs/odroid.h b/include/configs/odroid.h
index 0fbda7dd76..abae044b66 100644
--- a/include/configs/odroid.h
+++
Signed-off-by: Vagrant Cascadian
---
include/configs/odroid.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/configs/odroid.h b/include/configs/odroid.h
index 6cc7dd16a2..0fbda7dd76 100644
--- a/include/configs/odroid.h
+++
At the moment we ignore any errors due to missing FIT properties,
instead go ahead and calculate our addresses with the -1 return value.
Fix this and bail out if any of the mandatory properties are missing.
Signed-off-by: Andre Przywara
---
common/spl/spl_fit.c | 15
Currently the SPL FIT loader always looks only for the first image in
the /images node a FIT tree, which it loads and later executes.
Generalize this by looking for a "firmware" property in the matched
configuration subnode, or, if that does not exist, for the first string
in the "loadables"
So far we were not using the FIT image format to its full potential:
The SPL FIT loader was just loading the first image from the /images
node plus one of the listed DTBs.
Now with the refactored loader code it's easy to load an arbitrary
number of images in addition to the two mentioned above.
As
SPL_FIT obviously requires libfdt in SPL, so let Kconfig express that by
selecting SPL_OF_LIBFDT.
Also make the actual options that users want (SPL signature and SPL FIT
loading) visible in the menu and let them select the SPL_FIT as a
requirement.
Also remove the now redundant SPL_OF_LIBFDT from
The generic ARMv8 assembly code contains routines for setting up
a CCN interconnect, though the Freescale SoCs are the only user.
Link this code only for Freescale targets, this saves some precious
bytes in the chronically tight SPL.
Signed-off-by: Andre Przywara
---
mksunxiboot limits the size of the resulting SPL binaries to pretty
conservative values to cover all SoCs and all boot media (NAND).
It turns out that we have limit checks in place in the build process,
so mksunxiboot can be relaxed and allow packaging binaries up to the
actual 32KB the mask boot
On ARM v7M, the processor will return to ARM mode when executing blx
instruction with bit 0 of the address == 0. Always set it to 1 to stay
in thumb mode.
Similar commit:
f3c10882f7dc8ec35993d5febe59aac01e6a
Author: Matt Porter
Date: Tue May 5 15:00:23 2015 -0400
Some minor fixes version of the SPL FIT loading series and the respective
patches to enable this feature on 64-bit Allwinner SoCs.
There is a new patch (6/19) fixing the SPL_FIT dependencies, above all
selecting SPL_OF_LIBFDT when SPL_FIT is enabled. This reduces the number
of Kconfig symbols a
Currently the SPL FIT loader uses the spl_fit_select_fdt() function to
find the offset to the right DTB within the FIT image.
For this it iterates over all subnodes of the /configuration node in
the FIT tree and compares all "description" strings therein using a
board specific matching function.
Using distro_bootcmd standardizes board behavior across many
platforms. This is particularly useful for distributions supporting
multiple boards without requiring custom configuration for each board.
There are a few changes needed to support distro_bootcmd, such as
fixing the default value for
From: Siarhei Siamashka
This patch updates the mksunxiboot tool to optionally add
the default device tree name string to the SPL header. This
information can be used by the firmware upgrade tools to
protect users from harming themselves by trying to upgrade
to an
The SPL stack is usually located at the end of SRAM A1, where it grows
towards the end of the SPL.
For the really big AArch64 binaries the stack overwrites code pretty
soon, so move the SPL stack to the end of SRAM A2, which is unused at this
time.
Signed-off-by: Andre Przywara
Hi Andre,
On 31 March 2017 at 16:31, Andre Przywara wrote:
> Some minor fixes version of the SPL FIT loading series and the respective
> patches to enable this feature on 64-bit Allwinner SoCs.
> There is a new patch (6/19) fixing the SPL_FIT dependencies, above all
>
Using distro_bootcmd standardizes board behavior across many
platforms. This is particularly useful for distributions supporting
multiple boards without requiring custom configuration for each board.
Signed-off-by: Vagrant Cascadian
---
include/configs/odroid.h | 20
At the moment we load two images from a FIT image: the actual U-Boot
image and the .dtb file. Both times we have very similar code, that deals
with alignment requirements the media we load from imposes upon us.
Factor out this code into a new function, which we just call twice.
Signed-off-by:
Not every SoC needs to set up the GIC interrupt controller, so link
think code only when the respective config option is set.
This shaves off some bytes from the SPL code size.
Signed-off-by: Andre Przywara
Reviewed-by: Simon Glass
---
Now that the Makefile can call a generator script to build a more
advanced FIT image, let's use this feature to address the needs of
Allwinner boards with 64-bit SoCs (A64 and H5).
The (DTB stripped) U-Boot binary and the ATF are static, but we allow
an arbitrary number of supported device trees
When a board uses a FIT image to load U-Boot proper, it requires a list
of supported device trees to be supplied, from which it chooses the
right one at runtime.
Add this list for the Pine64 and OrangePi PC2 board.
Signed-off-by: Andre Przywara
---
Now that we can store a DT name in the SPL header, use this string (if
available) when finding the right DT blob to load for U-Boot proper.
This allows a generic U-Boot (proper) image to be combined with a bunch
of supported DTs, with just the SPL (possibly only that string) to be
different.
With the DRAM init code and the SPL's ability to load the ATF binary as
well, we can now officially get rid of the boot0 boot method, which
involed a closed-source proprietary blob to be used.
Rework the Pine64 README file to document how to build the firmware.
Signed-off-by: Andre Przywara
On 31/03/17 23:43, Simon Glass wrote:
> Hi Andre,
>
> On 31 March 2017 at 16:31, Andre Przywara wrote:
>> Some minor fixes version of the SPL FIT loading series and the respective
>> patches to enable this feature on 64-bit Allwinner SoCs.
>> There is a new patch (6/19)
> -Original Message-
> From: york sun
> Sent: Saturday, March 25, 2017 10:30 PM
> To: Santan Kumar ; u-boot@lists.denx.de
> Cc: Priyanka Jain ; Abhimanyu Saini
>
> Subject: Re: [PATCH 1/2][v3] armv8: ls2080a:
On 28 March 2017 at 02:58, Philipp Tomsich
wrote:
> Signed-off-by: Philipp Tomsich
> ---
>
> configs/puma_defconfig | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/configs/puma_defconfig
Hi Konstanitin,
On 30 March 2017 at 07:58, Konstantin Porotchkin wrote:
>
>
> On 03/30/2017 04:31 PM, Stefan Roese wrote:
>>
>> (adding Simon to Cc for PCI related question)
>>
>> On 28.03.2017 17:36, kos...@marvell.com wrote:
>>>
>>> From: Konstantin Porotchkin
On 28 March 2017 at 10:48, Philipp Tomsich
wrote:
> This commit adds the baseline defconfig for the RK3399-Q7 (Puma) SoM
> (under the name 'puma-rk3399_defconfig') featuring the Rockchip RK3399
> in a Qseven compatible module.
>
> This subsumes the following
Hi,
On 24 March 2017 at 06:24, Jean-Jacques Hiblot wrote:
> From: Mugunthan V N
>
> Prepare sata driver for DM conversion by abstracting sata phy
> init to seperate function.
>
> Signed-off-by: Mugunthan V N
> Signed-off-by:
On 29 March 2017 at 13:20, Philipp Tomsich
wrote:
> Signed-off-by: Philipp Tomsich
Always nice to have a commit message. Also, please can you always add
a 'rockchip: ' tag?
> ---
>
> Changes in v3: None
>
>
Hi Stefan, Simon,
On Wed, Feb 22, 2017 at 3:07 PM, Stefan Roese wrote:
> Hi Simon,
>
> On 22.02.2017 04:59, Simon Glass wrote:
>
>
>
> What if the board mounts a flash with a different SPI flash command
> set? Will this work?
Frankly, I can't tell for
On 20 March 2017 at 14:48, Vikas Manocha wrote:
> With this gpio driver supporting DM, there is no need to enable clocks
> for different gpios (for pin muxing) in the board specific code.
>
> Need to increase the allocatable area required before relocation from 0x400 to
>
Hi Patrice,
On 22 March 2017 at 03:54, wrote:
> From: Patrice Chotard
>
> This patch adds the ST glue logic to manage the DWC3 HC
> on STiH407 SoC family. It configures the internal glue
> logic and syscfg registers.
>
> Part of this code been
Hi Jernej,
On 20 March 2017 at 16:01, Jernej Skrabec wrote:
> This series implements support for HDMI output. This is done using
> DM video framework and sharing the HDMI controller code with RK3288.
>
> Patch 1 splits out RK3288 HDMI code in a way that it is appropriate
Hi Heiko,
On 21 March 2017 at 17:30, Heiko Stuebner wrote:
> Most Rockchip socs have the ability to either map the bootrom or a sram
> area to the starting address of the cpu by flipping a bit in the GRF.
>
> Newer socs leave this untouched and mapped to the bootrom but the
On 22 March 2017 at 22:44, Wenyou Yang wrote:
> The intention of the removal is the preparation to introduce the
> new AT91 PIO pinctrl driver.
>
> Use the union to make the PIO3 and PIO2's registers be together
> and make their offset aligned.
>
> Signed-off-by: Wenyou
Hi Marcel,
On 24 March 2017 at 18:18, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> This patch adds board support for the Toradex Apalis TK1 a computer on
> module which can be used on different carrier boards.
>
> The module consists of a
On 22 March 2017 at 22:50, Wenyou Yang wrote:
> Add the clock support.
>
> Signed-off-by: Wenyou Yang
> ---
>
> drivers/serial/atmel_usart.c | 37 +++--
> 1 file changed, 35 insertions(+), 2 deletions(-)
Reviewed-by:
On 20 March 2017 at 16:01, Jernej Skrabec wrote:
> Video driver for older Allwinner SoCs uses cfb console framework which
> in turn uses struct ctfb_res_modes to hold timing informations. However,
> DM video framework uses different structure - struct display_timing.
>
>
On 28 March 2017 at 02:58, Philipp Tomsich
wrote:
> From: Jakob Unterwurzacher
>
> The RK3399-Q7 (Puma) unsually (this is a build-time option for
> customised boards) has an on-module SPI-flash connected to SPI1.
On 29 March 2017 at 13:20, Philipp Tomsich
wrote:
> The RK3399 hangs during DMA of the Designware MMC controller, when
> performing DMA-based transactions in SPL due to the DDR security settings
> left behind by the BootROM (i.e. accesses to the first MB of
On 28 March 2017 at 02:58, Philipp Tomsich
wrote:
> From: Jakob Unterwurzacher
>
> On the RK3399-Q7 we need to enable a number of configuration options
> (e.g. CONFIG_SPI_FLASH_WINBND) dependent on Kconfig seeing
Hi James,
On 26 March 2017 at 23:55, James Balean wrote:
> Enables the pinctrl-single driver to support 8 and 16-bit registers.
> Only 32-bit registers were supported previously.
Can you explain in your commit message why we want this?
>
> Signed-off-by: James Balean
Hi Vikas,
On 29 March 2017 at 13:33, Vikas MANOCHA wrote:
> Hi Michal/Simon,
>
>> -Original Message-
>> From: Vikas MANOCHA
>> Sent: Friday, March 24, 2017 2:48 PM
>> To: u-boot@lists.denx.de
>> Cc: Vikas MANOCHA ; Michal Simek
>>
On 23 March 2017 at 03:29, wrote:
> From: Ken Ma
>
> - Add generic scsi device tree bindings doc, the doc includes:
> - Brief introduction for scsi;
> - Scsi's properties' introduction;
> - Add marvell mvebu scsi binding doc with the example of armada3700
On 22 March 2017 at 22:51, Wenyou Yang wrote:
> Align the at91 pmc's compatibles with Kernel's.
>
> Signed-off-by: Wenyou Yang
> ---
>
> Changes in v2:
> - Rebase on v2017.03.
>
> drivers/clk/at91/pmc.c | 6 ++
> 1 file changed, 6 insertions(+)
On 28 March 2017 at 10:48, Philipp Tomsich
wrote:
> For the initial validation of the RK3399-Q7 (Puma), the DDR3 has been
> clocked at 666MHz (i.e. DDR3-1333) using the same (safe) settings as
> used in Rockchip's MiniLoader.
>
> Signed-off-by: Philipp
Hi,
On 28 March 2017 at 08:37, Andre Przywara wrote:
> Hi,
>
> On 28/03/17 15:16, Dan Handley wrote:
>> Hi Kever
>>
>>> -Original Message-
>>> From: Kever Yang [mailto:kever.y...@rock-chips.com]
>>> Sent: 28 March 2017 08:23
>>>
>>> Hi Andre,
>>>
>>>
>>> On
Hi Ken,
On 27 March 2017 at 02:28, Ken Ma wrote:
> Hi Stefan
>
>
>
> Thanks a lot for your kind reply.
>
>
>
> But I still do not think it's very good to change sata's uclass id from
> "UCLASS_AHCI" to "UCLASS_SCSI".
>
> If we do such change, UCLASS_AHCI is lost since from the
Hi Andre,
On 27 March 2017 at 18:45, Andre Przywara wrote:
> A fixed version of the SPL FIT loading series.
> The error handling has been improved, also quite some comments and
> documentation has been added.
> The README.pine64 file has been totally reworked to reflect
Hi Philipp,
On 28 March 2017 at 02:58, Philipp Tomsich
wrote:
> This change adds support for configuring the module clocks for SPI1 and
> SPI5 from the 594MHz GPLL.
>
> Note that the driver (rk_spi.c) always sets this to 99MHz, but the
> implemented
Hi Joakim,
On 23 March 2017 at 11:02, Joakim Tjernlund
wrote:
> ft_cpu_setup() already calls fdt_fixup_ethernet(), calling it
> in image_setup_libfdt() is both redundant and breaks any modifications
> done by ft_board_setup(). Restore the old behavior by removing
>
On 29 March 2017 at 17:23, Jernej Skrabec wrote:
> MiQi is rk3288 based development board with 1 or 2 GB SDRAM, 16 GB eMMC,
> micro SD card interface, 4 USB 2.0 ports, HDMI, gigabit Ethernet and
> expansion ports.
>
> Signed-off-by: Jernej Skrabec
On 29 March 2017 at 05:31, Philipp Tomsich
wrote:
> From: Jakob Unterwurzacher
>
> On the RK3399-Q7 we need to enable a number of configuration options
> (e.g. CONFIG_SPI_FLASH_WINBND) dependent on Kconfig seeing
On 31 March 2017 at 00:09, Stefan Roese wrote:
> Checking 'is_zimage' at this time will always fail and therefore booting
> a FIT style image will always lead to this error message:
>
> "## Kernel loading failed (missing x86 kernel setup) ..."
>
> This change now removes this check
On 29 March 2017 at 05:31, Philipp Tomsich
wrote:
> To include the ability to load from an SPI flash in SPL, it's not
> sufficient to define SPL_SPI_SUPPORT and SPL_SPI_FLASH_SUPPORT via
> Kconfig... so we conditionally define SPL_SPI_LOAD if SPI support
>
On 29 March 2017 at 05:31, Philipp Tomsich
wrote:
> This commit adds support for the pin-configuration of the SPI5
> controller of the RK3399 through the following changes:
> * grf_rk3399.h: adds definition for configuring the SPI5 pins
>
Hi Tom,
On 31 March 2017 at 22:19, Simon Glass wrote:
> Hi Tom,
>
> On 6 February 2017 at 08:32, Simon Glass wrote:
>>
>> Hi Tom,
>>
>> On 23 January 2017 at 10:22, Tom Rini wrote:
>> > On Fri, Jan 20, 2017 at 07:07:35AM -0700, Simon
On 27 March 2017 at 08:38, wrote:
> From: Ziping Chen
>
> The status of a GPIO-connected LED can be read back by reading the GPO
> value.
>
> Add the support for get_status function in led_gpio driver.
>
> Signed-off-by: Ziping Chen
On Tue, Mar 14, 2017 at 9:44 AM, Bin Meng wrote:
> On Mon, Mar 6, 2017 at 7:51 PM, Andy Shevchenko
> wrote:
>> There is option which is not used:
>> CONFIG_ZBOOT_32
>>
>> Remove it from default x86 config and from whitelist.
>>
>>
On Fri, Mar 17, 2017 at 11:26 AM, Simon Glass wrote:
> On 16 March 2017 at 08:26, Bin Meng wrote:
>> At present there are only 8-bit and 32-bit read/write routines in
>> the rtc uclass driver. This adds the 16-bit support.
>>
>> Signed-off-by: Bin Meng
On 22 March 2017 at 03:54, wrote:
> From: Patrice Chotard
>
> Add support for on-chip ohci controller available
> on STMicrolectronics SoCs.
> Ohci support will be then available on both type A
> USB 2.0 connectors.
>
> Signed-off-by: Patrice
Hi Patrice,
On 22 March 2017 at 03:54, wrote:
> From: Patrice Chotard
>
> Add support for on-chip ehci controller available
> on STMicrolectronics SoCs.
> ehci support will be then available on both type A
> USB 2.0 connectors.
>
> Signed-off-by:
Hi Patrice,
On 23 March 2017 at 03:59, Patrice CHOTARD wrote:
> Hi Simon
>
> On 03/22/2017 02:05 PM, Simon Glass wrote:
>> Hi,
>>
>> On 17 March 2017 at 10:25, wrote:
>>> From: Patrice Chotard
>>>
>>> Add support for
On 22 March 2017 at 22:55, Wenyou Yang wrote:
> When the CONFIG_ATMEL_LEGACY is undefined, according to the following
> defines, at91_set_gpio_value() references to at91_set_pio_value(x, y)
> with two parameters.
> #define at91_set_gpio_value(x, y)
Hi Tom,
On 21 March 2017 at 08:07, Tom Rini wrote:
> On Sat, Feb 04, 2017 at 07:34:59PM -0800, Simon Glass wrote:
>> Hi,
>>
>> On 17 January 2017 at 21:50, Simon Glass wrote:
>> > So far U-Boot uses a 'flat' device tree, which means that it is decoded
>> >
1 - 100 of 171 matches
Mail list logo