On Fri, 20 Mar 2020 01:53:16 -0400
Sean Anderson wrote:
> Some of the debug messages in the clock subsystem can be made more
> informative by adding the clock name or adding the explicit error.
>
> Signed-off-by: Sean Anderson
> ---
>
> drivers/clk/clk-uclass.c | 24 +---
On 19/03/20 7:20 pm, Rasmus Villemoes wrote:
> On 19/03/2020 14.23, Vignesh Raghavendra wrote:
>>
>
>>> For the read side, it seems that just replacing the UINT_MAX in the two
>>> copies of spi_nor_read_data with some smaller constant should suffice.
>>> But I don't know if I should make that
Dear Heinrich,
In message you wrote:
>
> > To me this sounds very much like what you are adding here (plus a
> > few features more). Does it make sense to unify such code?
>
> It seems you are relating to
> https://lore.kernel.org/lkml/844oyrqvvb@sauna.l.org/t/
No, I'm not. I was talking
Fix wrong environment variable of board for ls1012afrwy
Signed-off-by: Biwen Li
---
include/configs/ls1012afrwy.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/configs/ls1012afrwy.h b/include/configs/ls1012afrwy.h
index 8ed4defa21..aa57320ac2 100644
---
On Tue, Mar 17, 2020 at 4:01 AM Simon Goldschmidt
wrote:
>
> Am 16.03.2020 um 20:55 schrieb Dalon L Westergreen:
> >
> >
> > On Mon, 2020-03-16 at 20:06 +0100, Marek Vasut wrote:
> >> On 3/16/20 8:04 PM, Simon Goldschmidt wrote:
> >>> Am 16.03.2020 um 19:04 schrieb Dalon L Westergreen:
>
>
On 02/03/2020 14:15, Kristian Amlie wrote:
On 02/03/2020 14:01, Tom Rini wrote:
On Mon, Mar 02, 2020 at 11:22:27AM +0100, Kristian Amlie wrote:
On 28/02/2020 16:32, Tom Rini wrote:
On Tue, Feb 25, 2020 at 06:22:16PM +0100, Kristian Amlie wrote:
EFI was disabled in f95b8a4b5f64f because of
From: Jonathan Corbet
commit 3bc8088464712fdcb078eefb68837ccfcc413c88 upstream.
Our version check in Documentation/conf.py never envisioned a world where
Sphinx moved beyond 1.x. Now that the unthinkable has happened, fix our
version check to handle higher version numbers correctly.
Hi Bin,
Thanks a lot for your comments!
> -Original Message-
> From: Bin Meng
> Sent: 2020年3月19日 19:57
> To: Z.q. Hou
> Cc: U-Boot Mailing List ; Priyanka Jain
>
> Subject: Re: [PATCH 11/12] board: fsl: ls2080a: Initialize the GIC
> redistributor
> tables
>
> On Thu, Mar 19, 2020 at
Hello Wolfgang, Heinrich,
Am 20.03.2020 um 09:08 schrieb Wolfgang Denk:
Dear Heinrich,
In message you wrote:
To me this sounds very much like what you are adding here (plus a
few features more). Does it make sense to unify such code?
It seems you are relating to
Base autodetection is failing for this case:
if test 257 -gt 3ae; then echo first; else echo second; fi
It is because base for 3ae is recognized by _parse_integer_fixup_radix() as
10. The code detects the first char which is not between 'a'/'A' or 'f'/'F'
to change base from dec to hex.
Delay required for clock propagation is tighly coupled with initialization
done in psu_init(). That's why call it also for u-boot proper with
CONFIG_ZYNQMP_PSU_INIT_ENABLED enabled.
Signed-off-by: Michal Simek
---
arch/arm/mach-zynqmp/spl.c | 3 ---
board/xilinx/zynqmp/zynqmp.c | 3 +++
2
board_early_init_f() is the right location where debug uart can be
configurated (after MIO initialization).
The patch is taking this call from SPL to also make it available for U-Boot
proper.
Signed-off-by: Michal Simek
---
arch/arm/mach-zynqmp/spl.c | 6 --
board/xilinx/zynqmp/zynqmp.c
Hi Wolfgang,
> Dear Philippe,
>
> In message <1584644739-10258-1-git-send-email-philippe.rey...@softathome.com>
> you wrote:
>> This commit add the command ubi rename to rename an ubi volume.
>> The format of the command is: ubi rename .
>
> Can we plase make this optional / configurable?
Hello Alex,
Am 20.03.2020 um 01:57 schrieb Alex Nemirovsky:
From: Arthur Li
Add I2C controller support for Cortina Access CA SoCs
Signed-off-by: Arthur Li
Signed-off-by: Alex Nemirovsky
CC: Heiko Schocher
---
Changes in v3: None
Changes in v2: None
MAINTAINERS | 4
From: Yuantian Tang
Add sd and emmc bootcmd environments to facilitate
the boot process.
Signed-off-by: Yuantian Tang
---
v2:
- updated some variable slightly.
include/configs/ls1028aqds.h | 39 ---
1 file changed, 28 insertions(+), 11 deletions(-)
From: Yuantian Tang
Move the environment variables from command head file to
ls1028ardb specific head file so that they will mess up
with ls1028aqds board.
Also updated some variable slightly.
There is no function change by this patch.
Signed-off-by: Yuantian Tang
---
When using CONFIG_(SPL_)WDT, the watchdog_reset function is a lot more
complicated than just poking a few SOC-specific registers - it
involves accessing all kinds of global data, and if the interrupt
happens at the wrong time (say, in the middle of an WATCHDOG_RESET()
call from ordinary code),
The code, which is likely copied from arch/powerpc/lib/interrupts.c,
lacks a fallback definition of CONFIG_SYS_WATCHDOG_FREQ and refers to
a non-existing timestamp variable - obviously priv->timestamp is
meant.
Signed-off-by: Rasmus Villemoes
---
drivers/timer/mpc83xx_timer.c | 6 +-
1 file
From: Tudor Ambarus
This feature should not be enabled in release but can be useful for
developers who need to monitor register accesses at some specific places.
Helped me identify a bug in u-boot, by comparing the register accesses
from the u-boot driver with the ones from its linux variant.
From: Tudor Ambarus
The sama5d2 QSPI controller memory space is limited to 128MB:
0x9000_0-0x9800_0/0XD000_--0XD800_.
There are nor flashes that are bigger in size than the memory size
supported by the controller: Micron MT25QL02G (256 MB).
Check if the address exceeds the MMIO
From: Tudor Ambarus
Commit: 0ebb261a0b2d ("spi: spi-mem: Add SPI_MEM_NO_DATA to the
spi_mem_data_dir enum")
in linux.
When defining spi_mem_op templates we don't necessarily know the size
that will be passed when the template is actually used, and basing the
supports_op() check on
Dear Vignesh,
In message <20200320101448.10714-1-rasmus.villem...@prevas.dk> Rasmus Villemoes
wrote:
> I have a board for which doing "sf erase 0x10 0x8"
> consistently causes the external watchdog circuit to reset the
> board. Make sure to pet the watchdog during slow operations such as
Hi Wolfgang, Heinrich, Heiko,
On 20/03/2020 09:08, Wolfgang Denk wrote:
Dear Heinrich,
In message you wrote:
To me this sounds very much like what you are adding here (plus a
few features more). Does it make sense to unify such code?
It seems you are relating to
Adjust environment kernel_addr_r from 0x9600 to 0x9200
to fix a bug that failed to boot kernel for ls1012afrwy with 512MiB RAM,
=> tftpboot $kernel_addr_r Image (Image size is 36 MiB)
TFTP error: trying to overwrite reserved memory...
Signed-off-by: Biwen Li
---
Dear Frédéric,
In message <03674974-2a2c-3804-ce02-4f3d38ff0...@collabora.com> you wrote:
>
> > I understand what Linus has is one-way, only focussing on crash
> > dump, i. e. it does not allow to pass information from U-Boot to Linux?
>
> Yes, currently it is not possible to pass information
Dear Wolfgang,
On 20/03/2020 11:35, Wolfgang Denk wrote:
Dear Frédéric,
In message <03674974-2a2c-3804-ce02-4f3d38ff0...@collabora.com> you wrote:
I understand what Linus has is one-way, only focussing on crash
dump, i. e. it does not allow to pass information from U-Boot to Linux?
Yes,
This patch adds a new pstore command allowing to display or save ramoops
logs (oops, panic, console, ftrace and user) generated by a previous
kernel crash.
PStore parameters can be set in U-Boot configuration file, or at run-time
using "pstore set" command. Records size should be the same as the
This serie of patches adds a new pstore command allowing to display or save
ramoops logs (oops, panic, console, ftrace and user) generated by a previous
kernel crash.
PStore parameters can be set in U-Boot configuration file, or at run-time
using "pstore set" command. For kernel using Device Tree,
Hi Petr,
On 18. 03. 20 10:57, Petr Štetiar wrote:
> At this moment unusable binaries are produced if bl31.bin file is
> missing in order to allow passing of various CI tests. This intention of
> broken binaries has to be now explicitly confirmed via new
> BUILDBOT_BROKEN_BINARIES config option,
Dear Rasmus,
In message <20200320105248.24518-1-rasmus.villem...@prevas.dk> you wrote:
> The code, which is likely copied from arch/powerpc/lib/interrupts.c,
> lacks a fallback definition of CONFIG_SYS_WATCHDOG_FREQ and refers to
> a non-existing timestamp variable - obviously priv->timestamp is
Hi Sean,
On 3/19/20 7:37 PM, Sean Anderson wrote:
diff --git a/test/py/tests/test_dm.py b/test/py/tests/test_dm.py
index f6fbf8ba4c..97203b536e 100644
--- a/test/py/tests/test_dm.py
+++ b/test/py/tests/test_dm.py
@@ -4,14 +4,32 @@
import pytest
@pytest.mark.buildconfigspec('cmd_dm')
This commit add the command ubi rename to rename an ubi volume.
The format of the command is: ubi rename .
To enable this command, the option CMD_UBI_RENAME must be selected.
Signed-off-by: Philippe Reynes
---
cmd/Kconfig | 8
cmd/ubi.c | 43
Add PStore command to sandbox and sandbox64 defconfigs.
Add test checking:
- 'pstore display' of all records
- 'pstore display' only the 2nd dump record
- 'pstore save' of all records
Signed-off-by: Frédéric Danis
Cc: Tom Rini
Cc: Heinrich Schuchardt
Cc: Wolfgang Denk
Cc: Heiko Schocher
---
To simplify configuration and keep synchronized the PStore/Ramoops between
U-Boot and the Linux kernel, this commit dynamically adds the Ramoops
parameters defined in the U-Boot session to the Device Tree.
Signed-off-by: Frédéric Danis
Cc: Tom Rini
Cc: Heinrich Schuchardt
Cc: Wolfgang Denk
Some boards have a watchdog with a short (~1s) timeout and a slowish
nor flash. For example, I'm currently working on a board where doing a
2MB read from the flash will cause the board to reset.
Similar to the various CHUNKSZ, CHUNKSZ_SHA1 etc. defines that are
used to chop hash digest and/or
I have a board for which doing "sf erase 0x10 0x8"
consistently causes the external watchdog circuit to reset the
board. Make sure to pet the watchdog during slow operations such as
erasing or writing large areas of a spi nor flash.
Signed-off-by: Rasmus Villemoes
---
Dear Frédéric,
In message <9b0b5776-cb47-dfb2-ab77-36c89dc64...@collabora.com> you wrote:
>
> But, when debugging kernel crashes occurring either early in boot or
> hard crashes later, it can be helpful to be able to retrieve logs using
> the U-Boot session.
Full agreement, and we had such a
Dear Rasmus,
In message <20200320140414.19689-1-rasmus.villem...@prevas.dk> you wrote:
>
> Having different fw_env.config files for the different revisions is
> highly impractical, and the correct information is already available
> right at our fingertips. So use the erasesize returned by the
>
On 20/03/2020 15.11, Wolfgang Denk wrote:
> Dear Rasmus,
>
> In message <20200320140414.19689-1-rasmus.villem...@prevas.dk> you wrote:
>>
>> Having different fw_env.config files for the different revisions is
>> highly impractical, and the correct information is already available
>> right at our
We have a board with several revisions. The older ones use a nor flash
with 64k erase size, while the newer have a flash with 4k sectors. The
environment size is 8k.
Currently, we have to put a column containing 0x1 (64k) in
fw_env.config in order for it to work on the older boards. But that
On 20/03/2020 15.27, Rasmus Villemoes wrote:
> On 20/03/2020 15.11, Wolfgang Denk wrote:
>> Dear Rasmus,
>>
>> In message <20200320140414.19689-1-rasmus.villem...@prevas.dk> you wrote:
>>>
>>> Having different fw_env.config files for the different revisions is
>>> highly impractical, and the
As of today 'random' command return 1 (CMD_RET_FAILURE) in case
of successful execution and 0 (CMD_RET_SUCCESS) in case of bad
arguments. Fix that.
NOTE: we remove printing usage information from command body
so it won't print twice.
Signed-off-by: Eugeniy Paltsev
---
cmd/mem.c | 9 -
This patch adds .dtsi file(sync with Linux 5.5-rc6 with hash "b3a987b0264d")
and required binding for S700 SoC that is a 64-bit Quad-core ARM
Cortex-A53 cores.
It also provisions dts file to be built based on selected
platform(CONFIG_MACH_S900/S700).
Reviewed-by: Andre Przywara
Signed-off-by:
The Cubieboard is a single board computer containing a
Actions S700 SoC(with 4 ARMv8 Cortex-A53 cores).
This patch adds respective defconfig alongwith .dts(copied
from Linux v5.5-rc6 with hash "b3a987b0264d").
Reviewed-by: Andre Przywara
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
Devices like uart and clk are needed to be enabled before relocation.
this patch adds u-boot.dtsi file that mark these device as dm-pre-reloc.
Reviewed-by: Andre Przywara
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* No changes.
Changes since v5:
* Added reviwed-by
This adds build and flash steps for Actions S700
based Cubieboard7 board.
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* No changes.
Changes since v5:
* No changes.
Changes since v4:
* No changes.
Changes since v3:
* Convert plain text documentation to
This adds Cubieboard7[1] support based on Action Semi's S700 SoC[2], It's
Quad-core ARMv8 SoC
with Cortex-A53 cores. Peripheral like UART seems to be compatible with S900
SoC(basic support
for it is alreay present in u-boot).
This Series(v7) fixes a serious Bug that breaks S900, it was there
Now that memory maps(for both S700 and S900 SoCs) can be managed using
a common file, rename sysmap-s900 to sysmap-owl to reflect the same.
Reviewed-by: Manivannan Sadhasivam
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* No changes.
Changes since v5:
* No changes.
This patch adds "actions,owl-uart" string to the owl uart driver. It
is also defined in Linux kernel.
Reviewed-by: Andre Przywara
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* Added Reviewd-by tag.
Changes since v5:
* Moved it to from 06/11 to 03/11.
* Used
Devices like uart and clk are needed to be enabled before relocation.
This patch adds u-boot.dtsi file that mark these device as dm-pre-reloc.
Reviewed-by: Manivannan Sadhasivam
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* No changes.
Changes since v5:
* No changes.
There is established way to provide I²C timings, or actually counters,
to the OS via ACPI. Fill them for Intel Merrifield platform.
Signed-off-by: Andy Shevchenko
---
.../asm/arch-tangier/acpi/southcluster.asl| 20 +++
1 file changed, 20 insertions(+)
diff --git
On Mon, Mar 16, 2020 at 05:51:51PM +0100, Jan-Christoph Tebbe wrote:
> When generating the MAC address based on the boards serial number
> the last digit was overwritten with the null termination. That way
> boards with serial numbers close to each other would use the same
> MAC address.
>
>
This patch converts S900 clock driver to something common that can
be used for other SoCs, for instance S700(few of clk registers are same).
Reviewed-by: Andre Przywara
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* Fixed the bug that breaks S900(missing break in switch
This patch adds basic support for Actions Semi based S700
SoC, which is driven by common owl framework.
Reviewed-by: Andre Przywara
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* No changes.
Changes since v5:
* Added reviewed-by tag.
Changes since v4:
* Moved it
Synchronize device tree bindings with v5.5-rc6 tag with commit id
"b3a987b0264d".
Also, it removes older clock binding defined for S900 along with undocumented
compatible string "actions,s900-serial" from serial driver and adapts clock
driver to cater to new bindings.
Reviewed-by: Andre Przywara
This patch moves some of the config options from bubblegum_96_defconfig
to platform specific Kconfig file.
Reviewed-by: Andre Przywara
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* remove unnecessary string from SYS_PROMPT.
Changes since v5:
* Newly added patch, was
This commit adds common arch support for Actions Semi Owl
series SoCs and removes the Bubblegum96 board files.
Signed-off-by: Amit Singh Tomar
---
Changes since v6:
* No change.
Changes since v5:
* No change.
Changes since v4:
* No change.
Changes since v3:
*
There is established way to provide I²C timings, or actually counters,
to the OS via ACPI. Fill them for Intel Merrifield platform.
Signed-off-by: Andy Shevchenko
---
v2: added high speed mode counters
.../asm/arch-tangier/acpi/southcluster.asl| 30 +++
1 file changed, 30
GetNextVariableName should report the length of the variable including the
final 0x in bytes.
Check this in the unit test.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_selftest/efi_selftest_variables.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
The runtime service GetNextVariable() returns the length of the next
variable including the closing 0x. This length should be in bytes.
Comparing the output of EDK2 and U-Boot shows that this is currently not
correctly implemented:
EDK2:
OsIndicationsSupported: 46
PlatformLang: 26
On Mon, Mar 16, 2020 at 08:09:53PM +0100, Jan Kiszka wrote:
> Hi all,
>
> => ls mmc 0:1 /usr/lib/linux-image-4.9.11-1.3.0-dirty
> CACHE: Misaligned operation at range [bdfff998, bdfffd98]
> CACHE: Misaligned operation at range [bdfff998, bdfffd98]
> CACHE: Misaligned operation at range [bdfff998,
On Wed, Mar 18, 2020 at 09:48:36AM +0100, Michal Simek wrote:
> Hi,
>
> long time ago I was playing with switching among consoles.
> I have two IPs with the same driver where main console is probed and
> used which is visible via dm tree.
>
> serial1 [ + ] serial_zynq |
The runtime service GetNextVariable() returns the length of the next
variable including the closing 0x. This length should be in bytes.
Comparing the output of EDK2 and U-Boot shows that this is currently not
correctly implemented:
EDK2:
OsIndicationsSupported: 46
PlatformLang: 26
On Wed, Mar 18, 2020 at 01:14:43PM +0100, marek.bykow...@gmail.com wrote:
> From: Marek Bykowski
>
> If a system wants the malloc to get moved around from one to another
> memory range it should call mem_malloc_init() with the updated memory
> ranges. However setting aside the new memory alone
On Mon, Feb 10, 2020 at 4:05 PM wrote:
>
> From: Alexandre GRIVEAUX
>
> Add Inet 86V Rev 2 support, based upon Inet 86VS.
>
> Missing things:
> - Accelerometer (MXC6225X)
> - Touchpanel (Sitronix SL1536)
> - Nand (29F32G08CBACA)
> - Camera (HCWY0308)
>
> Signed-off-by: Alexandre GRIVEAUX
> ---
From: Josip Kelečić
Sort the Armada series dts in the Makefile alphabetically
prior to adding new board support.
Signed-off-by: Josip Kelečić
Reviewed-by: Luka Kovacic
Cc: Luka Perkov
---
arch/arm/dts/Makefile | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
From: Tom Warren
Add Macronix MX25U3235F flash device description.
This is the 4MB part used on Jetson Nano.
Signed-off-by: Tom Warren
---
drivers/mtd/spi/spi-nor-ids.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
index
From: Tom Warren
This Tegra QSPI driver hadn't been brought up to date with how
DM drivers are fetching data from the FDT now, and was pulling
in bogus data for base, max freq, etc. Fixed ofdata_to_platdata
to work the same way it does in the tegra114 SPI driver, using
dev_read_ functions.
On 18/03/2020 18:25, Amit Singh Tomar wrote:
Hi,
> This commit adds common arch support for Actions Semi Owl
> series SoCs and removes the Bubblegum96 board files.
>
> Signed-off-by: Amit Singh Tomar
> ---
> Chanes since v5:
> * No change.
> Chanes since v4:
> * No change.
>
69 matches
Mail list logo
