On Thu, 7 Mar 2024 at 02:54, Volodymyr Babchuk
wrote:
>
>
> Hi Caleb,
>
> Caleb Connolly writes:
>
> [...]
> +};
> +
> + {
> + /* U-Boot pinctrl driver does not understand multiple tiles */
> + reg = <0x0 0x0300 0x0 0x100>;
> +
On Thu, 7 Mar 2024 at 01:08, Sam Edwards wrote:
>
>
>
> On 3/6/24 06:23, Ilias Apalodimas wrote:
> > On Wed, 6 Mar 2024 at 12:37, Ilias Apalodimas
> > wrote:
> >>
> >> On Wed, 6 Mar 2024 at 11:35, Ilias Apalodimas
> >> wrote:
> >>>
> >>> Hi Sam,
> >>>
> >>>
> >>> On Wed, 6 Mar 2024 at 10:22,
On Thu, 7 Mar 2024 at 00:19, Sam Edwards wrote:
>
>
> On 3/6/24 02:13, Ilias Apalodimas wrote:
> > Hi Sam,
> >
> > Again thank you for the elaborate review. This really helps a lot.
> >
> > On Wed, 6 Mar 2024 at 10:14, Sam Edwards wrote:
> >>
> >>
> >>
> >> On 3/4/24 02:01, Ilias Apalodimas
On Wed, 6 Mar 2024 at 22:56, Tim Harvey wrote:
>
> On Tue, Mar 5, 2024 at 4:47 PM Adam Ford wrote:
> >
> > On Tue, Mar 5, 2024 at 7:51 AM Adam Ford wrote:
> > >
> > > On Tue, Mar 5, 2024 at 7:48 AM Sumit Garg wrote:
> > > >
> > > > Hi Adam,
> > > >
> > > > On Wed, 28 Feb 2024 at 12:29, Sumit
Hi,
On 3/6/2024 7:14 PM, Wadim Egorov wrote:
> Hi Vignesh,
>
> Am 04.03.24 um 06:06 schrieb Vignesh Raghavendra:
>> Hi Wadim,
>>
>> On 26/02/24 19:00, Wadim Egorov wrote:
>>> Texas Instruments has begun enabling security settings on the SoCs it
>>> produces to instruct ROM and TIFS to begin
Hi Caleb,
Caleb Connolly writes:
[...]
+};
+
+ {
+ /* U-Boot pinctrl driver does not understand multiple tiles */
+ reg = <0x0 0x0300 0x0 0x100>;
+ /delete-property/ reg-names;
>>>
>>> This won't be needed if we can make the tiles offset
Hi Sumit,
Sumit Garg writes:
> Hi Volodymyr,
>
> On Wed, 6 Mar 2024 at 06:23, Volodymyr Babchuk
> wrote:
>>
>> SA8155P Automotive Development Platform is Qualcomm SA8155-based board
>> for developers. The nice thing that it has unlocked loaders with test
>> keys support, which means that
On Thu, Mar 07, 2024 at 12:36:42AM +0100, Angelo Dureghello wrote:
> Hi,
>
> On 05/03/24 1:34 PM, Michal Simek wrote:
> >
> >
> > On 3/3/24 22:58, Angelo Dureghello wrote:
> > > Hi Tom,
> > > > On Tue, Feb 20, 2024 at 01:11:38PM +0530, Love Kumar wrote:
> > > > > Add a test for reset commands
Hey all,
I'm not opposed to using the kernel ecdsa.c and have taken a quick look at
`ecdsa_verify()` - but I'd love if someone could point me in the right
direction for how to set up the context and public key. The
akcipher_request structure seems to address both the signature and the
digest, but
From: Maxim Moskalets
Added the ability to use FDT for ELF applications, required to run some
OS. To make FDT setup, you need to set the -d fdt_addr_r cmd option for
bootelf command.
Signed-off-by: Maxim Moskalets
Cc: Tom Rini
---
cmd/elf.c | 27 ---
1 file changed,
Hi,
On 05/03/24 1:34 PM, Michal Simek wrote:
On 3/3/24 22:58, Angelo Dureghello wrote:
Hi Tom,
On Tue, Feb 20, 2024 at 01:11:38PM +0530, Love Kumar wrote:
Add a test for reset commands which performs resetting of CPU, It
does COLD reset by default and WARM reset with -w option.
On 3/6/24 06:23, Ilias Apalodimas wrote:
On Wed, 6 Mar 2024 at 12:37, Ilias Apalodimas
wrote:
On Wed, 6 Mar 2024 at 11:35, Ilias Apalodimas
wrote:
Hi Sam,
On Wed, 6 Mar 2024 at 10:22, Sam Edwards wrote:
On 3/4/24 02:01, Ilias Apalodimas wrote:
image_copy_start/end are defined as c
Hey all,
I think I addressed the nit of the missing blank line in my last email on
this thread. Wondering if there's more action to be had on my part or if
this just gets accepted etc.
Thanks!
Bob Wolff
On Tue, Feb 27, 2024 at 3:57 PM Bob Wolff wrote:
> If mixed rsa and ecdsa keys are
On 3/6/24 02:13, Ilias Apalodimas wrote:
Hi Sam,
Again thank you for the elaborate review. This really helps a lot.
On Wed, 6 Mar 2024 at 10:14, Sam Edwards wrote:
On 3/4/24 02:01, Ilias Apalodimas wrote:
__efi_runtime_start/end are defined as c variables for arm7 only in
order to
On 18:47-20240306, Kumar, Udit wrote:
>
> On 3/6/2024 12:07 PM, Aniket Limaye wrote:
> > - Add the missing bootph-all property in the flash subnode for ospi
> > - Add the missing overrides for the ospi node in the r5 devicetree
>
> Please see , if you can add more o
On 18:41-20240306, Kumar, Udit wrote:
>
> On 3/6/2024 12:07 PM, Aniket Limaye wrote:
> > Add the necessary configs required for OSPI functionality.
> > Also update the ospi flash partition offsets as per the devicetree.
> >
> > Signed-off-by: Aniket
On 06/03/2024 19:14, Volodymyr Babchuk wrote:
>
> Hi Sumit,
>
> Sumit Garg writes:
>
>> Hi Volodymyr,
>>
>> On Wed, 6 Mar 2024 at 06:23, Volodymyr Babchuk
>> wrote:
>>>
>>> SA8155P Automotive Development Platform is Qualcomm SA8155-based board
>>> for developers. The nice thing that it has
Reuse common logic between existing mmc and new introduced
block implementation
Signed-off-by: Dmitrii Merkurev
Cc: Alex Kiernan
Cc: Patrick Delaunay
Cc: Simon Glass
Cc: Mattijs Korpershoek
Cc: Ying-Chun Liu (PaulLiu)
---
drivers/fastboot/Makefile | 4 +-
drivers/fastboot/fb_block.c |
1. Get partition info/size
2. Erase partition
3. Flash partition
4. BCB
Signed-off-by: Dmitrii Merkurev
Cc: Alex Kiernan
Cc: Patrick Delaunay
Cc: Simon Glass
Cc: Mattijs Korpershoek
Cc: Ying-Chun Liu (PaulLiu)
---
drivers/fastboot/fb_command.c | 8
drivers/fastboot/fb_common.c |
Signed-off-by: Dmitrii Merkurev
Cc: Patrick Delaunay
Cc: Simon Glass
Cc: Mattijs Korpershoek
Cc: Ying-Chun Liu (PaulLiu)
---
drivers/fastboot/Kconfig | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/drivers/fastboot/Kconfig b/drivers/fastboot/Kconfig
Co-developed-by: Cody Schuffelen
Signed-off-by: Cody Schuffelen
Signed-off-by: Dmitrii Merkurev
Cc: Tuomas Tynkkynen
Cc: Simon Glass
Cc: Mattijs Korpershoek
Cc: Ying-Chun Liu (PaulLiu)
---
drivers/virtio/virtio_blk.c | 91 +++--
drivers/virtio/virtio_blk.h |
Hello,
In looking through the source, I'm not yet seeing logic that allows U-Boot to actually use MTD partition information found in the device tree. Does this logic exist and I'm just missing it? Or do I
need to parse the device tree partitions manually and create the mtdparts env variable?
Hello Guys,
Guided by the "Sending patches" tutorial, I would like to present a
problem I have encountered and eventually discuss whether it would be
ok to submit a patch for that issue.
The problem is in ARM arch and is related to the asm function
"__asm_dcache_level" from
On Tue, Mar 5, 2024 at 4:47 PM Adam Ford wrote:
>
> On Tue, Mar 5, 2024 at 7:51 AM Adam Ford wrote:
> >
> > On Tue, Mar 5, 2024 at 7:48 AM Sumit Garg wrote:
> > >
> > > Hi Adam,
> > >
> > > On Wed, 28 Feb 2024 at 12:29, Sumit Garg wrote:
> > > >
> > > > Hi Adam,
> > > >
> > > > On Wed, 28 Feb
Hi Alexey,
On 01.03.24 14:42, Alexey Romanov wrote:
> Hi Frieder,
>
> On Thu, Feb 29, 2024 at 09:51:04AM +0100, Frieder Schrempf wrote:
>> Hi Alexey,
>>
>> On 27.02.24 11:04, Alexey Romanov wrote:
>>> Hello!
>>>
>>> This series adds support for the mtdblock device, which
>>> allows to read/write
Hi Bruce,
On 01.03.24 09:01, Bruce Sun wrote:
> Add support for XTX XT26G0xA and XT26xxxD,the driver is ported from
> linux-6.7.1.
This patch is missing your Signed-off-by tag. And it seems to be
formatted incorrectly. At least I can't apply it to master or nand-next.
How do you create the
On Wed, 14 Feb 2024 10:30:03 -0600, Andrew Davis wrote:
> Explanation for this series is mostly in [4/6]. First 3
> patches should be safe to take independent of the last 3.
>
> Thanks,
> Andrew
>
> Andrew Davis (6):
> arm: mach-k3: Add default ATF location for AM62/AM62a
> arm: mach-k3:
This patch is to enable Agilex5 platform for Intel
product. Changes, modification and new files are
created for board, dts, configs and makefile to
create the base for Agilex5.
Signed-off-by: Jit Loon Lim
---
Changes v1 -> v2:
- fixed git auto merge issue
---
arch/arm/Kconfig
V1:
https://patchwork.ozlabs.org/project/uboot/patch/20240220143603.22091-1-jit.loon@intel.com/
V2: Fixed Git auto-merge causing misalignment of code and insert/delete
Jit Loon Lim (1):
arch: arm: Agilex5 enablement
arch/arm/Kconfig | 4 +-
Use the new device devicetree files in dts/upstream/ and delete the old
ones. Still keep the -u-boot.dtsi with all u-boot specifics around.
There is one catch and that is fsl-ls1028a-kontron-sl28-var3.dts which
is not available upstream (yet!). For now, the base dts is used for this
variant as
We need to differ between PCL-070 and PCM-070. PCL-070 supports 2GHz RAM
timings from pcb rev 1 or newer. PCM-070 supports 2GHz RAM timings from
pcb rev 3 or newer.
Signed-off-by: Benjamin Hahn
---
board/phytec/phycore_imx8mp/spl.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
PCL-070 supports 2GHz RAM-timings from pcb_rev 1 and newer. PCM-070
supports 2GHz RAM-timings only from pcb_rev 3 and newer.
Signed-off-by: Benjamin Hahn
---
Changes in v3:
- change variable name from somtyp to somtype
- change enum names from PCL to SOM_TYPE_PCL
- Link to v2:
Add a function that gets the som_type from the EEPROM.
Add an enum for the som_type.
Signed-off-by: Benjamin Hahn
---
board/phytec/common/phytec_som_detection.c | 10 ++
board/phytec/common/phytec_som_detection.h | 8
2 files changed, 18 insertions(+)
diff --git
On March 6, 2024 thus sayeth Andrew Davis:
> On 3/6/24 7:35 AM, Bryan Brattlof wrote:
> > On February 14, 2024 thus sayeth Andrew Davis:
> > > The address we load TF-A and OP-TEE to is configurable by Kconfig
> > > CONFIG_K3_{ATF,OPTEE}_LOAD_ADDR, but the DT nodes reserving this memory
> > > are
The 'PolarFire Hart Software Services' SBI implementation returns the
version of the incorporated OpenSBI. Format the number accordingly.
Signed-off-by: Heinrich Schuchardt
---
cmd/riscv/sbi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/cmd/riscv/sbi.c b/cmd/riscv/sbi.c
index
On Wed, Mar 06, 2024 at 03:44:02PM +0100, Heinrich Schuchardt wrote:
> For an unknown implementation ID an output like
>
> SBI 1.0Unknown implementation ID 16777216
> Extensions:
> sbi_set_timer
> ...
>
> was shown. The number 16777216 is not the implementation ID.
>
> *
On Wed, Mar 06, 2024 at 03:48:52PM +0100, Heinrich Schuchardt wrote:
> The 'PolarFire Hart Software Services' SBI implementation returns the
> version of the incorporated OpenSBI. Format the number accordingly.
>
> Signed-off-by: Heinrich Schuchardt
FWIW, the reason we added a custom
Hi Volodymyr,
On 06/03/2024 00:53, Volodymyr Babchuk wrote:
> Now sub-drivers for particular SoCs can register them as power domain
> drivers. This is needed for upcoming SM8150 support, because it needs
> to power up the Ethernet module.
>
> Signed-off-by: Volodymyr Babchuk
>
> ---
>
>
The 'PolarFire Hart Software Services' SBI implementation returns the
version of the incorporated OpenSBI. Format the number accordingly.
Signed-off-by: Heinrich Schuchardt
---
cmd/riscv/sbi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/cmd/riscv/sbi.c b/cmd/riscv/sbi.c
index
For an unknown implementation ID an output like
SBI 1.0Unknown implementation ID 16777216
Extensions:
sbi_set_timer
...
was shown. The number 16777216 is not the implementation ID.
* Show the correct number
* Use a hexadecimal output format
* Add a missing line feed
On 06/03/2024 00:53, Volodymyr Babchuk wrote:
> Add clock, reset and power domain driver for SM8150. Driver code is
> based on the similar U-Boot drivers. All constants are taken from the
> corresponding Linux driver.
>
> This driver supports clock rate setting only for the debug UART and
>
On 06/03/2024 00:53, Volodymyr Babchuk wrote:
> Add pinctrl and GPIO driver for SM8150. Driver code is based on the
> similar U-Boot drivers. All constants are taken from the corresponding
> Linux driver. This drivers differs from the similar U-Boot drivers,
> because SM8150 SoC have different
On 06/03/2024 00:53, Volodymyr Babchuk wrote:
> SA8155P Automotive Development Platform is Qualcomm SA8155-based board
> for developers. The nice thing that it has unlocked loaders with test
> keys support, which means that U-Boot for this platform can be
> launched at earlier stages.
>
> This
On 3/6/24 7:35 AM, Bryan Brattlof wrote:
On February 14, 2024 thus sayeth Andrew Davis:
The address we load TF-A and OP-TEE to is configurable by Kconfig
CONFIG_K3_{ATF,OPTEE}_LOAD_ADDR, but the DT nodes reserving this memory
are often statically defined. As these binaries are dynamically
On 2/28/24 12:24 AM, Manorit Chawdhry wrote:
Hi Andrew,
On 10:30-20240214, Andrew Davis wrote:
The address we load TF-A and OP-TEE to is configurable by Kconfig
CONFIG_K3_{ATF,OPTEE}_LOAD_ADDR, but the DT nodes reserving this memory
are often statically defined. As these binaries are
UBI block is virtual block device, which is an abstraction
over MTD layer. Therefore it is logical to use it in combination
with MTD drivers.
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/spi/core.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
UBI partition is abstraction over UBI volumes.
Can be used by UBI block device.
Signed-off-by: Alexey Romanov
---
drivers/mtd/ubi/Makefile | 1 +
drivers/mtd/ubi/part.c | 99
include/part.h | 2 +
3 files changed, 102 insertions(+)
create
Block devices can already set partition type at initialization
stage, so, in this case is no point in searching for partition type.
Signed-off-by: Alexey Romanov
---
disk/part.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/disk/part.c b/disk/part.c
index 0fc5cc0419..362c9de609
UBI block is an virtual device, that runs on top
of the MTD layer. The blocks are UBI volumes.
Intended to be used in combination with other MTD
drivers.
Despite the fact that it, like mtdblock abstraction,
it used with UCLASS_MTD, they can be used together
on the system without conflicting. For
Introduce ubi_volume_offset_write() helper, which
allow to write to ubi volume with specified offset.
Signed-off-by: Alexey Romanov
---
cmd/ubi.c | 71 +++--
env/ubi.c | 10 +++
include/ubi_uboot.h | 2 +-
3 files changed, 74
Now user can pass an additional parameter 'offset'
to ubi_volume_read() function.
Signed-off-by: Alexey Romanov
---
cmd/ubi.c | 6 +++---
env/ubi.c | 6 +++---
include/ubi_uboot.h | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/cmd/ubi.c b/cmd/ubi.c
Hello!
This series adds support for the UBI block device, which
allows to read/write data block by block. For example,
it can now be used for BCB or Android AB command:
$ bcb load ubi 0 part_name
Tested only on SPI NAND, so bind is made only for
SPI NAND drivers. Can be used with mtdblock
On 2/28/24 12:21 AM, Manorit Chawdhry wrote:
Hi Andrew,
On 10:30-20240214, Andrew Davis wrote:
Much like we have for ATF, OP-TEE has a standard address that we load
it too and run it from. Add a Kconfig item for this to remove some
hard-coding and allow this address to be more easily changed.
Hi Vignesh,
Am 04.03.24 um 06:06 schrieb Vignesh Raghavendra:
Hi Wadim,
On 26/02/24 19:00, Wadim Egorov wrote:
Texas Instruments has begun enabling security settings on the SoCs it
produces to instruct ROM and TIFS to begin protecting the Security
Management Subsystem (SMS) from other
Use function callbacks for volt2val, val2volt and slewrate lookups.
This makes it easier to add support for TPS65224 PMIC regulators.
Signed-off-by: Bhargav Raviprakash
---
drivers/power/regulator/tps65941_regulator.c | 61 +++-
1 file changed, 48 insertions(+), 13 deletions(-)
Reuse TPS65941 regulator driver to adds support for
TPS65224 PMIC's regulators. 4 BUCKs and 3 LDOs, where
BUCK1 and BUCK2 can be configured in dual phase mode.
Signed-off-by: Bhargav Raviprakash
---
drivers/power/regulator/tps65941_regulator.c | 280 ++-
1 file changed, 267
Adds compatible and data field values of TPS65224 driver in
TPS65941 PMIC driver.
Signed-off-by: Bhargav Raviprakash
---
drivers/power/pmic/tps65941.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/power/pmic/tps65941.c b/drivers/power/pmic/tps65941.c
index 727b42747a..ef63eb733a
Adds macros for buck and ldo ids and switched to using switch
case instead of if else in probe functions. Helps in adding
support for TPS65224 PMIC.
Signed-off-by: Bhargav Raviprakash
---
drivers/power/regulator/tps65941_regulator.c | 54 +++-
1 file changed, 42 insertions(+),
Re-use the TPS65941 PMIC driver for TPS65224 PMIC.
Add additional macros of TPS65224 to aid in the driver
re-use.
Signed-off-by: Bhargav Raviprakash
---
include/power/tps65941.h | 30 ++
1 file changed, 30 insertions(+)
diff --git a/include/power/tps65941.h
TPS65224 is a Power Management IC which provides regulators and others
features like GPIOs, RTC, watchdog, ADC, ESMs (Error Signal Monitor),
and PFSM (Pre-configurable Finite State Machine). The SoC and the PMIC
can communicate through the I2C.
Data Sheet for TPS65224:
On Fri, 23 Feb 2024 14:37:48 +0300, Dan Carpenter wrote:
> On Fri, Feb 23, 2024 at 02:42:12PM +0530, Bhargav Raviprakash wrote:
> > + int mask = TPS65224_LDO_VOLT_MASK >> 1;
> > +
> > + if (idx > 0) {
> > + base = TPS65224_LDO23_VOLT_MIN;
> > + max =
On February 14, 2024 thus sayeth Andrew Davis:
> The current address of TF-A in DRAM is just below the 512MB address line.
> This means if the DRAM in a system is 512MB then TF-A is right at the
> end of memory which is often reused, for instance U-Boot relocates itself
> here. If a system has
On February 14, 2024 thus sayeth Andrew Davis:
> The address we load TFA and OP-TEE to is configurable by
> CONFIG_K3_{ATF,OPTEE}_LOAD_ADDR, but the DT nodes reserving this memory
> are static. Fix that by updating this node when the loaded address
> does not match the address in DT.
>
>
On February 14, 2024 thus sayeth Andrew Davis:
> The address we load TF-A and OP-TEE to is configurable by Kconfig
> CONFIG_K3_{ATF,OPTEE}_LOAD_ADDR, but the DT nodes reserving this memory
> are often statically defined. As these binaries are dynamically loadable,
> and in the case of OP-TEE may
On Fri, 23 Feb 2024 15:11:56 +0530, Dhruva Gole wrote:
> On Feb 23, 2024 at 14:42:11 +0530, Bhargav Raviprakash wrote:
> > Use function callbacks for volt2val, val2volt and slewrate lookups.
> > This makes it easier to add support for TPS65224 PMIC regulators.
> >
> > Signed-off-by: Bhargav
On February 14, 2024 thus sayeth Andrew Davis:
> Much like we have for ATF, OP-TEE has a standard address that we load
> it too and run it from. Add a Kconfig item for this to remove some
> hard-coding and allow this address to be more easily changed.
>
> Signed-off-by: Andrew Davis
Acked-by:
On February 14, 2024 thus sayeth Andrew Davis:
> There is a default ATF load address that is used for devices that have
> ATF running in SRAM. For AM62 and AM62a, ATF runs from DRAM. Instead
> of having to override the address in every defconfig, make add a
> default for these ATF in DRAM devices.
On Wed, 6 Mar 2024 at 12:37, Ilias Apalodimas
wrote:
>
> On Wed, 6 Mar 2024 at 11:35, Ilias Apalodimas
> wrote:
> >
> > Hi Sam,
> >
> >
> > On Wed, 6 Mar 2024 at 10:22, Sam Edwards wrote:
> > >
> > > On 3/4/24 02:01, Ilias Apalodimas wrote:
> > > > image_copy_start/end are defined as c
On 3/6/2024 12:07 PM, Aniket Limaye wrote:
Correcting the clock-frequency property of the mcu_timer0 node
Fixes: df73e791ce09 ("arm: dts: j7200: dts sync with Linux 6.6-rc1")
Signed-off-by: Aniket Limaye
---
arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 2 +-
1 file changed, 1
On 3/6/2024 12:07 PM, Aniket Limaye wrote:
- Add the missing bootph-all property in the flash subnode for ospi
- Add the missing overrides for the ospi node in the r5 devicetree
Please see , if you can add more on this why we are adding this
also, if this patch fixes some previous commit
On 3/6/2024 12:07 PM, Aniket Limaye wrote:
Add the necessary configs required for OSPI functionality.
Also update the ospi flash partition offsets as per the devicetree.
Signed-off-by: Aniket Limaye
---
configs/j7200_evm_a72_defconfig | 10 --
configs/j7200_evm_r5_defconfig | 9
On 3/6/2024 12:07 PM, Aniket Limaye wrote:
Support for OSPI probe and also read/write is broken and/or missing in current
master branch.
Its broken :)
- sf probe failure from u-boot prompt & OSPI boot failure [0]
This series adds necessary configs, as well as fixes some bugs in the
Hi,
On Wed Mar 6, 2024 at 3:56 AM CET, Marek Vasut wrote:
> > I'd argue if one wants to use the locking at all, you have to set
> > UNLOCK_ALL=n. Otherwise, the bootloader might come alone and just
> > clear your locking bits again. Clearing the WPS bit there is just
> > one more thing which IMHO
Hi Devarsh,
On 22/02/24 18:38, Devarsh Thakkar wrote:
> Create separate helper for just reserving framebuffer region without
> creating or enabling simple-framebuffer node.
>
> This is useful for scenarios where user want to preserve the bootloader
> splash screen till OS boots up and display
Hi Devarsh,
On 22/02/24 18:38, Devarsh Thakkar wrote:
> If SPL is passing video handoff structure to U-boot then it is safe to
> assume that SPL has already enabled video and that's why it is passing
> video handoff structure to U-boot so that U-boot can preserve the
> framebuffer.
>
>
Hi Devarsh,
On 22/02/24 18:38, Devarsh Thakkar wrote:
> Enable and update simple-framebuffer node using the video handoff
> bloblist if video was enabled at SPL stage and corresponding video
> bloblist was received at u-boot proper with necessary parameters.
>
> Signed-off-by: Devarsh Thakkar
>
Corrects the ti,sci property to point to dm_tifs node for proper
functioning of mcu_ringacc and mcu_udmap.
Fixes: df73e791ce09 ("arm: dts: j7200: dts sync with Linux 6.6-rc1")
Signed-off-by: Aniket Limaye
---
arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 8
1 file changed, 8
Correcting the clock-frequency property of the mcu_timer0 node
Fixes: df73e791ce09 ("arm: dts: j7200: dts sync with Linux 6.6-rc1")
Signed-off-by: Aniket Limaye
---
arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
- Add the missing bootph-all property in the flash subnode for ospi
- Add the missing overrides for the ospi node in the r5 devicetree
Signed-off-by: Aniket Limaye
---
arch/arm/dts/k3-j7200-common-proc-board-u-boot.dtsi | 4
arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 5 +
2
Add the necessary configs required for OSPI functionality.
Also update the ospi flash partition offsets as per the devicetree.
Signed-off-by: Aniket Limaye
---
configs/j7200_evm_a72_defconfig | 10 --
configs/j7200_evm_r5_defconfig | 9 +++--
2 files changed, 15 insertions(+), 4
Support for OSPI probe and also read/write is broken and/or missing in current
master branch.
- sf probe failure from u-boot prompt & OSPI boot failure [0]
This series adds necessary configs, as well as fixes some bugs in the existing
u-boot devicetree,
to add OSPI boot support for the
On Tue, 5 Mar 2024 at 19:45, Caleb Connolly wrote:
>
> [trimmed CC list a bit as this is getting offtopic for the original thread]
>
> On 05/03/2024 13:14, Sumit Garg wrote:
> > On Tue, 5 Mar 2024 at 18:21, Caleb Connolly
> > wrote:
> >>
> >>
> >>
> >> On 05/03/2024 12:35, Sumit Garg wrote:
>
On 06/03/2024 00:52, Volodymyr Babchuk wrote:
> There are cases when previous bootloader stage leaves some seemingly
> valid value in r0, which in fact does not point to valid FDT
> blob. This behavior was encountered when trying to boot U-Boot as
> "hyp" loader on SA8155P-ADP.
>
> To be sure
Arm's GIC-600 features a Power Register (GICR_PWRR),
which needs to be programmed to enable redistributor
operation. Power on the redistributor and wait until
the power on state is reflected by checking the bit
GICR_PWRR.RDPD == 0. While running U-Boot in EL3
without enabling this register,
On Wed, 6 Mar 2024 at 11:35, Ilias Apalodimas
wrote:
>
> Hi Sam,
>
>
> On Wed, 6 Mar 2024 at 10:22, Sam Edwards wrote:
> >
> > On 3/4/24 02:01, Ilias Apalodimas wrote:
> > > image_copy_start/end are defined as c variables in order to force the
> > > compiler
> > > emit relative references.
On Wed, 6 Mar 2024 at 11:08, Ilias Apalodimas
wrote:
>
> Hi Sam,
>
> First of all, thanks for taking the time to review this.
>
> On Wed, 6 Mar 2024 at 09:32, Sam Edwards wrote:
> >
> > On 3/4/24 02:01, Ilias Apalodimas wrote:
> > > commit 3ebd1cbc49f0 ("arm: make __bss_start and __bss_end__
>
FMC2 IP supports up to 4 chip select. On MP1 SoC, only 2 of them are
available when on MP25 SoC, the 4 chip select are available.
Let's use a platform data structure for parameters that will differ.
Signed-off-by: Christophe Kerello
---
drivers/mtd/nand/raw/stm32_fmc2_nand.c | 47
Hi Eugen,
On 2024/3/5 13:40, Eugen Hristev wrote:
On 3/5/24 04:10, Trevor Woerner wrote:
Following the pattern of other Rockchip devices, enable the U-Boot
environment to be stored in MMC. This patch specifically assumes the
environment will be stored on the SDcard.
Signed-off-by: Trevor
On MP1 SoC, RNB signal (NAND controller signal) and NWAIT signal (PSRAM
controller signal) have been integrated together in the SoC. That means
that the NAND controller and the PSRAM controller (if the signal is
used) can not be used at the same time. On MP25 SoC, the 2 signals can
be used outside
The FMC2 revision 2 supports security and isolation compliant with
the Resource Isolation Framework (RIF). From RIF point of view,
the FMC2 is composed of several independent resources, listed below,
which can be assigned to different security and compartment domains:
- 0: Common FMC_CFGR
Add the support of the revision 2 of FMC2 IP.
- PCSCNTR register has been removed,
- CFGR register has been added,
- the bit used to enable the IP has moved from BCR1 to CFGR,
- the timeout for CEx deassertion has moved from PCSCNTR to BCRx,
- the continuous clock enable
Hi Sam,
On Wed, 6 Mar 2024 at 10:22, Sam Edwards wrote:
>
> On 3/4/24 02:01, Ilias Apalodimas wrote:
> > image_copy_start/end are defined as c variables in order to force the
> > compiler
> > emit relative references. However, defining those within a section
> > definition
> > will do the
Hi Sam,
Again thank you for the elaborate review. This really helps a lot.
On Wed, 6 Mar 2024 at 10:14, Sam Edwards wrote:
>
>
>
> On 3/4/24 02:01, Ilias Apalodimas wrote:
> > __efi_runtime_start/end are defined as c variables for arm7 only in
> > order to force the compiler emit relative
Hi Sam,
First of all, thanks for taking the time to review this.
On Wed, 6 Mar 2024 at 09:32, Sam Edwards wrote:
>
> On 3/4/24 02:01, Ilias Apalodimas wrote:
> > commit 3ebd1cbc49f0 ("arm: make __bss_start and __bss_end__
> > compiler-generated")
> > and
> > commit f84a7b8f54db ("ARM: Fix
On 3/5/24 16:16, Dan Carpenter wrote:
Select CONFIG_64BIT so that we pass the -m64 option (instead of -m32) to
static analysis tools.
Signed-off-by: Dan Carpenter
---
arch/sandbox/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/sandbox/Kconfig b/arch/sandbox/Kconfig
index
On 3/4/24 02:01, Ilias Apalodimas wrote:
image_copy_start/end are defined as c variables in order to force the compiler
emit relative references. However, defining those within a section definition
will do the same thing.
So let's remove the special sections from the linker scripts, the
On 3/4/24 02:01, Ilias Apalodimas wrote:
__efi_runtime_start/end are defined as c variables for arm7 only in
order to force the compiler emit relative references. However, defining
those within a section definition will do the same thing. On top of that
the v8 linker scripts define it as a
97 matches
Mail list logo
