Macronix NAND Flash devices are available in
different configurations and densities.
MX"35" means SPI NAND
MX35"LF"/"UF" , LF means 3V and UF meands 1.8V
MX35LF"2G" , 2G means 2Gbits
MX35LF2G"E4"/"24"/"14",
E4 means internal ECC and Quad I/O(x4)
24 means 8-bit ecc requirement and Quad I/O(x4)
14
The continuous read operation including: firstly, starting
with the page read command and the 1st page data will be
read into the cache after the read latency tRD. Secondly,
Issuing the Read From Cache commands (03h/0Bh/3Bh/6Bh/BBh/EBh)
to read out the data from cache continuously. After all the
The patch supports setting the "CONT" bit of the configuration
register and adding a continuous read mode flag for identification.
Signed-off-by: Zhengxun
---
drivers/mtd/nand/spi/core.c | 11 +++
include/linux/mtd/spinand.h | 2 ++
2 files changed, 13 insertions(+)
diff --git
Add continuous read state and initialize state to
default false.
Signed-off-by: Zhengxun
---
drivers/mtd/nand/spi/core.c | 8
include/linux/mtd/spinand.h | 2 ++
2 files changed, 10 insertions(+)
diff --git a/drivers/mtd/nand/spi/core.c b/drivers/mtd/nand/spi/core.c
index
This series add support continuous read mode for SPI NAND.
Zhengxun (4):
mtd: spinand: Add support continuous read mode
mtd: spinand: Add continuous read state
mtd: spinand: Add support continuous read operation
mtd: spinand: macronix: Add support for MX35LF2GE4AD
The change in commit c1af358 (imx: mx6ull: fix REFTOP_VBGADJ setting)
is not correct. According to latest i.MX6ULL fuse table,
the REFTOP_TRIM[2:0] fuse is defined as below. So the previous codes
are correct, only need to fix the comments.
Set the REFTOP_VBGADJ field in PMU_MISC0 register based
Hi Stefan,
On Mon, Mar 7, 2022 at 6:39 AM Stefan Roese wrote:
>
> On 3/7/22 12:40, Pali Rohár wrote:
> > Hello!
> >
> > On Sunday 06 March 2022 14:38:57 Tony Dinh wrote:
> >> Hi Pali,
> >>
> >> I have an observation, which is not related to this patch. But about
> >> the kwboot options changes
Hi Pali,
I've tested this patch series and it's all working fine!
Thanks,
Tony
Tested-by: Tony Dinh
On Mon, Mar 7, 2022 at 10:04 AM Pali Rohár wrote:
>
> Commit 9e6d71d2b55f ("tools: kwboot: Allow to use -b without image path as
> the last getopt() option") broke usage of kwboot with
This patch add the support of PWM controller which can be found at aspeed
ast2600 soc. The pwm supoorts up to 16 channels and it's part function
of multi-function device "pwm-tach controller".
Signed-off-by: Billy Tsai
---
drivers/pwm/Kconfig | 8 ++
drivers/pwm/Makefile | 1 +
This series adds driver support for the PWM controller found in
Aspeed's AST2600 BMC SoCs, but isn't compatible with the AST2400
and AST2500.
Billy Tsai (3):
pwm: Add Aspeed ast2600 PWM support
pinctrl: Add the pinctrl setting for PWM.
ARM: dts: ast2600: Add PWM to device tree
This patchs add the signal description array for PWM pinctrl settings.
Signed-off-by: Billy Tsai
---
arch/arm/dts/ast2600.dtsi| 80 +++
drivers/pinctrl/aspeed/pinctrl_ast2600.c | 120 +++
2 files changed, 200 insertions(+)
diff --git
Add the PWM node and enable it for AST2600 EVB
Signed-off-by: Billy Tsai
---
arch/arm/dts/ast2600-evb.dts | 20
arch/arm/dts/ast2600.dtsi| 15 +++
2 files changed, 35 insertions(+)
diff --git a/arch/arm/dts/ast2600-evb.dts b/arch/arm/dts/ast2600-evb.dts
On Sat, Mar 05, 2022 at 10:37:15AM +0100, Heinrich Schuchardt wrote:
>
>
> On 3/5/22 02:03, AKASHI Takahiro wrote:
> > Heinrich,
> >
> > On Sat, Mar 05, 2022 at 12:51:00AM +0100, Heinrich Schuchardt wrote:
> > > The block IO protocol may be installed on any handle. We should make
> > > no
Use the common GSC driver.
This allows us to do some additional cleanup:
- use the GSC driver functions
- move waiting for the EEPROM to the SPL int (it will always be ready
after this)
- move eeprom functions into eeprom file and elimate GSC_I2C_BUS
- eliminate some redundant EEPROM reads
On Fri, Mar 4, 2022 at 5:30 PM Andre Przywara wrote:
> this series is the continuation of last year's effort to support the new
> Armv8-R64 application profile. This led to a significant rework of the
> existing fastmodel (FVP) support, to both upgrade it to newest U-Boot
> standards (OF_CONTROL
Use the common GSC driver.
This allows us to do some additional cleanup:
- rename gsc{.c,.h} to eeprom{.c.h} for clarity
- collapse eeprom_get_dev
- remove unnecessary header files and alphabatize includes
Signed-off-by: Tim Harvey
---
arch/arm/dts/imx8mm-venice-u-boot.dtsi | 4 +
Add a driver for the Gateworks System Controller used on Gateworks boards
which provides a boot watchdog, power control, temperature monitor,
and voltage ADCs.
Signed-off-by: Tim Harvey
---
MAINTAINERS | 6 +
drivers/misc/Kconfig | 8 +
drivers/misc/Makefile | 1 +
DM is not used for the SPL and a generic DT is used in the SPL
which requires no fixups. Remove the call in the SPL and move the function
into the U-Boot code.
Signed-off-by: Tim Harvey
---
board/gateworks/gw_ventana/common.c | 148
convert to DM_I2C for U-Boot while leaving SPL legacy I2C:
- Move I2C config from common to SPL
- Move PMIC config from common to SPL (no need to re-configure pmic)
- add DM_I2C support to eeprom/gsc functions shared by SPL and U-Boot
Signed-off-by: Tim Harvey
---
Move gpio configuration out of common and into u-boot code as it is
not used by the SPL.
Signed-off-by: Tim Harvey
---
board/gateworks/gw_ventana/common.c | 86 -
board/gateworks/gw_ventana/common.h | 2 -
board/gateworks/gw_ventana/gw_ventana.c | 85
Since DM_SERIAL is used for U-Boot we no longer need legacy UART code in
common.c shared by the SPL and U-Boot. Move the legacy UART config to
the non-DM SPL.
Signed-off-by: Tim Harvey
---
board/gateworks/gw_ventana/common.c | 11 ---
board/gateworks/gw_ventana/common.h
This series Adds a driver for the Gateworks System Controller (GSC)
present on boards from Gateworks Corporation.
Patches 1-4 are gw_ventana cleanups to prepare for using the DM_I2C
based driver.
Patch 5 is for the driver itself
Patch 6 moves gw_ventana over to using the GSC driver
Patch 7 moves
dwmci_setup_cfg was clearing all modes except the mode equivalent to
required bus width. Moreover, for buswidth = 1 was set the 4-bit mode.
This sets host caps to all modes from 1-bit up to the required mode.
Signed-off-by: Jan Havran
---
drivers/mmc/dw_mmc.c | 10 ++
1 file changed, 6
On Mon, Feb 28, 2022 at 02:12:50PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> U-Boot uses environment variables for storing device setup data. It
> usually needs to be accessed by a bootloader, kernel and often
> user-space.
>
> This binding allows describing environment data located
On Fri, Feb 18, 2022 at 01:28:43PM +0100, Lukasz Majewski wrote:
> This code has been ported from Linux v5.16.9 arch/arm/boot/dts/am33xx.dtsi
> file to allow correct usage of MMC2 controller in U-Boot.
>
> This IP block is a bit specific as it is connected to L3 interconnect bus,
> whereas
On Fri, Feb 18, 2022 at 01:28:42PM +0100, Lukasz Majewski wrote:
> This change provides similar aliases definitions as now present in
> Linux kernel v5.16.9 for am33xx.dtsi file.
>
> Signed-off-by: Lukasz Majewski
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP
On Fri, Feb 18, 2022 at 01:28:41PM +0100, Lukasz Majewski wrote:
> In the Linux kernel (v5.16) for this SoC there are two separate drivers
> - namely sdhci-omap.c and omap_hsmmc.c which have separate set of
> compatibles.
>
> The U-Boot's drivers/mmc/omap_hsmmc.c driver supports both eMMC and
>
On Thu, Feb 17, 2022 at 05:17:07PM +0100, Philippe Reynes wrote:
> Enable the led support on the refboard bcm96753ref.
>
> Signed-off-by: Philippe Reynes
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Thu, Feb 17, 2022 at 05:17:06PM +0100, Philippe Reynes wrote:
> Enable the led in the device tree of the refboard bcm96753ref.
> It also defines two leds (led_red ad led_green).
>
> Signed-off-by: Philippe Reynes
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP
On Thu, Feb 17, 2022 at 05:17:05PM +0100, Philippe Reynes wrote:
> Add a node leds to support the LED IP in the
> device tree of the bcm6753.
>
> Signed-off-by: Philippe Reynes
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Wed, Feb 16, 2022 at 10:26:58AM +1030, Andrew Jeffery wrote:
> Build in the driver for the Aspeed GPIO controller and turn on the
> `gpio` shell command.
>
> Signed-off-by: Andrew Jeffery
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Thu, Feb 17, 2022 at 05:17:04PM +0100, Philippe Reynes wrote:
> Add the support of the LED IP for bcm6357. This
> LED IP supports blinking, fading and pulsating,
> but for the moment, only blinking is supported.
>
> Signed-off-by: Philippe Reynes
Applied to u-boot/next, thanks!
--
Tom
On Wed, Feb 16, 2022 at 10:26:57AM +1030, Andrew Jeffery wrote:
> Populate gpio_count in the gpio subsystem for the AST2500.
>
> Signed-off-by: Andrew Jeffery
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Wed, Feb 16, 2022 at 10:26:56AM +1030, Andrew Jeffery wrote:
> The Aspeed GPIO driver supports the GPIO controllers found in the
> AST2400, AST2500 and AST2600 BMC SoCs. The implementation is a cut-down
> copy of the upstream Linux kernel driver, adapted for u-boot.
>
> Signed-off-by: Andrew
On Fri, Feb 11, 2022 at 07:18:38PM +0100, Philippe Reynes wrote:
> This add the initial support of the broadcom reference
> board bcm96753ref with a bcm6753 SoC.
>
> This board has 1 GB of RAM, 256 MB of flash (nand),
> 2 USB port, 1 UART, and 4 ethernet ports.
>
> Signed-off-by: Philippe
On Fri, Feb 11, 2022 at 07:18:37PM +0100, Philippe Reynes wrote:
> This IP is also used on some arm SoC, so we allow to
> use it on arm bcm6753 too.
>
> Signed-off-by: Philippe Reynes
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Fri, Feb 11, 2022 at 07:18:36PM +0100, Philippe Reynes wrote:
> This adds the nand support for chipset bcm6753.
>
> Signed-off-by: Philippe Reynes
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Fri, Feb 11, 2022 at 07:18:35PM +0100, Philippe Reynes wrote:
> This IP is also used on some arm SoC, so we allow to
> use it on arm bcm6753 too.
>
> Signed-off-by: Philippe Reynes
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Fri, Feb 11, 2022 at 07:18:34PM +0100, Philippe Reynes wrote:
> This add the initial support of the broadcom bcm6753 SoC family.
>
> Signed-off-by: Philippe Reynes
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
Hi Patrice
On 07.03.22 18:38, Patrice CHOTARD wrote:
> Hi Johannes
>
> +Alexandre who is STM32 kernel maintainer.
Okay, no problem. :)
> On 3/7/22 18:24, Johannes (krjdev) Krottmayer wrote:
>> Hi Patrice
>>
>> Thanks for the answer.
>>
>> On 07.03.22 17:09, Patrice CHOTARD wrote:
But
On Mon, Mar 7, 2022 at 12:51 AM Michael Walle wrote:
>
> > On Mon, Feb 28, 2022 at 12:01 PM Tim Harvey wrote:
> >>
> >> Greetings,
> >>
> >> I'm wondering if it is proper in U-Boot for phy_connect_dev() to
> >> always call phy_reset() which generates a soft reset via BMCR_RESET.
>
> FWIW, a PHY
Remap PCI I/O space to the bus address 0x0 in the Armada 37xx device-tree
in order to support legacy I/O port based cards which have hardcoded I/O
ports in low address space.
Some legacy PCI I/O based cards do not support 32-bit I/O addressing.
Signed-off-by: Pali Rohár
---
Same change was
Commit 9e6d71d2b55f ("tools: kwboot: Allow to use -b without image path as
the last getopt() option") broke usage of kwboot with following arguments:
kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-spl.kwb
Fix parsing of option -b with optional argument again.
Fixes: 9e6d71d2b55f ("tools: kwboot:
Call kwboot_open_tty() which baudrate value which was specified at the
command line by option -B. This function returns error if baudrate is not
supported by selected tty device.
Initial baudrate for image transfer is always 115200, so call
kwboot_tty_change_baudrate() with value 115200
Custom baudrate different than 115200 may be specified only when kwboot is
not going to send boot/debug message pattern or when it is going to send
boot message pattern with image file (in which case baudrate change happens
after sending kwbimage header). BootROM detects boot/debug message pattern
Since commit e2e95e5e2542 ("spi: Update speed/mode on change")
when calling "sf probe" or "env save" on SPI flash,
spi_set_speed_mode() is called twice.
spi_get_bus_and_cs()
|--> spi_claim_bus()
| |--> spi_set_speed_mode(speed and mode from DT)
...
|-->
On Monday 07 March 2022 17:45:53 Marek Behún wrote:
> On Mon, 7 Mar 2022 15:39:33 +0100
> Stefan Roese wrote:
>
> > On 3/7/22 12:40, Pali Rohár wrote:
> > > Hello!
> > >
> > > On Sunday 06 March 2022 14:38:57 Tony Dinh wrote:
> > >> Hi Pali,
> > >>
> > >> I have an observation, which is not
Hi Johannes
+Alexandre who is STM32 kernel maintainer.
On 3/7/22 18:24, Johannes (krjdev) Krottmayer wrote:
> Hi Patrice
>
> Thanks for the answer.
>
> On 07.03.22 17:09, Patrice CHOTARD wrote:
>>> But there some issues on the website:
>>> - According the website, the board has 256Mbit
Hi Patrice
Thanks for the answer.
On 07.03.22 17:09, Patrice CHOTARD wrote:
>> But there some issues on the website:
>> - According the website, the board has 256Mbit external SDRAM
>>
>> That's not true. There is a 512MBit SDRAM from ISSI mounted.
It's a 256Mbit SDRAM mounted on the board.
On Mon, 7 Mar 2022 15:39:33 +0100
Stefan Roese wrote:
> On 3/7/22 12:40, Pali Rohár wrote:
> > Hello!
> >
> > On Sunday 06 March 2022 14:38:57 Tony Dinh wrote:
> >> Hi Pali,
> >>
> >> I have an observation, which is not related to this patch. But about
> >> the kwboot options changes in
The new define has been added in Vivado 2021.2.
Signed-off-by: Adrian Fiergolski
---
tools/zynqmp_pm_cfg_obj_convert.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/zynqmp_pm_cfg_obj_convert.py
b/tools/zynqmp_pm_cfg_obj_convert.py
index 0a44710e1e..239991a526 100755
---
Hi Michal
On 3/7/22 16:48, Michal Simek wrote:
> There is really no value to check empty spaces. That's why use
> ut_assert_nextlinen() instead of ut_assert_nextline().
> This change ensures that PINMUX_SIZE can be increased without changing
> tests.
>
> Signed-off-by: Michal Simek
> ---
>
>
Hi Johannes
On 3/2/22 16:26, Johannes (krjdev) Krottmayer wrote:
> Hi,
>
> I want add support for STM32H747I-DISCO from STMicroelectronics,
> for the purpose of education. Want to use U-Boot as boot-loader
> for my projects.
>
> Here you the official website from the board:
>
There is really no value to check empty spaces. That's why use
ut_assert_nextlinen() instead of ut_assert_nextline().
This change ensures that PINMUX_SIZE can be increased without changing
tests.
Signed-off-by: Michal Simek
---
Hello Gaurav,
> -Original Message-
> From: U-Boot On Behalf Of Gaurav Jain
> Sent: Monday, March 7, 2022 3:10 PM
> To: ZHIZHIKIN Andrey ; Stefano Babic
> ; u-boot@lists.denx.de; Marek Vasut
> Cc: Fabio Estevam ; Peng Fan ; Simon
> Glass
> ; Priyanka Jain ; Ye Li
> ;
> Horia Geanta ;
On Mon, Mar 07, 2022 at 12:03:42PM +, Gaurav Jain wrote:
>
>
> > -Original Message-
> > From: Michael Walle
> > Sent: Monday, March 7, 2022 5:12 PM
> > To: Gaurav Jain
> > Cc: sba...@denx.de; Varun Sethi ; Adrian Alonso
> > ; Alison Wang ; Andy Tang
> > ; feste...@gmail.com; Franck
On 3/7/22 12:40, Pali Rohár wrote:
Hello!
On Sunday 06 March 2022 14:38:57 Tony Dinh wrote:
Hi Pali,
I have an observation, which is not related to this patch. But about
the kwboot options changes in general, I hope it is OK to mention it
here.
Before the changes you've made to solve the
On 3/6/22 14:05, Marek Behún wrote:
On Sun, 6 Mar 2022 13:38:30 +0100
Pali Rohár wrote:
Custom baudrate different than 115200 may be specified only when kwboot is
not going to send boot/debug message pattern or when it is going to send
boot message pattern with image file (in which case
On Fri, Mar 04, 2022 at 08:42:57AM -0700, Simon Glass wrote:
> LTO (Link-Time Optimisation) is an very useful feature which can
> significantly reduce the size of U-Boot binaries. So far it has been
> made available for selected ARM boards and sandbox.
>
> However, incremental builds are much
Hello Andrey
> -Original Message-
> From: ZHIZHIKIN Andrey
> Sent: Monday, March 7, 2022 1:08 AM
> To: Stefano Babic ; Gaurav Jain ; u-
> b...@lists.denx.de; Marek Vasut
> Cc: Fabio Estevam ; Peng Fan ;
> Simon Glass ; Priyanka Jain ; Ye
> Li ; Horia Geanta ; Ji Luo
> ; Franck Lenormand
On 14:50-20220307, Vignesh Raghavendra wrote:
> Patch 1 switches AM64 to use GTC as system timer at A53 SPL/U-boot
> stage as done in other TI K3 platforms
Minor nuance clarification:
We don't use System timer (aka GTC) directly. System timer[1] feeds the
armv8 per cpu timer[2] - and the p
> -Original Message-
> From: Michael Walle
> Sent: Monday, March 7, 2022 5:12 PM
> To: Gaurav Jain
> Cc: sba...@denx.de; Varun Sethi ; Adrian Alonso
> ; Alison Wang ; Andy Tang
> ; feste...@gmail.com; Franck Lenormand
> ; Horia Geanta ; Ji Luo
> ; ma...@denx.de; Meenakshi Aggarwal
> ;
Am 2022-03-07 12:33, schrieb Gaurav Jain:
-Original Message-
From: Michael Walle
Sent: Monday, March 7, 2022 4:39 PM
To: Gaurav Jain
Cc: sba...@denx.de; Varun Sethi ; Adrian Alonso
; Alison Wang ; Andy Tang
; feste...@gmail.com; Franck Lenormand
; Horia Geanta ; Ji
Luo
;
Hello!
On Sunday 06 March 2022 14:38:57 Tony Dinh wrote:
> Hi Pali,
>
> I have an observation, which is not related to this patch. But about
> the kwboot options changes in general, I hope it is OK to mention it
> here.
>
> Before the changes you've made to solve the problem with the -b
>
Am Mo., 7. März 2022 um 12:18 Uhr schrieb Christian Gmeiner
:
>
> Am Mo., 28. Feb. 2022 um 05:56 Uhr schrieb Hari Nagalla :
> >
> > On AM64x devices, it is possible to route Main ESM0 error events to MCU
> > ESM. MCU ESM high error output can trigger the reset logic to reset the
> > device. So,
> -Original Message-
> From: Michael Walle
> Sent: Monday, March 7, 2022 4:39 PM
> To: Gaurav Jain
> Cc: sba...@denx.de; Varun Sethi ; Adrian Alonso
> ; Alison Wang ; Andy Tang
> ; feste...@gmail.com; Franck Lenormand
> ; Horia Geanta ; Ji Luo
> ; ma...@denx.de; Meenakshi Aggarwal
> ;
Am Mo., 28. Feb. 2022 um 05:56 Uhr schrieb Hari Nagalla :
>
> On AM64x devices, it is possible to route Main ESM0 error events to MCU
> ESM. MCU ESM high error output can trigger the reset logic to reset the
> device. So, for these devices we expect two ESM device nodes in the
> device tree, one
Le Mon, 7 Mar 2022 11:06:17 +,
a écrit :
> > diff --git a/configs/sama5d2_icp_mmc_defconfig
> > b/configs/sama5d2_icp_mmc_defconfig
> > index 7761a57e0c..2eb2e92110 100644
> > --- a/configs/sama5d2_icp_mmc_defconfig
> > +++ b/configs/sama5d2_icp_mmc_defconfig
> > @@ -83,5 +83,6 @@
Le Mon, 7 Mar 2022 10:57:02 +,
a écrit :
> On 04.03.2022 13:05, Clément Léger wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> > content is safe
> >
> > Add a driver for the timer counter block that can be found on sama5d2.
> > This driver will be
Am 2022-03-07 11:56, schrieb Gaurav Jain:
-Original Message-
From: Michael Walle
Sent: Monday, March 7, 2022 3:28 PM
To: sba...@denx.de
Cc: Varun Sethi ; Adrian Alonso
;
Alison Wang ; Andy Tang ;
feste...@gmail.com; Franck Lenormand ;
Gaurav Jain ; Horia Geanta
; Ji
Luo ;
> -Original Message-
> From: Michael Walle
> Sent: Monday, March 7, 2022 3:28 PM
> To: sba...@denx.de
> Cc: Varun Sethi ; Adrian Alonso ;
> Alison Wang ; Andy Tang ;
> feste...@gmail.com; Franck Lenormand ;
> Gaurav Jain ; Horia Geanta ; Ji
> Luo ; ma...@denx.de; Meenakshi Aggarwal
> ;
On 7.03.2022 11:24, Alexander Dahl wrote:
Hei hei,
just want to give a little more background here from embedded non
openwrt point of view. See below.
Am Mon, Feb 28, 2022 at 12:32:11PM +0100 schrieb Rafał Miłecki:
On 25.02.2022 17:42, Rob Herring wrote:
On Thu, Feb 17, 2022 at 02:02:35PM
Hei hei,
just want to give a little more background here from embedded non
openwrt point of view. See below.
Am Mon, Feb 28, 2022 at 12:32:11PM +0100 schrieb Rafał Miłecki:
> On 25.02.2022 17:42, Rob Herring wrote:
> > On Thu, Feb 17, 2022 at 02:02:35PM +0100, Rafał Miłecki wrote:
> > > From:
Hello Sean,
Thanks for the feedback.
Sorry I missed your post end Feb.
On Fri, 25 Feb 2022 at 07:33, Sean Anderson wrote:
>
> Hi Etienne,
>
>
> On 2/21/22 3:22 AM, Etienne Carriere wrote:
> > Implements SCMI APIs to retrieve the number exposed SCMI clocks using
> > SCMI_PROTOCOL_ATTRIBUTES
> On 03.03.22 14:41, Gaurav Jain wrote:
>> As we have not received any response from imx6dl_mamoj board maintainer.
>> I propose the below solution
>>
>> --- a/arch/arm/mach-imx/Kconfig
>> +++ b/arch/arm/mach-imx/Kconfig
>> @@ -49,8 +49,8 @@ config USE_IMXIMG_PLUGIN config IMX_HAB
>> -
MCU Timer0 runs at 250MHz, and the clock-frequency defined in DT appears
incorrect.
Without this delays in R5 SPL are 10x off.
Signed-off-by: Vignesh Raghavendra
---
arch/arm/dts/k3-j721s2-common-proc-board-u-boot.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Timer0 runs at 200MHz,and the clock-frequency defined in DT appears
is incorrect.
Signed-off-by: Vignesh Raghavendra
---
arch/arm/dts/k3-am642-evm-u-boot.dtsi | 2 +-
arch/arm/dts/k3-am642-sk-u-boot.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Patch 1 switches AM64 to use GTC as system timer at A53 SPL/U-boot
stage as done in other TI K3 platforms
Patch 2 corrects DM timer freq to be 200MHz (used at R5 SPL stage)
Vignesh Raghavendra (2):
configs: am64x_evm_a53_defconfig: Switch to GTC as tick timer
ARM: dts: k3-am642: Fix correct
GTC is to be used as tick timer for A53 SPL/U-Boot, but currently
AM64 ends up using DM timer as driver is enabled in the config,
drop OMAP DM Timer related configs so that GTC is used by default.
Signed-off-by: Vignesh Raghavendra
---
configs/am64x_evm_a53_defconfig | 3 ---
1 file changed, 3
>On Wed, 19 Jan 2022 at 04:45, Heinrich Schuchardt wrote:
>>
>> On 1/19/22 02:43, Simon Glass wrote:
>> > Add a bootmeth driver which handles EFI boot, using EFI_LOADER.
>> >
>> > In effect, this provides the same functionality as the 'bootefi' command
>> > and shares the same code. But the
> On Mon, Feb 28, 2022 at 12:01 PM Tim Harvey wrote:
>>
>> Greetings,
>>
>> I'm wondering if it is proper in U-Boot for phy_connect_dev() to
>> always call phy_reset() which generates a soft reset via BMCR_RESET.
FWIW, a PHY might also get a hardware reset prior to probing in
eth_phy_pre_probe()
st 23. 2. 2022 v 16:17 odesílatel Michal Simek napsal:
>
> Hi,
>
> kv-g boards have been moved to new model where u-boot configures a lot of
> things at run time which requires updates in DTs especially in connection
> to enabling clocks for these platforms.
> There are also small adjustment to
út 1. 3. 2022 v 9:13 odesílatel Michal Simek napsal:
>
> Microblaze can also have reserved space in DT which u-boot has to avoid to
> placing self to that location. The same change was done in Zynqmp by commit
> ce39ee28ec31 ("zynqmp: Do not place u-boot to reserved memory location").
>
> This
út 1. 3. 2022 v 9:11 odesílatel Michal Simek napsal:
>
> Remove private xpm_configobject[] and use zynqmp_pmufw_node() which
> provides the same functionality.
> Also add debug messages for easier debugging.
>
> Fixes: e0283cbdfd49 ("power: zynqmp: Add power domain driver for ZynqMP")
>
st 23. 2. 2022 v 16:21 odesílatel Michal Simek napsal:
>
> From: T Karthik Reddy
>
> slg7xl45106 is i2c based 8-bit gpo expander, gpo pins are set and get by
> writing and reading corresponding gpo bit value into its data register.
>
> Signed-off-by: T Karthik Reddy
> Signed-off-by: Michal
85 matches
Mail list logo
