linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Jonathan Corbet <corbet@lwn.net>, Corey Minyard <minyard@acm.org>,
	Jean Delvare <jdelvare@suse.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Duggan <aduggan@synaptics.com>,
	Christopher Heiny <cheiny@synaptics.com>,
	linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v5 1/4] i2c: add a protocol parameter to the alert callback
Date: Tue, 15 Mar 2016 21:08:48 +0100	[thread overview]
Message-ID: <20160315200848.GQ22340@mail.corp.redhat.com> (raw)
In-Reply-To: <20160315152940.GA5284@roeck-us.net>

On Mar 15 2016 or thereabouts, Guenter Roeck wrote:
> On Tue, Mar 15, 2016 at 03:53:41PM +0100, Benjamin Tissoires wrote:
> > .alert() is meant to be generic, but there is currently no way
> > for the device driver to know which protocol generated the alert.
> > Add a parameter in .alert() to help the device driver to understand
> > what is given in data.
> > 
> > This patch is required to have the support of SMBus Host Notify protocol
> > through .alert().
> > 
> > Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > ---
> >  drivers/char/ipmi/ipmi_ssif.c | 6 +++++-
> >  drivers/hwmon/lm90.c          | 3 ++-
> >  drivers/i2c/i2c-smbus.c       | 3 ++-
> >  include/linux/i2c.h           | 7 ++++++-
> >  4 files changed, 15 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/char/ipmi/ipmi_ssif.c b/drivers/char/ipmi/ipmi_ssif.c
> > index 5f1c3d0..84d07bc 100644
> > --- a/drivers/char/ipmi/ipmi_ssif.c
> > +++ b/drivers/char/ipmi/ipmi_ssif.c
> > @@ -568,12 +568,16 @@ static void retry_timeout(unsigned long data)
> >  }
> >  
> >  
> > -static void ssif_alert(struct i2c_client *client, unsigned int data)
> > +static void ssif_alert(struct i2c_client *client,
> > +		       enum i2c_alert_protocol protocol, unsigned int data)
> >  {
> >  	struct ssif_info *ssif_info = i2c_get_clientdata(client);
> >  	unsigned long oflags, *flags;
> >  	bool do_get = false;
> >  
> > +	if (protocol != I2C_PROTOCOL_SMBUS_ALERT)
> > +		return;
> > +
> >  	ssif_inc_stat(ssif_info, alerts);
> >  
> >  	flags = ipmi_ssif_lock_cond(ssif_info, &oflags);
> > diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c
> > index c9ff08d..2b77dbd 100644
> > --- a/drivers/hwmon/lm90.c
> > +++ b/drivers/hwmon/lm90.c
> > @@ -1624,7 +1624,8 @@ static int lm90_remove(struct i2c_client *client)
> >  	return 0;
> >  }
> >  
> > -static void lm90_alert(struct i2c_client *client, unsigned int flag)
> > +static void lm90_alert(struct i2c_client *client, enum i2c_alert_protocol type,
> > +		       unsigned int flag)
> >  {
> 
> For IPMI you added a check for the alert type. It would seem to be prudent to
> add one here as well, unless you expect the driver to be able to handle all
> alert types without modification. In that case, though, I would expect some
> note that this is the case.

Hi Guenter,

yes, this is a miss from my side. I'll update the series tomorrow.
Hopefully by then, the kbuild bot will find the remaining issues (2 in a
row is kind of shameful).

Cheers,
Benjamin

> 
> Thnaks,
> Guenter
> 
> >  	u16 alarms;
> >  
> > diff --git a/drivers/i2c/i2c-smbus.c b/drivers/i2c/i2c-smbus.c
> > index abb55d3..3b6765a 100644
> > --- a/drivers/i2c/i2c-smbus.c
> > +++ b/drivers/i2c/i2c-smbus.c
> > @@ -56,7 +56,8 @@ static int smbus_do_alert(struct device *dev, void *addrp)
> >  	if (client->dev.driver) {
> >  		driver = to_i2c_driver(client->dev.driver);
> >  		if (driver->alert)
> > -			driver->alert(client, data->flag);
> > +			driver->alert(client, I2C_PROTOCOL_SMBUS_ALERT,
> > +				      data->flag);
> >  		else
> >  			dev_warn(&client->dev, "no driver alert()!\n");
> >  	} else
> > diff --git a/include/linux/i2c.h b/include/linux/i2c.h
> > index 200cf13b..baae02a 100644
> > --- a/include/linux/i2c.h
> > +++ b/include/linux/i2c.h
> > @@ -126,6 +126,10 @@ i2c_smbus_read_i2c_block_data_or_emulated(const struct i2c_client *client,
> >  					  u8 command, u8 length, u8 *values);
> >  #endif /* I2C */
> >  
> > +enum i2c_alert_protocol {
> > +	I2C_PROTOCOL_SMBUS_ALERT,
> > +};
> > +
> >  /**
> >   * struct i2c_driver - represent an I2C device driver
> >   * @class: What kind of i2c device we instantiate (for detect)
> > @@ -181,7 +185,8 @@ struct i2c_driver {
> >  	 * For the SMBus alert protocol, there is a single bit of data passed
> >  	 * as the alert response's low bit ("event flag").
> >  	 */
> > -	void (*alert)(struct i2c_client *, unsigned int data);
> > +	void (*alert)(struct i2c_client *, enum i2c_alert_protocol protocol,
> > +		      unsigned int data);
> >  
> >  	/* a ioctl like command that can be used to perform specific functions
> >  	 * with the device.
> > -- 
> > 2.5.0
> > 

  reply	other threads:[~2016-03-15 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 14:53 [PATCH v5 0/4] i2c-smbus: add support for HOST NOTIFY Benjamin Tissoires
2016-03-15 14:53 ` [PATCH v5 1/4] i2c: add a protocol parameter to the alert callback Benjamin Tissoires
2016-03-15 15:29   ` Guenter Roeck
2016-03-15 20:08     ` Benjamin Tissoires [this message]
2016-03-15 14:53 ` [PATCH v5 2/4] i2c-smbus: add SMBus Host Notify support Benjamin Tissoires
2016-03-15 14:53 ` [PATCH v5 3/4] i2c: i801: add support of Host Notify Benjamin Tissoires
2016-03-15 15:35   ` kbuild test robot
2016-03-15 18:53   ` kbuild test robot
2016-03-15 14:53 ` [PATCH v5 4/4] Input: synaptics-rmi4 - add SMBus support 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=20160315200848.GQ22340@mail.corp.redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=aduggan@synaptics.com \
    --cc=cheiny@synaptics.com \
    --cc=corbet@lwn.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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).