linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZrYMne34hVa33qKf@smile.fi.intel.com>
Date: Fri, 9 Aug 2024 15:33:33 +0300
From: Andy Shevchenko <andy@...nel.org>
To: Zhang Ning <zhangn1985@...look.com>
Cc: gregkh@...uxfoundation.org, rafael@...nel.org,
	linux-kernel@...r.kernel.org, lee@...nel.org
Subject: Re: mfd: intel_soc_pmic_bxtwc: irq 0 issue, tmu and typec components
 fail to probe.

On Fri, Aug 09, 2024 at 08:02:43PM +0800, Zhang Ning wrote:
> 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.

Hold on, how the heck you got 0 in the first place?

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

-- 
With Best Regards,
Andy Shevchenko