<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/drivers/ram, branch v2025.10-rc2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/drivers/ram?h=v2025.10-rc2</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/drivers/ram?h=v2025.10-rc2'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2025-06-14T15:10:48Z</updated>
<entry>
<title>Merge patch series "Hex value prefix case cleanup"</title>
<updated>2025-06-14T15:10:48Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2025-06-14T15:10:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=03817a2a8046ea89dac2be72ce0c16a9faa5570b'/>
<id>urn:sha1:03817a2a8046ea89dac2be72ce0c16a9faa5570b</id>
<content type='text'>
E Shattow &lt;e@freeshell.de&gt; says:

Make consistent use of lowercase hexadecimal prefix '0x' throughout U-Boot.

There are a few remaining uses of uppercase 'X' to denote hexadecimal prefix
or placeholder in documentation and error messages.

External devicetree-rebasing dts/upstream and the generated code of
xilinx/zynq are ignored for the series.

Link: https://lore.kernel.org/r/20250606224558.1117422-1-e@freeshell.de
</content>
</entry>
<entry>
<title>drivers: use lowercase hex prefix style</title>
<updated>2025-06-14T15:09:39Z</updated>
<author>
<name>E Shattow</name>
<email>e@freeshell.de</email>
</author>
<published>2025-06-06T22:44:58Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=449a5566522f07b4c8d58f3a6bdc36a74400e672'/>
<id>urn:sha1:449a5566522f07b4c8d58f3a6bdc36a74400e672</id>
<content type='text'>
Use consistent lowercase hex prefix style in drivers/*

Does not change hex prefix case in allcaps uppercase style error messages

Signed-off-by: E Shattow &lt;e@freeshell.de&gt;
</content>
</entry>
<entry>
<title>ram: Move Kconfig options into their own menu entry</title>
<updated>2025-06-12T22:14:33Z</updated>
<author>
<name>Yao Zi</name>
<email>ziyao@disroot.org</email>
</author>
<published>2025-06-02T10:15:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=548d997229b7929bd7f0782415952d5a85eb7e64'/>
<id>urn:sha1:548d997229b7929bd7f0782415952d5a85eb7e64</id>
<content type='text'>
RAM drivers using Device Model currently lack of their own Kconfig menu
entry, which makes Kconfig put all options of the class in the top-level
menu of device drivers. These options are also incorrectly grouped with
pinctrl options in the generated .config, which is hard to read. Let's
create a menu entry for these drivers.

Fixes: 6c51df6859f ("dm: Add support for RAM drivers")
Signed-off-by: Yao Zi &lt;ziyao@disroot.org&gt;
Reviewed-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>ram: stm32mp1: Add STM32MP13xx support</title>
<updated>2025-06-11T07:42:56Z</updated>
<author>
<name>Marek Vasut</name>
<email>marek.vasut@mailbox.org</email>
</author>
<published>2025-05-12T17:09:05Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=447d1bd05acbfb155abe66514d71629f11fb3927'/>
<id>urn:sha1:447d1bd05acbfb155abe66514d71629f11fb3927</id>
<content type='text'>
Add support for configuring DRAM controller on STM32MP13xx SoC.
The DRAM controller is basically identical to the DWC controller
on STM32MP15xx SoC, except the bus width is reduced from 32bit to
16bit and a few registers and bits are therefore not present.

Handle the difference by factoring these parts out. Use IS_ENABLE()
as much as possible to assure code which is not enabled on builds
for a single SoC gets compiled out. Handle the different offset of
RCC_DDRITFCR register and missing DDRC2 clock the same way.

Signed-off-by: Marek Vasut &lt;marek.vasut@mailbox.org&gt;
</content>
</entry>
<entry>
<title>ram: rockchip: Fix dependency of RAM_ROCKCHIP_DEBUG</title>
<updated>2025-06-06T09:12:20Z</updated>
<author>
<name>Lukasz Czechowski</name>
<email>lukasz.czechowski@thaumatec.com</email>
</author>
<published>2025-05-20T11:36:41Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6773a46f1131fe95bcddb7472635e07a5fd249f8'/>
<id>urn:sha1:6773a46f1131fe95bcddb7472635e07a5fd249f8</id>
<content type='text'>
The RAM_ROCKCHIP_DEBUG can be used only if DEBUG_UART is
available.
The next commit introduces changes in definition of debug
uart functions, so that DEBUG_UART is required to be defined
in order to initialize uart and use print functions.

Signed-off-by: Lukasz Czechowski &lt;lukasz.czechowski@thaumatec.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
Reviewed-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
</content>
</entry>
<entry>
<title>ram: thead: Add initial DDR controller support for TH1520</title>
<updated>2025-05-21T08:49:52Z</updated>
<author>
<name>Yao Zi</name>
<email>ziyao@disroot.org</email>
</author>
<published>2025-05-13T09:04:57Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=05240d541a407fbb62eec43f40a2b831bb1c1fe0'/>
<id>urn:sha1:05240d541a407fbb62eec43f40a2b831bb1c1fe0</id>
<content type='text'>
This patch cleans the vendor code of DDR initialization up, converts the
driver to fit in DM framework and use a firmware[1] packaged by binman to
ship PHY configuration.

Currently the driver is only capable of initializing the controller to
work with dual-rank 3733MHz LPDDR4, which is shipped by 16GiB variants
of LicheePi 4A boards and I could test with. Support for other
configurations could be easily added later.

Link: https://github.com/ziyao233/th1520-firmware # [1]
Signed-off-by: Yao Zi &lt;ziyao@disroot.org&gt;
Reviewed-by: Leo Yu-Chi Liang &lt;ycliang@andestech.com&gt;
</content>
</entry>
<entry>
<title>ram: rockchip: Add rk3576 ddr driver support</title>
<updated>2025-04-23T14:12:05Z</updated>
<author>
<name>Heiko Stuebner</name>
<email>heiko@sntech.de</email>
</author>
<published>2025-04-15T21:51:20Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c0d9ac0b00bb5792ce7e4772115b655670185097'/>
<id>urn:sha1:c0d9ac0b00bb5792ce7e4772115b655670185097</id>
<content type='text'>
Add ddr driver for rk3576 to get the ram capacity.

Signed-off-by: Heiko Stuebner &lt;heiko@sntech.de&gt;
Reviewed-by: Jonas Karlman &lt;jonas@kwiboo.se&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>ram: rockchip: Add basic support for RK3528</title>
<updated>2025-04-23T14:12:04Z</updated>
<author>
<name>Jonas Karlman</name>
<email>jonas@kwiboo.se</email>
</author>
<published>2025-04-07T22:46:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=d26203beb99a431c514f434afe6c984cc9637547'/>
<id>urn:sha1:d26203beb99a431c514f434afe6c984cc9637547</id>
<content type='text'>
Add support for reading DRAM size information from PMUGRF os_reg18 reg.

Compared to most Rockchip SoCs the RK3528 use os_reg18 for DRAM info,
instead of os_reg2.

Signed-off-by: Jonas Karlman &lt;jonas@kwiboo.se&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>arm: mach-k3: j721e: Split out J7200 SoC support from J721e</title>
<updated>2025-04-06T00:28:02Z</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2025-03-19T18:54:58Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=03e3fdd3d09e5e586f7e1420f30510ea2d614f7a'/>
<id>urn:sha1:03e3fdd3d09e5e586f7e1420f30510ea2d614f7a</id>
<content type='text'>
Currently in j721e_init.c we check which firewalls to remove using
the board configuration (e.g CONFIG_TARGET_J721E_R5_EVM). We do this
as J721e and J7200 have different IP and firewalls but use the same
SoC definition (SOC_K3_J721E) even though they are different SoCs.

The idea was they would be similar enough that they both could use
the same SoC config to help with common code sharing. Board checks
would then be used differentiate.

This has grown far too messy to maintain any more, especially now
that there is more than one board using J721e (EVM, SK, Beagle AI64).
As differentiation is done based on board, every one of these boards
would have to have checks added for them. Instead let's split J7200
support out from J721e like how normal new SoC support is done.

This patch touches several subsystems and could not be split much better
as when we add SOC_K3_J7200 we want to make use of it in all spots that
once used the combined SOC_K3_J721E so we can turn off SOC_K3_J721E when
building for J7200 boards.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
</content>
</entry>
<entry>
<title>ram: renesas: dbsc5: Pass udevice and MODEMR0 to dbsc5_get_board_data()</title>
<updated>2025-03-29T01:33:24Z</updated>
<author>
<name>Marek Vasut</name>
<email>marek.vasut+renesas@mailbox.org</email>
</author>
<published>2025-03-25T22:43:33Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=47dad5cc61dd955cca342bbda8c146548ef3409c'/>
<id>urn:sha1:47dad5cc61dd955cca342bbda8c146548ef3409c</id>
<content type='text'>
Pass DBSC5 udevice and MODEMR0 register values to board specific
function dbsc5_get_board_data(). The board specific implementation
of dbsc5_get_board_data() can return struct renesas_dbsc5_board_config
which matches the board based on the content of MODEMR0 or content
of DT accessible via the udevice.

Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
</content>
</entry>
</feed>
