[ICL] i5-1038NG7 on MacBookPro16,2 misdetected as Jasper Lake
kernel 5.15.0-rc3, drm-tip: 2021y-09m-30d-10h-45m-10s UTC
This is MacBookPro16,2 (13" 2020 model) running i5-1038NG7 CPU, no dedicated or secondary GPU, 2560x1600 display. Although everything seemingly works, I'm having trouble with USB-C -> DP adapters unable to reach HBR2 speeds (works fine under OS X), likely due to pruned sink rates. The first thing that caught my eye was this warning:
[ 41.744888] i915 0000:00:02.0: [drm:intel_pch_type] Found Jasper Lake PCH
[ 41.744892] ------------[ cut here ]------------
[ 41.744893] i915 0000:00:02.0: drm_WARN_ON(!(IS_PLATFORM(dev_priv, INTEL_JASPERLAKE) || IS_PLATFORM(dev_priv, INTEL_ELKHARTLAKE)))
[ 41.744900] WARNING: CPU: 7 PID: 1 at drivers/gpu/drm/i915/intel_pch.c:128 intel_pch_type+0x17b/0xa60
[ 41.744904] Modules linked in:
[ 41.744906] CPU: 7 PID: 1 Comm: swapper/0 Tainted: G W 5.15.0-rc3-gae92aa302baf-dirty #3
[ 41.744907] Hardware name: Apple Inc. MacBookPro16,2/Mac-5F9802EFE386AA28, BIOS 1554.120.19.0.0 (iBridge: 18.16.14663.0.0,0) 05/07/2021
[ 41.744908] RIP: 0010:intel_pch_type+0x17b/0xa60
[ 41.744911] Code: 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 ae 70 18 00 48 c7 c1 28 ce 4f 9c 4c 89 e2 48 c7 c7 82 7e 4e 9c 48 89 c6 e8 0b de 55 00 <0f> 0b b8 07 00 00 00 e9 1f 01 00 00 66 81 fe 00 1e 0f 84 6a 06 00
[ 41.744913] RSP: 0000:ffffb02940057c18 EFLAGS: 00010286
[ 41.744914] RAX: 0000000000000000 RBX: ffff959cc63f0000 RCX: 0000000000000000
[ 41.744915] RDX: 0000000000000001 RSI: 0000000000000001 RDI: 00000000ffffffff
[ 41.744916] RBP: ffff959cc1454000 R08: ffffffff9cbda5e8 R09: 0000000000000003
[ 41.744917] R10: ffffffff9c85a600 R11: ffffffff9c85a600 R12: ffff959cc13bdaa0
[ 41.744918] R13: ffff959cc63f0000 R14: 0000000000003880 R15: ffff959cc63f07d0
[ 41.744919] FS: 0000000000000000(0000) GS:ffff95a41ffc0000(0000) knlGS:0000000000000000
[ 41.744921] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 41.744921] CR2: 0000000000000000 CR3: 00000002d680f001 CR4: 00000000005706e0
[ 41.744922] PKRU: 55555554
[ 41.744923] Call Trace:
[ 41.744924] intel_detect_pch+0x60/0x2f0
[ 41.744928] i915_driver_probe+0x50f/0xd60
[ 41.744930] ? __kernfs_new_node+0x180/0x1f0
[ 41.744935] i915_pci_probe+0x41/0x1c0
[ 41.744938] ? _raw_spin_unlock_irqrestore+0x16/0x30
[ 41.744943] local_pci_probe+0x3b/0x80
[ 41.744946] ? pci_match_device+0xd2/0x120
[ 41.744949] pci_device_probe+0xf5/0x1b0
[ 41.744952] really_probe.part.0+0xaa/0x280
[ 41.744956] __driver_probe_device+0x8b/0x120
[ 41.744960] driver_probe_device+0x19/0xd0
[ 41.744963] __driver_attach+0xa3/0x170
[ 41.744966] ? __device_attach_driver+0xe0/0xe0
[ 41.744969] bus_for_each_dev+0x6c/0xb0
[ 41.744973] bus_add_driver+0x106/0x1b0
[ 41.744976] driver_register+0x8a/0xe0
[ 41.744978] i915_init+0x15/0x81
[ 41.744981] ? mipi_dsi_bus_init+0xc/0xc
[ 41.744984] do_one_initcall+0x3c/0x1e0
[ 41.744987] kernel_init_freeable+0x1c7/0x20f
[ 41.744990] ? rest_init+0xc0/0xc0
[ 41.744991] kernel_init+0x11/0x110
[ 41.744993] ret_from_fork+0x1f/0x30
[ 41.744995] ---[ end trace 50cea711749320c5 ]---Let's deal with this first and let me retest the adapter once fixed. The USB-C -> DP adapter was not connected at the time the attached dmesg snapshot was taken.
dmesg drm.debug=0x1e (extra drm debug checks compiled in)