On 4/19/19 5:22 AM, AKASHI Takahiro wrote:
> In the current implementation, bootefi command and EFI boot manager
> don't use load_image API, instead, use more primitive and internal
> functions. This will introduce duplicated code and potentially
> unknown bugs as well as inconsistent behaviours.
>
On 4/19/19 11:18 PM, Lukasz Majewski wrote:
> Dear Marek,
>
> The following changes since commit
> 1f4ae66eaab29bfb5d1eb44996f7826c9cd01ed1:
>
> Merge tag 'arc-for-2019.07' of git://git.denx.de/u-boot-arc
> (2019-04-18 12:12:16 -0400)
>
> are available in the git repository at:
>
> git://
On 4/19/19 10:52 PM, Simon Goldschmidt wrote:
>
>
> Marek Vasut mailto:ma...@denx.de>> schrieb am Fr., 19.
> Apr. 2019, 11:29:
>
> On 4/19/19 8:17 AM, Ley Foon Tan wrote:
> > A mailbox command contains 1-DWORD header + arguments. The "len"
> variable
> > only contains the length
Hi,all
1. When I tested and compiled some spiboot boards, I found that the board
compilation of these spiflash boot configurations failed.
These boards all support the dm mode of spl, and the boot mode used is spiboot.
Here is the board configuration I compiled:
configs/sama5d2_xplained_sp
> At present this function uses printf() format strings that are not
> supported in SPL, so the output just consists of %llx strings on 64-bit.
> machines. Fix this by adding a special case.
>
> Signed-off-by: Simon Glass
> Reviewed-by: Philipp Tomsich
> ---
>
> Changes in v2: None
>
> lib/di
> It is helpful to print the clock number as well as the index, so that this
> can be looked up in the binding file. Update the debug() statement to do
> this.
>
> Signed-off-by: Simon Glass
> Reviewed-by: Philipp Tomsich
> ---
>
> Changes in v2: None
>
> drivers/clk/clk-uclass.c | 4 ++--
>
> At present this file uses GPIO_OUTPUT and GPIO_INPUT as its sub-command
> values. These are pretty generic names. Add a 'C' suffix to avoid possible
> conflicts.
>
> Signed-off-by: Simon Glass
> Reviewed-by: Philipp Tomsich
> ---
>
> Changes in v2: None
>
> cmd/gpio.c | 37 +
> Other make_fit script (like imx or sunxi) use the BL31 environment
> variable to indicate the location of the file.
> Also do that for rockchip so we don't need to copy the file in the source
> directory.
>
> Signed-off-by: Emmanuel Vadot
> Reviewed-by: Philipp Tomsich
> ---
> arch/arm/mach-r
> The SPL for the Tinker Board has to fit into 32 KiB. Currently this limit
> is exceeded.
>
> CONFIG_SPL_I2C_SUPPORT is not needed to move to main U-Boot. So let's
> disable it.
>
> Suggested-by: David Wu
> Signed-off-by: Heinrich Schuchardt
> Reviewed-by: David Wu
> ---
> This solves only on
On Tue, Feb 5, 2019 at 4:24 PM Emmanuel Vadot wrote:
>
> Other make_fit script (like imx or sunxi) use the BL31 environment
> variable to indicate the location of the file.
> Also do that for rockchip so we don't need to copy the file in the source
> directory.
>
> Signed-off-by: Emmanuel Vadot
>
On Fri, Apr 19, 2019 at 03:32:55PM +0200, Michael Nazzareno Trimarchi wrote:
> Hi Tom
>
> On Fri, Apr 19, 2019 at 2:42 PM Tom Rini wrote:
> >
> > On Fri, Apr 19, 2019 at 11:25:47AM +0200, Marek Vasut wrote:
> > > On 4/19/19 8:55 AM, Jagan Teki wrote:
> > > > Dropped
> > > > - mxs_spi driver
> > >
> This failed and caused a boot failure on c201, and afaik
> the pins should be setup by the new pinctrl driver.
>
> Signed-off-by: Urja Rannikko
> Reviewed-by: Simon Glass
> ---
> arch/arm/mach-rockchip/rk3288-board.c | 12
> 1 file changed, 12 deletions(-)
>
Reviewed-by: Philip
> This fixes RK3288 SPL hanging or hitting this assert:
> drivers/core/ofnode.c:183: ofnode_first_subnode: Assertion
> `ofnode_valid(node)' failed.
>
> Signed-off-by: Urja Rannikko
> Reviewed-by: Simon Glass
> ---
> drivers/pinctrl/pinctrl-uclass.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> Sync rk3399-opp.dtsi from Linux.
>
> Linux commit details about the rk3399-opp.dtsi sync:
> "arm64: dts: rockchip: use SPDX-License-Identifier"
> (sha1: 4ee99cebd486238ac433da823b95cc5f8d8a6905)
>
> Signed-off-by: Jagan Teki
> ---
> arch/arm/dts/rk3399-opp.dtsi | 133 +
> Since rockchip have an individual doc/README.rockchip, it would
> be better to update the same instead of maintaining it separately
> in board files.
>
> So, add the documentation for rk3399
> - procedure to build
> - procedure to boot from SD
>
> Signed-off-by: Jagan Teki
> ---
> doc/README.
> Add initial support for Orangepi RK3399 board.
>
> Specification
> - Rockchip RK3399
> - 2GB/4GB DDR3
> - 16GB eMMC
> - SD card slot
> - RTL8211E 1Gbps
> - AP6356S WiFI/BT
> - HDMI In/Out, DP, MIPI DSI/CSI
> - Mini PCIe
> - Sensors, Keys etc
> - DC12V-2A and DC5V-2A
>
> Commit details about Lin
> u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and
> which is U-Boot specific devicetrees binding.
>
> Move it on global rk3399-u-boot.dtsi file and rest of the U-Boot
> bindings will move it future based on the requirement.
>
> This would help to sync the devicetrees from Linux
On Fri, Apr 19, 2019 at 12:18:59PM +0530, Jagan Teki wrote:
> Dropped
> - lpc32xx_ssp driver
> - CONFIG_LPC32XX_SSP, LPC32XX_SSP_TIMEOUT items
>
> Dropped due to:
> - no active updates
> - no dm conversion
> - multiple pings for asking dm-conversion
> - no response for dm converted patch
> - driv
On 4/21/19 8:41 PM, Tom Rini wrote:
> On Fri, Apr 19, 2019 at 03:32:55PM +0200, Michael Nazzareno Trimarchi wrote:
>> Hi Tom
>>
>> On Fri, Apr 19, 2019 at 2:42 PM Tom Rini wrote:
>>>
>>> On Fri, Apr 19, 2019 at 11:25:47AM +0200, Marek Vasut wrote:
On 4/19/19 8:55 AM, Jagan Teki wrote:
> D
On Wed, 17 Apr 2019 at 11:17, Neil Armstrong wrote:
>
> When fixing sandbox test for regmap_read_poll_timeout(), the
> sandbox_timer_add_offset was introduced but only defined in sandbox code
> thus generating warnings when used out of sandbox :
>
> include/regmap.h:289:2: note: in expansion of ma
On Mon, 1 Apr 2019 at 03:47, Eugeniu Rosca wrote:
>
> Prepare for booting Android images which lack any DTB in the second
> area by using 'fdtaddr' environment variable as source/address of FDT.
> No functional/behavioral change expected in this patch.
>
> Signed-off-by: Eugeniu Rosca
> ---
> Cha
On Mon, 1 Apr 2019 at 03:47, Eugeniu Rosca wrote:
>
> Increase the readability of boot_get_fdt().
> No change in behavior is expected.
>
> Signed-off-by: Eugeniu Rosca
> ---
> Changes in v2:
> - NA
> - Link v1: https://patchwork.ozlabs.org/patch/1071588/
> ---
> common/image-fdt.c | 8 ++--
On Mon, 1 Apr 2019 at 03:46, Eugeniu Rosca wrote:
>
> The 'no_fdt' goto label was introduced by v2015.01 commit [0] and it
> had two review stages [1-2]. The *documented* purpose behind commit [0]
> is (excerpt from commit description):
>
> > allows both FDT and non-FDT kernels to boot by making t
Hi Eugeniu,
On Mon, 1 Apr 2019 at 03:54, Eugeniu Rosca wrote:
>
> Our platform doesn't store the DTB into the Android image second area,
> but rather copies the DTB to RAM from a dedicated dtb.img partition [0],
> prior to booting the Android image by calling bootm.
>
> Similar to [1], we find it
Hi Stefan,
On Fri, 12 Apr 2019 at 02:46, Stefan Mavrodiev wrote:
>
> When using fdt_fixup_mtdparts() offset and length cell sizes
> are limited to 4 bytes (1 cell). However if the mtd device is
> bigger then 4GiB, then #address-cells and #size-cells are
> 8 bytes (2 cells) [1].
>
> This patch rea
On 4/19/19 10:47 PM, Simon Goldschmidt wrote:
>
>
> Marek Vasut mailto:ma...@denx.de>> schrieb am Di., 16.
> Apr. 2019, 23:14:
>
> On 4/16/19 10:08 PM, Simon Goldschmidt wrote:
> > Hi Marek,
> >
> > Am 12.04.2019 um 12:31 schrieb Marek Vasut:
> >> On 4/11/19 10:07 PM, Simon G
The following changes since commit 75ce8c938d39bd22460be66e6bf318bd2410c17b:
Merge tag 'u-boot-imx-20190415' of git://git.denx.de/u-boot-imx
(2019-04-15 07:31:14 -0400)
are available in the Git repository at:
git://git.denx.de/u-boot-socfpga.git master
for you to fetch changes up to e09c1a1
The following changes since commit 1f4ae66eaab29bfb5d1eb44996f7826c9cd01ed1:
Merge tag 'arc-for-2019.07' of git://git.denx.de/u-boot-arc
(2019-04-18 12:12:16 -0400)
are available in the Git repository at:
git://git.denx.de/u-boot-usb.git master
for you to fetch changes up to 7fd9f31c6bd1360
Hi Patrick,
On Mon, 8 Apr 2019 at 08:18, Patrick Delaunay wrote:
>
> We can remove the pre reloc property in SPL and TPL device-tree:
pre-reloc
> - u-boot,dm-pre-reloc
> - u-boot,dm-spl
> - u-boot,dm-tpl
> As only the needed node are kept by fdtgrep (1st pass).
>
> The associated function (XXX_
Add the device trees for
* vexpress_ca5x2_defconfig
* vexpress_ca9x4_defconfig
* vexpress_ca15_tc2_defconfig
as available in Linux 5.1 rc5.
We are using the vexpress_ca15_tc2_defconfig and vexpress_ca9x4_defconfig
for Travis testing via QEMU.
The UEFI base Embedded Base Boot Requirements Specif
vexpress_ca15_tc2_defconfig and vexpress_ca9x4_defconfig do not provide
device trees (as $fdtcontroladdr) as needed to pass our Travis CI tests.
As we are on the move to requiring block devices to be based on the driver
model these boards either will have to be converted to use device trees or
wil
Add callback to configure, and de-configure, pin as a GPIO on the
pin controller side. This matches similar functionality in Linux
and aims to replace the ad-hoc implementations present in U-Boot.
Signed-off-by: Marek Vasut
Cc: Alex Kiernan
Cc: Christoph Muellner
Cc: Eugeniu Rosca
Cc: Patrice
This function is now replaced by common pin controller GPIO configuration
functionality, drop it.
Signed-off-by: Marek Vasut
Cc: Alex Kiernan
Cc: Christoph Muellner
Cc: Eugeniu Rosca
Cc: Patrice Chotard
Cc: Patrick DELAUNAY
Cc: Philipp Tomsich
Cc: Simon Glass
---
drivers/pinctrl/renesas/p
Add missing cfg->type = PINMUX_TYPE_GPIO upon successfully setting pin
as a GPIO to retain the pin configuration information.
Signed-off-by: Marek Vasut
Cc: Alex Kiernan
Cc: Christoph Muellner
Cc: Eugeniu Rosca
Cc: Patrice Chotard
Cc: Patrick DELAUNAY
Cc: Philipp Tomsich
Cc: Simon Glass
--
Implement the gpio_request_enable/gpio_disable_free callbacks to let
the GPIO driver call the pin control framework and let it reconfigure
pins as GPIOs.
Signed-off-by: Marek Vasut
Cc: Alex Kiernan
Cc: Christoph Muellner
Cc: Eugeniu Rosca
Cc: Patrice Chotard
Cc: Patrick DELAUNAY
Cc: Philipp
Switch to generic pin controller API for configuring pins as GPIOs
instead of using the ad-hoc call into the R-Car PFC driver. Moreover,
add .free() implementation for the GPIO controller.
Signed-off-by: Marek Vasut
Cc: Alex Kiernan
Cc: Christoph Muellner
Cc: Eugeniu Rosca
Cc: Patrice Chotard
On 4/4/19 2:42 PM, Eugeniu Rosca wrote:
> Hi Marek,
Hi,
> On Thu, Apr 04, 2019 at 03:36:45AM +0200, Marek Vasut wrote:
> [..]
>> I was thinking about this patch further and I think the best way forward
>> would be to extend the pinmux/pinctrl API with a callback to set a pin
>> as GPIO and then j
To assure the pins on R-Car Gen3 SoCs are configured correctly, always
select pin control drivers on Gen3 SoCs.
Signed-off-by: Marek Vasut
Cc: Nobuhiro Iwamatsu
---
arch/arm/mach-rmobile/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-rmobile/Kconfig b/arch/arm/mach
On Fri, Apr 19, 2019 at 04:03:24PM +, Patrice CHOTARD wrote:
> Hi Tom
>
> Please find the pull request for STM32 round 2
>
> The following changes since commit 1f4ae66eaab29bfb5d1eb44996f7826c9cd01ed1:
>
> Merge tag 'arc-for-2019.07' of git://git.denx.de/u-boot-arc
> (2019-04-18 12:12:16
On Sat, Apr 20, 2019 at 07:37:47PM +0200, Heinrich Schuchardt wrote:
> On 4/20/19 10:37 AM, Heinrich Schuchardt wrote:
> > On 4/19/19 5:22 AM, AKASHI Takahiro wrote:
> >> In the current implementation, bootefi command and EFI boot manager
> >> don't use load_image API, instead, use more primitive a
On Sat, Apr 20, 2019 at 10:07:20AM +0200, Heinrich Schuchardt wrote:
> On 4/19/19 5:22 AM, AKASHI Takahiro wrote:
> >+/*
> >+ * FIXME: Who is responsible for
> >+ * free(loaded_image_info->load_options);
> >+ * Once efi_exit() is implemented correctly,
> >+ * handle itself
On Sat, Apr 20, 2019 at 10:37:54AM +0200, Heinrich Schuchardt wrote:
> On 4/19/19 5:22 AM, AKASHI Takahiro wrote:
> >In the current implementation, bootefi command and EFI boot manager
> >don't use load_image API, instead, use more primitive and internal
> >functions. This will introduce duplicated
On Sun, Apr 21, 2019 at 4:30 PM Marek Vasut wrote:
>
> On 4/19/19 10:52 PM, Simon Goldschmidt wrote:
> >
> >
> > Marek Vasut mailto:ma...@denx.de>> schrieb am Fr., 19.
> > Apr. 2019, 11:29:
> >
> > On 4/19/19 8:17 AM, Ley Foon Tan wrote:
> > > A mailbox command contains 1-DWORD header + ar
This converts the following to Kconfig:
CONFIG_TRACE_BUFFER_SIZE
CONFIG_TRACE_EARLY_SIZE
CONFIG_TRACE_EARLY
CONFIG_TRACE_EARLY_ADDR
Signed-off-by: Simon Glass
---
Changes in v2: None
lib/Kconfig | 48
lib/trace.c
On Wed, Apr 10, 2019 at 8:46 PM Lukas Auer
wrote:
>
> Boards such as qemu-riscv, which receive their device tree at runtime,
> for example from QEMU or firmware, are unable to add the appropriate
> device tree properties to make devices available pre relocation.
> Instead, they must rely on the DM
At present many functions in this file return -1. Update them to return a
valid error code. Also tidy up the 'return' statements at the same time,
since these should have a blank line before them.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to tidy up error returns in trace.c
Enable this by default so that tracing can be inspected if enabled. This
cannot rely on the 'imply' in lib/Kconfig since this method of enabling
tracing relates on an environment variable (FTRACE) and does not use
Kconfig.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to enable t
This converts the following to Kconfig:
CONFIG_TRACE
Signed-off-by: Simon Glass
---
Changes in v2: None
cmd/Kconfig | 2 +-
lib/Kconfig | 9 +
scripts/config_whitelist.txt | 1 -
3 files changed, 10 insertions(+), 2 deletions(-)
Applied to u-boot-d
Hi Stefan,
On Fri, Apr 12 2019, Stefan Roese wrote:
> Testing has shown that the current DM implementation of a platform /
> board specific translation offset, as its needed for the SPL on MVEBU
> platforms is buggy. The translation offset is confingured too late,
> after the driver bind functions
It is possible for this to happen if something goes wrong very early in
the init sequence. Add a check for this.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to allow calling bootstage_mark() before bootstage_init()
common/bootstage.c | 7 +++
1 file changed, 7 insertions(
Hi Eugeniu,
On Thu, 18 Apr 2019 at 03:18, Eugeniu Rosca wrote:
>
> Hi Simon,
>
> On Wed, Apr 17, 2019 at 09:33:06PM -0700, Simon Glass wrote:
> > Hi Eugeniu,
> >
> > On Mon, 1 Apr 2019 at 03:46, Eugeniu Rosca wrote:
> > >
> > > Paranoid programming [1] lies at the foundation of proper software
>
Hi Eugeniu,
On Mon, 1 Apr 2019 at 03:54, Eugeniu Rosca wrote:
>
> Our platform doesn't store the DTB into the Android image second area,
> but rather copies the DTB to RAM from a dedicated dtb.img partition [0],
> prior to booting the Android image by calling bootm.
>
> Similar to [1], we find it
This was really intended for debugging. Drop it.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add a new patch to drop the printf() in setup_ram_buf()
arch/sandbox/cpu/start.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
Applied to u-boot-dm, thanks!
This buffer is too small now that sandbox has grown in size. Increase it.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to increase the early-trace-buffer size for sandbox
include/configs/sandbox.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Applied to u-boot-dm, tha
This file should not include header files. They have already been included
by the time initcall.h is included. Also, document how to enable debugging
in this file.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to drop use of header files in initcall.h
include/initcall.h | 11 ++
On Mon, 1 Apr 2019 at 03:47, Eugeniu Rosca wrote:
>
> Increase the readability of boot_get_fdt().
> No change in behavior is expected.
>
> Signed-off-by: Eugeniu Rosca
> ---
> Changes in v2:
> - NA
> - Link v1: https://patchwork.ozlabs.org/patch/1071588/
> ---
> common/image-fdt.c | 8 ++--
These two buffers currently conflict if tracing is enabled. Move the
pre-console buffer and update the documentation.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to move pre-console buffer out of the way of tracing
board/sandbox/README.sandbox | 3 +++
configs/sandbox_defconf
These functions still use uint32_t and uint64_t but checkpatch now
requests that the kernel types be used instead. Update them as well as a
few resulting checkpatch errors.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to use kernel types in div64
include/div64.h | 70 +
At present if one of the initcalls fails on sandbox the address printing
is not help, e.g.:
initcall sequence 557678967c80 failed at call 5576709dfe1f (err=-96)
This is because U-Boot gets relocated high into memory and the relocation
offset (gd->reloc_off) does not work correctly for s
Allocation routines were adjusted to ensure that the returned addresses
are a multiple of the page size, but the header code was not updated to
take account of this. These routines assume that the header size is the
same as the page size which is unlikely.
At present os_realloc() does not work cor
This function may be called from tracing code, since that code needs to
read the timer and this often requires calling do_div(), which calls
__div64_32(). If this function is instrumented it causes an infinite loop,
since emitting a trace record requests the time, which in turn emits a
trace record
On Mon, 1 Apr 2019 at 03:46, Eugeniu Rosca wrote:
>
> The 'no_fdt' goto label was introduced by v2015.01 commit [0] and it
> had two review stages [1-2]. The *documented* purpose behind commit [0]
> is (excerpt from commit description):
>
> > allows both FDT and non-FDT kernels to boot by making t
> On 05.04.2019, at 13:03, Christoph Muellner
> wrote:
>
> When using boot scripts it can become quite hard to understand
> which commands are actually executed during bootup (e.g. where
> is a kernel image loaded from or which DTB is in use).
>
> Shell scripts suffer from a similar problem and m
On Mon, 1 Apr 2019 at 03:47, Eugeniu Rosca wrote:
>
> Prepare for booting Android images which lack any DTB in the second
> area by using 'fdtaddr' environment variable as source/address of FDT.
> No functional/behavioral change expected in this patch.
>
> Signed-off-by: Eugeniu Rosca
> ---
> Cha
On Fri, 5 Apr 2019 at 19:12, Ramon Fried wrote:
>
> Add Cadence PCIe endpoint driver supporting configuration
> of header, bars and MSI for device.
>
> Signed-off-by: Ramon Fried
> ---
>
> .../pci_endpoint/cdns,cdns-pcie-ep.txt| 18 +
> drivers/pci_endpoint/Kconfig |
Hi Ramon,
On Fri, 5 Apr 2019 at 19:12, Ramon Fried wrote:
>
> Introduce new UCLASS_PCI_EP class for handling PCI endpoint
> devices, allowing to set various attributes of the PCI endpoint
> device, such as:
> * configuration space header
> * BAR definitions
> * outband memory mapping
> * start/st
On Fri, 5 Apr 2019 at 19:12, Ramon Fried wrote:
>
> PCI_MSI_FLAGS_MASKBIT was missing from include file,
> add it.
>
> Signed-off-by: Ramon Fried
> ---
>
> include/pci.h | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Simon Glass
___
U-Boot mail
Hi,
May I know whether this patch-set is in reviewing?
Actually it's blocking QorIQ eSDHC UHS-I/HS200 new features development, since
the way of implementation is totally different with i.MX.
Thanks a lot.
Best regards,
Yangbo Lu
> -Original Message-
> From: Y.b. Lu
> Sent: Wednesday,
Hi Lukasz,
> Subject: Re: [U-Boot] Is mmc still being actively maintained?
>
> Hi Peng,
>
> > Hi All, Jaehoon
> >
> > Is mmc still being actively maintained?
>
> As fair as I can tell, it is "maintained" by Tom and Marek as last PR by
> Jaehoon
> has been sent on:
> Tue, 8 May 2018 16:22:14 +0
Hi Y.b
Sorry for top post, just a general comments for now.
Is it ok to keep FSL_ESDHC for i.MX compatible devices and use FSL_ESDHC_XX for
QoriQ devices? In this way, you could minimize code changes.
.
Regards,
Peng.
> > >
> > > > -Original Message-
> > > > From: Y.b. Lu
> > > > Sent: Thu
Hi Philipp,
On Mon, Apr 22, 2019 at 12:11 AM Philipp Tomsich
wrote:
>
> > u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and
> > which is U-Boot specific devicetrees binding.
> >
> > Move it on global rk3399-u-boot.dtsi file and rest of the U-Boot
> > bindings will move it future
when compiling dts file using DTC_FLAG='-@', the device tree compiler
reports these warnings:
Warning (alias_paths): /aliases: aliases property name must include
only lowercase and '-'
Fixed the node aliases to silence these warnings.
Signed-off-by: Pankaj Bansal
---
board/freescale/ls1043aqds
72 matches
Mail list logo
