Wi-Fi SD8987 + iMX8mp can't get IP after HDMI patch

DrRamm · ‎03-06-2024

Hi, I am facing this problem on Android 13 1.0.0 and kernel 5.15.71, imx8mp cpu

My device works fine with SD8987 Wi-Fi SDIO, but after adding the HDMI patch from NXP, the Wi-Fi module cannot connect to channels 1/2/3/4 at 2.4 GHz. I am referring to frequencies 2412 2417 2422 2427. It connects to the other channels/frequencies (5-11) without problems. I can't understand how the HDMI patch affects the wifi module. And why exactly the first four channels do not connect.

P.S. Access point sees, but can not get an IP address. Only this commit breaks the work. And if I delete the item above in samsung_phy_pll_cfg, all channels work again

From 4e3dc9e454fa9b30620c14abf9bcccdd9e97f6d7 Mon Sep 17 00:00:00 2001
From: Richard Kim <richard.kim@nxp.com>
Date: Tue, 28 Sep 2021 11:18:29 +0900
Subject: [PATCH] 1024x768@60Hz 65MHz support

---
drivers/phy/freescale/phy-fsl-samsung-hdmi.c | 9 +++++++++
1 file changed, 9 insertions(+)

diff --git a/drivers/phy/freescale/phy-fsl-samsung-hdmi.c b/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
index c0ba6e8073452..26673c455264e 100644
--- a/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
+++ b/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
@@ -325,6 +325,15 @@ const struct phy_config samsung_phy_pll_cfg[] = {
0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0xE0, 0x83, 0x0F, 0x3E, 0xF8, 0x00, 0x00,
},
+ }, {
+ 65000000, {
+ 0x00, 0xD1, 0x51, 0x58, 0x8D, 0x04, 0x9A, 0x57,
+ 0x4F, 0x30, 0x33, 0x65, 0x10, 0xBE, 0x24, 0x80,
+ 0x6C, 0xF2, 0x67, 0x00, 0x10, 0x85, 0x30, 0x3A,
+ 0x74, 0x8F, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,
+ 0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
+ 0x00, 0xE0, 0x83, 0x0F, 0x3E, 0xF8, 0x00, 0x00,
+ },
}, {
67500000, {
0x00, 0xD1, 0x54, 0x52, 0x87, 0x03, 0x80, 0x40,
--
GitLab

[ 0.000000][ T0] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000][ T0] Linux version 5.15.71-g4e3dc9e454fa-dirty-abmp1V91221 (nobody@android-build) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29)) 10.3.1 20210621, GNU ld (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29)) 2.36.1.20210621) #1 SMP PREEMPT Wed Mar 6 11:23:52 MSK 2024
[ 0.000000][ T0] Machine model: NXP i.MX8MPlus EVK board
[ 0.000000][ T0] Stack Depot is disabled
[ 0.000000][ T0] efi: UEFI not found.
[ 0.000000][ T0] Reserved memory: created DMA memory pool at 0x0000000094300000, size 1 MiB
[ 0.000000][ T0] OF: reserved mem: initialized node vdev0buffer@94300000, compatible id shared-dma-pool
[ 0.000000][ T0] NUMA: No NUMA configuration found
[ 0.000000][ T0] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000bfffffff]
[ 0.000000][ T0] NUMA: NODE_DATA [mem 0xbfbd20c0-0xbfbd4fff]
[ 0.000000][ T0] kvm [0]: Reserved 16 MiB at 0xbea00000
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] DMA [mem 0x0000000040000000-0x00000000bfffffff]
[ 0.000000][ T0] DMA32 empty
[ 0.000000][ T0] Normal empty
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000040000000-0x0000000055ffffff]
[ 0.000000][ T0] node 0: [mem 0x0000000058000000-0x00000000923fffff]
[ 0.000000][ T0] node 0: [mem 0x0000000092400000-0x00000000943fffff]
[ 0.000000][ T0] node 0: [mem 0x0000000094400000-0x00000000bfffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bfffffff]
[ 0.000000][ T0] On node 0, zone DMA: 8192 pages in unavailable ranges
[ 0.000000][ T0] cma: Reserved 480 MiB at 0x000000009e000000

[ 7.395320][ T216] wlan: Loading MWLAN driver
[ 7.417783][ T219] random: hwservicemanage: uninitialized urandom read (40 bytes read)
[ 7.426978][ T216] wlan: Register to Bus Driver...
[ 7.452281][ T219] random: hwservicemanage: uninitialized urandom read (16 bytes read)
[ 7.463016][ T216] vendor=0x02DF device=0x9149 class=0 function=1
[ 7.466307][ T219] random: hwservicemanage: uninitialized urandom read (0 bytes read)
[ 7.472570][ T216] Attach moal handle ops, card interface type: 0x105
[ 7.489346][ T216] SD8987: init module param from usr cfg
[ 7.494925][ T216] card_type: SD8987, config block: 0
[ 7.500098][ T216] cfg80211_wext=0xf
[ 7.503796][ T216] sta_name=wlan
[ 7.507143][ T216] uap_name=wlan
[ 7.510479][ T216] wfd_name=p2p
[ 7.513741][ T216] max_vir_bss=1
[ 7.517082][ T216] cal_data_cfg=none
[ 7.520785][ T216] ps_mode = 2
[ 7.524003][ T216] auto_ds = 2
[ 7.534570][ T216] host_mlme=enable
[ 7.543236][ T216] fw_name=sdiouart8987_combo_v0.bin
[ 7.543285][ T216] SDIO: max_segs=128 max_seg_size=65472
[ 7.556345][ T216] rx_work=1 cpu_num=4
[ 7.556372][ T216] Attach mlan adapter operations.card_type is 0x105.
[ 7.587427][ T216] wlan: Enable TX SG mode
[ 7.602421][ T216] wlan: Enable RX SG mode
[ 7.687234][ T216] Request firmware: sdiouart8987_combo_v0.bin
[ 7.953168][ T216] Wlan: FW download over, firmwarelen=603832 downloaded 603832
[ 8.823046][ T216] WLAN FW is active
[ 8.826955][ T216] on_time is 8824068000
[ 8.888673][ T20] fw_cap_info=0x181d7f03, dev_cap_mask=0xffffffff
[ 8.894979][ T20] max_p2p_conn = 8, max_sta_conn = 8
[ 8.900465][ T20] SDIO rx aggr: 1 block_size=512
[ 8.905428][ T20] wlan: Enable RX SG mode
[ 8.909710][ T20] mpa_rx_buf_size=65280
[ 8.914535][ T259] EXT4-fs (dm-6): Ignoring removed nomblk_io_submit option
[ 8.924745][ T259] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic. Quota mode: journalled.
[ 8.927986][ T216] wlan: version = SD8987----16.92.21.p69.3-MM5X16344.p3-GPL-(FP92)
[ 8.945977][ T1] loop2: detected capacity change from 0 to 6780
[ 8.947367][ T216] wlan: Register to Bus Driver Done
[ 8.957996][ T216] wlan: Driver loaded successfully

[ 117.075702][ T2065] wlan: Received disassociation request on wlan0, reason: 3
[ 117.082925][ T2065] wlan: REASON: (Deauth) Sending STA is leaving (or has left) IBSS or ESS
[ 117.091327][ T2065] Already disconnected
[ 121.232677][ T150] wlan: SCAN COMPLETED: scanned AP count=25
[ 121.304403][ T1736] wlan: wlan0 START SCAN
[ 122.606673][ T150] usb 1-1.2.1.2: USB disconnect, device number 6
[ 125.825286][ T150] wlan: SCAN COMPLETED: scanned AP count=27
[ 125.840113][ T2065] wlan: HostMlme wlan0 send auth to bssid 6c:XX:XX:XX:d4:64
[ 127.166634][ T1736] wlan: wlan0 START SCAN
[ 130.851850][ T2065] wlan: Received disassociation request on wlan0, reason: 3
[ 130.859026][ T2065] wlan: REASON: (Deauth) Sending STA is leaving (or has left) IBSS or ESS
[ 130.867393][ T2065] Already disconnected
[ 132.905403][ T150] wlan: SCAN COMPLETED: scanned AP count=29
[ 132.983645][ T2065] wlan: HostMlme wlan0 send auth to bssid 6c:XX:XX:XX:d4:64
[ 134.678759][ T1736] wlan: wlan0 START SCAN
[ 137.994655][ T2065] wlan: Received disassociation request on wlan0, reason: 3
[ 138.001858][ T2065] wlan: REASON: (Deauth) Sending STA is leaving (or has left) IBSS or ESS
[ 138.010249][ T2065] Already disconnected
[ 138.623755][ T4111] audit: audit_lost=407 audit_rate_limit=5 audit_backlog_limit=64
[ 138.631510][ T4111] audit: rate limit exceeded
[ 140.007820][ T150] wlan: SCAN COMPLETED: scanned AP count=27
[ 140.091134][ T2065] wlan: HostMlme wlan0 send auth to bssid 6c:XX:XX:XX:d4:64
[ 142.142183][ T1736] wlan: wlan0 START SCAN
[ 145.101498][ T2065] wlan: Received disassociation request on wlan0, reason: 3
[ 145.108692][ T2065] wlan: REASON: (Deauth) Sending STA is leaving (or has left) IBSS or ESS
[ 145.117076][ T2065] Already disconnected
[ 147.199056][ T150] wlan: SCAN COMPLETED: scanned AP count=28
[ 147.285430][ T2065] wlan: HostMlme wlan0 send auth to bssid 6c:XX:XX:XX:d4:64
[ 148.100347][ T269] wlan0:
[ 148.100362][ T269] wlan: HostMlme Auth received from 6c:XX:XX:XX:d4:64
[ 149.228682][ T150] ASSOC_RESP: Association Failed, status code = 1, error = 0xfffc, a_id = 0xffff
[ 149.237829][ T150] IOCTL failed: 00000000dc935728 id=0x20000, sub_id=0x20001 action=1, status_code=0xfffc0001
[ 149.247886][ T2065] HostMlme wlan0: bss_start Fails
[ 149.252899][ T2065] wlan: HostMlme wlan0 Failed to connect to bssid 6c:XX:XX:XX:d4:64
[ 149.676738][ T1736] wlan: wlan0 START SCAN
[ 154.153894][ T150] wlan: SCAN COMPLETED: scanned AP count=26
[ 154.243081][ T2065] wlan: HostMlme wlan0 send auth to bssid 6c:XX:XX:XX:d4:64
[ 154.680139][ T1736] wlan: wlan0 START SCAN
[ 159.255254][ T2065] wlan: Received disassociation request on wlan0, reason: 3
[ 159.262443][ T2065] wlan: REASON: (Deauth) Sending STA is leaving (or has left) IBSS or ESS
[ 159.270841][ T2065] Already disconnected
[ 161.222368][ T150] wlan: SCAN COMPLETED: scanned AP count=29
[ 161.327843][ T2065] wlan: HostMlme wlan0 send auth to bssid 6c:XX:XX:XX:d4:64
[ 161.347127][ T1736] wlan: wlan0 START SCAN
[ 166.365790][ T2065] wlan: Received disassociation request on wlan0, reason: 3
[ 166.372963][ T2065] wlan: REASON: (Deauth) Sending STA is leaving (or has left) IBSS or ESS
[ 166.381328][ T2065] Already disconnected
[ 168.308602][ T150] wlan: SCAN COMPLETED: scanned AP count=29
[ 168.405199][ T2065] wlan: HostMlme wlan0 send auth to bssid 6c:XX:XX:XX:d4:64
[ 169.661253][ T1736] wlan: wlan0 START SCAN

DrRamm · ‎04-03-2024

Hi! Do you want a joke?) This patch fixes Wi-Fi. But I still need an explanation of what happened and why HDMI affects Wi-Fi.

I've worked a lot with mtk and qcom, but I've never encountered that changing the HDMI driver affects any other components. This is crazy

--- a/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
+++ b/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
@@ -330,7 +330,7 @@ const struct phy_config samsung_phy_pll_cfg[] = {
0x00, 0xD1, 0x51, 0x58, 0x8D, 0x04, 0x9A, 0x57,
0x4F, 0x30, 0x33, 0x65, 0x10, 0xBE, 0x24, 0x80,
0x6C, 0xF2, 0x67, 0x00, 0x10, 0x85, 0x30, 0x3A,
- 0x74, 0x8F, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,
+ 0x60, 0x8F, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,
0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0xE0, 0x83, 0x0F, 0x3E, 0xF8, 0x00, 0x00,
},
--
GitLab

So the correct settings are

                65000000, {
                        0x00, 0xD1, 0x51, 0x58, 0x8D, 0x04, 0x9A, 0x57,
                        0x4F, 0x30, 0x33, 0x65, 0x10, 0xBE, 0x24, 0x80,
                        0x6C, 0xF2, 0x67, 0x00, 0x10, 0x85, 0x30, 0x3A,
                        0x60, 0x8F, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,
                        0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                        0x00, 0xE0, 0x83, 0x0F, 0x3E, 0xF8, 0x00, 0x00,
                },

在原帖中查看解决方案

DrRamm · ‎04-03-2024

Hi! Do you want a joke?) This patch fixes Wi-Fi. But I still need an explanation of what happened and why HDMI affects Wi-Fi.

I've worked a lot with mtk and qcom, but I've never encountered that changing the HDMI driver affects any other components. This is crazy

--- a/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
+++ b/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
@@ -330,7 +330,7 @@ const struct phy_config samsung_phy_pll_cfg[] = {
0x00, 0xD1, 0x51, 0x58, 0x8D, 0x04, 0x9A, 0x57,
0x4F, 0x30, 0x33, 0x65, 0x10, 0xBE, 0x24, 0x80,
0x6C, 0xF2, 0x67, 0x00, 0x10, 0x85, 0x30, 0x3A,
- 0x74, 0x8F, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,
+ 0x60, 0x8F, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,
0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0xE0, 0x83, 0x0F, 0x3E, 0xF8, 0x00, 0x00,
},
--
GitLab

So the correct settings are

                65000000, {
                        0x00, 0xD1, 0x51, 0x58, 0x8D, 0x04, 0x9A, 0x57,
                        0x4F, 0x30, 0x33, 0x65, 0x10, 0xBE, 0x24, 0x80,
                        0x6C, 0xF2, 0x67, 0x00, 0x10, 0x85, 0x30, 0x3A,
                        0x60, 0x8F, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,
                        0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                        0x00, 0xE0, 0x83, 0x0F, 0x3E, 0xF8, 0x00, 0x00,
                },

Christine_Li · ‎04-03-2024

Hi, @DrRamm

I am so sorry about the inconvenient and late reply.

These days I am stuck in other higher priority cases because of customer's project process is stuck.

So from this reply, it seems that you have found the root cause. Am I right?

Anything else I can do for you on this case?

Best regards,

Christine.

DrRamm · ‎04-03-2024

Can you provide datasheet for this HDMI module? I randomly picked this value. I don't know what it does. Maybe my camera doesn't work now or one of the processor cores is turned off.

Because if changes in hdmi affect wifi -- absolutely anything can happen with NXP device.

Christine_Li · ‎04-03-2024

Hi, @DrRamm

I am not sure whether is this PCMF2HDMI2S you are talking about.

If yes, please refer to below link for its datasheet.

https://pdf1.alldatasheet.com/datasheet-pdf/download/858385/NXP/PCMF2HDMI2S.html

Personally, I don't think the HDMI patch will have any influence on Wi-Fi.

Best regards,

Christine.

DrRamm · ‎04-03-2024

I use the standard HDMI output that is used in the imx8mp evk.

And yes, I couldn't think that hdmi affects wifi either. That's why it took me about two weeks to find the cause. And sadly, hdmi is the cause.

I think the reason is the PLL frequencies and their dividers. Maybe they overlap somewhere.

And yes, there is another commit that also disables the first four channels of 2.4 ghz. Guess what it does? Disables the use of lcdif frequency in the kernel so that continuous splash works from u-boot.

So without documentation on the samsung_phy_pll_cfg structure in the phy-fsl-samsung-hdmi file, I can't figure out what the cause really is and what this might lead to in the future

UPD found this commit https://github.com/nxp-imx/linux-imx/commit/c26e074aa4492f66ad48dfbb2e5894cf5d4a67e7

Christine_Li · ‎04-07-2024

Hi, @DrRamm

Thanks for your feedback.

So right now you are requesting me to provide to you: documentation on the samsung_phy_pll_cfg structure in the phy-fsl-samsung-hdmi file, am I right?

And also, I saw the link you shared has been committed to Linux kernel 6.1.22.

Can you please help to try with our newer release: Android 13.0.0_2.2.0 (L6.1.36_2.1.0 BSP) or Android 13.0.0_2.0.0 (L6.1.22_2.0.0 BSP), then let me know your results?

I also attach our Android release link for your convenience as below:

https://www.nxp.com/design/design-center/software/embedded-software/i-mx-software/android-os-for-i-m...

Best regards,

Christine.

DrRamm · ‎04-09-2024

> documentation on the samsung_phy_pll_cfg structure in the phy-fsl-samsung-hdmi file, am I right?

Yes

Christine_Li · ‎04-10-2024

Hi, @DrRamm

Thank you so much for your reply.

I checked internally, we do not have this kind of document, it is SAMSUNG internally defined.

Sorry for the inconvenience to you.

Have a nice day~

Best regards,

Christine.

DrRamm · ‎03-15-2024

    DMT 0x10:  1024x768    60.004 Hz   4:3    48.363 kHz  65.000 MHz
    DMT 0x11:  1024x768    70.069 Hz   4:3    56.476 kHz  75.000 MHz
    DMT 0x12:  1024x768    75.029 Hz   4:3    60.023 kHz  78.750 MHz

Can I ask for HDMI patches for these three resolutions from my EDID config I sent above? I mean file drivers/phy/freescale/phy-fsl-samsung-hdmi.c and samsung_phy_pll_cfg

I want to test different frequencies for HDMI. Maybe your wi-fi module will work correctly on them

DrRamm · ‎03-26-2024

Any news?

Christine_Li · ‎03-27-2024

Hi, @DrRamm

I am so sorry, these days I am a little busy.

This week I will try to continue on this thread.

Can you please continue your project with other resolutions which work fine?

Best regards,

Christine.

DrRamm · ‎03-06-2024

patch attached

Christine_Li · ‎03-11-2024

Hi， @DrRamm

Thanks for creating case to us.

I will check and update to you my findings.

Best regards,

Christine.

DrRamm · ‎03-11-2024

Discovered a very interesting Wi-Fi behavior.

If the patch is applied:

- Wi-Fi connects correctly when HDMI is disconnected

- If you connect a 1024*600 monitor via HDMI, Wi-Fi stops connecting. To the same network without rebooting the device

If the patch is NOT applied:

- Without HDMI connected, everything works correctly

- When connecting 1024*600 monitor Wi-Fi also works correctly. But the resolution on the monitor is 1920*1080 (FHD)

I think the reason is due to configuration timings/clocks. Can you double-check?

I concede that I have the wrong memory settings. My board has 2GB RAM instead of 6GB and I could have made a mistake in the DTS settings

	resmem: reserved-memory {
		#address-cells = <2>;
		#size-cells = <2>;
		ranges;

		ocram: ocram@900000 {
			no-map;
			reg = <0 0x900000 0 0x70000>;
		};

/*
 *		Memory reserved for optee usage. Please do not use.
 *		This will be automaticky added to dtb if OP-TEE is installed.
 *		optee@56000000 {
 *   			reg = <0 0x56000000 0 0x2000000>;
 *			no-map;
 *		};
 */
		/* global autoconfigured region for contiguous allocations */
		linux,cma {
			compatible = "shared-dma-pool";
			reusable;
			size = <0 0x3c000000>;
			alloc-ranges = <0 0x40000000 0 0xC0000000>;
			linux,cma-default;
		};

		dsp_reserved: dsp@92400000 {
			reg = <0 0x92400000 0 0x1000000>;
			no-map;
		};
		dsp_reserved_heap: dsp_reserved_heap {
			reg = <0 0x93400000 0 0xef0000>;
			no-map;
		};
		dsp_vdev0vring0: vdev0vring0@942f0000 {
			reg = <0 0x942f0000 0 0x8000>;
			no-map;
		};
		dsp_vdev0vring1: vdev0vring1@942f8000 {
			reg = <0 0x942f8000 0 0x8000>;
			no-map;
		};
		dsp_vdev0buffer: vdev0buffer@94300000 {
			compatible = "shared-dma-pool";
			reg = <0 0x94300000 0 0x100000>;
			no-map;
		};

		/* used only by tuning tool, can be removed for normal case 
		isp0_reserved: isp0@94400000 {
			no-map;
			reg = <0 0x94400000 0 0x10000000>;
		};*/
	};

	memory@40000000 {
		device_type = "memory";
		reg = <0x0 0x40000000 0 0x80000000>;
	};

&{/reserved-memory/linux,cma} {
	status = "disabled";
};

/*
&isp0_reserved {
	no-map;
	reg = <0 0x82400000 0 0x10000000>;
};*/

&resmem {
	ramoops@94400000 {
		compatible = "ramoops";
		reg = <0 0x94400000 0 0x00100000>;
		record-size     = <0x00020000>;
		console-size    = <0x00020000>;
		ftrace-size     = <0x00020000>;
		pmsg-size       = <0x00020000>;
        };

	secure_region: secure {
		 compatible = "imx-secure-ion-pool";
		 reg = <0x0 0x82400000 0 0x10000000>;
	};
};

DrRamm · ‎03-12-2024

I tested some hypotheses. I applied the patch to add 65 MHz.
1. If HDMI is not connected -- connects to Wi-Fi correctly
2. If you connect a FullHD monitor -- connects to Wi-Fi correctly
3. If you connect a 1024x600 monitor, it does NOT connect to Wi-Fi.

At the same time, the access point (SSID) itself is visible, it just does not obtain IP. The access point itself (MiktoTik hAP ac lite) does not even have logs of connection attempts in third case.

I also checked the Wi-Fi on Android 10 with kernel 5.4.70 -- all three cases above work correctly.

On kernel 5.4.70 this patch (65 MHz for 1024x600) is applied and everything works correctly

DrRamm · ‎03-12-2024

I m sorry, resolution is 1024x768

Also I found thread https://community.nxp.com/t5/i-MX-Processors/HDMI-DRM-custom-resolution-and-clock-frequency/m-p/1177...

but links for tool are broken

$ edid-decode < /sys/class/drm/card0-DP-2/edid 
edid-decode (hex):

00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00
0c 17 01 04 a5 00 00 00 02 d7 a5 a2 59 4a 96 24
14 50 54 af ce 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 64 19 00 40 41 00 26 30 18 88
36 00 3f 43 21 00 00 18 00 00 00 fd 00 32 4c 1e
50 10 00 0a 20 20 20 20 20 20 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fc
00 41 41 41 0a 20 20 20 20 20 20 20 20 20 00 a6

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: ROW
    Model: 0
    Made in: week 12 of 2013
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 8
    DisplayPort interface
    Image size is variable
    Gamma: 1.00
    Supported color formats: RGB 4:4:4
    First detailed timing includes the native pixel format and preferred refresh rate
  Color Characteristics:
    Red  : 0.6357, 0.3486
    Green: 0.2900, 0.5888
    Blue : 0.1425, 0.0800
    White: 0.3134, 0.3291
  Established Timings I & II:
    IBM     :   720x400    70.082 Hz   9:5    31.467 kHz  28.320 MHz
    DMT 0x04:   640x480    59.940 Hz   4:3    31.469 kHz  25.175 MHz
    DMT 0x05:   640x480    72.809 Hz   4:3    37.861 kHz  31.500 MHz
    DMT 0x06:   640x480    75.000 Hz   4:3    37.500 kHz  31.500 MHz
    DMT 0x08:   800x600    56.250 Hz   4:3    35.156 kHz  36.000 MHz
    DMT 0x09:   800x600    60.317 Hz   4:3    37.879 kHz  40.000 MHz
    DMT 0x0a:   800x600    72.188 Hz   4:3    48.077 kHz  50.000 MHz
    DMT 0x0b:   800x600    75.000 Hz   4:3    46.875 kHz  49.500 MHz
    DMT 0x10:  1024x768    60.004 Hz   4:3    48.363 kHz  65.000 MHz
    DMT 0x11:  1024x768    70.069 Hz   4:3    56.476 kHz  75.000 MHz
    DMT 0x12:  1024x768    75.029 Hz   4:3    60.023 kHz  78.750 MHz
  Standard Timings: none
  Detailed Timing Descriptors:
    DTD 1:  1024x768    60.004 Hz   4:3    48.363 kHz  65.000 MHz (575 mm x 323 mm)
                 Hfront   24 Hsync 136 Hback 160 Hpol N
                 Vfront    3 Vsync   6 Vback  29 Vpol N
  Display Range Limits:
    Monitor ranges (GTF): 50-76 Hz V, 30-80 kHz H, max dotclock 160 MHz
    Empty Descriptor
    Display Product Name: 'AAA'
Checksum: 0xa6

my EDID

Christine_Li · ‎03-12-2024

Hi, @DrRamm

Thanks for your trying and sharings.

Can you please have a try with the tool (mentioned in your comment), I sent to your private email and let me know whether it works for you?

Best regards,

Christine.

Christine_Li · ‎03-13-2024

Hi, @DrRamm

As I know you have received the tool I have sent to your private email.

Let's continue to discuss this issue here.

I have to say sorry that I am also not familiar with this tool because I am not in charge of HDMI domain right now. Just get it from the previous you shared community link's replier.

Please try to change the parameters and

1. Fill yellow fields for a selected pixel clock and format
2. Make sure there is no ""ERR"" status displayed
3. Go to ""Table 8"" sheet for PHY programming settings"

Also can refer that previous community link to see whether there is any useful info.

If still have questions, please let me know and I may need to ask our internal colleague for help about this tool.

Best regards,

Christine.

DrRamm · ‎03-13-2024

Thank you! I have matched the parameters (found guide https://community.nxp.com/t5/i-MX-Processors/Custom-Resolution-800x480/td-p/1403769), but I don't understand how to convert them for the samsung_phy_phy_pll_cfg structure in drivers/phy/freescale/phy-fsl-samsung-hdmi.c file

Add these values to API code (t28hpc_hdmitx_table.c: t28hpc_hdmitx_clock_control_table_pixel_out[][]).								
Make sure there are PLL tuning settings defined for the new VCO frequency (t28hpc_hdmitx_table.c: t28hpc_hdmitx_pll_tuning_table_pixel_out[][]).														
In case there is no matching VCO frequency, define new one using closest match settings

Christine_Li · ‎03-19-2024

Hi， @DrRamm

Sorry, I was in PTO and come back to office today.

Right now I am a little busy for some issues, once have any updates on this issue, I will let you know.

Best regards,

Christine.