On 19.05.22 11:11, Pali Rohár wrote:
It does not matter what is DT node name of atsha device. So find it via
atsha driver and not by DT node name.
Signed-off-by: Pali Rohár
Just curious: What exactly does this patch fix? Is there a turris
board with a differently named atsha DT entry?
On 20.05.22 06:39, Chris Packham wrote:
board_get_usable_ram_top() conflated the RAM size with the top address
of RAM. On systems where RAM starts at address 0 these numbers are the
same so it went unnoticed. Update board_get_usable_ram_top() to take
CONFIG_SYS_SDRAM_BASE into account when
On 19.05.22 18:48, Pierre-Clément Tosi wrote:
Add a check for calloc() failing to allocate the requested memory.
Make decode_regions() return an error code.
Cc: Bin Meng
Cc: Simon Glass
Cc: Stefan Roese
Signed-off-by: Pierre-Clément Tosi
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
board_get_usable_ram_top() conflated the RAM size with the top address
of RAM. On systems where RAM starts at address 0 these numbers are the
same so it went unnoticed. Update board_get_usable_ram_top() to take
CONFIG_SYS_SDRAM_BASE into account when determining the top address.
Signed-off-by:
On 5/20/22 00:24, Tim Harvey wrote:
[...]
diff --git a/include/power/pca9450.h b/include/power/pca9450.h
index 27703bb1f91..b714fc3477d 100644
--- a/include/power/pca9450.h
+++ b/include/power/pca9450.h
@@ -56,4 +56,15 @@ enum {
int power_pca9450_init(unsigned char bus, unsigned char addr);
Add PCA9450 regulator driver. This is complementary driver for the BUCKn
and LDOn regulators provided by the PCA9450 PMIC driver. Currently the
driver permits reading the settngs and configuring the BUCKn and LDOn
regulators.
Reviewed-by: Fabio Estevam
Signed-off-by: Marek Vasut
Cc: Fabio
The upstream DT regulators node subnodes are named BUCKn and LDOn,
the downstream DT regulators node subnodes are named buckn and ldon,
add the upstream match.
Reviewed-by: Fabio Estevam
Signed-off-by: Marek Vasut
Cc: Fabio Estevam
Cc: Peng Fan
Cc: Stefano Babic
---
V2: Add RB by Fabio
V3:
arch/*/lib/bootm.c is for the boot Linux commands, not just for
bootm command.
This commit makes CONFIG_BOOTM_LINUX selected by the boot Linux
commands and arch/*/lib/bootm.c will be built if enabled
CONFIG_BOOTM_LINUX.
Signed-off-by: Rover Mo
---
arch/arc/lib/Makefile| 2 +-
To prevent booting unsigned images, don't enable the non-secure boot
commands(booti, bootz .etc) by default if secure boot enabled.
Signed-off-by: Rover Mo
---
boot/Kconfig | 2 +-
cmd/Kconfig | 11 +--
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/boot/Kconfig
Changes for v3:
- Add [2/2] for fixing build error on iot_devkit
Changes for v2:
- Don't enable the non-secure boot commands too if !EFI_SECURE_BOOT
- Update the help information
- Changed commit title
Rover Mo (2):
boot: don't enable the non-secure boot commands by default if
Linux determines its console based on several sources:
1. the console command line parameter
2. device tree (e.g. /chosen/stdout-path)
3. various other board- and arch-specific sources
If the console parameter specifies a real console (e.g. ttyS0) then that is
used as /dev/console. However, if
On Sun, Apr 24, 2022 at 2:41 PM Marek Vasut wrote:
>
> Add PCA9450 regulator driver. This is complementary driver for the BUCKn
> and LDOn regulators provided by the PCA9450 PMIC driver. Currently the
> driver permits reading the settngs and configuring the BUCKn and LDOn
> regulators.
>
>
Add support for DH electronics i.MX8M Plus DHCOM SoM on PDK2 carrier board.
Currently supported are serial console, EQoS and FEC ethernets, eMMC, SD,
SPI NOR and USB 3.0 host.
Signed-off-by: Marek Vasut
Cc: Fabio Estevam
Cc: Peng Fan
Cc: Stefano Babic
---
arch/arm/dts/Makefile
The dev_read_stringlist_search() in generic_phy_get_by_name()
returns -ENODATA in case of missing "phy-names", which is the
case on everything except ZynqMP. Handle this -ENODATA instead
of failing outright, which fixes the glue on everything else.
Fixes: 142d50fbce7 ("usb: dwc3: Add support for
On Thu, 19 May 2022, Peter Geis wrote:
> On Thu, May 19, 2022 at 1:36 PM Peter Geis wrote:
> >
> > On Thu, May 19, 2022 at 1:23 PM Lee Jones wrote:
> > >
> > > On Thu, 19 May 2022, Lee Jones wrote:
> > >
> > > > On Thu, 19 May 2022, Peter Geis wrote:
> > > >
> > > > > On Thu, May 19, 2022 at
On Thu, May 19, 2022 at 1:36 PM Peter Geis wrote:
>
> On Thu, May 19, 2022 at 1:23 PM Lee Jones wrote:
> >
> > On Thu, 19 May 2022, Lee Jones wrote:
> >
> > > On Thu, 19 May 2022, Peter Geis wrote:
> > >
> > > > On Thu, May 19, 2022 at 11:47 AM Lee Jones wrote:
> > > > >
> > > > > On Thu, 19
On Thu, May 19, 2022 at 1:23 PM Lee Jones wrote:
>
> On Thu, 19 May 2022, Lee Jones wrote:
>
> > On Thu, 19 May 2022, Peter Geis wrote:
> >
> > > On Thu, May 19, 2022 at 11:47 AM Lee Jones wrote:
> > > >
> > > > On Thu, 19 May 2022, Lee Jones wrote:
> > > >
> > > > > On Thu, 19 May 2022, Peter
On Thu, May 19, 2022 at 04:25:48PM +0200, Francesco Dolcini wrote:
> On Thu, May 19, 2022 at 04:22:26PM +0200, Francesco Dolcini wrote:
> > Add a new device tree property "u-boot,version" in the chosen node to
> > pass the U-Boot version to the operating system.
> > This can be useful to implement
On Thu, 19 May 2022, Lee Jones wrote:
> On Thu, 19 May 2022, Peter Geis wrote:
>
> > On Thu, May 19, 2022 at 11:47 AM Lee Jones wrote:
> > >
> > > On Thu, 19 May 2022, Lee Jones wrote:
> > >
> > > > On Thu, 19 May 2022, Peter Geis wrote:
> > > >
> > > > > On Thu, May 19, 2022 at 10:56 AM Lee
For indicating the address and size of a memory region other commands use a
[:] syntax. Do the same for bootefi.
Fixes: 2058983689f0 ("cmd: bootefi: restore ability to boot arbitrary blob")
Signed-off-by: Heinrich Schuchardt
---
cmd/bootefi.c | 21 +++--
On Thu, 19 May 2022, Peter Geis wrote:
> On Thu, May 19, 2022 at 11:47 AM Lee Jones wrote:
> >
> > On Thu, 19 May 2022, Lee Jones wrote:
> >
> > > On Thu, 19 May 2022, Peter Geis wrote:
> > >
> > > > On Thu, May 19, 2022 at 10:56 AM Lee Jones wrote:
> > > > >
> > > > > > > > > It's not clear
Hi
On 5/18/22 19:03, Marek Vasut wrote:
On 5/18/22 18:53, Patrick DELAUNAY wrote:
Hi,
Hi,
[...]
I let you handle OF_LIVE for your boards (code & defconfig),
FYI: it is already enable for STMicroelectronics boards (defconfig
and in driver, mach-stm32mp and board code).
But look:
Activate the live DT with CONFIG_OF_LIVE to reduce the DT parsing
time.
Signed-off-by: Patrick Delaunay
---
configs/stm32mp15_dhcom_basic_defconfig | 1 +
configs/stm32mp15_dhcor_basic_defconfig | 1 +
2 files changed, 2 insertions(+)
diff --git a/configs/stm32mp15_dhcom_basic_defconfig
Replace call to fdt_*() functions and access to gd->fdt_blob
with call to ofnode_*() functions to support a live tree.
Signed-off-by: Patrick Delaunay
---
board/dhelectronics/dh_stm32mp1/board.c | 38 +++--
1 file changed, 16 insertions(+), 22 deletions(-)
diff --git
On Thu, May 19, 2022 at 11:47 AM Lee Jones wrote:
>
> On Thu, 19 May 2022, Lee Jones wrote:
>
> > On Thu, 19 May 2022, Peter Geis wrote:
> >
> > > On Thu, May 19, 2022 at 10:56 AM Lee Jones wrote:
> > > >
> > > > > > > > It's not clear how this issue (present 3 years ago) was finally
> > > > > >
Add a directory in drivers/clk to regroup the clock drivers for all
STM32 Soc with CONFIG_ARCH_STM32 (MCUs with cortex M) or
CONFIG_ARCH_STM32MP (MPUs with cortex A).
Signed-off-by: Patrick Delaunay
---
Changes in v2:
- replace '_' by '-' in file names to be consistant with other clk drivers
Add the RCC node, not yet in Linux kernel device tree
to handle the U-Boot RCC drivers with the needed U-Boot
property "u-boot,dm-pre-reloc" property as the clock and reset drivers
are required during pre-location.
Signed-off-by: Patrick Delaunay
---
(no changes since v1)
Prepare the support of STM32MP13 RCC, the reset and clock controller
- update of the RCC MISC driver to bind the correct clock and reset driver
- reset driver, same than STM32MP15x = drivers/reset/stm32-reset.c
- clock driver, add a stm32 sub directory to prepare the addition of
stm32mp13
Add the MISC RCC driver for STM32MP13, and bind it to the RCC reset
driver, required for initial support.
Signed-off-by: Patrick Delaunay
---
(no changes since v1)
drivers/misc/stm32_rcc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/misc/stm32_rcc.c
On Thu, 19 May 2022, Lee Jones wrote:
> On Thu, 19 May 2022, Peter Geis wrote:
>
> > On Thu, May 19, 2022 at 10:56 AM Lee Jones wrote:
> > >
> > > > > > > It's not clear how this issue (present 3 years ago) was finally
> > > > > > > resolved. From the thread, it looks as if the fix might have
On Thu, 19 May 2022, Peter Geis wrote:
> On Thu, May 19, 2022 at 10:56 AM Lee Jones wrote:
> >
> > > > > > It's not clear how this issue (present 3 years ago) was finally
> > > > > > resolved. From the thread, it looks as if the fix might have made
> > > > > > its
> > > > > > way into ATF, but
On Thu, May 19, 2022 at 10:56 AM Lee Jones wrote:
>
> > > > > It's not clear how this issue (present 3 years ago) was finally
> > > > > resolved. From the thread, it looks as if the fix might have made its
> > > > > way into ATF, but I'm 87.6% sure ATF is not running on this platform
> > > > >
On 5/9/22 09:23, Chin-Ting Kuo wrote:
Add FWSPICS1 and SPI1CS1 in AST2500 pinctrl group.
On AST2500 EVB, FWSPICS1 can be supported by default.
An extra jumper, J45, should be configured before
enabling SPI1CS1.
Signed-off-by: Chin-Ting Kuo
Reviewed-by: Cédric Le Goater
Thanks,
C.
---
> > > > It's not clear how this issue (present 3 years ago) was finally
> > > > resolved. From the thread, it looks as if the fix might have made its
> > > > way into ATF, but I'm 87.6% sure ATF is not running on this platform
> > > > (yet).
> > >
> > > The rk3399 SoC has a hardware bug where the
Hi Rasmus,
On Tue, May 17, 2022 at 04:27:06PM +0200, Rasmus Villemoes wrote:
> Since the phy_{read,write}_mmd functions are static inlines using
> other static inline functions, they cause code using them to explode.
>
> Defining local wrappers cuts the size of the generated code by 50%:
>
> $
Hi Anderson,
> -Original Message-
> From: Sean Anderson
> Sent: Thursday, May 19, 2022 9:35 PM
> Subject: Re: [PATCH v2 07/11] spi-mem: Add dirmap API from Linux
>
> On 5/9/22 3:23 AM, Chin-Ting Kuo wrote:
> > This adds the dirmap API originally introduced in Linux commit aa167f3
> >
Hi Patrick,
On 5/17/22 4:12 AM, Patrick DELAUNAY wrote:
Hi,
On 5/11/22 18:44, Sean Anderson wrote:
Hi Patrick,
On 5/10/22 3:51 AM, Patrick Delaunay wrote:
Add a minimal support for STM32MP13 RCC, the reset and clock controller
- update of the RCC MISC driver to bind the correct clock and
On 5/9/22 3:23 AM, Chin-Ting Kuo wrote:
This adds the dirmap API originally introduced in Linux commit aa167f3
("spi: spi-mem: Add a new API to support direct mapping"). This also
includes several follow-up patches and fixes.
Changes from Linux include:
* Added Kconfig option
* Changed struct
On 5/15/22 10:42 PM, Weijie Gao wrote:
This patch adds a clock driver for MediaTek MT7621 SoC.
This driver provides clock gate control as well as getting clock frequency
for CPU/SYS/XTAL and some peripherals.
Signed-off-by: Weijie Gao
---
v5 changes:
Remove the use of common.h
Use
On Thursday 19 May 2022 13:03:43 Vladimir Oltean wrote:
> On Thu, May 19, 2022 at 02:49:12PM +0200, Pali Rohár wrote:
> > Commit c677fb1e3196 ("phy: Move PHY_INTERFACE_MODE_NA to the beginning of
> > the enum definition") broke function phy_string_for_interface(). And
> > therefore completely
Hi Tim,
On Wed, May 18, 2022 at 09:15:26AM -0700, Tim Harvey wrote:
> On Wed, May 18, 2022 at 7:41 AM Vladimir Oltean
> wrote:
> >
> > On Wed, May 11, 2022 at 05:20:03PM -0700, Tim Harvey wrote:
> > > Add MV88E61XX DSA support:
> > > - update dt: U-Boot dsa driver requires different
On Thu, May 19, 2022 at 02:49:12PM +0200, Pali Rohár wrote:
> Commit c677fb1e3196 ("phy: Move PHY_INTERFACE_MODE_NA to the beginning of
> the enum definition") broke function phy_string_for_interface(). And
> therefore completely broke support for 2500base-x mode in Armada 3720
> comphy driver.
>
On 18/05/2022 19:15, Neil Armstrong wrote:
On 18/05/2022 17:52, Tom Rini wrote:
On Wed, May 18, 2022 at 10:40:12AM +0200, Neil Armstrong wrote:
Hi,
On 14/10/2021 10:40, Peter Hoyes wrote:
From: Peter Hoyes
If using OF_CONTROL, fdtcontroladdr is set to the fdt used to
configure
U-Boot.
On 5/19/22 13:08, Philip Oberfichtner wrote:
Before this commit device tree selection could rely solely on
differentiating the iMX6 processor variant Q and DL. After adding two new
carrier boards, the DRC02 and the picoITX, the interchangeability of SoMs
makes this approach infeasible.
It is
Hi Mark,
Am 19.05.22 um 13:21 schrieb Mark Kettenis:
From: Josua Mayer
Date: Thu, 19 May 2022 12:31:58 +0300
The Cubox has an unstable phy address - which can appear at either
address 0 (intended) or 4 (unintended).
SoM revision 1.9 has replaced the ar8035 phy with an adin1300, which
will
Commit c677fb1e3196 ("phy: Move PHY_INTERFACE_MODE_NA to the beginning of
the enum definition") broke function phy_string_for_interface(). And
therefore completely broke support for 2500base-x mode in Armada 3720
comphy driver.
Since that commit function phy_string_for_interface() returns
On 19/05/2022 08:08, Philip Oberfichtner wrote:
return 0;
- }
+ /* Determine carrier board at compile time and SoM at runtime */
+ const size_t size = 32;
+ char *car, *som, dt[size];
+
+ car = strchr(CONFIG_DEFAULT_DEVICE_TREE, '-'); /* i.e. -dhcom-drc02
On 5/19/22 13:08, Philip Oberfichtner wrote:
Add a u-boot dtsi for configuring the fec node of the DH DRC02.
nit: FEC (in caps), means Freescale Ethernet Controller or some such.
Reviewed-by: Marek Vasut
On 5/19/22 13:08, Philip Oberfichtner wrote:
Add a u-boot dtsi for configuring the fec node of the DH picoITX.
Reviewed-by: Marek Vasut
On 5/19/22 13:08, Philip Oberfichtner wrote:
Firstly the fec can now use the regulator reg_eth_vio from
imx6qdl-dhcom-som.dtsi instead of defining its own.
Secondly the node is moved to the more generic SoM device tree
file, because it can be used by multiple boards.
Reviewed-by: Marek Vasut
On 5/19/22 13:08, Philip Oberfichtner wrote:
In the dhelectronics iMX6 board file fix the outdated eeprom path by
nit: DH electronics
using a DT label instead.
The label has been newly created for all iMX6QDL DHCOM boards.
Signed-off-by: Philip Oberfichtner
Reviewed-by: Marek Vasut
Hi Fabio
On Thu, May 19, 2022 at 2:14 PM Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> The imx6q arm2 board support has been removed from U-Boot
> as it did not get converted to DM.
>
> Remove the MX6Q_ARM2 related ifdefery in the driver.
>
> Signed-off-by: Fabio Estevam
> ---
>
On 19/05/2022 13.50, Aswath Govindraju wrote:
> Understood, thanks for the explanation. I am good with this patch.
>
> Acked-by: Aswath Govindraju
>
Thanks.
For completeness, to expand on this:
>> it's somewhat fragile to rely on (at least one of) the
>> nodes in question to even have a
From: Fabio Estevam
The imx6q arm2 board support has been removed from U-Boot
as it did not get converted to DM.
Remove the MX6Q_ARM2 related ifdefery in the driver.
Signed-off-by: Fabio Estevam
---
drivers/usb/host/ehci-mx6.c | 5 -
1 file changed, 5 deletions(-)
diff --git
Hi Fabio
On Thu, May 19, 2022 at 2:00 PM Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> There is no reason for disabling I-cache and D-cache
> in SPL.
>
> Remove the unneeded CONFIG_SPL_SYS_ICACHE_OFF and
> CONFIG_SPL_SYS_DCACHE_OFF options.
>
> Signed-off-by: Fabio Estevam
> ---
>
From: Fabio Estevam
There is no reason for disabling I-cache and D-cache
in SPL.
Remove the unneeded CONFIG_SPL_SYS_ICACHE_OFF and
CONFIG_SPL_SYS_DCACHE_OFF options.
Signed-off-by: Fabio Estevam
---
configs/cgtqmx8_defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git
From: Fabio Estevam
There is no reason for disabling I-cache and D-cache
in SPL.
Remove the unneeded CONFIG_SPL_SYS_ICACHE_OFF and
CONFIG_SPL_SYS_DCACHE_OFF options.
Signed-off-by: Fabio Estevam
---
configs/imx8mp_rsb3720a1_4G_defconfig | 2 --
configs/imx8mp_rsb3720a1_6G_defconfig | 2
From: Fabio Estevam
There is no reason for disabling I-cache and D-cache
in SPL.
Remove the unneeded CONFIG_SPL_SYS_ICACHE_OFF and
CONFIG_SPL_SYS_DCACHE_OFF options.
Signed-off-by: Fabio Estevam
---
configs/imx8mm-cl-iot-gate-optee_defconfig | 2 --
configs/imx8mm-cl-iot-gate_defconfig
The Bosch ACC (Air Center Control) Board is based on the i.MX6D.
The device tree is copied from Linux, see [1]. The only difference
compared to the Linux DT is the removal of usbphynop properties. They are
defined in the Linux version of imx6qdl.dtsi, but not in the u-boot
version.
[1] Commit
Hi Rasmus,
On 19/05/22 16:58, Rasmus Villemoes wrote:
> On 19/05/2022 12.41, Aswath Govindraju wrote:
>> Hi Rasmus,
>>
>> On 19/05/22 14:40, Rasmus Villemoes wrote:
>>> Asking if the alias we found actually points at the device tree node
>>> we passed in (in the guise of its offset from blob) can
On 16/05/2022 14:07, Andrew Abbott wrote:
> Binman is now being used to build the final flashable images for
> Rockchip devices, thus enabling it for all Rockchip targets here. But
> it is not yet being used to generate the FIT image (u-boot.itb),
> thus we need to force it to be built.
>
>
On 16/05/2022 14:07, Andrew Abbott wrote:
> This needs to be accessible to binman (via CONFIG_ preprocessor macros)
> so it can build SPI images using the correct offset.
>
> The documentation at 'doc/device-tree-bindings/config.txt' says that
> the 'u-boot,spl-payload-offset' device tree option
On 16/05/2022 14:07, Andrew Abbott wrote:
> This pulls in binman definitions so images can be built for all
> Rockchip platforms.
>
> Signed-off-by: Andrew Abbott
> ---
See Simon's patch [1] for this, which contains these changes and is more
complete. I think the 'imply BINMAN's there achieve
On 16/05/2022 14:07, Andrew Abbott wrote:
> Currently, building for Rockchip targets produces:
>
> - idbloader.img
> - rksd-formatted TPL with SPL appended; or
> - rksd-formatted SPL
> - u-boot.itb
> - U-Boot Proper FIT image
> - u-boot-rockchip.bin
> - idbloader.img + u-boot.itb,
On 16/05/2022 14:07, Andrew Abbott wrote:
> mkimage supports combining multiple input binaries separating them
> with colons (':'). This is used at least for Rockchip platforms to
> encode payload offsets and sizes in the image header. It is required for
> Rockchip SPI boot since for the rkspi
On 16/05/2022 14:07, Andrew Abbott wrote:
> My original goal was to produce SPI images for Rockchip platforms
> (specifically
> for me, ROCKPro64, and in the future ROCK64). Looking into it, it seemed nicer
> to just switch the SD/MMC image generation over to binman as well in the
> process.
>
>
On 27/04/2022 12:22, Johan Jonker wrote:
> [...]
>
> There's a trend to solve everything in python.
> Don't have knowledge about python, but there's a 3rd image format for
> NAND [1]. Could someone advise how to fit the extra XXX padding option
> in the mkimage.py file? (Simon ?)
Binman's
On Wed, 18 May 2022, Peter Geis wrote:
> On Wed, May 18, 2022 at 7:56 AM Lee Jones wrote:
> >
> > Looping int a few relevant/active kernel people/lists for full coverage.
> >
> > On Sun, 01 Dec 2019, Hugh Cole-Baker wrote:
> > > > On 29 Nov 2019, at 01:06, Vasily Khoruzhick wrote:
> > > > On
>From bc1eae1b8883dca98c2874efca1d3e492db20cf3 Mon Sep 17 00:00:00 2001
From: judyw
Date: Tue, 3 May 2022 14:04:40 +0800
Subject: [PATCH] drivers:optee:rpmb: initialize drivers of mmc devices in
UCLASS_BLK for rpmb access
CONFIG_MMC only initializes drivers for devices in UCLASS_MMC,
we
On 19/05/2022 12.41, Aswath Govindraju wrote:
> Hi Rasmus,
>
> On 19/05/22 14:40, Rasmus Villemoes wrote:
>> Asking if the alias we found actually points at the device tree node
>> we passed in (in the guise of its offset from blob) can be done simply
>> by asking if the fdt_path_offset() of the
On Thu, May 19, 2022 at 4:17 AM Lee Jones wrote:
>
> On Wed, 18 May 2022, Peter Geis wrote:
> > On Wed, May 18, 2022 at 7:56 AM Lee Jones wrote:
> > >
> > > Looping int a few relevant/active kernel people/lists for full coverage.
> > >
> > > On Sun, 01 Dec 2019, Hugh Cole-Baker wrote:
> > > > >
Add a u-boot dtsi for configuring the fec node of the DH DRC02.
Signed-off-by: Philip Oberfichtner
---
arch/arm/dts/imx6s-dhcom-drc02-u-boot.dtsi | 10 ++
1 file changed, 10 insertions(+)
create mode 100644 arch/arm/dts/imx6s-dhcom-drc02-u-boot.dtsi
diff --git
Before this commit device tree selection could rely solely on
differentiating the iMX6 processor variant Q and DL. After adding two new
carrier boards, the DRC02 and the picoITX, the interchangeability of SoMs
makes this approach infeasible.
It is now required to specify the carrier board
On 5/19/22 02:35, AKASHI Takahiro wrote:
I thought I had sent out my comment when this patch was submitted first time,
but it seems that it has never reached out to ML.
On Sun, Apr 10, 2022 at 04:05:55PM -0500, kev...@freebsd.org wrote:
From: Kyle Evans
Up until commit 5f59518a7b1ae
Add a u-boot dtsi for configuring the fec node of the DH picoITX.
Signed-off-by: Philip Oberfichtner
---
arch/arm/dts/imx6dl-dhcom-picoitx-u-boot.dtsi | 10 ++
1 file changed, 10 insertions(+)
create mode 100644 arch/arm/dts/imx6dl-dhcom-picoitx-u-boot.dtsi
diff --git
Firstly the fec can now use the regulator reg_eth_vio from
imx6qdl-dhcom-som.dtsi instead of defining its own.
Secondly the node is moved to the more generic SoM device tree
file, because it can be used by multiple boards.
Signed-off-by: Philip Oberfichtner
---
Migrate DH picoITX device trees from Linux commit 42226c989789
(tag v5.18-rc7). No changes have been made, the DTs are exact copies.
Furthermore add the DTB to dh_imx6_defconfig.
Reviewed-by: Marek Vasut
Signed-off-by: Philip Oberfichtner
---
arch/arm/dts/Makefile | 1 +
Use phy address from device tree instead of CONFIG_FEC_MXC_PHYADDR from
board header. This is required, because the DH picoITX and DRC02 boards
require different settings than PDK2. The corresponding 'phy-handle'
device tree properties are already there.
I tested this change on picoITX and DRC02,
Migrate DH DRC02 device trees from Linux commit 42226c989789
(tag v5.18-rc7). No changes have been made, the DTs are exact copies.
Furthermore add the DTB to dh_imx6_defconfig.
Reviewed-by: Marek Vasut
Signed-off-by: Philip Oberfichtner
---
arch/arm/dts/Makefile | 1 +
In the dhelectronics iMX6 board file fix the outdated eeprom path by
using a DT label instead.
The label has been newly created for all iMX6QDL DHCOM boards.
Signed-off-by: Philip Oberfichtner
---
arch/arm/dts/imx6qdl-dhcom-u-boot.dtsi | 11 +++
board/dhelectronics/dh_imx6/dh_imx6.c
This patch series adds support for the DHCOM DRC02 and DH picoITX
baseboards by DH electronics.
The two boards can be equipped with different SoMs. The STM32MP15xx based
versions are already mainlined. This patch adds support for the iMX6QDL
based variants.
Philip Oberfichtner (8):
ARM:
Hi Rasmus,
On 19/05/22 14:40, Rasmus Villemoes wrote:
> Asking if the alias we found actually points at the device tree node
> we passed in (in the guise of its offset from blob) can be done simply
> by asking if the fdt_path_offset() of the alias' path is identical to
> offset.
>
> In fact, the
> From: Josua Mayer
> Date: Thu, 19 May 2022 12:31:58 +0300
>
> The Cubox has an unstable phy address - which can appear at either
> address 0 (intended) or 4 (unintended).
>
> SoM revision 1.9 has replaced the ar8035 phy with an adin1300, which
> will always appear at address 1.
>
> Change
Hold off on this one, I found a mistake in the switch case below.
While fully functional, it does enable both phy nodes for addresses 0
and 4 unconditionally.
Cubox requires both, as do potentially any derivate devices - but the
HummingBoards do not.
Am 19.05.22 um 12:31 schrieb Josua Mayer:
Hi Jerome,
On Tue May 17, 2022 at 1:13 AM AEST, Jerome Forissier wrote:
> I use this kind of configuration on ROCKPi 4B (U-Boot with TF-A BL31 and
> OP-TEE),
> so I could at least run some tests. Please note that I recently sent a patch
> to
> fix the OP-TEE support in make_fit_atf.py [1].
On Wednesday 18 May 2022 11:35:18 Tom Rini wrote:
> On Wed, May 18, 2022 at 05:27:09PM +0200, Pali Rohár wrote:
> > On Wednesday 18 May 2022 11:18:18 Tom Rini wrote:
> > > On Wed, May 18, 2022 at 03:19:19PM +0200, Pali Rohár wrote:
> > > > On Wednesday 18 May 2022 08:19:36 Tom Rini wrote:
> > > >
SoM revision 1.9 has replaced the ar8035 phy address 0 with an adin1300
at address 1. Because early SoMs had a hardware flaw, the ar8035 can
also appear at address 4 - making it a total of 3 phy nodes in the DTB.
To avoid confusing Linux with probe errors, fixup the dtb to only enable
the phy
Since SoMs revision 1.9 the ar8035 phy has been replaced by adin1300.
Enable the driver so that the new SoMs have functional networking.
Signed-off-by: Josua Mayer
---
configs/mx6cuboxi_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/mx6cuboxi_defconfig
From: Nate Drude
Currently, the adin driver fails to compile.
The original patch introducing the adin driver used the function
phy_get_interface_by_name to support the adi,phy-mode-override
property. Unfortunately, a few days before the adin patch
was accepted, another patch removed support for
The Cubox has an unstable phy address - which can appear at either
address 0 (intended) or 4 (unintended).
SoM revision 1.9 has replaced the ar8035 phy with an adin1300, which
will always appear at address 1.
Change the reg property of the phy node to the magic value 0x,
which indicates
The ADIN1300 supports generating certain clocks on its GP_CLK pin, as
well as providing the reference clock on CLK25_REF.
Add support for selecting the clock via device-tree properties.
This patch is based on the Linux implementation for this feature,
which has been added to netdev/net-next.git
As of Revision 1.9 the SolidRun i.MX6 SoMs ship with a new PHY - an
ADIN1300 at address 1. This patchset carries many small parts to
facilitate proper operation of the ethernet port in U-Boot as well as
Linux:
1. Fix a compile error in the recently added phy driver
2. Add support for configuring
It does not matter what is DT node name of atsha device. So find it via
atsha driver and not by DT node name.
Signed-off-by: Pali Rohár
---
board/CZ.NIC/turris_atsha_otp.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/board/CZ.NIC/turris_atsha_otp.c
Asking if the alias we found actually points at the device tree node
we passed in (in the guise of its offset from blob) can be done simply
by asking if the fdt_path_offset() of the alias' path is identical to
offset.
In fact, the current method suffers from the possibility of false
negatives:
Greetings everybody,
The changes to the adin phy device-tree bindings and driver have been
applied to netdev/net-next:
https://patchwork.kernel.org/project/netdevbpf/cover/20220517085143.3749-1-jo...@solid-run.com/
As there have been no further comments, I will send v2 soon including
some
Clean up asm/io.h by
- removing commented code
- removing outdated comments
- removing unused definitions (for mem_isa, mem_pci)
This massively improves the readability of the file.
Suggested by commits:
7ab2e47d27c9 ("arm: Clean up asm/io.h")
909d0399a519 ("ARM: asm/io.h: kill off confusing
Hi,
As described in the subject. We have an x86 image with U-boot as a EFI
Payload.
It crashes the VM in VMware (Player 16) with a x86 triple fault.
I have tried with a clean U-boot build with efi-x86_payload64_defconfig.
I can see in the VM it prints U-boot EFI Payload and then throws the
Hi Marcel,
On 19.05.22 10:03, Marcel Ziswiler wrote:
On Tue, 2022-05-17 at 00:21 +0200, Marcel Ziswiler wrote:
From: Marcel Ziswiler
Move the preloader_console_init() call after spl_early_init() to avoid
board hang in SPL.
While at it remove explicit in-code console/debug UART pinmuxing
On Thursday 19 May 2022 07:01:19 Stefan Roese wrote:
> On 17.05.22 22:45, Pali Rohár wrote:
> > Commit b1a14f8a1c2e ("UBIFS: Change ubifsload to not read beyond the
> > requested size") added optimization to do not read more bytes than it is
> > really needed. But this commit introduced incorrect
Replace gd->fdt_blob access with fdt_getprop() function to the
function ofnode_get_property() to support a live tree.
Signed-off-by: Patrick Delaunay
---
board/engicam/stm32mp1/stm32mp1.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
1 - 100 of 102 matches
Mail list logo
