Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1465526 > unrolled thread
| Started by | Javier Martinez Canillas <javier@osg.samsung.com> |
|---|---|
| First post | 2016-08-18 16:30 +0200 |
| Last post | 2016-08-19 03:40 +0200 |
| Articles | 5 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() Javier Martinez Canillas <javier@osg.samsung.com> - 2016-08-18 16:30 +0200
Re: [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() Arend van Spriel <arend.vanspriel@broadcom.com> - 2016-08-19 03:00 +0200
Re: [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() Javier Martinez Canillas <javier@osg.samsung.com> - 2016-08-19 04:30 +0200
Re: [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() Arend van Spriel <arend.vanspriel@broadcom.com> - 2016-08-19 03:10 +0200
Re: [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() Javier Martinez Canillas <javier@osg.samsung.com> - 2016-08-19 03:40 +0200
| From | Javier Martinez Canillas <javier@osg.samsung.com> |
|---|---|
| Date | 2016-08-18 16:30 +0200 |
| Subject | [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() |
| Message-ID | <s7wuv-WK-63@gated-at.bofh.it> |
If request_irq() fails in mwifiex_sdio_probe_of(), only an error message is printed but the actual error is not propagated to the caller function. Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> --- drivers/net/wireless/marvell/mwifiex/sdio.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/marvell/mwifiex/sdio.c b/drivers/net/wireless/marvell/mwifiex/sdio.c index d3e1561ca075..00727936ad6e 100644 --- a/drivers/net/wireless/marvell/mwifiex/sdio.c +++ b/drivers/net/wireless/marvell/mwifiex/sdio.c @@ -125,6 +125,7 @@ static int mwifiex_sdio_probe_of(struct device *dev, struct sdio_mmc_card *card) dev_err(dev, "Failed to request irq_wifi %d (%d)\n", cfg->irq_wifi, ret); + return ret; } disable_irq(cfg->irq_wifi); } -- 2.5.5
[toc] | [next] | [standalone]
| From | Arend van Spriel <arend.vanspriel@broadcom.com> |
|---|---|
| Date | 2016-08-19 03:00 +0200 |
| Subject | Re: [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() |
| Message-ID | <s7Gka-6XF-9@gated-at.bofh.it> |
| In reply to | #1465526 |
On 18-08-16 21:29, Javier Martinez Canillas wrote: > Hello Arend, > > Thanks a lot for your feedback. > > On 08/18/2016 03:14 PM, Arend van Spriel wrote: >> On 18-08-16 16:17, Javier Martinez Canillas wrote: >>> If request_irq() fails in mwifiex_sdio_probe_of(), only an error message >>> is printed but the actual error is not propagated to the caller function. >> >> Hmm. The caller function, ie. mwifiex_sdio_probe(), does not seem to care. >> > > Hmm, I'm not so sure about that. It's checking the wifiex_sdio_probe_of() > return value. Ok. I looked at 4.7 sources on lxr [1]. > If the IRQ request failing is not an error, then at the very least the call > to disable_irq() should be avoided if request_irq() fails, and the message > should be changed from dev_err() to dev_dgb() or dev_info(). agree. >> The device may still function without this wake interrupt. >> > > That's correct, the binding says that the "interrupts" property in the child > node is optional since is just a wakeup IRQ. Now the question is if should > be an error if the IRQ is defined but fails to be requested. Clearly it indicates an error in the DT specification so behavior is not as expected. Personally I would indeed consider it an error, but I was just indicating that it might have done like this intentionally. Regards, Arend [1] http://lxr.free-electrons.com/source/drivers/net/wireless/marvell/mwifiex/sdio.c#L192 >> Regards, >> Arend >> > > Best regards, >
[toc] | [prev] | [next] | [standalone]
| From | Javier Martinez Canillas <javier@osg.samsung.com> |
|---|---|
| Date | 2016-08-19 04:30 +0200 |
| Subject | Re: [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() |
| Message-ID | <s7HJf-84B-3@gated-at.bofh.it> |
| In reply to | #1465674 |
Hello Arend, On 08/18/2016 03:49 PM, Arend van Spriel wrote: > > > On 18-08-16 21:29, Javier Martinez Canillas wrote: >> Hello Arend, >> >> Thanks a lot for your feedback. >> >> On 08/18/2016 03:14 PM, Arend van Spriel wrote: >>> On 18-08-16 16:17, Javier Martinez Canillas wrote: >>>> If request_irq() fails in mwifiex_sdio_probe_of(), only an error message >>>> is printed but the actual error is not propagated to the caller function. >>> >>> Hmm. The caller function, ie. mwifiex_sdio_probe(), does not seem to care. >>> >> >> Hmm, I'm not so sure about that. It's checking the wifiex_sdio_probe_of() >> return value. > > Ok. I looked at 4.7 sources on lxr [1]. > Oh, right. That was fixed quite recently indeed. >> If the IRQ request failing is not an error, then at the very least the call >> to disable_irq() should be avoided if request_irq() fails, and the message >> should be changed from dev_err() to dev_dgb() or dev_info(). > > agree. > >>> The device may still function without this wake interrupt. >>> >> >> That's correct, the binding says that the "interrupts" property in the child >> node is optional since is just a wakeup IRQ. Now the question is if should >> be an error if the IRQ is defined but fails to be requested. > > Clearly it indicates an error in the DT specification so behavior is not > as expected. Personally I would indeed consider it an error, but I was > just indicating that it might have done like this intentionally. > Yes, might had been done intentionally indeed but I don't think that is the case since the driver lacked error checking and propagation in many places. But if someone thinks that's better to not honor the DT and at least have the driver working without the wake up capability, then I'm happy to respin the patch and change the print log level to info/debug. > Regards, > Arend > Best regards, -- Javier Martinez Canillas Open Source Group Samsung Research America
[toc] | [prev] | [next] | [standalone]
| From | Arend van Spriel <arend.vanspriel@broadcom.com> |
|---|---|
| Date | 2016-08-19 03:10 +0200 |
| Subject | Re: [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() |
| Message-ID | <s7Gka-6XF-11@gated-at.bofh.it> |
| In reply to | #1465526 |
On 18-08-16 16:17, Javier Martinez Canillas wrote: > If request_irq() fails in mwifiex_sdio_probe_of(), only an error message > is printed but the actual error is not propagated to the caller function. Hmm. The caller function, ie. mwifiex_sdio_probe(), does not seem to care. The device may still function without this wake interrupt. Regards, Arend > Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> > --- > > drivers/net/wireless/marvell/mwifiex/sdio.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/net/wireless/marvell/mwifiex/sdio.c b/drivers/net/wireless/marvell/mwifiex/sdio.c > index d3e1561ca075..00727936ad6e 100644 > --- a/drivers/net/wireless/marvell/mwifiex/sdio.c > +++ b/drivers/net/wireless/marvell/mwifiex/sdio.c > @@ -125,6 +125,7 @@ static int mwifiex_sdio_probe_of(struct device *dev, struct sdio_mmc_card *card) > dev_err(dev, > "Failed to request irq_wifi %d (%d)\n", > cfg->irq_wifi, ret); > + return ret; > } > disable_irq(cfg->irq_wifi); > } >
[toc] | [prev] | [next] | [standalone]
| From | Javier Martinez Canillas <javier@osg.samsung.com> |
|---|---|
| Date | 2016-08-19 03:40 +0200 |
| Subject | Re: [PATCH] mwifiex: propagate error if IRQ request fails in mwifiex_sdio_of() |
| Message-ID | <s7Gka-6XF-13@gated-at.bofh.it> |
| In reply to | #1465702 |
Hello Arend, Thanks a lot for your feedback. On 08/18/2016 03:14 PM, Arend van Spriel wrote: > On 18-08-16 16:17, Javier Martinez Canillas wrote: >> If request_irq() fails in mwifiex_sdio_probe_of(), only an error message >> is printed but the actual error is not propagated to the caller function. > > Hmm. The caller function, ie. mwifiex_sdio_probe(), does not seem to care. > Hmm, I'm not so sure about that. It's checking the wifiex_sdio_probe_of() return value. If the IRQ request failing is not an error, then at the very least the call to disable_irq() should be avoided if request_irq() fails, and the message should be changed from dev_err() to dev_dgb() or dev_info(). > The device may still function without this wake interrupt. > That's correct, the binding says that the "interrupts" property in the child node is optional since is just a wakeup IRQ. Now the question is if should be an error if the IRQ is defined but fails to be requested. > Regards, > Arend > Best regards, -- Javier Martinez Canillas Open Source Group Samsung Research America
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web