linux-kernel - mfd: intel_soc_pmic_bxtwc: irq 0 issue, tmu and typec components fail to probe.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <TY2PR01MB3322FEDCDC048B7D3794F922CDBA2@TY2PR01MB3322.jpnprd01.prod.outlook.com>
Date: Fri, 9 Aug 2024 20:02:43 +0800
From: Zhang Ning <zhangn1985@...look.com>
To: gregkh@...uxfoundation.org, rafael@...nel.org,
	linux-kernel@...r.kernel.org
Cc: zhangn1985@...look.com, andy@...nel.org, lee@...nel.org
Subject: mfd: intel_soc_pmic_bxtwc: irq 0 issue, tmu and typec components
 fail to probe.

Hi, Greg & Rafael

recently, when I try to enable mfd components for intel_soc_pmic_bxtwc
for debian kernel[0]. I find tmu and typec failed to probe.

after check source code, I find irq for these two devices are 0, when
use platform_get_irq, it will alway fail.

	if (WARN(!ret, "0 is an invalid IRQ number\n"))
		return -EINVAL;
	return ret;

My workaround for debian is to hardcode irq to 0, instead to use api.

I don't know how to write a good solution, thus send an email to you.

BR.
Ning.

[0]: https://salsa.debian.org/kernel-team/linux/-/merge_requests/1156/diffs