Am 2022-02-02 07:35, schrieb Jan Kiszka:
From: Jan Kiszka
Do not suggest successful operation if a flash area to be changed is
actually locked, thus will not execute the request. Rather report an
error and bail out. That's way more user-friendly than asking them to
manually check for this case.
hi Masami,
On Wed, 2 Feb 2022 at 12:33, Masami Hiramatsu
wrote:
>
> Hi Sughosh,
>
> 2022年2月2日(水) 14:35 Sughosh Ganu :
> >
> > hi Masami,
> >
> > On Wed, 2 Feb 2022 at 05:39, Masami Hiramatsu
> > wrote:
> > >
> > > Hi Sughosh,
> > >
> > > Could you tell me why do you need to do the FWU code in th
>-Original Message-
>From: Tom Rini
>Sent: Saturday, January 22, 2022 10:05 PM
>To: Pali Rohár ; Alison Wang ;
>Priyanka Jain ; Mingkai Hu ;
>Rajesh Bhagat
>Cc: Simon Glass ; Alexandru Gagniuc
>; Yann Dirson ; Stefan
>Roese ; Marek Behún ; u-
>b...@lists.denx.de
>Subject: Re: [PATCH v2
On 02.02.22 09:21, Michael Walle wrote:
> Am 2022-02-02 07:35, schrieb Jan Kiszka:
>> From: Jan Kiszka
>>
>> Do not suggest successful operation if a flash area to be changed is
>> actually locked, thus will not execute the request. Rather report an
>> error and bail out. That's way more user-frie
Add a driver for the timer counter block that can be found on sama5d2.
This driver will be used when booting under OP-TEE since the pit timer
which is part of the SYSC is secured. Channel 1 & 2 are configured to
be chained together which allows to have a 64bits counter.
Signed-off-by: Clément Lége
When booting under OP-TEE, the SYSC is secured which means the PIT is
also not accessible by non-secure world. The TCB 0 however is always
available for non-secure world and thus can be used.
This series add a TCB driver and enables it in sama5d2 configs.
Clément Léger (3):
timer: atmel_tcb_time
Add the device-tree node to describe the TCB timer.
Signed-off-by: Clément Léger
---
arch/arm/dts/sama5d2.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/dts/sama5d2.dtsi b/arch/arm/dts/sama5d2.dtsi
index 038cd73c03..c03a9d423c 100644
--- a/arch/arm/dts/sama5d2.dtsi
+++ b
This will allow using the TCB timer instead of the PIT one when running
under OP-TEE.
Signed-off-by: Clément Léger
---
configs/sama5d2_icp_mmc_defconfig| 1 +
configs/sama5d2_ptc_ek_mmc_defconfig | 1 +
configs/sama5d2_ptc_ek_nandflash_defconfig | 1 +
configs/sama5d2_xplai
Am 2022-02-02 10:38, schrieb Jan Kiszka:
On 02.02.22 09:21, Michael Walle wrote:
Am 2022-02-02 07:35, schrieb Jan Kiszka:
From: Jan Kiszka
Do not suggest successful operation if a flash area to be changed is
actually locked, thus will not execute the request. Rather report an
error and bail o
On 02.02.22 10:38, Jan Kiszka wrote:
> On 02.02.22 09:21, Michael Walle wrote:
>> Am 2022-02-02 07:35, schrieb Jan Kiszka:
>>> From: Jan Kiszka
>>>
>>> Do not suggest successful operation if a flash area to be changed is
>>> actually locked, thus will not execute the request. Rather report an
>>>
On Mon, Jan 31, 2022 at 2:48 PM Adam Ford wrote:
>
> On Mon, Jan 31, 2022 at 2:45 PM Michael Nazzareno Trimarchi
> wrote:
> >
> > Hi
> >
> > On Mon, Jan 31, 2022 at 9:34 PM Adam Ford wrote:
> > >
> > > On Mon, Jan 31, 2022 at 2:25 PM Michael Nazzareno Trimarchi
> > > wrote:
> > > >
> > > > HI A
Implement PSCI system suspend and placement of DRAM into SSR while the
CPUs are in suspend. This saves non-trivial amount of power in suspend,
on 2x W632GU6NB-15 ~710mW.
Signed-off-by: Marek Vasut
Cc: Patrick Delaunay
Cc: Patrice Chotard
---
arch/arm/mach-stm32mp/include/mach/stm32.h | 3 +
Hi all
I have now able to pack those combination and all of them look ok
- mainline uboot
- optee 3.15.0
- atf 2.5
- mainline kernel
- mainline uboot
- optee 3.15.0
- imx-atf rel_imx_5.4.70_2.3.2
- Linux rel_imx_5.4.70_2.3.2
I have a setup where I can test some peripherals. I can run an optee
t
nulldev_serial_input is static and not used in this file,
so remove it.
Signed-off-by: Heiko Schocher
---
azure build is clean
https://dev.azure.com/hs0298/hs/_build/results?buildId=78&view=results
drivers/serial/serial_nulldev.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/s
if CONFIG_DM_STDIO is defined but SERIAL_PRESENT not,
gcc drops warnings for serial_stub_* functions
that they are defined but not used.
Fix it.
Signed-off-by: Heiko Schocher
---
azure build is clean
https://dev.azure.com/hs0298/hs/_build/results?buildId=78&view=results
drivers/serial/serial-u
On Wed, Feb 2, 2022 at 6:24 AM Michael Nazzareno Trimarchi
wrote:
>
> Hi all
>
> I have now able to pack those combination and all of them look ok
>
> - mainline uboot
> - optee 3.15.0
> - atf 2.5
> - mainline kernel
>
> - mainline uboot
> - optee 3.15.0
> - imx-atf rel_imx_5.4.70_2.3.2
> - Linux
Hi Adam
On Wed, Feb 2, 2022 at 2:02 PM Adam Ford wrote:
>
> On Wed, Feb 2, 2022 at 6:24 AM Michael Nazzareno Trimarchi
> wrote:
> >
> > Hi all
> >
> > I have now able to pack those combination and all of them look ok
> >
> > - mainline uboot
> > - optee 3.15.0
> > - atf 2.5
> > - mainline kernel
Hi,
Here is the 3rd version of the reset after capsule-on-disk. This version
updates the patch description and use do_reset() and halt or reset_cpu()
if available, according to Takahiro and Sughosh's comment.
The reset after completing the capsule-on-disk is stated in the UEFI
specification 2.9,
Since the efi_update_capsule() represents the UpdateCapsule() runtime
service, it has to handle the capsule flags and update ESRT.
However, the capsule-on-disk doesn't need to care about such things.
Thus, the capsule-on-disk should use the efi_capsule_update_firmware()
directly instead of calling
Add a config option to reset system soon after processing capsule update
on disk. This is required in UEFI specification 2.9 Section 8.5.5
"Delivery of Capsules via file on Mass Storage device" as;
In all cases that a capsule is identified for processing the system is
restarted after caps
On 1/31/22 15:49, Simon Glass wrote:
This converts the following to Kconfig:
CONFIG_SCSI_AHCI_PLAT
CONFIG_SYS_SCSI_MAX_SCSI_ID
CONFIG_SYS_SCSI_MAX_LUN
CONFIG_SYS_SATA_MAX_DEVICE
Drop CONFIG_SCSI for everything except the sandbox build. We only need
one build for tests.
Signed-of
Hey,
We're supporting a device that has some hardware variants. As those variants
can be of A different kinds on B different interfaces, we end up with A*B = N
different hardware variations.
Currently we have N device trees in the FIT image, but we noticed that it
doesn't scale anymore: Any new
On 2022-01-31 07:20, Ovidiu Panait wrote:
There are no boards that define CONFIG_SYS_RESET_ADDR, so drop the
remaining comments referencing it and also the config_whitelist.txt
entry.
Signed-off-by: Ovidiu Panait
---
include/configs/10m50_devboard.h | 9 -
include/configs/3c120_devb
Add the device-tree node to describe the TCB timer.
Signed-off-by: Clément Léger
---
arch/arm/dts/sama5d2.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/dts/sama5d2.dtsi b/arch/arm/dts/sama5d2.dtsi
index 038cd73c03..fc6a4fbe4d 100644
--- a/arch/arm/dts/sama5d2
This will allow using the TCB timer instead of the PIT one when running
under OP-TEE.
Signed-off-by: Clément Léger
---
configs/sama5d2_icp_mmc_defconfig| 1 +
configs/sama5d2_ptc_ek_mmc_defconfig | 1 +
configs/sama5d2_ptc_ek_nandflash_defconfig | 1 +
configs/sama5d2_xplai
Add a driver for the timer counter block that can be found on sama5d2.
This driver will be used when booting under OP-TEE since the pit timer
which is part of the SYSC is secured. Channel 1 & 2 are configured to
be chained together which allows to have a 64bits counter.
Signed-off-by: Clément Lége
When booting under OP-TEE, the SYSC is secured which means the PIT is
also not accessible by non-secure world. The TCB 0 however is always
available for non-secure world and thus can be used.
This series add a TCB driver and enables it in sama5d2 configs.
---
Changes in v2:
- Reworked driver to u
Update to the 5.16 imx8mq dts files and dt bindings
Changes since v1:
Dropped rfkill.h that is not in linux mainline yet.
Signed-off-by: Angus Ainslie
---
arch/arm/dts/imx8mq.dtsi | 203 --
include/dt-bindings/interconnect/imx8mq.h | 48 +
2 files chan
On Wed, Feb 2, 2022 at 5:04 AM Michael Nazzareno Trimarchi
wrote:
>
> Hi Adam
>
> On Wed, Feb 2, 2022 at 2:02 PM Adam Ford wrote:
> >
> > On Wed, Feb 2, 2022 at 6:24 AM Michael Nazzareno Trimarchi
> > wrote:
> > >
> > > Hi all
> > >
> > > I have now able to pack those combination and all of them
Hi Angus,
On Wed, Feb 2, 2022 at 12:31 PM Angus Ainslie wrote:
>
> Update to the 5.16 imx8mq dts files and dt bindings
>
> Changes since v1:
>
> Dropped rfkill.h that is not in linux mainline yet.
Nit: the "Changes since v1" text should go after the --- line.
Reviewed-by: Fabio Estevam
Hi guys
On Sun, 2021-11-21 at 18:05 +0200, Oleksandr Suvorov wrote:
>
> Add support of the Fairchild's FXL6408 i2c gpio expander and enable
> this driver for Toradex Colibri iMX8QXP SoM.
Any progress in applying this patch series?
I just applied it again on today's master and it still cleanly a
On Wed, Feb 2, 2022 at 3:36 AM Adam Ford wrote:
>
> On Mon, Jan 31, 2022 at 2:48 PM Adam Ford wrote:
> >
> > On Mon, Jan 31, 2022 at 2:45 PM Michael Nazzareno Trimarchi
> > wrote:
> > >
> > > Hi
> > >
> > > On Mon, Jan 31, 2022 at 9:34 PM Adam Ford wrote:
> > > >
> > > > On Mon, Jan 31, 2022 at
On Mon, Jan 31, 2022 at 10:44 PM Fabio Estevam wrote:
>
> Hi Marcel,
>
> On Mon, Jan 31, 2022 at 7:08 PM Marcel Ziswiler wrote:
> >
> > From: Marcel Ziswiler
> >
> > Seems that we need the waterlevel setting not only for PIO mode as
> > without this at least the i.MX 8M Mini won't boot anymore w
Hi Tim et al.
On Wed, 2022-02-02 at 08:27 -0800, Tim Harvey wrote:
> On Wed, Feb 2, 2022 at 3:36 AM Adam Ford wrote:
[snip]
>
> To give some numbers to the SPL size issue here is what I've found:
> - lpddr4 dram config structs are about 3K each (I know I have 3 of
> them currently in my IMX8MM
Hi Marcel,
[Adding Tom and Marek]
On Wed, Feb 2, 2022 at 2:40 PM Marcel Ziswiler
wrote:
> > The blocker to getting non-dm-spl-usb support for IMX8M appears to be
> > the base addresses and instead of adding more of them to imx-regs.h we
> > need to get them from DT via of_platdata which nobody
The pstore command tries to create a reserved-memory node but fails if
it is already present with:
Add 'reserved-memory' node failed: FDT_ERR_EXISTS
This patch creates the node only if it does not exist and adapts the reg
values sizes depending on already present #address-cells and #size-cell
AM64x devices have a main ESM and a MCU ESM. The ESM driver enables
routing of the error events from various sources to different processors
or to reset hardware logic. Only the MCU ESM's high output can trigger
reset logic. The main RTI0 WWDT output can be routed to the MCU
highoutput to trigger r
In the Linux implementation of adc-keys
(drivers/input/keyboard/adc-keys.c), `press-threshold-microvolt` is not
really interpreted as a threshold, but rather as the "nominal voltage"
of the button. When the voltage read from the ADC is closest to a
button's `press-threshold-microvolt`, the button i
Sorry.. The patches are being re-submitted after rebasing.
Thanks
-Original Message-
From: U-Boot On Behalf Of Nagalla, Hari
Sent: Wednesday, February 2, 2022 11:10 AM
To: u-boot@lists.denx.de
Cc: Menon, Nishanth
Subject: [PATCH 0/5] Add ESM driver support for AM64x R5
AM64x devices ha
AM64x devices have a main ESM and a MCU ESM. The ESM driver enables
routing of the error events from various sources to different processors
or to reset hardware logic. Only the MCU ESM's high output can trigger
reset logic. The main RTI0 WWDT output can be routed to the MCU
highoutput to trigger r
Enable acces to ESM0 configuration space and add Main ESM0 and MCU ESM
nodes to the AM64 device tree.
Signed-off-by: Hari Nagalla
---
arch/arm/dts/k3-am64.dtsi| 1 +
arch/arm/dts/k3-am642-r5-evm.dts | 19 +++
arch/arm/dts/k3-am642-r5-sk.dts | 19 +++
3 f
Enable ESM driver for AM64x R5 SPL/u-boot builds.
Signed-off-by: Hari Nagalla
---
configs/am64x_evm_r5_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/am64x_evm_r5_defconfig b/configs/am64x_evm_r5_defconfig
index 61138dd1a9..e29e99c2d1 100644
--- a/configs/am64x_evm_r5_defc
On AM64x devices, it is possible to route Main ESM0 error events to MCU
ESM. MCU ESM high error output can trigger the reset logic to reset the
device. So, for these devices we expect two ESM device nodes in the
device tree, one for Main ESM and the another MCU ESM in the device tree.
When these E
Add functionality to enable, set priority to the input events and to
route to MCU ESM. On AM64x/AM62x devices, it is possible to route Main
ESM0 error events to MCU ESM. When these error events are routed to MCU
ESM high output, it can trigger the reset logic to reset the device,
when CTRLMMR_MCU_R
On Wed, Feb 02, 2022 at 02:45:44PM -0300, Fabio Estevam wrote:
> Hi Marcel,
>
> [Adding Tom and Marek]
>
> On Wed, Feb 2, 2022 at 2:40 PM Marcel Ziswiler
> wrote:
>
> > > The blocker to getting non-dm-spl-usb support for IMX8M appears to be
> > > the base addresses and instead of adding more of
On Wed, Feb 2, 2022 at 12:42 PM Tom Rini wrote:
>
> On Wed, Feb 02, 2022 at 02:45:44PM -0300, Fabio Estevam wrote:
> > Hi Marcel,
> >
> > [Adding Tom and Marek]
> >
> > On Wed, Feb 2, 2022 at 2:40 PM Marcel Ziswiler
> > wrote:
> >
> > > > The blocker to getting non-dm-spl-usb support for IMX8M ap
Mirroring commit 97ab802aa36f ("adc: meson-saradc: add support for
getting reference voltage value") for meson-saradc, this adds support
for getting the "vref-supply" regulator and register it as the ADC's
reference voltage regulator, so clients can translate sampled ADC values
to voltage.
Signed-
Hi Tom,
I've attached version 2 of the patch. I believe this should adhere more
closely to your suggestions.
Keep in mind, CONFIG_IS_ENABLED will not work for checking
CMD_BOOTI/CMD_BOOTZ in this case, as there is no CONFIG_SPL_CMD_BOOTx. So,
I'm just directly checking if it's defined instead.
Hi Tom,
I've attached v2 of this patch. I've also confirmed again that the
offending lines are entirely unnecessary and amended the patch to delete
them instead.
Sincerely,
Nathan
On Mon, Jan 31, 2022 at 10:23 AM Tom Rini wrote:
> On Mon, Jan 31, 2022 at 10:16:08AM -0500, Nathan Barrett-Morri
SION (Software Input On Field) - force the select mode input path
Signed-off-by: Angus Ainslie
---
arch/arm/include/asm/mach-imx/iomux-v3.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/include/asm/mach-imx/iomux-v3.h
b/arch/arm/include/asm/mach-imx/iomux-v3.h
index 9330a32fe9..2
dwc3 driver fixes to work better with the linux kernel.
Angus Ainslie (2):
usb: dwc3: dwc3-generic: check the parent nodes
usb: dwc3: core: stop the core when it's removed
drivers/usb/dwc3/core.c | 9 +
drivers/usb/dwc3/dwc3-generic.c | 25 -
2 files
If u-boot doesn't stop the core when it's finished with it then
linux can't find it.
Signed-off-by: Angus Ainslie
---
drivers/usb/dwc3/core.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index ce1c0e88c2..b592a487e0 100644
--- a/d
The kernel devicetree has definitions for port and hub nodes as subnodes
to the USB devices. These subnodes don't contain all of the data required
to properly configure the dwc3. Check the parent nodes if the data is not
in the port/hub node.
Here's an example from the librem5 kernel dts file
&us
Put guards around the devres code so that it isn't compiled during the SPL.
Signed-off-by: Angus Ainslie
---
drivers/core/devres.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/core/devres.c b/drivers/core/devres.c
index 313ddc7089..92a237c64c 100644
--- a/driver
Hi
On Wed, Feb 2, 2022 at 4:54 PM Tim Harvey wrote:
>
> On Wed, Feb 2, 2022 at 5:04 AM Michael Nazzareno Trimarchi
> wrote:
> >
> > Hi Adam
> >
> > On Wed, Feb 2, 2022 at 2:02 PM Adam Ford wrote:
> > >
> > > On Wed, Feb 2, 2022 at 6:24 AM Michael Nazzareno Trimarchi
> > > wrote:
> > > >
> > >
On 1/31/22 7:41 PM, Andre Przywara wrote:
> According to their TRMs, Cortex ARMv7 CPUs with SMP support require the
> ACTLR.SMPEN bit to be set as early as possible, before any cache or TLB
> maintenance operations are done. As we do those things still in start.S,
> we need to move the SMPEN bit se
On 1/31/22 7:41 PM, Andre Przywara wrote:
> Remove some pointless #ifdefs from this file, as there are quite too
> many of them already.
>
> Some definitions don't really hurt to have in any case, so remove the
> pointless CONFIG_MMC guard around CONFIG_MMC_SUNXI_SLOT.
>
> The BOARD_SIZE_LIMIT ap
Hi Samuel and Andre,
On Wed, Feb 2, 2022 at 10:06 PM Samuel Holland wrote:
> > ENTRY(cpu_init_cp15)
> > +
> > +#if CONFIG_IS_ENABLED(ARMV7_SET_CORTEX_SMPEN)
>
> There is no SPL-prefixed symbol, so you probably want plain old "#if defined"
> here instead. Otherwise, this code will always be omit
On Wed, Feb 02, 2022 at 10:54:43PM +0900, Masami Hiramatsu wrote:
> Add a config option to reset system soon after processing capsule update
> on disk.
We no longer have a new config option :)
> This is required in UEFI specification 2.9 Section 8.5.5
> "Delivery of Capsules via file on Mass Sto
The vdd_io regulator is present only on DHCOR SoM configured for 1V8 IO,
as populated on Avenger96, but not present on 3V3 DHCOR SoM. Move these
extras to Avenger96 u-boot DT extras.
Fixes: 3919aa1722a ("ARM: dts: stm32: Add DFU support for DHCOR recovery")
Signed-off-by: Marek Vasut
Cc: Patrice
On Wed, Feb 02, 2022 at 06:02:50AM +, Priyanka Jain wrote:
> Dear Tom,
>
> Please find my pull-request for u-boot-fsl-qoriq/master
> https://github.com/u-boot/u-boot/pull/107
>
> Summary
> Update and fixes for ls1088a, FMAN, ls1046ardb, ls1043ardb
> sync ls1028ardb u-boot and Linux device-tr
Hi Takahiro,
2022年2月3日(木) 10:24 AKASHI Takahiro :
>
> On Wed, Feb 02, 2022 at 10:54:43PM +0900, Masami Hiramatsu wrote:
> > Add a config option to reset system soon after processing capsule update
> > on disk.
>
> We no longer have a new config option :)
Oops, that's my fault.
>
> > This is requ
Hello Andrey
> -Original Message-
> From: ZHIZHIKIN Andrey
> Sent: Tuesday, February 1, 2022 3:15 AM
> To: Gaurav Jain ; u-boot@lists.denx.de
> Cc: Stefano Babic ; Fabio Estevam ;
> Peng Fan ; Simon Glass ; Michael
> Walle ; Priyanka Jain ; Ye Li
> ; Horia Geanta ; Ji Luo
> ; Franck Lenor
Hi Takahiro,
We forgot a simple fact. The warm reset doesn't load the new firmware
from media.
If this reset is for reloading the new firmware, we anyway need the
cold reset :-)
(and I can't think of any reason other than this)
Thank you,
2022年2月3日(木) 13:34 Masami Hiramatsu :
>
> Hi Takahiro,
>
Hi Marek
On 2/3/22 02:49, Marek Vasut wrote:
> The vdd_io regulator is present only on DHCOR SoM configured for 1V8 IO,
> as populated on Avenger96, but not present on 3V3 DHCOR SoM. Move these
> extras to Avenger96 u-boot DT extras.
>
> Fixes: 3919aa1722a ("ARM: dts: stm32: Add DFU support for D
65 matches
Mail list logo
