CTCaer 7652d9cdb1 bdk: display: use mipi cal sw war on T210 also ... As per Nvidia, the pad brick separates clock and data terminations. This necessitates doing the calibration twice. Nvidia/Nintendo probably never updated that part on T210 since it's from around 2015/2016. T210B01 is based on 2017 codebase so it has it. HOS (nvservices, not boot) is probably updated to also do that. If not, then they should fix it. There are 0 known issue reports with that on T210, but well.		2024-06-05 01:11:04 +03:00
..
display	bdk: display: use mipi cal sw war on T210 also	2024-06-05 01:11:04 +03:00
ianos
input	bdk: use static where it should	2024-06-02 07:09:34 +03:00
libs	bdk: fatfs: update copyright	2024-06-02 07:42:35 +03:00
mem	bdk: minerva: add emc src div disable	2024-06-02 06:46:28 +03:00
power	bdk: max77620: raise sd1 max voltage	2024-02-16 15:55:40 +02:00
rtc	bdk: rtc: handle offset adjustment in-place	2024-03-12 15:08:55 +02:00
sec	bdk: bpmp: add and use bpmp_clk_rate_relaxed	2024-06-02 06:51:06 +03:00
soc	bdk: clock: always set DISPA source	2024-06-02 08:00:42 +03:00
storage	bdk: use static where it should	2024-06-02 07:09:34 +03:00
thermal	bdk: bpmp: add and use bpmp_clk_rate_relaxed	2024-06-02 06:51:06 +03:00
usb	bdk: usb: hid: don't send a packet if no new data	2024-06-02 07:40:11 +03:00
utils	bdk: rename exec_cfg to reg_write_array	2024-06-05 00:49:15 +03:00
bdk.h
exception_handlers.S
fatfs_cfg.h
fatfs_conf.h
gfx_utils.h
memory_map.h	bdk: smmu: refactor driver and allow other asid	2024-03-13 01:54:46 +02:00
module.h