Received-SPF: pass (google.com: domain of linux-kernel+bounces-55303-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Tue, 6 Feb 2024 11:10:56 -0500
From: =?utf-8?B?TsOtY29sYXMgRi4gUi4gQS4=?= Prado <nfraprado@collabora.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Chen-Yu Tsai <wenst@chromium.org>
Cc: regressions@lists.linux.dev, linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com
Subject: Probe regression of efuse@11f10000 on
 mt8183-kukui-jacuzzi-juniper-sku16 running next-20240202
Message-ID: <47cdeac1-121d-4b1a-a3ac-e2affc7a2fc3@notapiano>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Hi,

KernelCI has identified a regression [1] on the
mt8183-kukui-jacuzzi-juniper-sku16 machine running on next-20240202 compared to
next-20240118:

<4>[    0.627077] sysfs: cannot create duplicate filename '/bus/nvmem/devices/mtk-efuse0'
<4>[    0.634945] CPU: 7 PID: 1 Comm: swapper/0 Not tainted 6.8.0-rc2-next-20240202 #1
<4>[    0.642542] Hardware name: Google juniper sku16 board (DT)
<4>[    0.648237] Call trace:
<4>[    0.650917]  dump_backtrace+0x94/0xec
<4>[    0.654815]  show_stack+0x18/0x24
<4>[    0.658359]  dump_stack_lvl+0x48/0x60
<4>[    0.662252]  dump_stack+0x18/0x24
<4>[    0.665796]  sysfs_warn_dup+0x64/0x80
<4>[    0.669688]  sysfs_do_create_link_sd+0xf0/0xf8
<4>[    0.674353]  sysfs_create_link+0x20/0x40
<4>[    0.678500]  bus_add_device+0x64/0x104
<4>[    0.682475]  device_add+0x33c/0x778
<4>[    0.686193]  nvmem_register+0x514/0x714
<4>[    0.690256]  devm_nvmem_register+0x1c/0x6c
<4>[    0.694577]  mtk_efuse_probe+0xe8/0x170
<4>[    0.698637]  platform_probe+0x68/0xd8
<4>[    0.702525]  really_probe+0x148/0x2b4
<4>[    0.706413]  __driver_probe_device+0x78/0x12c
<4>[    0.710990]  driver_probe_device+0xdc/0x160
<4>[    0.715394]  __driver_attach+0x94/0x19c
<4>[    0.719453]  bus_for_each_dev+0x74/0xd4
<4>[    0.723512]  driver_attach+0x24/0x30
<4>[    0.727312]  bus_add_driver+0xe4/0x1e8
<4>[    0.731284]  driver_register+0x60/0x128
<4>[    0.735343]  __platform_driver_register+0x28/0x34
<4>[    0.740265]  mtk_efuse_init+0x20/0x5c
<4>[    0.744155]  do_one_initcall+0x6c/0x1b0
<4>[    0.748214]  kernel_init_freeable+0x1c8/0x290
<4>[    0.752795]  kernel_init+0x20/0x1dc
<4>[    0.756512]  ret_from_fork+0x10/0x20
<4>[    0.760353] mediatek,efuse: probe of 11f10000.efuse failed with error -17

This efuse probe failure causes the probe failure of other components that
depend on it, including the display pipeline:

/soc/dsi-phy@11e50000
/soc/dsi@14014000
/soc/efuse@11f10000
/soc/i2c@11008000/anx7625@58
/soc/i2c@11008000/anx7625@58/aux-bus/panel
/soc/thermal@1100b000

There is a series already addressing the issue [2]. The first two patches have
been merged into the mediatek tree, but that tree isn't currently being
integrated into linux-next. Besides that, patch 3 hasn't been merged into the
nvmem tree yet, and it is required in order to solve the issue.

I'm sending this regression report so we can properly track the regression while
the fixes don't land on linux-next.

Thanks,
N?colas

[1] https://linux.kernelci.org/test/plan/id/65bd63c3f12d8a95e200a225/
[2] https://lore.kernel.org/linux-mediatek/20240130095656.3712469-1-wenst@chromium.org/

#regzbot introduced next-20240118..next-20240202