On Fri, Jun 04, 2021 at 10:02:03PM +0300, Alper Nebi Yasak wrote:
> The filesystem and EFI (capsule and secure boot) test setups try to use
> guestmount and virt-make-fs respectively to prepare disk images to run
> tests on. However, these libguestfs tools need a kernel image and fail
> with the
On Fri, Jun 04, 2021 at 03:15:52PM +0200, Stefan Roese wrote:
> Hi Tom,
>
> please pull the next batch of Marvell Armada related patches:
>
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On 6/4/21 9:02 PM, Alper Nebi Yasak wrote:
Some sandbox-only test setups use virt-make-fs and guestmount, which
require a readable kernel to work. However, no such kernel is currently
available on the Docker container image that is used to run the tests on
CIs.
Although a previous patch adds a
On 6/4/21 9:02 PM, Alper Nebi Yasak wrote:
The filesystem and EFI (capsule and secure boot) test setups try to use
guestmount and virt-make-fs respectively to prepare disk images to run
tests on. However, these libguestfs tools need a kernel image and fail
with the following message (revealed in
The doc says CONFIG_SKIP_LOWLEVEL_INIT is in ax25-ae350.h, while
actually it is not. Remove it.
Signed-off-by: Bin Meng
---
doc/board/AndesTech/ax25-ae350.rst | 19 ---
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/doc/board/AndesTech/ax25-ae350.rst
Some filesystem tests are failing when their image is prepared with
guestmount, but succeeding if loop mounts are used instead. The reason
seems to be a race condition the guestmount(1) manual page explains:
When guestunmount(1)/fusermount(1) exits, guestmount may still be
running and
If guestmount isn't available on the system, filesystem test setup falls
back to using loop mounts to prepare its disk images. If guestmount is
available but fails to work, the tests are immediately skipped. Instead
of giving up on a guestmount failure, try using loop mounts as an
attempt to keep
Some sandbox-only test setups use virt-make-fs and guestmount, which
require a readable kernel to work. However, no such kernel is currently
available on the Docker container image that is used to run the tests on
CIs.
Although a previous patch adds a kernel package to the Dockerfile used
to
The filesystem test setup needs to prepare disk images for its tests,
with either guestmount or loop mounts. The former requires access to the
host fuse device (added in a previous patch), the latter requires access
to host loop devices. Both mounts also need additional privileges since
docker's
The EFI secure boot and capsule test setups need to prepare disk images
for their tests using virt-make-fs, which requires access to the host
fuse device. This is not exposed to the docker container by default and
has to be added explicitly.
Since these tests are marked to run only on the sandbox
The filesystem and EFI (capsule and secure boot) test setups try to use
guestmount and virt-make-fs respectively to prepare disk images to run
tests on. However, these libguestfs tools need a kernel image and fail
with the following message (revealed in debug/trace mode) if it can't
find one:
After my previous patch to fix filesystem tests [1] was merged, I
noticed the GitLab CI was still skipping them and wanted to figure out
why. In short: libguestfs tools (virt-make-fs, guestmount) fail because
they need an installed kernel and the host /dev/fuse device, loop mounts
need the host
Hi Chris:
It's my honor to read about spi-rockchip-sfc driver from you, and your code has
made a big difference to me.
Recently, we happen to be willing to submit the spi-mem rk sfc drivers, and we
have tried some of them
in the internal process. Compared with the RK internal code, I have the
ZeroPi is a new board of high performance with low cost
designed by FriendlyElec., using the Allwinner H3 SOC.
ZeroPi features
- Allwinner H3, Quad-core Cortex-A7@1.2GHz
- 256MB/512MB DDR3 RAM
- microsd slot
- 10/100/1000Mbps Ethernet
- Debug Serial Port
- DC 5V/2A power-supply
Signed-off-by:
On 2021/06/04 12:58, Sean Anderson wrote:
> This is something I've been meaning to do for a while but only just got around
> to. The CCF has been quite unwieldy in a few ways:
>
> * It is very rigid, and there are not easy ways to hook into it without
> rewriting many things. See e.g. things
On 6/4/21 1:26 PM, Adam Ford wrote:
The driver is based on the Versaclock driver from the Linux code, but
due differences in the clock API between them, some pieces had to be
changed.
This driver creates a mux, pfd, pll, and a series of fod ouputs.
Rate Usecnt Name
The driver is based on the Versaclock driver from the Linux code, but
due differences in the clock API between them, some pieces had to be
changed.
This driver creates a mux, pfd, pll, and a series of fod ouputs.
Rate Usecnt Name
--
Hi Patrice,
On 2/26/21 1:44 PM, Patrice Chotard wrote:
At early U-Boot stage, before relocation, MMU is not yet configured
and disabled. DDR may not be configured with the correct memory
attributes (can be configured in MT_DEVICE instead of MT_MEMORY).
In this case, usage of memcpy_{from,
Hi Patrice,
On 2/24/21 1:48 PM, Patrice Chotard wrote:
From: Patrice Chotard
Fix following compilation issue when SYS_DCACHE_OFF is enable:
drivers/misc/scmi_agent.c:128: undefined reference to
`mmu_set_region_dcache_behaviour'
when SYS_DCACHE_OFF is enable,
Thanks Patrice,
On 4/20/21 12:24 PM, Patrice CHOTARD wrote:
Hi Patrick
On 3/4/21 5:47 PM, Patrick Delaunay wrote:
For NOR devices the logical DFU buffer size is the sector_size,
as it is done in dfu_sf.c or in spi/sf_mtd.c
(sf_mtd_info.erasesize = flash->sector_size)
For NAND the DFU size
Aswath, Suman, Dave, Gowtham, Vignesh
On 6/4/21 11:49 AM, Aswath Govindraju wrote:
Hi Praneeth,
On 04/06/21 10:18 pm, Praneeth Bajjuri wrote:
On 6/4/21 11:30 AM, Aswath Govindraju wrote:
The following series of patches add support for the following
- Kconfig symbol for giving the load
Add the missing dependency for the command ums:
- CONFIG_BLK: call of blk_* functions in usb_mass_storage.c
- CONFIG_USB_GADGET: required to select CONFIG_USB_FUNCTION_MASS_STORAGE
Signed-off-by: Patrick Delaunay
---
Changes in v2:
- NEW: Add dependency for ums command
cmd/Kconfig | 5 -
V2 for [1], after Heinrich remarks.
[1] doc: usage: man-page for ums command
http://patchwork.ozlabs.org/project/uboot/list/?series=246862=both=*
Changes in v2:
- NEW: Add dependency for ums command
- clarify description
- add reference to and align parameter name
- correct information for
Provide a man-page for the ums command - USB Mass Storage.
Signed-off-by: Patrick Delaunay
---
Changes in v2:
- clarify description
- add reference to and align parameter name
- correct information for partition = 0 (expose all partitions)
- update dependency
doc/usage/index.rst | 1 +
Hi Praneeth,
On 04/06/21 10:18 pm, Praneeth Bajjuri wrote:
>
>
> On 6/4/21 11:30 AM, Aswath Govindraju wrote:
>> The following series of patches add support for the following
>> - Kconfig symbol for giving the load address for ATF
>> - USB Mass storage boot mode in AM642-EVM
>> - DFU boot mode
On 6/4/21 11:30 AM, Aswath Govindraju wrote:
The following series of patches add support for the following
- Kconfig symbol for giving the load address for ATF
- USB Mass storage boot mode in AM642-EVM
- DFU boot mode in AM642-EVM
- Host and peripheral modes for AM642-EVM in U-Boot
- Set the
Enable config options required to add support for USB Mass storage boot,
USB DFU boot, host and device modes in U-Boot.
Signed-off-by: Aswath Govindraju
---
configs/am64x_evm_a53_defconfig | 39 +
configs/am64x_evm_r5_defconfig | 36
Due to a limitation for USB DFU boot mode, SPL load address has to be less
than or equal to 0x70001000. So, load address of SPL and ATF have been
moved to 0x7000 and 0x701a respectively.
Also, the maximum size of ATF has been increased to 0x1c000 [1].
Therefore, update ATF's location
For USB DFU boot mode there is a limitation on the load address of boot
images that they have to be less than 0x70001000. Therefore, move the
SPL_TEXT_BASE address to 0x7000.
Currently ATF is being loaded at 0x7000, if the SPL is being loaded at
0x7000 then ATF would overwrite SPL
Add U-Boot tags and fix the dr_mode as peripheral in U-Boot to support DFU
by default.
Signed-off-by: Aswath Govindraju
---
arch/arm/dts/k3-am642-evm-u-boot.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/dts/k3-am642-evm-u-boot.dtsi
AM64 EVM board has a micro USB 2.0 AB connector and the USB0_VBUS is
connected with a resistor divider in between. USB0_DRVVBUS pin is muxed
between USB0_DRVVBUS and GPIO1_79 signals.
Add the corresponding properties and set the pinmux mode for USB subsystem
in the evm dts file.
Signed-off-by:
Add DT node for the single USB subsystem in main dtsi file.
Signed-off-by: Aswath Govindraju
---
arch/arm/dts/k3-am64-main.dtsi | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/dts/k3-am64-main.dtsi b/arch/arm/dts/k3-am64-main.dtsi
index
Set the core voltage of USB PHY in AM64x to 0.85V in spl_board_init().
Signed-off-by: Aswath Govindraju
---
board/ti/am64x/evm.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/board/ti/am64x/evm.c b/board/ti/am64x/evm.c
index 35cd9e027c04..cdbb9a87bc44 100644
---
U-Boot either supports USB host or device mode for a node at a time in the
device tree nodes. To support both host and dfu bootmodes, dr_mode is set
to "peripheral" by default and then fixed based on the mode selected by
the boot mode config dip switches on the board.
This needs to happen before
Add support for identifying USB host and device boot modes
Signed-off-by: Aswath Govindraju
---
arch/arm/mach-k3/am642_init.c | 13 +++--
arch/arm/mach-k3/include/mach/am64_hardware.h | 5 +
arch/arm/mach-k3/include/mach/am64_spl.h | 6 --
3 files changed,
Add support for providing ATF load address with a Kconfig symbol.
Signed-off-by: Aswath Govindraju
Reviewed-by: Suman Anna
---
arch/arm/mach-k3/Kconfig | 7 +++
arch/arm/mach-k3/config.mk | 1 +
tools/k3_fit_atf.sh| 9 ++---
3 files changed, 14 insertions(+), 3 deletions(-)
The following series of patches add support for the following
- Kconfig symbol for giving the load address for ATF
- USB Mass storage boot mode in AM642-EVM
- DFU boot mode in AM642-EVM
- Host and peripheral modes for AM642-EVM in U-Boot
- Set the USB PHY core voltage to 0.85V
changes since v2,
-
Use the correct name for STMicroelectronics phys config properties,
replace '_' by '-':
"st,eth_clk_sel" => "st,eth-clk-sel"
"st,eth-ref-clk-sel" => st,eth-clk-sel"
These property name are aligned with the upstreamed Linux kernel binding:
Use the correct name for STMicroelectronics phys config properties,
replace '_' by '-':
"st,eth_clk_sel" => "st,eth-clk-sel"
"st,eth-ref-clk-sel" => st,eth-clk-sel"
These property name are aligned with the upstreamed Linux kernel binding:
On 6/4/21 11:56 AM, Adam Ford wrote:
On Fri, Jun 4, 2021 at 9:29 AM Sean Anderson wrote:
On 6/4/21 10:22 AM, Adam Ford wrote:
> The driver is based on the Versaclock driver from the Linux code, but
> due differences in the clock API between them, some pieces had to be
> changed.
On Fri, Jun 4, 2021 at 9:29 AM Sean Anderson wrote:
>
>
>
> On 6/4/21 10:22 AM, Adam Ford wrote:
> > The driver is based on the Versaclock driver from the Linux code, but
> > due differences in the clock API between them, some pieces had to be
> > changed.
> >
> > This driver creates a mux,
Am Fri, Jun 04, 2021 at 04:56:05AM + schrieb Anand Moon:
> Use the generic error number instead of specific error number.
> Changes fix the below error.
>
> drivers/pci/pcie_dw_rockchip.c: In function 'rk_pcie_read':
> drivers/pci/pcie_dw_rockchip.c:70:10: error: 'PCIBIOS_UNSUPPORTED'
>
Am Fri, Jun 04, 2021 at 04:56:06AM + schrieb Anand Moon:
> Drop the unused variable warning below.
>
> drivers/pci/pcie_dw_rockchip.c:161:6: warning: unused variable
> 'val' [-Wunused-variable]
> 161 | u32 val;
>| ^~~
> Cc: Patrick Wildt
> Cc: Neil Armstrong
> Cc: Kever Yang
Am Fri, Jun 04, 2021 at 04:56:07AM + schrieb Anand Moon:
> Replace msleep occurences by udelay.
>
> drivers/pci/pcie_dw_rockchip.c:254:3: warning: implicit
> declaration of function 'msleep' [-Wimplicit-function-declaration]
>
> Cc: Patrick Wildt
> Cc: Neil Armstrong
> Cc: Kever Yang
Hi Aleksandar,
On 6/3/21 6:40 AM, Aleksandar Gerasimovski wrote:
Hi Folks,
I hope you are all doing well!
Is it possible this patch to get some attention?
Thanks!
Regards,
Aleksandar
-Original Message-
From: Tom Rini
Sent: Freitag, 30. April 2021 13:53
To: Aleksandar Gerasimovski ;
On Fri, Jun 04, 2021 at 09:42:18PM +0800, 林鼎强 wrote:
>
> Hi Chris:
>
> It's my honor to read about spi-rockchip-sfc driver from you, and your code
> has made a big difference to me.
>
> Recently, we happen to be willing to submit the spi-mem rk sfc drivers, and
> we have tried some of them
>
On 6/4/21 10:22 AM, Adam Ford wrote:
> The driver is based on the Versaclock driver from the Linux code, but
> due differences in the clock API between them, some pieces had to be
> changed.
>
> This driver creates a mux, pfd, pll, and a series of fod ouputs.
> Rate Usecnt
Hi
On 6/2/21 8:06 PM, Heinrich Schuchardt wrote:
On 6/2/21 3:52 PM, Patrick Delaunay wrote:
Provide a man-page for the ums command for USB Mass Storage.
Signed-off-by: Patrick Delaunay
---
doc/usage/index.rst | 1 +
doc/usage/ums.rst | 54 +
On 6/4/21 1:05 PM, Zhengxun wrote:
The Clocking Wizard IP supports clock circuits customized
to your clocking requirements. The wizard support for
dynamically reconfiguring the clocking primitives for
Multiply, Divide, Phase Shift/Offset, or Duty Cycle.
Limited by U-Boot clk uclass without
The driver is based on the Versaclock driver from the Linux code, but
due differences in the clock API between them, some pieces had to be
changed.
This driver creates a mux, pfd, pll, and a series of fod ouputs.
Rate Usecnt Name
--
Current tsec adapter sets adapter gigabit capabilities by default, and in
reality this must not always be the case.
It is possible that tsec adapter is used for 100Mbps connection, and in
this case setting 1000Mbps capabilities can lead to some side effects such
longer autoneg process.
In our
Hi Tom,
please pull the next batch of Marvell Armada related patches:
- mvebu: a37xx: PCI related enhancements and fixes (Pali)
- mvebu: turris_omnia: Board specific updates, e.g. rescue
boot cmd etc (Marek)
On 28.05.21 10:00, Marek Behún wrote:
Make it possible to invoke rescue boot from U-Boot console, without
having to press the factory reset button. This is needed when accessing
the device remotely, for example.
Achieve this by putting rescue command into `bootcmd_rescue` default
environment
On 28.05.21 10:00, Marek Behún wrote:
Update rescue mode boot command on Turris Omnia. We are compressing the
image with lzma now.
Signed-off-by: Marek Behún
Applied to u-boot-marvell/master
Thanks,
Stefan
---
board/CZ.NIC/turris_omnia/turris_omnia.c | 9 +++--
1 file changed, 7
On 26.05.21 17:59, Pali Rohár wrote:
During our debugging of the Aardvark driver in Linux we have discovered
that the PCIE_CORE_LINK_CTRL_STAT_REG register in fact controls standard
PCIe Link Control Register for PCIe Root Bridge. This led us to discover
that the name of the
On Fri, Jun 4, 2021 at 8:05 PM Aleksandar Gerasimovski
wrote:
>
> Current tsec adapter sets adapter gigabit capabilities by default, and in
> reality this must not always be the case.
> It is possible that tsec adapter is used for 100Mbit connection, and in
> this case setting 1000Mbit
Current tsec adapter sets adapter gigabit capabilities by default, and in
reality this must not always be the case.
It is possible that tsec adapter is used for 100Mbit connection, and in
this case setting 1000Mbit capabilities can lead to some side effects such
longer autoneg process.
In our
On Fri, Jun 04, 2021 at 11:13:36AM +, Aleksandar Gerasimovski wrote:
> Current tsec adapter sets adapter gigabit capabilities by default, and in
> reality this must not always be the case.
> It is possible that tsec adapter is used for 100Mbit connection, and in
> this case setting 1000Mbit
Current tsec adapter sets adapter gigabit capabilities by default, and in
reality this must not always be the case.
It is possible that tsec adapter is used for 100Mbit connection, and in
this case setting 1000Mbit capabilities can lead to some side effects such
longer autoneg process.
In our
Enable EFI capsule update support. With the EFI capsule update,
you can update U-Boot, TF-A and OP-TEE. TF-A and OP-TEE are
usually combined as a FIP binary, but if the binary is bigger
than 480KB, you have to modify FIP header, split the OP-TEE
and stores the OP-TEE binary in the different place.
Since the EDK2 GenerateCapsule script is out of date and it
doesn't generate the supported version capsule file, the document
should refer the mkeficapsule in tools.
Signed-off-by: Masami Hiramatsu
---
doc/board/emulation/qemu_capsule_update.rst | 11 ++-
1 file changed, 2
Add the DeveloperBox 96boards EE support. This board is also
known as Socionext SynQuacer E-Series. It contians one "SC2A11"
SoC, which has 24-cores of arm Cortex-A53, and 4 DDR3 slots,
3 PCIe slots (1 4x port and 2 1x ports which are expanded via
PCIe bridge chip), 2 USB 3.0 ports and 2 USB 2.0
Add device trees for 96boards EE DeveloperBox and basement SynQuacer
SoC dtsi. These files are imported from EDK2
commit 83d38b0b4c0f240d4488c600bbe87cea391f3922
as-is (except for the changes #include path and some macros).
And add U-Boot specific changes in
From: Jassi Brar
Add driver for class of I2C controllers found on
Socionext Synquacer platform.
Signed-off-by: Jassi Brar
---
drivers/i2c/Kconfig |7 +
drivers/i2c/Makefile|1
drivers/i2c/synquacer_i2c.c | 338 +++
3 files
From: Jassi Brar
Add SynQuacer's NETSEC GbE controller driver.
Since this driver will load the firmware from SPI NOR flash,
this depends on CONFIG_SYNQUACER_SPI=y.
Signed-off-by: Jassi Brar
---
drivers/net/Kconfig |8
drivers/net/Makefile |1
drivers/net/sni_netsec.c | 1134
From: Jassi Brar
This is a driver for the HSSPI SPI controller on SynQuacer SoC.
The HSSPI has command sequence mode (memory mapped) and
direct mode (FIFO access). The driver will operate it under
the direct mode. And before booting OS, it switch back to the
command sequence mode since that is
From: Jassi Brar
Signed-off-by: Jassi Brar
Signed-off-by: Masami Hiramatsu
Reviewed-by: Jaehoon Chung
---
Changes in v4:
- Add Jaehoon's reviewed-by.
Changes in v3:
- Rename config name to MMC_SDHCI_F_SDH30.
- Remove unneeded wait in drivers/mmc/sdhci.c.
- Rename probe function to
Add ECAM based SynQuacer PCIe RC driver. This driver configures the
PCIe RC and filter out a ghost pcie config.
Since the Linux kernel expects "socionext,synquacer-pcie-ecam" device
is configured by firmware (EDK2), it doesn't re-configure in the kernel.
So as same as EDK2, U-Boot needs to
Since some SoCs and boards do not hae extra asm/arch/gpio.h,
introduce CONFIG_GPIO_EXTRA_HEADER instead of adding
!define(CONFIG_ARCH_) in asm/gpio.h.
Signed-off-by: Masami Hiramatsu
---
Changes in v3:
- Change the config name to positive and selected by the
opposite
When running the efidebug capsule disk-update command, the efi_fmp_raw
protocol installation is failed with 2 (EFI_INVALID_PARAMETER) as
below. This is because the code passes efi_root instaed of handle.
=> efidebug capsule disk-update
EFI: Call: efi_install_multiple_protocol_interfaces( ,
Commit bbbcb5262839 ("dm: pci: Enable VGA address forwarding on bridges")
sets the VGA bridge bits by checking pplat->class, but if the parent
device is the pci host bus device, it can be skipped. Moreover, it
shouldn't access the pplat because the parent has different plat data.
Without this
Without this fix, scsi-scan will cause a synchronous abort
when accessing ops->scan.
Signed-off-by: Masami Hiramatsu
Reviewed-by: Simon Glass
---
drivers/ata/ahci-pci.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/ata/ahci-pci.c b/drivers/ata/ahci-pci.c
index
Hi,
Here is the 5th version of the series (including some fixes for build
errors) to add SynQuacer/DeveloperBox 96board EE suport on U-Boot.
This series includes not only DeveloperBox support but also some fixes
for the issues which I faced while porting U-Boot on the DeveloperBox.
First 3
On 28.05.21 10:00, Marek Behún wrote:
Make it possible to invoke rescue boot from U-Boot console, without
having to press the factory reset button. This is needed when accessing
the device remotely, for example.
Achieve this by putting rescue command into `bootcmd_rescue` default
environment
On 28.05.21 10:00, Marek Behún wrote:
Update rescue mode boot command on Turris Omnia. We are compressing the
image with lzma now.
Signed-off-by: Marek Behún
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
board/CZ.NIC/turris_omnia/turris_omnia.c | 9 +++--
1 file changed, 7
On 02.06.21 14:42, Marek Behún wrote:
On Wed, 2 Jun 2021 07:12:50 +0200
Stefan Roese wrote:
Hello Stefan! Thank you for review. Would you be sending these A3720
patches to 2021.07 version?
My plan was to postpone these patches to the next release, as they
seem quite intrusive. But please
Commit df86d32 breaks linux kernel and product application boot.
Linux kernel and our product application scripts are expecting 0x prefix
for hexadecimal values, while env_set_hex writes them without a prefix.
This patch partially revert env_set_hex usage for affected env variables.
During the mainlining of the board this was by mistake set to sector size.
Our user space env scripts are expecting envsize of 0x4000, and setting
this differently will break our cross-platform compatibility.
Signed-off-by: Aleksandar Gerasimovski
---
configs/pg_wcom_seli8_defconfig | 2 +-
1
Add the devicetree binding for the xilinx clocking wizard.
Signed-off-by: Zhengxun
---
.../clock/xlnx,clocking-wizard.txt| 43 +++
1 file changed, 43 insertions(+)
create mode 100644 doc/device-tree-bindings/clock/xlnx,clocking-wizard.txt
diff --git
The Clocking Wizard IP supports clock circuits customized
to your clocking requirements. The wizard support for
dynamically reconfiguring the clocking primitives for
Multiply, Divide, Phase Shift/Offset, or Duty Cycle.
Limited by U-Boot clk uclass without set_phase API, this
patch only provides
Add support to enable clock wizard for zynq platform.
Changes in v5:
- add devicetree binding
- use FIELD_PREP and FIELD_GET
- use clk_get_by_name()
- add clk_free()
Changes in v4:
- rearrange functions
- remove Superfluous words
- check kernel-doc comments
Changes in v3:
- remove incorrect
On Mon, May 17, 2021 at 10:03 AM Bin Meng wrote:
>
> Hi Simon,
>
> On Fri, Apr 30, 2021 at 9:17 PM Bin Meng wrote:
> >
> > 'dma-ranges' frequently exists without parent nodes having 'dma-ranges'.
> > While this is an error for 'ranges', this is fine because DMA capable
> > devices always have a
82 matches
Mail list logo
