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>

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

Signed-off-by: Wesley Yao <wesley.yao@rock-chips.com>
Change-Id: I841e377f40d15af5a3454e3f64c88baea41841e1

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

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

Signed-off-by: Weiwen Chen <cww@rock-chips.com>
Change-Id: I1ecb93ade73c85ead6c5d6875b549c7ecab004b3

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

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

Don't overwrite memory between 32bit and 64bit. And properly
map them and let host drivers to get proper regions.

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

First, it need to free gpio if fails to link up
the device. And do proper hardware level settings.

=> pci e
pcie@2a200000: PCIe Linking... LTSSM is 0x0
pcie@2a200000: PCIe Linking... LTSSM is 0x2
pcie@2a200000: PCIe Linking... LTSSM is 0x2
pcie@2a200000: PCIe Linking... LTSSM is 0x3
pcie@2a200000: PCIe-0 Link Fail
pcie@2a210000: PCIe Linking... LTSSM is 0x0
pcie@2a210000: PCIe Linking... LTSSM is 0x3
pcie@2a210000: PCIe Linking... LTSSM is 0x3
pcie@2a210000: PCIe-0 Link Fail

Retry enum:

=> pci e
pcie@2a200000: PCIe Linking... LTSSM is 0x0
pcie@2a200000: PCIe Linking... LTSSM is 0x0
pcie@2a200000: PCIe Link up, LTSSM is 0x130011
pcie@2a200000: PCIE-0: Link up (Gen2-x1, Bus0)
pcie@2a200000: invalid flags type!
pcie@2a210000: PCIe Linking... LTSSM is 0x0
pcie@2a210000: PCIe Linking... LTSSM is 0x2
pcie@2a210000: PCIe Link up, LTSSM is 0x130011
pcie@2a210000: PCIE-2: Link up (Gen2-x1, Bus2)
=> nvme scan
=> nvme info
Device 0: Vendor: 0x1e49 Rev: YM0500C6 Prod: YMA2256JA22314008G
            Type: Hard Disk
	    Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
Device 1: Vendor: 0x1d97 Rev: V0218G0 Prod: MCC3212000213
	    Type: Hard Disk
	    Capacity: 488386.3 MB = 476.9 GB (1000215216 x 512)

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

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

This patch enable CONFIG_USB_DWC2 for usb otg host mode.

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

Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Signed-off-by: Xuhui Lin <xuhui.lin@rock-chips.com>
Change-Id: Ib88062a2e8230729f267841e657529109675f7b9

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

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

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

Use discard to erase the desired LBA

[1]
=> md.l 0x44000000 0x200     #先读一下0x44000000的内存地址
44000000: 00000000 00000000 20014080 00000200    .........@. ....
44000010: 44004400 02010108 00002000 24000200    .D.D..... .....$
44000020: 08801000 10000000 00000000 80008018    ................

[2]
=> nvme read 0x44000000 0x0 1     #NVMe LBA 0读一个block到0x44000000

nvme read: device 0 block # 0, count 1 ... 1 blocks read: OK

[3]
=> md.l 0x44000000 0x200         #再读一下0x44000000的内存地址，变了
44000000: 4a400000 00000001 17c00000 00000002    ..@J............
44000010: 4aa00000 00000001 16700000 00000002    ...J......p.....

[4]
=> nvme erase 0x0 0x1		#0地址开始，擦除一个block

nvme erase: device 0 block # 0, count 1 ... 1 blocks erased: OK

[5]
=> nvme read 0x44000000 0x0 1   #再从NVMe的LBA 0地址读一个block数据到0x44000000

nvme read: device 0 block # 0, count 1 ... 1 blocks read: OK

[6]
=> md.l 0x44000000 0x200        #NVMe第一个block的数据已经清除了
44000000: 00000000 00000000 00000000 00000000    ................
44000010: 00000000 00000000 00000000 00000000    ................
44000020: 00000000 00000000 00000000 00000000    ................
...

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

Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
Change-Id: I8876ee37827c388e821159d0a41faf2e83326216

This adds px30 phy tuning to open pre-emphasize in non-chirp
state for both otg and host port.

Change-Id: If1a450c2fff4da49d7ebc1894c735e0b3b237b54
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>

This adds a new udevice compatible for PX30 SoCs.

Change-Id: I830e322ecbfa24f0f6fec616a25d7ded322e3ec6
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>

The rockchip SoCs need to disable usb2 phy enter suspend
mode which depends on the dwc3 suspend condition, otherwise
the usb2 phy doesn't get out of suspend and cause U-Boot
panic with the following log when scan some udisks.

XHCI timeout on event type 33... cannot recover.
BUG: failure at drivers/usb/host/xhci-ring.c:474/xhci_wait_for_event()!
BUG!

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

1. Fix the csc matrix. For YUV709L to YUV709L, YUV601L to
YUV601L, YUV2020L to YUV2020L, The csc matrix should be
identity matrix. For YUV601L to YUV709L, modeify the csc
matrix.
2. optimize the final calculation result. Use the new r2y
and y2r matrix for csc yuv2yuv and rgb2rgb case. A simple
round is used for csc yuv2yuv and rgb2rgb case for a more
precise result.

Signed-off-by: Zhang Yubing <yubing.zhang@rock-chips.com>
Change-Id: I59c38257cc3ca07e75c057eac710c9fa1e966ba9