On Thu, 2023-05-18 at 11:24 -0700, emohand...@linux.microsoft.com
wrote:
>
> From: Ehsan Mohandesi
>
> The argument len passed to function process_ra is the length of the
> IPv6
> router advertisement message and needs to be between 0 and MTU
> because
> it is assigned to remaining_option_len an
On Thu, 2023-05-18 at 11:24 -0700, emohand...@linux.microsoft.com
wrote:
> From: Ehsan Mohandesi
>
> The structure icmp6_ra_prefix_info needs to be packed because it is
> read
> from a network stream.
>
> Signed-off-by: Ehsan Mohandesi
> ---
> include/net6.h | 2 +-
> 1 file changed, 1 inserti
On 5/19/23 06:30, Venkatesh Yadav Abbarapu wrote:
From: Algapally Santosh Sagar
The DEFAULT_ENV_IS_RW is moved to the Kconfig for easier configuration.
Hence, the CONFIG_DEFAULT_ENV_IS_RW config is added to the defconfig files
to allow enabling them for armada boards.
Signed-off-by: Algapal
On 5/19/23 06:30, Venkatesh Yadav Abbarapu wrote:
From: Algapally Santosh Sagar
The DEFAULT_ENV_IS_RW is moved to the Kconfig for easier configuration.
Hence, the CONFIG_DEFAULT_ENV_IS_RW config is added to the defconfig files
to allow enabling them for armada boards.
Signed-off-by: Algapal
Hi Marek,
> On 5/9/23 17:04, Lukasz Majewski wrote:
> > Hi Marek,
> >
> >> On 5/9/23 16:46, Lukasz Majewski wrote:
> >>> Hi Marek,
> >>
> >> Hi,
> >>
> On 5/9/23 16:32, Lukasz Majewski wrote:
> > This option sets the current limit for 5V source to zero, so all
> > the PMU o
.de/u-boot/custodians/u-boot-efi (2023-05-16 11:23:30 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-rockchip.git
tags/u-boot-rockchip-20230519
for you to fetch changes up to fd6e425be243dce518a02710482514faccf3c211:
rockchip: rk3588-rock-5b: E
Firmware version management is not implemented in the current
FMP implementation. This series aims to add the versioning support
in FMP.
Currently, there is no way to know the current running firmware
version through the EFI interface. FMP->GetImageInfo() returns
always 0 for the version number. S
The number of image array entries global variable is required
to support EFI capsule update. This information is exposed as a
num_image_type_guids variable, but this information
should be included in the efi_capsule_update_info structure.
This commit adds the num_images member in the
efi_capsule_u
Firmware version management is not implemented in the current
FMP protocol.
EDK II reference implementation capsule generation script inserts
the FMP Payload Header right before the payload, FMP Payload Header
contains the firmware version and lowest supported version.
This commit utilizes the FMP
Current FMP->GetImageInfo() always return 0 for the firmware
version, user can not identify which firmware version is currently
running through the EFI interface.
This commit reads the "FmpState" EFI variable, then fills the
firmware version in FMP->GetImageInfo().
Now FMP->GetImageInfo() and
This commit gets the lowest supported version from device tree,
then fills the lowest supported version in FMP->GetImageInfo().
Signed-off-by: Masahisa Kojima
---
Changed in v6:
- fw_version is removed from device tree
.../firmware/firmware-version.txt | 22
lib/efi_loader/
The FMP Payload Header which EDK II capsule generation scripts
insert has a firmware version.
This commit reads the lowest supported version stored in the
device tree, then check if the firmware version in FMP payload header
of the ongoing capsule is equal or greater than the
lowest supported versi
This commit describes the procedure to add the firmware version
into the capsule file.
Signed-off-by: Masahisa Kojima
---
Newly created in v6
doc/develop/uefi/uefi.rst | 29 +
1 file changed, 29 insertions(+)
diff --git a/doc/develop/uefi/uefi.rst b/doc/develop/uefi
Current mkeficapsule tool does not provide firmware
version management. EDK II reference implementation inserts
the FMP Payload Header right before the payload.
It coutains the fw_version and lowest supported version.
This commit adds a new parameters required to generate
the FMP Payload Header fo
This commit describe the procedure to configure lowest supported
version in the device tree for anti-rollback protection.
Signed-off-by: Masahisa Kojima
---
Newly created in v6
doc/develop/uefi/uefi.rst | 32
1 file changed, 32 insertions(+)
diff --git a/doc/de
This patch series fixes i.MX28 based XEA board to utilize DM_SERIAL
Changes:
- Patches 1-3 - fix DTS (after Linux update) to debrick XEA
- Patches 4-8 - prepare XEA's DTS to support DM_SERIAL
- Patches 9-11 - fixes serial_pl01x.c driver (as this driver is
used by XEA, I would pref
After the re-sync with Linux Kernel's DTS
(SHA1: 7d08ddd09b75e7a3c103cc0d0d3ed700287f268e), the XEA's
descripion has nodes and properties, which are NOT utilized
in the u-boot.
To avoid confusion - those are deleted.
Signed-off-by: Lukasz Majewski
---
arch/arm/dts/imx28-xea-u-boot.dtsi | 16 ++
After the commit (SHA1: 7d08ddd09b75e7a3c103cc0d0d3ed700287f268e) some
u-boot specific XEA FEC related properties have been replaced by ones
from the Linux kernel.
To be more specific - XEA board (and imx287 in general) has built L2
switch connected to FEC, which needs some special treatment.
In
After the re-sync with Linux kernel (v6.0) of the XEA DTS
(SHA1: 7d08ddd09b75e7a3c103cc0d0d3ed700287f268e) the alias
for SPI bus, to which SPI-NOR memory is connected, has changed from
'spi3' to 'spi2'.
To be in sync with current u-boot's xea dts, the default bus number
(which allows running 'sf
This code fixes following WARNING:
DTOCspl/dts/dt-plat.c
fsl_imx28_clkctrl: WARNING: the driver fsl_imx28_clkctrl was not found in the
driver list
As imx28 doesn't yet support common clock framework, this prevents from
DTOC warnings during SPL build.
Signed-off-by: Lukasz Majewski
---
b
After enabling DM_SERIAL for XEA board, the same serial shall be used
in the SPL (with SPL_OF_PLATDATA support).
Signed-off-by: Lukasz Majewski
---
arch/arm/dts/imx28-xea-u-boot.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/dts/imx28-xea-u-boot.dtsi
b/arch/arm/dts/imx28
The DM_SERIAL implicitly requires CONFIG_PL01X_SERIAL, which
allows support for both serial IP block versions (i.e. PL011 and
PL010).
The decision about used IP block is based on the compatible string,
when DM is used.
In the XEA, the OF_PLATDATA is used to allow usage of serial driver in
the SPL
The imx287 SoC doesn't support common clock framework (CCF), so the
'clocks' property is removed to avoid early (i.e. in SPL) errors when
SPL_OF_PLATDATA is used.
Signed-off-by: Lukasz Majewski
---
arch/arm/dts/imx28-xea-u-boot.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/d
As imx28 family of SoCs is NOT supporting the Common Clock Framework (CCF)
the 'clks' property shall NOT be enabled by default.
Without this change u-boot proper before relocation tries to bind driver
(which doesn't exists) for this device. As a result, pre-relocation DTB
parsing is finished with
This commit prepares the pl01x serial driver to be used with
SPL_OF_PLATDATA enabled.
Signed-off-by: Lukasz Majewski
---
drivers/serial/serial_pl01x.c | 12
include/dm/platform_data/serial_pl01x.h | 4
2 files changed, 16 insertions(+)
diff --git a/drivers/serial/s
Before this change, building this driver for SPL with enabled SPL_DM_SERIAL
was problematic, as '-Wunused-const-variable=' warning was visible.
Now, the code is only considered when u-boot proper is build.
Signed-off-by: Lukasz Majewski
---
drivers/serial/serial_pl01x.c | 2 +-
1 file changed,
Before this change the FR_TXFF (Transmit FIFO full) bit (5 in
HW_UARTDBG_FR) has been used to assess if there is still data pending
to be sent via UART.
This approach is problematic, as it may happen that serial is in the
middle of transmission (so the TX FIFO is NOT full anymore) and this
test re
The in-spl enabled DM serial console requires the board setup to be
able to parse SPL_OF_PLATDATA based serial driver (pl01x) for the
imx28 based XEA board.
Signed-off-by: Lukasz Majewski
---
board/liebherr/xea/xea.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/board/liebherr/xea/xea.c b
The CONFIG_PL011 used by all other ARCH_MX28 based boards is not
supporting DM_SERIAL. Instead, other define - namely CONFIG_PL01X_SERIAL
shall be used by boards supporting DM_SERIAL.
Signed-off-by: Lukasz Majewski
---
arch/arm/Kconfig | 2 +-
arch/arm/mach-imx/mxs/Kconfig | 1 +
2
The XEA board now supports the DM_SERIAL feature in u-boot.
The SPL is using the SPL_OF_PLATDATA - i.e. NOT SPL_DM_SERIAL to
reduce the overall size of the SPL binary.
Signed-off-by: Lukasz Majewski
---
configs/imx28_xea_defconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -
When DM_SERIAL is enabled on mxs (i.e. imx28) platform, the console
early initialization must be postponed until the driver model is
correctly setup.
Signed-off-by: Lukasz Majewski
---
arch/arm/cpu/arm926ejs/mxs/spl_boot.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
The single binary version of u-boot for XEA board is used to debrick and
factory programming.
The produced u-boot.sb is a single file, which allows having fully
operational u-boot prompt loaded with imx287 ROM.
Signed-off-by: Lukasz Majewski
---
configs/imx28_xea_sb_defconfig | 2 ++
1 file c
HI Jassi, Michal
Based on the discussion we had on the dt bindings, I am personally ok with
the notion of having those defined internally until we can prove it makes
sense for the to be sent to the dt-schema.
In the future we need to strip those from U-Boot, before we hand over the
DR to the OS,
Hi Colin,
On 19/05/2023 02:19, Colin Foster wrote:
> Hi Roger,
>
> I really appreciate the help!
>
> On Thu, May 18, 2023 at 01:55:38PM +0300, Roger Quadros wrote:
>> Hi Colin,
>>
>> On 17/05/2023 22:39, Colin Foster wrote:
>>>
>>> I swapped in just U-Boot (not the SPL) with your patch, and ever
On 5/19/23 10:41, Lukasz Majewski wrote:
Hello Lukasz,
On 5/9/23 16:32, Lukasz Majewski wrote:
This option sets the current limit for 5V source to zero, so all
the PMU outputs are primarily powered from battery source
(DCDC_BAT).
This option may be set on systems, where the 5V is NOT supposed
Hi Ilias,
On 5/19/23 14:21, Ilias Apalodimas wrote:
HI Jassi, Michal
Based on the discussion we had on the dt bindings, I am personally ok with
the notion of having those defined internally until we can prove it makes
sense for the to be sent to the dt-schema.
In the future we need to strip th
Hi Abdellatif
I still have some concerns on this
In the past [0] I asking why this needs to be a Kconfig option. Since FF-A
is a mechanism we can use to discover SPs, in theory we dont need the
ifdefery. We might need something if the code difference grows too much
but I think we are fine for n
On Fri, May 12, 2023 at 01:10:35PM +0100, Abdellatif El Khlifi wrote:
> add support for x0-x17 registers used by the SMC calls
>
> In SMCCC v1.2 [1] arguments are passed in registers x1-x17.
> Results are returned in x0-x17.
>
> This work is inspired from the following kernel commit:
>
> arm64:
Schema file in YAML must be provided in board/ti/common for validating
input config files and packaging system firmware. The schema includes
entries for rm-cfg, board-cfg, pm-cfg and sec-cfg.
Board config files must be provided in board/ti/ in YAML.
These can then be consumed for generation of bin
Buffers created through DEFINE_(CACHE_)ALIGN_BUFFER are actually
pointers to the real underlying buffer. Using sizeof(...) is
not appropriate in this case.
Signed-off-by: Sam Edwards
---
drivers/mmc/mmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/mmc.c b/dr
In this patch series
- Add support in Kconfig and convert for armada boards
- Fetch baudrate from the dtb and update
Changes in v4:
- Moved SERIAL_DT_BAUD to another patch
- Added doc file for fetching serial baudrate from DT.
- Changed Kconfig SERIAL_DT_BAUD to OF_SERIAL_DT_BAUD
- Added function
From: Algapally Santosh Sagar
The baudrate configured in .config is taken by default by serial. If
change of baudrate is required then the .config needs to changed and
u-boot recompilation is required or the u-boot environment needs to be
updated.
To avoid this, support is added to fetch the bau
From: Algapally Santosh Sagar
The DEFAULT_ENV_IS_RW is moved to the Kconfig for easier configuration.
Hence, the CONFIG_DEFAULT_ENV_IS_RW config is added to the defconfig files
to allow enabling them for armada boards.
Signed-off-by: Algapally Santosh Sagar
Signed-off-by: Venkatesh Yadav Abbara
From: Algapally Santosh Sagar
Add fallthrough statement in switch case to fix the sparse warning.
In function 'zynqmp_clk_get_rate': warning: this statement may
fall through [-Wimplicit-fallthrough=]
Signed-off-by: Algapally Santosh Sagar
Signed-off-by: Venkatesh Yadav Abbarapu
---
drivers/cl
From: Algapally Santosh Sagar
Add missing prototype to fix the sparse warning.
warning: no previous prototype for 'bl2_plat_get_bl31_params'
[-Wmissing-prototypes]
Signed-off-by: Algapally Santosh Sagar
Signed-off-by: Venkatesh Yadav Abbarapu
---
arch/arm/mach-zynqmp/handoff.c | 1 +
1 file c
Fix sparse warnings in below files
- Add fallthrough statement in the switch case
- Add missing header
Algapally Santosh Sagar (2):
clk: zynqmp: Add fallthrough statement in the switch case
mach-zynqmp: handoff: Add missing header
arch/arm/mach-zynqmp/handoff.c | 1 +
drivers/clk/clk_zynqmp.
Hi Tom,
Apologies for being late to the party
> On Thu, May 11, 2023 at 09:52:04AM -0400, Tom Rini wrote:
> On Fri, May 05, 2023 at 10:25:24AM +, Maxim Uvarov wrote:
>
> > Greetings,
> >
> > This RFC patchset is an attempt to try to use an already existing IP
> > network stack inside U-bo
Hi Ilias,
> Hi Abdellatif
>
> I still have some concerns on this
>
> In the past [0] I asking why this needs to be a Kconfig option. Since FF-A
> is a mechanism we can use to discover SPs, in theory we dont need the
> ifdefery. We might need something if the code difference grows too much
> bu
This series adds support for SPI controller which is used in newest
Allwinner SOCs R329/D1/R528/T113s. It includes changes for both
spl_spi_sunxi and uboot spi-sunxi drivers.
The series is based on Andre's attempt to add support for T113s SoC.
https://lore.kernel.org/u-boot/20221206004549.29015-
R528/T113 SoCs uses the same SPI IP as the H6, also have the same clocks
and reset bits layout, but the CCU base is different. Another difference
is that the new SoCs do not have a clock divider inside. Instead of this
we should configure sample mode depending on input clock rate.
The pin assignme
These SoCs have two SPI controllers that are quite similar to the SPI
on previous Allwinner SoCs. The main difference is that new SoCs
don't have a clock divider (SPI_CCR register) inside SPI IP.
Instead SPI sample mode should be configured depending on the input clock.
For now SPI input clock so
Some boards form the MangoPi family (MQ\MQ-Dual\MQ-R) may have
an optional SPI flash that connects to the SPI0 controller.
This controller is the same for R329/D1/R528/T113s SoCs and
should be supported by the sun50i-r329-spi driver.
So let's add its DT nodes.
Signed-off-by: Maxim Kiselev
---
On Fri, May 19, 2023 at 04:17:06PM +0300, Ilias Apalodimas wrote:
> Hi Tom,
>
> Apologies for being late to the party
>
> > On Thu, May 11, 2023 at 09:52:04AM -0400, Tom Rini wrote:
> > On Fri, May 05, 2023 at 10:25:24AM +, Maxim Uvarov wrote:
> >
> > > Greetings,
> > >
> > > This RFC patc
On Fri, May 19, 2023 at 02:36:55PM +0100, Abdellatif El Khlifi wrote:
> Hi Ilias,
>
> > Hi Abdellatif
> >
> > I still have some concerns on this
> >
> > In the past [0] I asking why this needs to be a Kconfig option. Since FF-A
> > is a mechanism we can use to discover SPs, in theory we dont ne
Remove the regulator_set_enable() call from device probe which
resolves a regulator imbalance. This is unnecessary as
regulator_set_enable() will be called when ehci_register calls the
init_after_reset hook.
Suggested-by: Marek Vasut
Signed-off-by: Tim Harvey
---
drivers/usb/host/ehci-mx6.c | 1
On Fri, May 19, 2023 at 02:45:26PM +0200, Michal Simek wrote:
> Hi Ilias,
>
> On 5/19/23 14:21, Ilias Apalodimas wrote:
> > HI Jassi, Michal
> >
> > Based on the discussion we had on the dt bindings, I am personally ok with
> > the notion of having those defined internally until we can prove it m
On Wed, May 3, 2023 at 9:11 AM Tim Harvey wrote:
>
> On Thu, Apr 27, 2023 at 11:09 AM Fabio Estevam wrote:
> >
> > From: Fabio Estevam
> >
> > Sync imx8mp.dtsi and imx8mp-clock.h with Linux 6.3.
> >
> > Signed-off-by: Fabio Estevam
> > ---
> > arch/arm/dts/imx8mp.dtsi | 374 +++
On Fri, May 19, 2023 at 5:19 PM Tim Harvey wrote:
>
> On Wed, May 3, 2023 at 9:11 AM Tim Harvey wrote:
> >
> > On Thu, Apr 27, 2023 at 11:09 AM Fabio Estevam wrote:
> > >
> > > From: Fabio Estevam
> > >
> > > Sync imx8mp.dtsi and imx8mp-clock.h with Linux 6.3.
> > >
> > > Signed-off-by: Fabio E
On Fri, May 19, 2023 at 3:27 PM Adam Ford wrote:
>
> On Fri, May 19, 2023 at 5:19 PM Tim Harvey wrote:
> >
> > On Wed, May 3, 2023 at 9:11 AM Tim Harvey wrote:
> > >
> > > On Thu, Apr 27, 2023 at 11:09 AM Fabio Estevam wrote:
> > > >
> > > > From: Fabio Estevam
> > > >
> > > > Sync imx8mp.dtsi
On Fri, May 19, 2023 at 3:31 PM Tim Harvey wrote:
>
> On Fri, May 19, 2023 at 3:27 PM Adam Ford wrote:
> >
> > On Fri, May 19, 2023 at 5:19 PM Tim Harvey wrote:
> > >
> > > On Wed, May 3, 2023 at 9:11 AM Tim Harvey wrote:
> > > >
> > > > On Thu, Apr 27, 2023 at 11:09 AM Fabio Estevam
> > > >
On Fri, May 19, 2023 at 5:34 PM Tim Harvey wrote:
>
> On Fri, May 19, 2023 at 3:31 PM Tim Harvey wrote:
> >
> > On Fri, May 19, 2023 at 3:27 PM Adam Ford wrote:
> > >
> > > On Fri, May 19, 2023 at 5:19 PM Tim Harvey wrote:
> > > >
> > > > On Wed, May 3, 2023 at 9:11 AM Tim Harvey wrote:
> > >
On Fri, May 19, 2023 at 3:35 PM Adam Ford wrote:
>
> On Fri, May 19, 2023 at 5:34 PM Tim Harvey wrote:
> >
> > On Fri, May 19, 2023 at 3:31 PM Tim Harvey wrote:
> > >
> > > On Fri, May 19, 2023 at 3:27 PM Adam Ford wrote:
> > > >
> > > > On Fri, May 19, 2023 at 5:19 PM Tim Harvey
> > > > wrot
62 matches
Mail list logo
