Change-Id: Ibeaae28330a1dc89227848deb377c2d3377dad7b
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Delay 3 seconds to make sure power supply is steady.

Change-Id: Ieefae68fa52f23efb7315221d425b31650ae0883
Signed-off-by: Xuhui Lin <xuhui.lin@rock-chips.com>

Change-Id: I865dd92c34d439b0a1e0d27a0b67410dfa2ef611
Signed-off-by: Xuhui Lin <xuhui.lin@rock-chips.com>

For rk3568, rsa4096 flag and secureboot flag should be
burned together because of ecc enable.

Change-Id: I75e6171d37abc589f433462d0f055df01e604799
Signed-off-by: Xuhui Lin <xuhui.lin@rock-chips.com>

1. If burn both flags(0x30ff) into OTP_SECURE_BOOT_ENABLE_ADDR,
0xff will be burned first. If power down happens when burn rsa4096 flag
(0xff is already burned), the device becomes bricked.

2. So, fix all OTP_SECURE_BOOT_ENABLE_SIZE from 2 bytes to 1 byte,
only allow to burn 1 byte to open secureboot. Add OTP_RSA4096_ENABLE_ADDR/SIZE
definition used for burn rsa4096 flag.

Change-Id: Ifc9767242bc86fd0cf69ff107b4f557bc3a4fdcd
Signed-off-by: Xuhui Lin <xuhui.lin@rock-chips.com>

Change-Id: I4a550b94b6128d9131762bfece447d4da9a93099
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: Idcea7eb5425dbf875376ad98851ea8b94b4be3d9
Signed-off-by: Zhihuan He <huan.he@rock-chips.com>

Change-Id: I21632dd799df231f03b9aee9c91be44d798b468a
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: Icb97fe90b50ebf44eae673b6f3e6979d65a59079
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: If1044efe918f854085c019adad803687e01449e9
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: Ib990fc028978f9b549c5d12fb3fb1c406858abc8
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

1. Delaying the initialization of phy can solve the problem of
UFS initialization getting stuck when phy is not powered on.
2. Config linkup timeout to 150ms.
3. Config NOP_OUT_TIMEOUT to 1500ms.
4. Add retry for dev init.

Signed-off-by: Yifeng Zhao <yifeng.zhao@rock-chips.com>
Change-Id: I7b3dc1d3245e27626ab81f0807146b7e05507f27

Change-Id: I8ac6c59fcf9035ea86c6601d46731d6c24c7ae8a
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: I4d4e2239d237307fc722f81e359283703f51cc50
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: I4416b004d315f2f5689312b1eb53e36fce7f6bbf
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

In order to enable dual NOR flash users to experience double the
capacity and avoid frequent switching between two NOR flash devices,
the two NOR flash devices are virtualized into one device, which
I name it auto_merge tech.

Change-Id: I5edd7cde0481b1de6a35fce7ac67068889ff5ffe
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

SATA/USB/GMAC default Qos is 0x0, it is too low for peripheral, set to 0x404
to be same as other peripherals.

Signed-off-by: CanYang He <hcy@rock-chips.com>
Change-Id: Ib16efb77c91f3a819eba1c1e18f66d53a8aab427

set DMAC0 to priority 0x404 to keep the same with DMAC1/2
which had been set 0x404 by default.

Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>
Change-Id: I752c03a0b7d1026fe852965b13f65b789e14ab27

Change-Id: I88edf35ccac836e8445d298c3b08420c47d10987
Signed-off-by: William Wu <william.wu@rock-chips.com>

This patch reset usb controller and resume usb phy to
normal mode, and also set the usb utmi bvalid to high
from grf for usb download mode.

Change-Id: I98c3e44183b2f5b4c11a62246c6dc9530b109963
Signed-off-by: William Wu <william.wu@rock-chips.com>

Change-Id: I760c800876faafc2ea4947a4d5c7884708c0e513
Signed-off-by: William Wu <william.wu@rock-chips.com>

Change-Id: Ie22d23b5a69a517166a60e127996f408c60215cf
Signed-off-by: XiaoDong Huang <derrick.huang@rock-chips.com>

Change-Id: If503220306d90f3b8660c93914d53568eeb7fdb4
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Avoid affecting spiflash startup.

Change-Id: I9b1ec00fabd5e7a5f57eb1eacd4d79658121cf45
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: I5f133bdc5331bafe00e715055c76e2ccf5e44045
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: Ifa4eb38170c4c59bf038897b3535d9059031c82c
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: I48805bad26195e0bc5c918b245f7ace5b7a6320d
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: I063526d31d0cd797a0b771c8aa9176ac63258c00
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: I9033d9e5de505afbe621aec8d2f9bfb9ca3c5cca
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

1.BLK_PRE_RW for spiflash async transmission
2.support_cont_read for spinand continuous read

Change-Id: I513278181a0aeeff1ab6c10ffd46c2a50e2a4bb8
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Change-Id: Ie74444587378f076fdb0e08eeacd1dab3c3f25f2
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>

Fixes: (523469f4 lib: sysmem: Bypass alloc check for periph device range)

Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: Idd397dc67dad0d5032d920751fbec35f33dbce36

Today of_address_to_resource() is called only in
ofnode_read_resource() for livetree support and
fdt_get_resource() is called when livetree is not supported.

The fdt_get_resource() doesn't do the address translation
so when it is required, but the address translation is done
by ofnode_read_resource() caller, for example in
drivers/firmware/scmi/smt.c::scmi_dt_get_smt_buffer() {
...
	ret = ofnode_read_resource(args.node, 0, &resource);
	if (ret)
		return ret;

	faddr = cpu_to_fdt32(resource.start);
	paddr = ofnode_translate_address(args.node, &faddr);
...

The both behavior should be aligned and the address translation
must be called in fdt_get_resource() and removed for each caller.

Change-Id: Ic4a3a19fe7401fc21e446793f453bbc1a8ab4001
Fixes: a4481012 ("dm: core: Add dev_read_resource() to read device resources")
Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
Acked-by: Etienne Carriere <etienne.carriere@linaro.org>
Signed-off-by: Xuhui Lin <xuhui.lin@rock-chips.com>

Some UFS particles do not support multiple execution of linkup.
This patch has been modified to only be done once.

Signed-off-by: Yifeng Zhao <yifeng.zhao@rock-chips.com>
Change-Id: Id8ff8e7c1cd246f07e2d9fce18dfe9bd5c83a653

The first 4MB of the user partition in UFS can also be erased.
When erasing data, the data stored by the vendor_storage can
also be erased.

Signed-off-by: Yifeng Zhao <yifeng.zhao@rock-chips.com>
Change-Id: I7eafad85909c6a20c8650ea7ed82abf06632881d

Change-Id: I8d4b13795d7f15bb0af42544b085fd75cdea67f7
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>

Signed-off-by: Ziwei Lin <ziwei.lin@rock-chips.com>
Change-Id: I940622c795f41652549397891238f5faa7c3c797

Change-Id: I9bf6e4ea14f6836e60bd0766aa98fe6026421576
Signed-off-by: ZiHan Huang <zack.huang@rock-chips.com>

Given considerations such as memory usage and the default
configuration of the parameter partition table, it is not
recommended to use excessively large BMP logo images.
Therefore, the MAX_IMAGE_BYTES limit is set to 8 MB. For
images exceeding this size, it is recommended to use BMP
images in BI_RLE4/BI_RLE8 formats.

The log may be like:

......
bmp[logo.bmp] data size[23MB] is over the limitation MAX_IMAGE_BYTES[8MB]
failed to display uboot logo
CLK: (uboot. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)
  bpll 816000 KHz
  lpll 816000 KHz
......

Change-Id: If9b804b29f4a477b5b29050231944a39c0342a84
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>

The limitation is from decode_bmp.c in libnsbmp-0.1.7.
Some RLE8 bmp images will be regarded as error becasuse
of the check, without which these images can be showed
successfully, so we remove the unexpected limitation.

The libnsbmp-0.1.7 can be got from:
https://git.netsurf-browser.org/libnsbmp.git



Change-Id: I4a418b3484db1904d8c47b6e8ee7410c2964145f
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>