On Fri, Jul 9, 2021 at 1:35 PM Patrick DELAUNAY
wrote:
>
> Hi Ramon,
>
> On 4/26/21 5:46 PM, Patrick Delaunay wrote:
> > It is the V2 version of [1] after Marek remarks: all commit are new.
> >
> > I change the DWC_ETH_QOS STM32 variant by using generic eth phy driver.
> >
> > This driver is updat
On Fri, Jul 9, 2021 at 12:53 PM Peter Hoyes wrote:
>
> From: Peter Hoyes
>
> Use same type as eth_device->iobase and support addresses greater
> than INT_MAX.
>
> Signed-off-by: Peter Hoyes
> ---
> drivers/net/smc9.c | 2 +-
> drivers/net/smc911x.c | 2 +-
> include/netdev.h | 4 ++--
This commit adds the command ubi swap to swap an ubi volumes.
The format of the command is: ubi swap .
To enable this command, the option CMD_UBI_SWAPVOL must be selected.
Signed-off-by: Ayoub Zaki
---
cmd/Kconfig | 8
cmd/ubi.c | 54 +
The rk3318 A95X Z2 boards are sold as TV box.
No further documentation is given, but from the dts files
extracted it seems that the rk3318 processor is simulair
to the rk3328. This dts file contains only the basic nodes
that have support in the mainline kernel. Included extra
dtsi file for U-boot s
From: Peter Hoyes
Use same type as eth_device->iobase and support addresses greater
than INT_MAX.
Signed-off-by: Peter Hoyes
---
drivers/net/smc9.c | 2 +-
drivers/net/smc911x.c | 2 +-
include/netdev.h | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers
Uboot implements the simple file protocol of ext4 file system, already.
However, the driver is embedded in Uboot. Is it possible to build a standalone
ext4 file system driver for UEFI, in the format of efi, just like the
helloworld.efi. So I can use the UEFI shell command: load to load the drive
Hi,
I have been writing SPI Driver in U-Boot for a RISCV Board and is currently
trying to use that to boot linux kernel from SD Card. Right now, I have the
card detected and can view files in various partitions in the SD Card.
After that I try to copy the uImage (created using mkimage command and
On Fri, Jul 09, 2021 at 07:19:36AM +0200, Stefan Roese wrote:
> Hi Tom,
>
> please pull the first batch of Marvell MVEBU related patches. Here the
> summary log:
>
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On Tue, Jun 29, 2021 at 07:33:04PM -0400, Tom Rini wrote:
> As seen with clang-12:
> warning: __asm_invalidate_l3_dcache changed binding to STB_WEAK
>
> As we indeed use ENTRY and then declare the function weak manually. Use
> the WEAK declarative from instead.
>
> Signed-off-by: Tom Rini
Ap
On Sat, May 29, 2021 at 01:34:32PM +0200, Marek Vasut wrote:
> On arm64, board info is not applicable and kernel command line patched into
> the DT, so the LMB reservation here makes no sense anymore. On legacy arm32,
> this might still be necessary on systems which do not use DT or use legacy
> A
On Wed, Feb 24, 2021 at 01:48:42PM +0100, 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, mmu_set_reg
On Wed, Feb 10, 2021 at 08:14:55PM +0100, Mark Kettenis wrote:
> On implementations that support VHE, the layout of the CPTR_EL2
> register depends on whether HCR_EL2.E2H is set. If the bit is
> set, CPTR_EL2 uses the same layout as CPACR_EL1 and can in fact
> be accessed through that register.
On Saturday 10 July 2021 02:43:12 Pali Rohár wrote:
> On Saturday 10 July 2021 02:31:32 Stefan Roese wrote:
> > Could you perhaps add this "SPL returns to BootROM" support as an
> > optional feature that can be selected on a per-board basis?
>
> Hi Stefan! I was thinking about it and it should not
On Saturday 10 July 2021 02:31:32 Stefan Roese wrote:
> Could you perhaps add this "SPL returns to BootROM" support as an
> optional feature that can be selected on a per-board basis?
Hi Stefan! I was thinking about it and it should not be hard. Based on
defconfig options you decide if you want to
Hi Marek,
On 09.07.21 16:08, Marek Behún wrote:
On Fri, 9 Jul 2021 14:35:15 +0200
Stefan Roese wrote:
Thanks. And could you please also do one (or more) boot-time
comparisons, old vs. new version? This way we can see, if and how the
boot-time is affected (perhaps improved, which would be grea
Greetings,
Has anyone successfully used secure boot with IMX8M Mini or other
IMX8M? Peng's recent series got merged with the exception of what
looks like the addition of couple of 'caam' commands to blob/deblob
DEK's.
There are no guides yet however I'm following the guides for the
downstream NXP
> - "bloblist" is a general term for concept of linked list and it's not
> exactly U-boot implementation. The proposed solution will cause some degree
> of changes in all the participating projects. For backward compatibility
> issue, we have already though about it and proposed to have build co
On Friday 09 July 2021 17:40:59 Marek Behún wrote:
> The config option CONFIG_DEBUG_UART_CLOCK is not used by Armada 3720's
> serial driver (it wasn't even before the recent update of that driver).
>
> Even if it was used, the value was incorrect (the frequency of the clock
> is 25 MHz, not 25.804
I recently broke my dominant wrist, so I apologize if this message is
hard to read.
I have been running some tests with the RZ/G2 MNH processors, and I
noticed a difference in behavior between a cold boot, a soft reset,
and a hardware reset.
If I'm in u-boot, an issue the reset instruction, and I
On Thu, Jul 08, 2021 at 08:22:35AM -0400, Trevor Woerner wrote:
> ping?
>
> Tom, have you had a chance to try out this update?
Thanks, I need to do a build/related PR shortly and I'll pick this up
then.
>
> On Tue, Jun 15, 2021 at 3:30 AM Trevor Woerner wrote:
>
> > Update U-Boot's version of
Acked-by twar...@nvidia.com
-Original Message-
From: Tom Rini
Sent: Friday, July 9, 2021 7:12 AM
To: u-boot@lists.denx.de
Cc: Tom Warren
Subject: [PATCHv2 2/4] tegra: Test on CONFIG_CMD_USB being enabled for distro
bootcmd
External email: Use caution opening links or attachments
Reu
On Fri, Jul 09, 2021 at 05:00:09PM +0200, Marek Behún wrote:
> On Fri, 9 Jul 2021 16:56:13 +0200
> Marek Behún wrote:
>
> > Commit e2e95e5e2542 ("spi: Update speed/mode on change") changed the
> > boot time on Turris Omnia from ~2.3s to over 8s, due to SPL loading
> > main U-Boot from SPI NOR at
On Fri, Feb 26, 2021 at 01:44:51PM +0100, 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 m
Please find my replies
To Julius's question:
Just to clarify: are you using "bloblist" as a general term for the concept of
a simple linked list of tagged data blobs, or to refer specifically to the
U-Boot implementation with that name? The existing TF-A implementation
(bl_aux_params) is basica
The config option CONFIG_DEBUG_UART_CLOCK is not used by Armada 3720's
serial driver (it wasn't even before the recent update of that driver).
Even if it was used, the value was incorrect (the frequency of the clock
is 25 MHz, not 25.8048 MHz).
Remove it from config files and set the default valu
Please ignore this. It seems that the option is needed, because it does
not have a default. A different way to solve this is needed. Will post
another patch.
Marek
On Friday 09 July 2021 17:27:02 Marek Behún wrote:
> The config option CONFIG_DEBUG_UART_CLOCK is not used by Armada 3720's
> serial driver (it wasn't even before the recent update of that driver).
>
> Remove it.
>
> Signed-off-by: Marek Behún
> Cc: Stefan Roese
> Cc: Pali Rohár
Reviewed-by:
On Fri, Jul 09, 2021 at 05:02:19PM +0200, Mark Kettenis wrote:
> > From: Tom Rini
> > Date: Fri, 9 Jul 2021 10:39:21 -0400
> >
> > When we build U-Boot with POSITION_INDEPENDENT we must have
> > SYS_TEXT_BASE be set to zero. Make this the default in that case.
>
> Makes sense. I had to set th
The config option CONFIG_DEBUG_UART_CLOCK is not used by Armada 3720's
serial driver (it wasn't even before the recent update of that driver).
Remove it.
Signed-off-by: Marek Behún
Cc: Stefan Roese
Cc: Pali Rohár
---
configs/mvebu_db-88f3720_defconfig | 1 -
configs/mvebu_espressobin
> From: Tom Rini
> Date: Fri, 9 Jul 2021 10:39:21 -0400
>
> When we build U-Boot with POSITION_INDEPENDENT we must have
> SYS_TEXT_BASE be set to zero. Make this the default in that case.
Makes sense. I had to set this for the (still in progress) Apple M1
support. So:
Reviewed-by: Mark Kett
On Fri, 9 Jul 2021 16:56:13 +0200
Marek Behún wrote:
> Commit e2e95e5e2542 ("spi: Update speed/mode on change") changed the
> boot time on Turris Omnia from ~2.3s to over 8s, due to SPL loading
> main U-Boot from SPI NOR at 1 MHz instead of 40 MHz.
>
> This is because the SPL code passes the CO
On Fri, 09 Jul 2021 17:54:25 +0300
Baruch Siach wrote:
> Hi Marek, Pali,
>
> On Thu, Jul 08 2021, Marek Behún wrote:
> > Hi Stefan and others,
> >
> > this is a series of improvements to kwboot, kwbimage and mvebu.
> >
> > The main goal of this series is to correctly use BootROM's code
> > for l
Now that the MTD subsystem properly supports OF partitions of a SPI NOR,
we can enable the MTD command and start using it instead of the
deprecated sf command.
Signed-off-by: Marek Behún
Cc: Stefan Roese
Cc: Pali Rohár
---
configs/turris_mox_defconfig | 3 +++
configs/turris_omnia_defconfig
Commit e2e95e5e2542 ("spi: Update speed/mode on change") changed the
boot time on Turris Omnia from ~2.3s to over 8s, due to SPL loading main
U-Boot from SPI NOR at 1 MHz instead of 40 MHz.
This is because the SPL code passes the CONFIG_SF_DEFAULT_SPEED option
to spi_flash_probe(), and with the ab
Hi Marek, Pali,
On Thu, Jul 08 2021, Marek Behún wrote:
> Hi Stefan and others,
>
> this is a series of improvements to kwboot, kwbimage and mvebu.
>
> The main goal of this series is to correctly use BootROM's code
> for loading U-Boot from NOR / NAND: currently only SPL is read by
> BootROM and
On Wed, Jul 7, 2021 at 5:58 AM Teresa Remmet wrote:
>
> Factor out the common node settings for dm-spl and dm-pre-reloc
> and move them to imx8mp-u-boot.dtsi
>
> Signed-off-by: Teresa Remmet
> Reviewed-by: Fabio Estevam
> Reviewed-by: Heiko Schocher
> ---
> Changes in v3:
> - Moved binman nodes
When we build U-Boot with POSITION_INDEPENDENT we must have
SYS_TEXT_BASE be set to zero. Make this the default in that case.
Signed-off-by: Tom Rini
---
common/Kconfig.boot | 1 +
1 file changed, 1 insertion(+)
diff --git a/common/Kconfig.boot b/common/Kconfig.boot
index 89a3161f1faa..f078743
Add the support to build a dedicated devicetree located in arch/$(ARCH)/dts
This devicetree does not need to be listed in the relevant devicetree
makefile.
Just run the following command to build the foo devicetree placed before
at the right path:
$ make foo.dtb
Signed-off-by: Kory Maincent
---
On Fri, Jul 09, 2021 at 08:02:03PM +0530, Kishon Vijay Abraham I wrote:
> Hi Tom,
>
> On 11/05/21 8:03 pm, Tom Rini wrote:
> > On Tue, May 11, 2021 at 07:28:10PM +0530, Kishon Vijay Abraham I wrote:
> >> Hi Tom,
> >>
> >> On 07/05/21 10:44 pm, Tom Rini wrote:
> >>> On Tue, May 04, 2021 at 04:11:54
Hi Tom,
On 11/05/21 8:03 pm, Tom Rini wrote:
> On Tue, May 11, 2021 at 07:28:10PM +0530, Kishon Vijay Abraham I wrote:
>> Hi Tom,
>>
>> On 07/05/21 10:44 pm, Tom Rini wrote:
>>> On Tue, May 04, 2021 at 04:11:54PM +0530, Kishon Vijay Abraham I wrote:
>>>
MAIN CPSW0 requires the PHY to be power
On Fri, Jul 09, 2021 at 07:36:45PM +0530, Kishon Vijay Abraham I wrote:
> Hi Tom,
>
> On 07/05/21 10:44 pm, Tom Rini wrote:
> > On Tue, May 04, 2021 at 04:11:48PM +0530, Kishon Vijay Abraham I wrote:
> >
> >> Partially sync with Linux's dts to add the entries required for USB3
> >> support on USB
As the deadline for migration to DM_USB, when using a USB host
controller has now gone two years past the deadline, enforce migration.
This is done by:
- Ensuring that all host controller options (other than the very legacy
old MUSB ones) now select USB_HOST. USB_HOST now enforces DM_USB and
As the logic here is only used when we have a USB host controller, test
on CONFIG_USB_HOST rather than CONFIG_USB in general. This lets us move
towards using CONFIG_USB only as a menu symbol to say that we have some
form of USB, and then USB_HOST or USB_GADGET depending on the role that
USB plays
Reuse the common logic to allow for BOOT_TARGET_DEVICES to list USB as a
possibility if we're building for a platform that will have USB but not
if we don't, so that we don't hit the link-time check for trying to have
USB boot on a non-USB system.
Cc: Tom Warren
Signed-off-by: Tom Rini
---
Chang
These USB defines do not change the build as there is no USB support
enabled currently.
Cc: Ian Ray
Cc: Sebastian Reichel
Signed-off-by: Tom Rini
---
Changes in v2:
- New patch
---
include/configs/ge_bx50v3.h | 11 ---
1 file changed, 11 deletions(-)
diff --git a/include/configs/ge_bx
On Fri, 9 Jul 2021 14:35:15 +0200
Stefan Roese wrote:
> Thanks. And could you please also do one (or more) boot-time
> comparisons, old vs. new version? This way we can see, if and how the
> boot-time is affected (perhaps improved, which would be great) by this
> patch series.
For Turris Omnia,
Hi Tom,
On 07/05/21 10:44 pm, Tom Rini wrote:
> On Tue, May 04, 2021 at 04:11:48PM +0530, Kishon Vijay Abraham I wrote:
>
>> Partially sync with Linux's dts to add the entries required for USB3
>> support on USB0.
>> Note that the default mode is still "peripheral" not "host". USB3 is
>> supporte
Hi Patrick
On 7/8/21 11:17 AM, Patrick Delaunay wrote:
> The MTD tee partitions used to save the OP-TEE binary are needed when
> TF-A doesn't use the FIP container to load binaries.
>
> This patch puts under CONFIG_STM32MP15x_STM32IMAGE flag the associated
> code in U-Boot binary and prepare the
Hi Patrick
One typo below
On 7/8/21 11:17 AM, Patrick Delaunay wrote:
> TF-A for STM32MP15 now supports the FIP: it is a packaging format which
> includes the secure monitor, u-boot-nodtb.bin and u-boot.dtb
>
> This FIP file is loaded by FSBL = TF-A BL2.
>
> This patch updates the board documen
Hi Patrick
On 7/8/21 11:17 AM, Patrick Delaunay wrote:
> Add TF-A FIP support for trusted boot on STM32MP15x,
> when STM32MP15x_STM32IMAGE is not activated.
>
> With FIP support the SSBL partition is named "fip" and its size is 4MB,
> so the ENV partition name in device tree (for SD card or eMMC
Hi Patrick
On 7/8/21 11:17 AM, Patrick Delaunay wrote:
> With FIP support in TF-A (when CONFIG_STM32MP15x_STM32IMAGE
> is not activated), the DT nodes needed by OP-TEE are added by OP-TEE
> firmware in U-Boot device tree, present in FIP.
>
> These nodes are only required in trusted boot, when TF-
Hi Patrick
On 7/8/21 11:17 AM, Patrick Delaunay wrote:
> By default for trusted boot with TF-A, U-Boot (u-boot-nodtb)
> is located in FIP container with its device tree and with
> the secure monitor (provided by TF-A or OP-TEE).
> The FIP file is loaded by TF-A BL2 and each components is
> extract
Hi Patrick
On 7/9/21 9:53 AM, Patrick Delaunay wrote:
> When a push-button is released and PA13/PA14 are defined as input (high-Z)
> the LED should not be active as the circuit is open but a small current
> leak through PCB or push-button close the circuit and allows a small LED
> bias giving erro
Hi Marek,
On 09.07.21 13:22, Marek Behún wrote:
Hi Stefan
On Fri, 9 Jul 2021 08:05:40 +0200
Stefan Roese wrote:
The main goal of this series is to correctly use BootROM's code
for loading U-Boot from NOR / NAND: currently only SPL is read by
BootROM and the main U-Boot is read by SPL. By usi
Add the missing SPI clock even if these instances are not available
on STMicroelectronics boards: SPI2_K, SPI3_K, SPI4_K, SPI6_K.
With this patch, the SPI2 / SPI3 / SPI4 / SPI6 instances can be used on
customer design without the clock driver error:
stm32mp1_clk_get_id: clk id 131 not found
Rev
On Fri, 9 Jul 2021 20:27:18 +0900
Masami Hiramatsu wrote:
> Hi Marek,
>
> 2021年7月9日(金) 19:54 Marek Behún :
> >
> > On Fri, 9 Jul 2021 19:50:27 +0900
> > Masami Hiramatsu wrote:
> >
> > > Add partition information to the spi-nor flash.
> > > This is required for accessing NOR flash via mtdpar
set_phase() functions are not modifying the ret value and returning
the same uninitialized ret, return 0 instead.
Keep the return type as int to return errors when the tapdelay's are
set via xilinx_pm_request() in future.
Signed-off-by: Ashok Reddy Soma
---
Changes in v3:
- Updated commmit des
Restrict tap_delay value to the allowed size(8bits for itap and 6 bits
for otap) before writing to the tap delay register.
Clear ITAP and OTAP delay bits before updating with the new tap value
for Versal platform.
Signed-off-by: Ashok Reddy Soma
---
Changes in v3:
- Updated macro's with BIT()
Allow configuring ITAP and OTAP values with zero to avoid failures in
some cases (one of them is SD boot mode). Legacy, SDR12 modes require
to program the ITAP and OTAP values as zero, whereas for SDR50 and SDR104
modes ITAP value is zero.
In SD boot mode firmware configures the SD ITAP and OTAP v
From: Michal Simek
Fix these kernel doc warnings:
drivers/mmc/zynq_sdhci.c:181: warning: contents before sections
drivers/mmc/zynq_sdhci.c:236: warning: contents before sections
drivers/mmc/zynq_sdhci.c:291: warning: contents before sections
drivers/mmc/zynq_sdhci.c:297: warning: Function paramet
From: Michal Simek
All these variables/structure are local and should be static.
Issues are reported by sparse:
drivers/mmc/zynq_sdhci.c:49:11: warning: symbol 'zynqmp_iclk_phases' was not
declared. Should it be static?
drivers/mmc/zynq_sdhci.c:50:11: warning: symbol 'zynqmp_oclk_phases' was no
Split arasan_zynqmp_set_tapdelay() to handle input and output tapdelays
separately. This is required to handle zero values for ITAP and OTAP
values. If we dont split, we will have to remove the if() in the
function, which makes ITAP values to be overwritten when OTAP values are
called to set and vi
This patch set fixes below issues in zynq_sdhc driver
- Fix issues in tap delay functions where it returns uninitialized values
- Allow configuring zero tap delay values
- Split tapdelay functions to set input and output tap delay's separately.
- Fix kernel doc warnings
- Make local structures
Hi Marek,
2021年7月9日(金) 19:54 Marek Behún :
>
> On Fri, 9 Jul 2021 19:50:27 +0900
> Masami Hiramatsu wrote:
>
> > Add partition information to the spi-nor flash.
> > This is required for accessing NOR flash via mtdparts.
> >
> > Signed-off-by: Masami Hiramatsu
> > ---
> > .../dts/synquacer-sc2a
Hi Stefan
On Fri, 9 Jul 2021 08:05:40 +0200
Stefan Roese wrote:
> > The main goal of this series is to correctly use BootROM's code
> > for loading U-Boot from NOR / NAND: currently only SPL is read by
> > BootROM and the main U-Boot is read by SPL. By using BootROM to also
> > load main U-Boot
Hi Michal,
> -Original Message-
> From: Michal Simek
> Sent: Friday, July 9, 2021 4:35 PM
> To: Ashok Reddy Soma ; u-boot@lists.denx.de
> Cc: peng@nxp.com; jh80.ch...@samsung.com; git ;
> mon...@monstr.eu; somaashokre...@gmail.com
> Subject: Re: [PATCH v2 1/6] mmc: zynq_sdhci: Resolve
HI Michal,
> -Original Message-
> From: Michal Simek
> Sent: Friday, July 9, 2021 4:37 PM
> To: Ashok Reddy Soma ; u-boot@lists.denx.de
> Cc: peng@nxp.com; jh80.ch...@samsung.com; git ;
> mon...@monstr.eu; somaashokre...@gmail.com
> Subject: Re: [PATCH v2 3/6] mmc: zynq_sdhci: Use Mas
On 7/9/21 12:47 PM, Ashok Reddy Soma wrote:
> Restrict tap_delay value to the allowed size(8bits for itap and 6 bits
> for otap) before writing to the tap delay register.
>
> Clear ITAP and OTAP delay bits before updating with the new tap value
> for Versal platform.
>
> Signed-off-by: Ashok R
On 7/9/21 12:46 PM, Ashok Reddy Soma wrote:
> set_phase() functions are not modifying the ret value and returning
> the same uninitialized ret, return 0 instead.
>
> Signed-off-by: Ashok Reddy Soma
> ---
>
> Changes in v2:
> - Changed "@degree" to "@degrees:" in function descriptions of tap
Hi Jaehoon,
> -Original Message-
> From: Jaehoon Chung
> Sent: Friday, July 9, 2021 4:21 PM
> To: Ashok Reddy Soma ; u-boot@lists.denx.de
> Cc: peng@nxp.com; git ; mon...@monstr.eu;
> somaashokre...@gmail.com
> Subject: Re: [PATCH 1/6] mmc: zynq_sdhci: Resolve uninitialized return val
On Fri, 9 Jul 2021 19:50:27 +0900
Masami Hiramatsu wrote:
> Add partition information to the spi-nor flash.
> This is required for accessing NOR flash via mtdparts.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../dts/synquacer-sc2a11-developerbox-u-boot.dtsi | 42
> 1 f
On Fri, 9 Jul 2021 19:50:18 +0900
Masami Hiramatsu wrote:
> Make the U-Boot bianry for SynQuacer position independent so
*binary
Enable UEFI secure boot on synquacer. Note that unless user
setup their keys, the secure boot will not work.
Signed-off-by: Masami Hiramatsu
---
configs/synquacer_developerbox_defconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/configs/synquacer_developerbox_defconfig
b/configs/syn
Since the U-Boot for the SynQuacer DeveloperBox is designed for
compatible with EDK2 boot, we don't need to support Ext2/4 fs
support by default. Drop it.
Signed-off-by: Masami Hiramatsu
---
configs/synquacer_developerbox_defconfig |2 --
1 file changed, 2 deletions(-)
diff --git a/configs/
Since MTD partitions are based on the devicetree name,
remove unneeded mtdparts settings and update DFU setting.
Signed-off-by: Masami Hiramatsu
---
configs/synquacer_developerbox_defconfig |2 --
include/configs/synquacer.h |2 +-
2 files changed, 1 insertion(+), 3 deletion
Add partition information to the spi-nor flash.
This is required for accessing NOR flash via mtdparts.
Signed-off-by: Masami Hiramatsu
---
.../dts/synquacer-sc2a11-developerbox-u-boot.dtsi | 42
1 file changed, 42 insertions(+)
diff --git a/arch/arm/dts/synquacer-sc2a11-
Make the U-Boot bianry for SynQuacer position independent so
that the previous bootloader (SCP firmware or BL2) can load
the U-Boot anywhere.
Signed-off-by: Masami Hiramatsu
---
configs/synquacer_developerbox_defconfig |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/con
Since the SCBM SMMU is not only connected to the NETSEC
but also shared with the F_SDH30 (eMMC controller), that
should be initialized at board level instead of NETSEC.
Move the SMMU initialization code into board support
and call it from board_init().
Without this fix, if the NETSEC is disabled,
Hi,
Here is the series of patches to update the DeveloperBox support.
[1/6] board: synquacer: Initialize SCBM SMMU at board_init()
- This is a driver cleanup, split the SMMU setup from the driver.
[2/6] configs: synquacer: Make U-Boot binary position independent
- This makes U-Boot position
Hi Ashok,
On 7/9/21 7:15 PM, Ashok Reddy Soma wrote:
> Hi Jaehoon,
>
>> -Original Message-
>> From: Jaehoon Chung
>> Sent: Friday, July 9, 2021 3:08 PM
>> To: Ashok Reddy Soma ; u-boot@lists.denx.de
>> Cc: peng@nxp.com; git ; mon...@monstr.eu;
>> somaashokre...@gmail.com
>> Subject:
Split arasan_zynqmp_set_tapdelay() to handle input and output tapdelays
separately. This is required to handle zero values for ITAP and OTAP
values. If we dont split, we will have to remove the if() in the
function, which makes ITAP values to be overwritten when OTAP values are
called to set and vi
From: Michal Simek
All these variables/structure are local and should be static.
Issues are reported by sparse:
drivers/mmc/zynq_sdhci.c:49:11: warning: symbol 'zynqmp_iclk_phases' was not
declared. Should it be static?
drivers/mmc/zynq_sdhci.c:50:11: warning: symbol 'zynqmp_oclk_phases' was no
Restrict tap_delay value to the allowed size(8bits for itap and 6 bits
for otap) before writing to the tap delay register.
Clear ITAP and OTAP delay bits before updating with the new tap value
for Versal platform.
Signed-off-by: Ashok Reddy Soma
---
(no changes since v1)
drivers/mmc/zynq_sdhc
This patch set fixes below issues in zynq_sdhc driver
- Fix issues in tap delay functions where it returns uninitialized values
- Allow configuring zero tap delay values
- Split tapdelay functions to set input and output tap delay's separately.
- Fix kernel doc warnings
- Make local structures
Allow configuring ITAP and OTAP values with zero to avoid failures in
some cases (one of them is SD boot mode). Legacy, SDR12 modes require
to program the ITAP and OTAP values as zero, whereas for SDR50 and SDR104
modes ITAP value is zero.
In SD boot mode firmware configures the SD ITAP and OTAP v
From: Michal Simek
Fix these kernel doc warnings:
drivers/mmc/zynq_sdhci.c:181: warning: contents before sections
drivers/mmc/zynq_sdhci.c:236: warning: contents before sections
drivers/mmc/zynq_sdhci.c:291: warning: contents before sections
drivers/mmc/zynq_sdhci.c:354: warning: contents before
set_phase() functions are not modifying the ret value and returning
the same uninitialized ret, return 0 instead.
Signed-off-by: Ashok Reddy Soma
---
Changes in v2:
- Changed "@degree" to "@degrees:" in function descriptions of tap
delay functions
drivers/mmc/zynq_sdhci.c | 24 ++--
As gd->ram_top = board_get_usable_ram_top() in board_r
the EFI loader don't need to call this function again and after relocation.
This patch avoid issue if board assumed that this function is called
only one time and before relocation.
Signed-off-by: Patrick Delaunay
---
https://source.denx.de
Hi Ramon,
On 4/26/21 5:46 PM, Patrick Delaunay wrote:
It is the V2 version of [1] after Marek remarks: all commit are new.
I change the DWC_ETH_QOS STM32 variant by using generic eth phy driver.
This driver is updated to use the gpio reset and assert/deassert delay
from DT with the generic bin
Hi Jaehoon,
> -Original Message-
> From: Jaehoon Chung
> Sent: Friday, July 9, 2021 3:12 PM
> To: Ashok Reddy Soma ; u-boot@lists.denx.de
> Cc: peng@nxp.com; git ; mon...@monstr.eu;
> somaashokre...@gmail.com; Michal Simek
> Subject: Re: [PATCH 5/6] mmc: zynq_sdhci: Fix kernel doc wa
Hi Jaehoon,
> -Original Message-
> From: Jaehoon Chung
> Sent: Friday, July 9, 2021 3:08 PM
> To: Ashok Reddy Soma ; u-boot@lists.denx.de
> Cc: peng@nxp.com; git ; mon...@monstr.eu;
> somaashokre...@gmail.com
> Subject: Re: [PATCH 1/6] mmc: zynq_sdhci: Resolve uninitialized return val
On Fri, Jul 09, 2021 at 09:05:09AM +0200, François Ozog wrote:
> Le ven. 9 juil. 2021 à 03:09, Julius Werner a écrit :
>
> > > Of course every project would like not to change...
> > >
> > > For TF-A I wonder whether it will/should in fact use devicetree if there
> > is a lot of complex data? TBD
Hi Patrick
On 7/8/21 10:53 AM, Patrick Delaunay wrote:
> When the TAMP register 20 have an invalid value (0x0 for example after
> TAMPER error) the "boot_device" U-Boot env variable have no value and
> no error is displayed in U-Boot log.
>
> The STM32MP boot command bootcmd_stm32mp failed with s
Hi Ashok,
On 7/9/21 4:17 PM, Ashok Reddy Soma wrote:
> From: Michal Simek
>
> Fix these kernel doc warnings:
> drivers/mmc/zynq_sdhci.c:181: warning: contents before sections
> drivers/mmc/zynq_sdhci.c:187: warning: Function parameter or member 'degrees'
> not described in 'sdhci_zynqmp_sdcardc
Hi Ashok,
On 7/9/21 4:17 PM, Ashok Reddy Soma wrote:
> set_phase() functions are not modifying the ret value and returning
> the same uninitialized ret, return 0 instead.
Why didn't you change from int to void?
Best Regards,
Jaehoon Chung
>
> Signed-off-by: Ashok Reddy Soma
> ---
>
> drive
On 7/6/21 11:54 PM, Stephan Gerhold wrote:
> For the eMMC on ST-Ericsson Ux500v2 we need slightly different
> configuration values. Use the existing switch statement to match
> the peripheral ID of Ux500v2 (0x10480180) and override the necessary
> values to make the eMMC work on devices with ST-Eri
On 7/6/21 11:54 PM, Stephan Gerhold wrote:
> Simplify the code a bit by using the common mmc_of_parse() function
> instead of duplicating the device tree parsing code. We can still get
> a default value for cfg->f_max by assigning it before calling
> mmc_of_parse().
>
> Another advantage of this r
On 7/6/21 11:54 PM, Stephan Gerhold wrote:
> Simplify the code a bit by using dev_read_addr_ptr() instead of
> dev_read_addr(). This avoids having to cast explicitly to void*.
>
> Signed-off-by: Stephan Gerhold
Reviewed-by: Jaehoon Chung
Best Regards,
Jaehoon Chung
> ---
>
> drivers/mmc/arm
On 7/6/21 11:54 PM, Stephan Gerhold wrote:
> The arm,primecell compatible is used for lots of different types
> of devices, e.g. I2C, SPI, coresight, ... We really should not bind
> the MMC driver to all of them.
>
> Looking through the device trees in U-Boot there seems to be always
> a second co
Hi,
On 5/31/21 7:43 PM, Alexandru Gagniuc wrote:
OP-TEE is very particular about how the TZC should be configured.
When booting an OP-TEE payload, an incorrect TZC configuration will
result in a panic.
Most information can be derived from the SPL devicetree. The only
information we don't have i
1 - 100 of 112 matches
Mail list logo
