Fiptool is used in a binman test. The test is skipped without the binary.
Signed-off-by: Heinrich Schuchardt
---
tools/docker/Dockerfile | 10 ++
1 file changed, 10 insertions(+)
diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
index 884b1089e0..a5df0847d0 100644
--- a/too
Bootgen is used in a binman test. The test is skipped without the binary.
Signed-off-by: Heinrich Schuchardt
---
tools/docker/Dockerfile | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
index 6122776bc6..884b1089e0 100644
--- a/tools/docker/Do
On Tue, Feb 27, 2024 at 04:40:01PM +0100, Sébastien Szymanski wrote:
> Commit 5d7a95f4 ("imx6ul/imx6ull: synchronise device trees with
> linux") removed the display timings from the board device tree whereas
> they are still needed by the mxsfb driver.
> Add the timings back (the correct ones)
On Wed, 28 Feb 2024 at 04:44, Adam Ford wrote:
>
> On Mon, Feb 26, 2024 at 2:05 AM Sumit Garg wrote:
> >
> > pcie_imx doesn't seem to share any useful code for iMX8 SoC and it is
> > tied to quite old port of pcie_designware driver from Linux which
> > suffices only iMX6 specific needs.
> >
> > B
Hi Adam,
On Wed, 28 Feb 2024 at 04:42, Adam Ford wrote:
>
> On Mon, Feb 26, 2024 at 2:05 AM Sumit Garg wrote:
> >
> > Add initial support for i.MX8M{M/P} PCIe PHY. On i.MX8M{M/P} SoCs PCIe
> > PHY initialization moved to this standalone PHY driver.
> >
> > Inspired from counterpart Linux kernel
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 dynamically loadable,
> and in the case of OP-TEE ma
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.
>
> Signed-off-by: Andrew Davis
> ---
>
Hi,
On Feb 26, 2024 at 13:23:41 +0100, Wadim Egorov wrote:
> Add documentation for PHYTEC phyCORE-AM64x SoM.
>
> Signed-off-by: Wadim Egorov
> ---
> doc/board/phytec/index.rst | 1 +
> doc/board/phytec/phycore-am64x.rst | 159 +
> 2 files changed, 160 inser
If mixed rsa and ecdsa keys are specified in dtsi, an rsa key can be sent
into the ecdsa verify. Without the ecdsa,curve property, this function will
crash due to lack of checking the null pointer return.
Signed-off-by: Bob Wolff
---
lib/ecdsa/ecdsa-verify.c | 5 +
1 file changed, 5 inserti
On Mon, Feb 26, 2024 at 2:05 AM Sumit Garg wrote:
>
> pcie_imx doesn't seem to share any useful code for iMX8 SoC and it is
> tied to quite old port of pcie_designware driver from Linux which
> suffices only iMX6 specific needs.
>
> But currently we have the common DWC specific bits which alligns
On Mon, Feb 26, 2024 at 2:05 AM Sumit Garg wrote:
>
> Add initial support for i.MX8M{M/P} PCIe PHY. On i.MX8M{M/P} SoCs PCIe
> PHY initialization moved to this standalone PHY driver.
>
> Inspired from counterpart Linux kernel v6.8-rc3 driver:
> drivers/phy/freescale/phy-fsl-imx8m-pcie.c.
I have a
On 2/20/24 14:52, Tom Rini wrote:
From: Florian Schmaus
Once u-boot's build system invokes
python3 scripts/dtc/pylibfdt/setup.py --quiet build_ext --inplace
it may fail with
scripts/dtc/pylibfdt/setup.py:40: SyntaxWarning: invalid escape sequence '\w'
RE_KEY_VALUE = re.compile('(?P\w+) *(
\w is not allowed as escape sequence is strings.
Mark the regular expression with r''.
Signed-off-by: Heinrich Schuchardt
---
scripts/dtc/pylibfdt/setup.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/dtc/pylibfdt/setup.py b/scripts/dtc/pylibfdt/setup.py
index 8baa
\s is not a valid escape sequence in strings.
Mark regular expressions with r''.
Signed-off-by: Heinrich Schuchardt
---
tools/dtoc/src_scan.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/dtoc/src_scan.py b/tools/dtoc/src_scan.py
index 3bef59d616..2437200a42
Hi Sumit,
On 22/02/2024 09:36, Sumit Garg wrote:
> Encourage SoC/board maintainers to migrate to using devicetree-rebasing
> subtree and maintain a regular sync with Linux kernel devicetree files
> and bindings.
>
> Along with that add documentation regarding how to run DT bindings
> schema check
On Mon, 22 Jan 2024 17:39:05 -0500, Tom Rini wrote:
> It is possible to have a platform which does not require a board.h file
> to build, but today we need an empty one for our generated config.h file
> to be valid. Allow for omitting this file if CONFIG_SYS_CONFIG_NAME is
> not set.
>
>
Applie
From: max
Currently fetching files bigger that cause a data transfer greater than
U16_MAX fails.
The reason is that the specification defines the datalength register
as a 16 bit wide register, but in u-boot it is used as if it is an
32 bit register. Therefore values greater than U16_MAX cause an
If SYSRESET support is enabled for the RAA215300 PMIC, we need to bind
the raa215300_sysreset driver as a child device of the PMIC.
Signed-off-by: Paul Barker
Reviewed-by: Marek Vasut
---
drivers/power/pmic/raa215300.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/power/p
With the SYSRESET subsystem enabled we do not need to implement
reset_cpu() in the board directory.
Signed-off-by: Paul Barker
Reviewed-by: Marek Vasut
---
board/renesas/rzg2l/rzg2l.c | 8
configs/renesas_rzg2l_smarc_defconfig | 2 ++
2 files changed, 2 insertions(+), 8 delet
This patch adds support for resetting a board via the RAA215300 PMIC.
Note that the RAA215300 documentation names the available reset types
differently to u-boot:
* A "warm" reset via the RAA215300 PMIC will fully reset the SoC
(CPU & GPIOs), so this corresponds to SYSRESET_COLD.
* A "co
Enable the appropriate PMIC driver as well as the `pmic` command.
Signed-off-by: Paul Barker
---
configs/renesas_rzg2l_smarc_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/configs/renesas_rzg2l_smarc_defconfig
b/configs/renesas_rzg2l_smarc_defconfig
index ad46297c6619..2cab793
The RZ/G2L SMARC module is powered via a Renesas RAA215300 PMIC which
provides several voltage converters, a real time clock (RTC) and reset
control. A basic driver is implemented for this device so that we can
read, write and dump the PMIC registers.
The raa215300_bind() function is added as a st
This driver supports the I2C module on the Renesas RZ/G2L (R9A07G044)
SoC, also known as the RIIC module.
This patch is based on both the u-boot driver in the Renesas RZ BSP
3.0.5 release [1] (commit 7fcc1fdc2534), and the Linux v6.7 driver
(commit 0dd3ee311255).
Support for deblocking the I2C bu
Pull in the recent changes to the RZ/G2L device tree and related dtsi
files so that we're aligned with Linux v6.7 (commit 0dd3ee311255).
Signed-off-by: Paul Barker
Reviewed-by: Marek Vasut
---
arch/arm/dts/r9a07g044.dtsi | 16 -
arch/arm/dts/r9a07g044l2-smarc.dts|
When enabling/disabling a clock or reset signal, confirm that the change
has completed before returning from the function. A somewhat arbitrary
100ms timeout is defined to ensure that the system doesn't lock up in
the case of an error.
Since we need to dynamically determine if we're waiting for a
This patch series extends the support for the Renesas RZ/G2L SMARC EVK
board (based on the R9A07G044L2 SoC) to include the following new
features:
* I2C bus support, including automatic deblocking if SDA is stuck low
due to another device on the board.
* Basic PMIC support, with the abili
Tom Rini writes:
> On Sat, Feb 24, 2024 at 11:34:36AM -0600, Jon Humphreys wrote:
>> Tom Rini writes:
>>
>> > On Fri, Feb 23, 2024 at 06:17:02PM -0600, Jonathan Humphreys wrote:
>> >> Add bootph DT tags to enable OSPI in SPL.
>> >> Set OSPI regs for R5 SPL to address OSPI's boot region.
>> >>
Hi Apurva
On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
> Add defconfigs for building R5 U-Boot SPL and A72 U-Boot.
>
> Signed-off-by: Hari Nagalla
> Signed-off-by: Apurva Nandan
> ---
> board/ti/j784s4/MAINTAINERS | 2 +
> configs/j784s4_evm_a72_defconfig | 159 ++
On Sat, Feb 24, 2024 at 11:34:36AM -0600, Jon Humphreys wrote:
> Tom Rini writes:
>
> > On Fri, Feb 23, 2024 at 06:17:02PM -0600, Jonathan Humphreys wrote:
> >> Add bootph DT tags to enable OSPI in SPL.
> >> Set OSPI regs for R5 SPL to address OSPI's boot region.
> >>
> >> Signed-off-by: Jonatha
On Tue, Feb 27, 2024 at 02:37:25AM +, Caleb Connolly wrote:
> HI Varada,
>
> On 26/02/2024 10:07, Varadarajan Narayanan wrote:
> > These patches introduce the initial support code needed
> > for the QTI IPQ9574 SoC and RDP433 board.
>
> Awesome!
Thanks for the feedback. Will rework based on th
On Mon, Feb 26, 2024 at 12:20:27PM +0200, Ilias Apalodimas wrote:
> Hi,
>
> Please resend the patch with a proper description.
I had given the description here with the 'Cover-letter:' tag and
naively assumed it would be copied to cover letter. However,
patman moved it to cover letter and this bec
Hi Apurva
On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
> Introduce the base dts files needed for u-boot or to augment the linux
> dtbs for use in the u-boot-spl and u-boot binaries.
>
> Signed-off-by: Hari Nagalla
> [ add binman and ddr dtsi files ]
> Signed-off-by: Neha Malcom Franci
Hi Apurva
On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
> From: Dasnavis Sabiya
>
> Introduce the base dts files needed for u-boot or to augment the linux
> dtbs for use in the u-boot-spl and u-boot binaries.
>
> Signed-off-by: Dasnavis Sabiya
> Signed-off-by: Apurva Nandan
> ---
>
Hi Apurva
On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
> Hello Everyone!
>
> This series will introduce basic support (SD and UART) support for Texas
> Instruments J784S4 EVM.
>
> The J784S4 SoC device tree patches are taken from kernel patch submissions
> and will be updated as they
Last board with this SoC has been removed in commit
0fb054b3f7ea ("arm: Remove armadillo-800eva board")
in August 2022. Drop the rest of unused code.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc: Paul Barker
Cc: Tom Rini
---
arch/arm/mach-rmobile/Kconfig.32 |3 -
a
Bind SPI-NAND driver to MTD block driver.
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/spi/core.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/mtd/nand/spi/core.c b/drivers/mtd/nand/spi/core.c
index 2a3dbcfcb4..1d9cf66e4a 100644
--- a/drivers/mtd/nand/s
Add new MTD partition driver, which can be useful with
mtdblock driver combination.
Signed-off-by: Alexey Romanov
---
disk/part.c | 5 +++-
drivers/mtd/Kconfig | 1 +
drivers/mtd/mtdpart.c | 69 +++
include/part.h| 2 ++
4 files chan
We have to compile efi_block abstraction only if option
EFI_PARTITION is enabled. For example, if the user
only enabled MTD_PARTITIONS, we would still compile
efi_block. This is incorrect.
Signed-off-by: Alexey Romanov
---
lib/efi_driver/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletio
MTD block - abstraction over MTD subsystem, allowing
to read and write in blocks using BLK UCLASS.
- Read algorithm:
1. Convert start block number to start address.
2. Read block_dev->blksz bytes using mtd_read() and
add to start address pointer block_dev->blksz bytes,
until the req
Hello!
This series adds support for the mtdblock 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 mtd 0 part_name
Tested only on SPI NAND, so bind is made only for
SPI NAND drivers.
Alexey Romanov (4):
drivers:
Add new renesas entry and update rmobile entry to match.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc: Paul Barker
Cc: Tom Rini
---
doc/git-mailrc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/git-mailrc b/doc/git-mailrc
index 0ceb9eb88b5..ca2f67a3b6e 10
Rename rmobile_is_gen3_mmc0() to rcar_is_gen3_mmc0() because
this particular function is specific to Renesas R-Car Gen3.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc: Paul Barker
Cc: Tom Rini
---
drivers/mmc/renesas-sdhi.c | 8
1 file changed, 4 insertions(+), 4 deletions(
Fix up remains of rename from rmobile to renesas,
namely file paths and remaining RMOBILE strings.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc: Paul Barker
Cc: Tom Rini
---
arch/arm/mach-renesas/cpu_info-rcar.c | 2 +-
arch/arm/mach-renesas/emac.c | 2 +-
arch/a
Rename arch-rmobile to arch-renesas and mach-rmobile to mach-renesas
because all the chips are made by Renesas, while only a subset of
them is from the R-Mobile line.
Use the following command to perform the rename, with manual move of
the directories using git mv and manual fix up to arch/arm/Mak
Rename ARCH_RMOBILE to ARCH_RENESAS because all the chips are made
by Renesas, while only a subset of them is from the R-Mobile
line.
Use the following command to perform the rename:
"
$ git grep -l 'ARCH_RMOBILE' | xargs -I {} sed -i
's@ARCH_RMOBILE@ARCH_RENESAS@g' {}
"
Signed-off-by: Marek Va
Rename rmobile.h to renesas.h because all the chips are made
by Renesas, while only a subset of them is from the R-Mobile
line.
Use the following command to perform the rename:
"
$ git grep -l 'include.*rmobile.h' | \
xargs -I {} sed -i '/include.*rmobile.h/ s@rmobile.h@renesas.h@g' {}
"
Signe
Rename CONFIG_ARCH_RMOBILE_EXTRAM_BOOT to CONFIG_RMOBILE_EXTRAM_BOOT
because the former symbol does not exist and it is only incorrectly
converted CONFIG_RMOBILE_EXTRAM_BOOT which does exist. Replace the
RMOBILE with RENESAS because all the chips are made by Renesas, while
only a subset of them is
Rename ARCH_RMOBILE_BOARD_STRING to ARCH_RENESAS_BOARD_STRING
because all the chips are made by Renesas, while only a subset
of them is from the R-Mobile line.
Use the following command to perform the rename:
"
$ git grep -l 'ARCH_RMOBILE_BOARD_STRING' | \
xargs -I {} sed -i 's@ARCH_RMOBILE_BOA
Rename rmobile_get_prr() to renesas_get_prr() because all the
chips are made by Renesas, while only a subset of them is from
the R-Mobile line.
Use the following command to perform the rename:
"
$ git grep -l '\' | \
xargs -I {} sed -i 's@\@renesas_get_prr@g' {}
"
Signed-off-by: Marek Vasut
-
Simplify the weak symbols use in cpu_info.c by using the __weak macro.
The result is identical, but the syntax is much simpler. Furthermore,
drop three more rmobile* symbols which are now unused.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc: Paul Barker
Cc: Tom Rini
---
arch/arm/ma
Rename rmobile_cpuinfo[] to renesas_cpuinfo[] because all
the chips are made by Renesas, while only a subset of them
is from the R-Mobile line.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc: Paul Barker
Cc: Tom Rini
---
arch/arm/mach-rmobile/cpu_info.c | 12 ++--
1 file chan
Rename rmobile_cpuinfo_idx() to renesas_cpuinfo_idx() because all
the chips are made by Renesas, while only a subset of them is from
the R-Mobile line.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc: Paul Barker
Cc: Tom Rini
---
arch/arm/mach-rmobile/cpu_info.c | 6 +++---
1 file cha
Rename RMOBILE_CPU_TYPE_* to RENESAS_CPU_TYPE_* because all
the chips are made by Renesas, while only a subset of them is
from the R-Mobile line.
Use the following command to perform the rename:
"
$ git grep -l '\' | \
xargs -I {} sed -i 's@\@RENESAS\1@g' {}
"
Signed-off-by: Marek Vasut
---
C
Rename rmobile_get_cpu_rev_*() to renesas_get_cpu_rev_*() because
all the chips are made by Renesas, while only a subset of them is
from the R-Mobile line.
Use the following command to perform the rename:
"
$ git grep -l '\' | \
xargs -I {} sed -i
's@\@renesas_get_cpu_rev_\1@g' {}
"
Signed-of
Rename rmobile_get_cpu_type() to renesas_get_cpu_type() because
all the chips are made by Renesas, while only a subset of them
is from the R-Mobile line.
Use the following command to perform the rename:
"
$ git grep -l '\' | \
xargs -I {} sed -i 's@\@renesas_get_cpu_type@g' {}
"
Signed-off-by:
This file is no longer used, the PFC pin controller driver is
superseded by drivers/pinctrl/renesas/pfc-r8a7790.c which
includes all the details of the hardware. Remove this file.
No functional change.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc: Paul Barker
Cc: Tom Rini
---
arch/
This file is no longer used, the MMCIF controller driver is
superseded by drivers/mmc/sh_mmcif.c which includes all the
details of the hardware. Remove this file include from all
board files and remove the file itself. No functional change.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwamatsu
Cc
This file is no longer used, the SDHI controller driver is long
superseded by drivers/mmc/renesas-sdhi.c which includes all the
details of the hardware. Remove this file include from all board
files and remove the file itself. No functional change.
Signed-off-by: Marek Vasut
---
Cc: Nobuhiro Iwam
Rename R-Mobile to Renesas all over the place because the chips are
made by Renesas, while only a subset of them is from the R-Mobile line.
Marek Vasut (19):
ARM: renesas: Drop remnants of R8A7740 support
ARM: renesas: Drop unused sh_sdhi.h
ARM: renesas: Drop unused mmc.h
ARM: renesas: Dro
On 2/26/24 4:05 PM, Paul Barker wrote:
This driver supports the I2C module on the Renesas RZ/G2L (R9A07G044)
SoC, also known as the RIIC module.
This patch is based on both the u-boot driver in the Renesas RZ BSP
3.0.5 release [1] (commit 7fcc1fdc2534), and the Linux v6.7 driver
(commit 0dd3ee31
On 2/26/24 4:05 PM, Paul Barker wrote:
The RZ/G2L SMARC module is powered via a Renesas RAA215300 PMIC which
provides several voltage converters, a real time clock (RTC) and reset
control. A basic driver is implemented for this device so that we can
read, write and dump the PMIC registers.
The r
On 2/26/24 4:05 PM, Paul Barker wrote:
With the SYSRESET subsystem enabled we do not need to implement
reset_cpu() in the board directory.
Signed-off-by: Paul Barker
Reviewed-by: Marek Vasut
On 2/26/24 4:05 PM, Paul Barker wrote:
If SYSRESET support is enabled for the RAA215300 PMIC, we need to bind
the raa215300_sysreset driver as a child device of the PMIC.
Signed-off-by: Paul Barker
Reviewed-by: Marek Vasut
On 2/26/24 4:05 PM, Paul Barker wrote:
If SYSRESET support is enabled for the RAA215300 PMIC, we need to bind
the raa215300_sysreset driver as a child device of the PMIC.
Signed-off-by: Paul Barker
Marek Vasut
On 2/26/24 4:05 PM, Paul Barker wrote:
This patch adds support for resetting a board via the RAA215300 PMIC.
Note that the RAA215300 documentation names the available reset types
differently to u-boot:
* A "warm" reset via the RAA215300 PMIC will fully reset the SoC
(CPU & GPIOs), so th
On Tue, Feb 27, 2024 at 04:40:01PM +0100, Sébastien Szymanski wrote:
> Commit 5d7a95f4 ("imx6ul/imx6ull: synchronise device trees with
> linux") removed the display timings from the board device tree whereas
> they are still needed by the mxsfb driver.
> Add the timings back (the correct ones)
Because of commit bf947d2a4b15 ("imx6ul: synchronise device tree with
linux"), the compatible property of lcdif in imx6ul.dtsi went from
compatible = "fsl,imx6ul-lcdif", "fsl,imx28-lcdif";
to
compatible = "fsl,imx6ul-lcdif", "fsl,imx6sx-lcdif";
without updating the mxsfb driver to match that ch
Commit 5d7a95f4 ("imx6ul/imx6ull: synchronise device trees with
linux") removed the display timings from the board device tree whereas
they are still needed by the mxsfb driver.
Add the timings back (the correct ones) in the
imx6ul-opos6uldev-u-boot.dtsi file and remove them from the
opos6uldev
Hi Danish,
On 2/27/24 05:26, MD Danish Anwar wrote:
On 09/02/24 3:38 pm, MD Danish Anwar wrote:
The fs-loader driver reads env storage_interface and uses it to load
firmware file into memory using the medium set by env. Update the driver
to use env fw_storage_interface as this variable is only
On 19/02/2024 17:33, Roger Quadros wrote:
> Some platforms have bus level Reset controlled
> by a GPIO line. If available then handle bus reset
> via GPIO.
>
> Signed-off-by: Roger Quadros
> ---
> include/phy.h | 7 +++
> net/mdio-uclass.c | 37 -
>
On 22/02/2024 08:59, Ravi Gunasekaran wrote:
>
>
> On 2/19/24 9:03 PM, Roger Quadros wrote:
>> Some platforms have bus level Reset controlled
>> by a GPIO line. If available then handle bus reset
>> via GPIO.
>>
>> Signed-off-by: Roger Quadros
>> ---
>> include/phy.h | 7 +++
>> net
Add default configuration for nand-flash to boot the linux kernel.
Add default configuration for qspi-flash to boot the linux kernel.
Add default configuration for sd-card to boot the linux kernel.
Configs are synced with savedefconfig.
Signed-off-by: Mihai Sain
---
configs/sama7g54_curiosity_mm
Add initial support for SAMA7G54 Curiosity board.
Hardware:
SoC: SAMA7G54D2G SiP 1000 MHz
DRAM: DDR3 256 MiB
PMIC: MCP16502
Debug: UART3
Flash: QSPI NOR 8 MiB, SLC NAND 512 MiB
M.2 slot for wireless
Mikrobus connectors x 2
SD-Card connectors x 1
USB 2.0 x 3
Signed-off-by: Mihai Sain
---
arch/ar
Add flexcom 10 node for usage on the SAMA7G54 Curiosity board.
Signed-off-by: Mihai Sain
---
arch/arm/dts/sama7g5.dtsi | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm/dts/sama7g5.dtsi b/arch/arm/dts/sama7g5.dtsi
index 746a5ba347..a17c58cbfc 100644
--- a/arc
This patch series adds initial support for Microchip SAMA7G54 Curiosity board.
Changes in v2:
--
* Update flexcom 10 node in order to match previous flexcom definitions.
* Sort in alphabetical order all nodes and pinctrl.
* Remove status okay from leds, nand, eeprom, flash.
* Add CONF
Add initial device tree of the SAMA7G54 Curiosity board.
Signed-off-by: Mihai Sain
---
arch/arm/dts/Makefile | 3 +
.../dts/at91-sama7g54_curiosity-u-boot.dtsi | 59 +
arch/arm/dts/at91-sama7g54_curiosity.dts | 242 ++
3 files changed, 304 in
On 27/02/2024 07:54, Viacheslav Bocharov wrote:
Update JetHub D1/D1+ board support files.
Viacheslav Bocharov (3):
board: amlogic: jethubj100: fix common config header
board: amlogic: jethubj100: update MAINTAINERS
board: amlogic: jethubj100: update docs
board/amlogic/jethub-j100/MAI
On 27.02.24 11:04, Alexey Romanov wrote:
MTD block - abstraction over MTD subsystem, allowing
to read and write in blocks using BLK UCLASS.
- Read algorithm:
1. Convert start block number to start address.
2. Read block_dev->blksz bytes using mtd_read() and
add to start address poin
On 27.02.24 11:04, Alexey Romanov wrote:
Add new MTD partition driver, which can be useful with
mtdblock driver combination.
Signed-off-by: Alexey Romanov
---
disk/part.c | 5 +++-
drivers/mtd/Kconfig | 1 +
drivers/mtd/mtdpart.c | 69 ++
On 27.02.24 11:04, Alexey Romanov wrote:
Bind SPI-NAND driver to MTD block driver.
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/spi/core.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/mtd/nand/spi/core.c b/drivers/mtd/nand/spi/core.c
index 2a3dbcfcb
On 27.02.24 11:04, Alexey Romanov wrote:
We have to compile efi_block abstraction only if option
EFI_PARTITION is enabled. For example, if the user
only enabled MTD_PARTITIONS, we would still compile
efi_block. This is incorrect.
Signed-off-by: Alexey Romanov
---
lib/efi_driver/Makefile | 2 +
On 2/27/24 8:38 AM, Janne Grunau wrote:
Hej,
On Sun, Feb 25, 2024, at 22:47, Marek Vasut wrote:
On 2/25/24 4:28 PM, Janne Grunau wrote:
On Wed, Feb 21, 2024, at 13:39, Marek Vasut wrote:
On 2/21/24 08:25, Janne Grunau via B4 Relay wrote:
From: Janne Grunau
Apple USB keyboards carry the H
On 2/27/24 8:13 AM, Janne Grunau wrote:
Hej,
On Mon, Feb 26, 2024, at 21:47, Mark Kettenis wrote:
Date: Sun, 25 Feb 2024 22:57:23 +0100
From: Marek Vasut
On 2/25/24 5:07 PM, Janne Grunau wrote:
Hej,
On Wed, Feb 21, 2024, at 13:41, Marek Vasut wrote:
On 2/21/24 08:25, Janne Grunau via B4 Re
On 24/01/24 02:27, Nishanth Menon wrote:
On 15:49-20240122, Chintan Vankar wrote:
On 12/01/24 18:00, Nishanth Menon wrote:
On 12:17-20240112, Siddharth Vadapalli wrote:
From: Kishon Vijay Abraham I
In order to support Ethernet boot on AM62x, probe AM65 CPSW NUSS driver
in board_init_f().
On 2/17/24 5:56 PM, MD Danish Anwar wrote:
> Add APIs to set a firmware_name to a rproc and boot the rproc with the
> same firmware.
>
> Clients can call rproc_set_firmware() API to set firmware_name for a rproc
> whereas rproc_boot() will load the firmware set by rproc_set_firmware() to
> a bu
On 2/27/24 09:57, Lukas Funke wrote:
On 27.02.2024 09:45, Michal Simek wrote:
On 2/27/24 09:40, lukas.funke-...@weidmueller.com wrote:
From: Lukas Funke
Some zynqmp SoCs (the cg series) only have two cpus. Thus, for some
cases the cpu-affinity has to adapted, because cpu3 and cpu4 are
On 09/02/24 3:38 pm, MD Danish Anwar wrote:
> The fs-loader driver reads env storage_interface and uses it to load
> firmware file into memory using the medium set by env. Update the driver
> to use env fw_storage_interface as this variable is only used to load
> firmwares. This is to keep all vari
On 26/02/2024 10:07, Varadarajan Narayanan wrote:
> Add few SMEM related defines that will be used for
> IPQ9574 based boards.
The tiny To/Cc list above is probably because this file isn't mentioned
in MAINTAINERS, please add myself, Neil, and Sumit (see the ARM
SNAPDRAGON section in MAINTAINER
Hi Sumit
On 27/02/24 14:29, Sumit Garg wrote:
Hi Neha,
On Tue, 27 Feb 2024 at 13:53, Neha Malcom Francis wrote:
Hi Bryan
On 27/02/24 02:49, Bryan Brattlof wrote:
Some boards that choose to utilize the OF_UPSTREAM directory for their
device tree files will need to specify that directory ins
Hi Neha,
On Tue, 27 Feb 2024 at 13:53, Neha Malcom Francis wrote:
>
> Hi Bryan
>
> On 27/02/24 02:49, Bryan Brattlof wrote:
> > Some boards that choose to utilize the OF_UPSTREAM directory for their
> > device tree files will need to specify that directory instead of the
> > traditional arch/$(AR
On 27.02.2024 09:45, Michal Simek wrote:
On 2/27/24 09:40, lukas.funke-...@weidmueller.com wrote:
From: Lukas Funke
Some zynqmp SoCs (the cg series) only have two cpus. Thus, for some
cases the cpu-affinity has to adapted, because cpu3 and cpu4 are
interrupt-affinity right?
Duh. Can you
On 2/27/24 09:40, lukas.funke-...@weidmueller.com wrote:
From: Lukas Funke
Some zynqmp SoCs (the cg series) only have two cpus. Thus, for some
cases the cpu-affinity has to adapted, because cpu3 and cpu4 are
interrupt-affinity right?
missing. By adding a label to the pmu fwnode the cpu
From: Lukas Funke
Some zynqmp SoCs (the cg series) only have two cpus. Thus, for some
cases the cpu-affinity has to adapted, because cpu3 and cpu4 are
missing. By adding a label to the pmu fwnode the cpu affinity can
be adapted in a device specific dt.
Signed-off-by: Lukas Funke
---
arch/arm/d
Hi Bryan
On 27/02/24 02:49, Bryan Brattlof wrote:
Some boards that choose to utilize the OF_UPSTREAM directory for their
device tree files will need to specify that directory instead of the
traditional arch/$(ARCH)/dts/* path.
Include the correct path to the board's dtbs depending on if OF_UPST
94 matches
Mail list logo
