[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024081349-erupt-reaction-efaa@gregkh>
Date: Tue, 13 Aug 2024 10:54:04 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Zhang Ning <zhangn1985@...look.com>
Cc: Andy Shevchenko <andy@...nel.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 Sat, Aug 10, 2024 at 01:27:18PM +0800, Zhang Ning wrote:
> On Fri, Aug 09, 2024 at 05:09:49PM +0300, Andy Shevchenko wrote:
> > On Fri, Aug 09, 2024 at 08:53:24PM +0800, Zhang Ning wrote:
> > > On Fri, Aug 09, 2024 at 03:33:33PM +0300, Andy Shevchenko wrote:
> > > > 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;
> > > > >
> Hi, Greg
> One more question, I don't understand why 0 is not a valid IRQ
> number for platform device?
Please search the archives for many many many discussions about this.
thanks,
greg k-h
Powered by blists - more mailing lists