linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: minyard@acm.org, linux-i2c@vger.kernel.org,
	Corey Minyard <cminyard@mvista.com>
Subject: Re: [PATCH] i2c-smbus: Don't report duplicate alerts
Date: Fri, 04 Mar 2016 11:15:57 +0100	[thread overview]
Message-ID: <1457086557.4527.15.camel@chaos.site> (raw)
In-Reply-To: <20160303205754.GE1711@katana>

Le Thursday 03 March 2016 à 21:57 +0100, Wolfram Sang a écrit :
> On Tue, Jan 19, 2016 at 11:00:48AM -0600, minyard@acm.org wrote:
> > From: Corey Minyard <cminyard@mvista.com>
> > 
> > Getting the same alert twice in a row is legal and normal,
> > especially on a fast device (like running in qemu).  Kind of
> > like interrupts.  So don't report duplicate alerts, and deliver
> > them normally.
> > 
> > Signed-off-by: Corey Minyard <cminyard@mvista.com>
> 
> Looks plausible to me, but I never used SMBALERT myself. Any chance this
> can cause a regression? Jean, what do you think?

I'm afraid I had a good reason to add this check back then. I'll test
with my ADM1032 evaluation board when I get back home (tomorrow at the
earliest.) Maybe my hardware was misbehaving, in which case I agree any
filtering should be done at the device driver level. But I must double
check what the SMBus specification says too.

Either way the patch's subject is misleading. Should be "Don't filter
out duplicate alerts" or something like that.

> > ---
> >  drivers/i2c/i2c-smbus.c | 7 -------
> >  1 file changed, 7 deletions(-)
> > 
> > diff --git a/drivers/i2c/i2c-smbus.c b/drivers/i2c/i2c-smbus.c
> > index 94765a8..cecd423 100644
> > --- a/drivers/i2c/i2c-smbus.c
> > +++ b/drivers/i2c/i2c-smbus.c
> > @@ -75,7 +75,6 @@ static void smbus_alert(struct work_struct *work)
> >  {
> >  	struct i2c_smbus_alert *alert;
> >  	struct i2c_client *ara;
> > -	unsigned short prev_addr = 0;	/* Not a valid address */
> >  
> >  	alert = container_of(work, struct i2c_smbus_alert, alert);
> >  	ara = alert->ara;
> > @@ -99,18 +98,12 @@ static void smbus_alert(struct work_struct *work)
> >  		data.flag = status & 1;
> >  		data.addr = status >> 1;
> >  
> > -		if (data.addr == prev_addr) {
> > -			dev_warn(&ara->dev, "Duplicate SMBALERT# from dev "
> > -				"0x%02x, skipping\n", data.addr);
> > -			break;
> > -		}
> >  		dev_dbg(&ara->dev, "SMBALERT# from dev 0x%02x, flag %d\n",
> >  			data.addr, data.flag);
> >  
> >  		/* Notify driver for the device which issued the alert */
> >  		device_for_each_child(&ara->adapter->dev, &data,
> >  				      smbus_do_alert);
> > -		prev_addr = data.addr;
> >  	}
> >  
> >  	/* We handled all alerts; re-enable level-triggered IRQs */


-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2016-03-04 10:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 17:00 [PATCH] i2c-smbus: Don't report duplicate alerts minyard
2016-03-03 20:57 ` Wolfram Sang
2016-03-04 10:15   ` Jean Delvare [this message]
2016-04-27 14:28     ` Corey Minyard
2016-06-19 12:06       ` Wolfram Sang
2016-06-20  9:31         ` Benjamin Tissoires

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=1457086557.4527.15.camel@chaos.site \
    --to=jdelvare@suse.de \
    --cc=cminyard@mvista.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=minyard@acm.org \
    --cc=wsa@the-dreams.de \
    /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;
as well as URLs for NNTP newsgroup(s).