<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/arch/arm, branch v2023.04</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/arch/arm?h=v2023.04</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/arch/arm?h=v2023.04'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2023-04-03T18:54:16Z</updated>
<entry>
<title>arm: dts: k3-j721e-sk-u-boot: fix boot on j721e SK</title>
<updated>2023-04-03T18:54:16Z</updated>
<author>
<name>Sinthu Raja</name>
<email>sinthu.raja@ti.com</email>
</author>
<published>2023-04-03T17:03:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1f77f9176efeec2936763d61b6552c5c62860775'/>
<id>urn:sha1:1f77f9176efeec2936763d61b6552c5c62860775</id>
<content type='text'>
J721e SK has been broken since at least March 2022.

The main-navss and mcu-navss nodes were renamed and this caused the
A72 SPL to fail early in the boot even before the serial port was
enabled. Fix this.

A later patch series between v2022.07 and v2022.10 additionally broke
boot on this board by introducing hbmc nodes which are not present on
this board. The right fix is to disable these by default in the SOC
dtsi file, but for now we can also disable them in the u-boot dtsi.

With both these fixed, we can now boot the j721e SK board fully from
mainline u-boot.

Fixes: 58d61fb5a77ef ("arm: dts: k3-j721e-sk: Add initial A72 specific dts support")
Fixes: 297daac43afb9 ("arm: dts: k3-j721e-mcu-wakeup: Add HyperBus Controller node")
Reported-by: Anand Gadiyar &lt;gadiyar@ti.com&gt;
Signed-off-by: Sinthu Raja &lt;sinthu.raja@ti.com&gt;
[gadiyar@ti.com: update commit description]
Signed-off-by: Anand Gadiyar &lt;gadiyar@ti.com&gt;
Cc: Bryan Brattlof &lt;bb@ti.com&gt;
</content>
</entry>
<entry>
<title>pico-imx6: Pass the mmc alias to fix boot regression</title>
<updated>2023-04-03T14:14:34Z</updated>
<author>
<name>Fabio Estevam</name>
<email>festevam@denx.de</email>
</author>
<published>2023-02-15T18:24:44Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8b6de0545f2a33a8a28babef6cb91eb2bf7cccb6'/>
<id>urn:sha1:8b6de0545f2a33a8a28babef6cb91eb2bf7cccb6</id>
<content type='text'>
Originally, the mmc aliases node was present in imx6qdl-pico.dtsi.

After the sync with Linux in commit d0399a46e7cd ("imx6dl/imx6qdl:
synchronise device trees with linux"), the aliases node is gone as
the upstream version does not have it.

This causes a boot regression in which the eMMC card cannot be found anymore.

Fix it by passing the alias node in the u-boot.dtsi file to
restore the original behaviour where the eMMC (esdhc3) was
mapped to mmc0.

Fixes: d0399a46e7cd ("imx6dl/imx6qdl: synchronise device trees with linux")
Signed-off-by: Fabio Estevam &lt;festevam@denx.de&gt;
</content>
</entry>
<entry>
<title>imx6sx-udoo-neo-basic: Introduce the u-boot.dtsi</title>
<updated>2023-03-28T14:58:16Z</updated>
<author>
<name>Fabio Estevam</name>
<email>festevam@denx.de</email>
</author>
<published>2023-03-22T19:59:31Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=565681e596381b5b6db59cf06931e698f2d829e5'/>
<id>urn:sha1:565681e596381b5b6db59cf06931e698f2d829e5</id>
<content type='text'>
After the conversion to DM_SERIAL in commit 01f372d8d62b ("udoo_neo:
Select DM_SERIAL and drop iomux board level init") the SPL log is gone
and the U-Boot proper log becomes incomplete:

Core:  80 devices, 18 uclasses, devicetree: separate
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
In:    serial@2020000
Out:   serial@2020000
Err:   serial@2020000
Net:   eth0: ethernet@2188000
Hit any key to stop autoboot:  0

Introduce the u-boot.dtsi file that passes the u-boot,dm-pre-reloc
properties to the relevant nodes so that UART can be used early in SPL.

With this change, the complete SPL and U-Boot messages are seen again.

Signed-off-by: Fabio Estevam &lt;festevam@denx.de&gt;
</content>
</entry>
<entry>
<title>rockchip: Use BOOTSTD_DEFAULTS if not DISTRO_DEFAULTS</title>
<updated>2023-03-27T15:16:04Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2023-03-24T20:58:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3be95cc292a149d1df40edd81afe5a72868c97f5'/>
<id>urn:sha1:3be95cc292a149d1df40edd81afe5a72868c97f5</id>
<content type='text'>
When we do not enable DISTRO_DEFAULTS (generally, to get distro_bootcmd)
we instea do want to imply BOOTSTD_DEFAULTS so that when using bootstd
the general distro boot functionality will still work.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>rockchip: Disable DISTRO_DEFAULTS for rk3399 boards</title>
<updated>2023-03-27T15:16:04Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2023-03-24T20:58:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2b9cc7845cf96955db363519faab9a78e166c453'/>
<id>urn:sha1:2b9cc7845cf96955db363519faab9a78e166c453</id>
<content type='text'>
These board have moved to standard boot but the old 'distro_bootcmd'
command is still active. Disable DISTRO_DEFAULTS to fix this.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Tested-by: Vagrant Cascadian &lt;vagrant@debian.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'rpi-2023.04' of https://source.denx.de/u-boot/custodians/u-boot-raspberrypi</title>
<updated>2023-03-24T21:00:41Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2023-03-24T21:00:41Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=78f67f11a9920ef988cbff5341616695c3e87ebd'/>
<id>urn:sha1:78f67f11a9920ef988cbff5341616695c3e87ebd</id>
<content type='text'>
- Fixes for booting newer revs of the SoC in the Raspberry Pi 4
- Propagate some firmware DT properties to the loaded DT
- Update the Zero2W upstream DT name
</content>
</entry>
<entry>
<title>mmc: bcm2835-host: let firmware manage the clock divisor</title>
<updated>2023-03-24T14:43:20Z</updated>
<author>
<name>Vincent Fazio</name>
<email>vfazio@xes-inc.com</email>
</author>
<published>2021-09-14T18:19:19Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=85bdd28d2bb0827f311913e00e4e338f8e4e6565'/>
<id>urn:sha1:85bdd28d2bb0827f311913e00e4e338f8e4e6565</id>
<content type='text'>
Newer firmware can manage the SDCDIV clock divisor register, allowing
the divisor to scale with the core as necessary.

Leverage this ability if the firmware supports it.

Adapted from the following raspberrypi Linux kernel commit:

  bcm2835-sdhost: Firmware manages the clock divisor
  https://github.com/raspberrypi/linux/commit/08532d242d7702ae0add95096aa49c5e96e066e2

Signed-off-by: Vincent Fazio &lt;vfazio@xes-inc.com&gt;
Signed-off-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;
</content>
</entry>
<entry>
<title>arm: rpi: fallback to max clock rate for MMC clock</title>
<updated>2023-03-24T14:43:20Z</updated>
<author>
<name>Vincent Fazio</name>
<email>vfazio@xes-inc.com</email>
</author>
<published>2021-09-14T18:19:18Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0a36afa82356b89ffc66ed7557d115186c5bd7f1'/>
<id>urn:sha1:0a36afa82356b89ffc66ed7557d115186c5bd7f1</id>
<content type='text'>
In rpi-firmware 25e2b597ebfb2495eab4816a276758dcc6ea21f1,
the GET_CLOCK_RATE mailbox property was changed to return the last
value set by SET_CLOCK_RATE.

https://github.com/raspberrypi/firmware/issues/1619#issuecomment-917025502

Due to this change in firmware behavior, bcm2835_get_mmc_clock now
returns a clock rate of zero since we do not issue SET_CLOCK_RATE.
This results in degraded MMC performance.

SET_CLOCK_RATE fixes the clock to a specific value and disables scaling
so is not an ideal solution.

Instead, fallback to GET_MAX_CLOCK_RATE in bcm2835_get_mmc_clock if
GET_CLOCK_RATE returns zero.

Signed-off-by: Vincent Fazio &lt;vfazio@xes-inc.com&gt;
Signed-off-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;
</content>
</entry>
<entry>
<title>arm: mach-k3: am62: move scratch board area to HSM RAM</title>
<updated>2023-03-22T16:51:09Z</updated>
<author>
<name>Kamlesh Gurudasani</name>
<email>kamlesh@ti.com</email>
</author>
<published>2023-03-02T14:10:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=d3882531c34d92e619f3aa30c6aa439c8ea732a7'/>
<id>urn:sha1:d3882531c34d92e619f3aa30c6aa439c8ea732a7</id>
<content type='text'>
On high security devices, ROM enables firewalls to protect the OCSRAM
region access during bootup. Only after TIFS has started (and had
time to disable the OCSRAM firewall region) will we have write access to
the region.

So, move scratch board area to HSM RAM.

Signed-off-by: Kamlesh Gurudasani &lt;kamlesh@ti.com&gt;
</content>
</entry>
<entry>
<title>console: Use flush() before panic and reset</title>
<updated>2023-03-22T16:51:08Z</updated>
<author>
<name>Tony Dinh</name>
<email>mibodhi@gmail.com</email>
</author>
<published>2023-03-15T00:24:26Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c5f4cdb8eb60cbfc71b356204245a046c74a30c1'/>
<id>urn:sha1:c5f4cdb8eb60cbfc71b356204245a046c74a30c1</id>
<content type='text'>
To make sure the panic and the reset messages will go out, console flush() should be used.
Sleep periods do not work in early u-boot phase when timer driver is not initialized yet.

Reference: https://lists.denx.de/pipermail/u-boot/2023-March/512233.html

Signed-off-by: Tony Dinh &lt;mibodhi@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
</feed>
