public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/4] i2c-i801: Fallback to polling if request_irq() fails
Date: Tue, 11 Nov 2014 14:55:24 +0100	[thread overview]
Message-ID: <20141111145524.318e700d@endymion.delvare> (raw)
In-Reply-To: <20141111105734.GA3794@katana>

Hi Wolfram,

Thanks for the quick review, very appreciated.

On Tue, 11 Nov 2014 11:57:34 +0100, Wolfram Sang wrote:
> On Mon, Nov 10, 2014 at 10:31:04PM +0100, Jean Delvare wrote:
> > The i2c-i801 driver can work without interrupts, so there is no reason
> > to make a request_irq failure fatal. Instead we can simply fallback
> > to polling.
> > 
> > Signed-off-by: Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>
> > Cc: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
> > ---
> >  drivers/i2c/busses/i2c-i801.c |    7 ++++---
> >  1 file changed, 4 insertions(+), 3 deletions(-)
> > 
> > --- linux-3.18-rc4.orig/drivers/i2c/busses/i2c-i801.c	2014-11-10 22:29:42.788955868 +0100
> > +++ linux-3.18-rc4/drivers/i2c/busses/i2c-i801.c	2014-11-10 22:29:44.416991298 +0100
> > @@ -1242,9 +1242,11 @@ static int i801_probe(struct pci_dev *de
> >  		if (err) {
> >  			dev_err(&dev->dev, "Failed to allocate irq %d: %d\n",
> >  				dev->irq, err);
> > -			goto exit_release;
> > +			priv->features &= ~FEATURE_IRQ;
> > +			dev_info(&dev->dev, "SMBus using polling\n");
> 
> Shouldn't this message also be printed for !FEATURE_IRQ? I'd think it
> should be moved to another place.

Good point, I'll rework that part of the code and resubmit.

> We can also deduce from the dev_err
> above that polling will be used, no?

Having to deduce things doesn't make my supporter's life easy. Given
the problems that have been reported by the i2c-i801 driver users
lately, I'd rather be verbose during initialization to make bug reports
easier to analyze.

> > +		} else {
> > +			dev_info(&dev->dev, "SMBus using PCI interrupt\n");
> >  		}
> > -		dev_info(&dev->dev, "SMBus using PCI Interrupt\n");
> >  	}
> >  
> >  	/* set up the sysfs linkage to our parent device */
> > @@ -1272,7 +1274,6 @@ static int i801_probe(struct pci_dev *de
> >  exit_free_irq:
> >  	if (priv->features & FEATURE_IRQ)
> >  		free_irq(dev->irq, priv);
> > -exit_release:
> >  	pci_release_region(dev, SMBBAR);
> >  exit:
> >  	kfree(priv);
> > 

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2014-11-11 13:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 21:26 [PATCH 0/4] i2c-i801: Make interrupt mode more robust Jean Delvare
     [not found] ` <20141110222655.13660613-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-11-10 21:30   ` [PATCH 1/4] i2c-i801: Use wait_event_timeout to wait for interrupts Jean Delvare
2014-11-10 21:31   ` [PATCH 2/4] i2c-i801: Fallback to polling if request_irq() fails Jean Delvare
     [not found]     ` <20141110223104.6419229d-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-11-11 10:57       ` Wolfram Sang
2014-11-11 13:55         ` Jean Delvare [this message]
2014-11-10 21:31   ` [PATCH 3/4] i2c-i801: Check if interrupts are disabled Jean Delvare
     [not found]     ` <20141110223139.02aafde4-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-11-11 10:58       ` Wolfram Sang
2014-11-11 14:32         ` Jean Delvare
     [not found]           ` <20141111153214.39dfaeb8-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-11-11 14:41             ` Wolfram Sang
2014-11-11 20:06               ` Jean Delvare
     [not found]                 ` <20141111210646.02b77c68-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-11-11 20:13                   ` Wolfram Sang
2014-11-10 21:32   ` [PATCH 4/4] i2c-i801: Drop useless debug message Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141111145524.318e700d@endymion.delvare \
    --to=jdelvare-l3a5bk7wagm@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox