[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <010401d99f6f$26d41600$747c4200$@trustnetic.com>
Date: Thu, 15 Jun 2023 17:52:52 +0800
From: Jiawen Wu <jiawenwu@...stnetic.com>
To: "'Michael Walle'" <michael@...le.cc>,
"'Andy Shevchenko'" <andy.shevchenko@...il.com>
Cc: <linus.walleij@...aro.org>, <brgl@...ev.pl>,
<shreeya.patel@...labora.com>, <linux-gpio@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2] gpiolib: Fix GPIO chip IRQ initialization restriction
On Thursday, June 15, 2023 5:26 PM, Michael Walle wrote:
> Am 2023-06-07 16:12, schrieb Andy Shevchenko:
> > +Cc: Michael
> >
> > On Wed, Jun 7, 2023 at 11:20 AM Jiawen Wu <jiawenwu@...stnetic.com>
> > wrote:
> >>
> >> In case of gpio-regmap, IRQ chip is added by regmap-irq and associated
> >> with
> >> GPIO chip by gpiochip_irqchip_add_domain(). The initialization flag
> >> was not
> >> added in gpiochip_irqchip_add_domain(), causing gpiochip_to_irq() to
> >> return
> >> -EPROBE_DEFER.
> >
> > Makes sense to me.
> > FWIW,
> > Reviewed-by: Andy Shevchenko <andy.shevchenko@...il.com>
> >
> > But it would be nice to hear from Michael about this.
>
> Thanks for bringing this to my attention. In fact, currently
> my sl28cpld is broken due to this. So:
Thanks for your test, it's exciting for me to actually fix a bug.
BTW, I wonder if it has problems when unregistering gpio-regmap.
Call Trace of irq_domain_remove() always exits in my test:
https://lore.kernel.org/all/011c01d98d3d$99e6c6e0$cdb454a0$@trustnetic.com/
Of course, it could be because there was something wrong with my
test code. But I want to be clear about this.
>
> Reviewed-by: Michael Walle <michael@...le.cc>
> Tested-by: Michael Walle <michael@...le.cc> # on kontron-sl28
>
> >> Fixes: 5467801f1fcb ("gpio: Restrict usage of GPIO chip irq members
> >> before initialization")
> >> Signed-off-by: Jiawen Wu <jiawenwu@...stnetic.com>
>
> -michael
>
Powered by blists - more mailing lists