From: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org"
<linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
"khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org"
<khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org"
<swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Matthew Longnecker
<MLongnecker-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org"
<lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>,
"linux-kernel-u79uwXL29TZX6JHB/w77yyCwEArCW2h5@public.gmane.org"
<linux-kernel-u79uwXL29TZX6JHB/w77yyCwEArCW2h5@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/3] hwmon: (lm90) add support to handle irq
Date: Tue, 9 Jul 2013 15:58:54 +0800 [thread overview]
Message-ID: <51DBC2BE.6050000@nvidia.com> (raw)
In-Reply-To: <20130709061514.GB17499@mithrandir>
On 07/09/2013 02:15 PM, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Thu, Jul 04, 2013 at 03:57:49PM +0800, Wei Ni wrote:
>> Add support to handle irq. When the temperature touch
>
> Nit: This first sentence can be dropped. It merely repeats the subject.
> And another nit: "irq" -> "IRQ"
Ok, I will update in my next version.
>
>> the limit value, the driver can handle the interrupt.
>>
>> Signed-off-by: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>> ---
>> drivers/hwmon/lm90.c | 25 +++++++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>>
>> diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c
>> index 2cb7f8e..fce9dfa 100644
>> --- a/drivers/hwmon/lm90.c
>> +++ b/drivers/hwmon/lm90.c
>> @@ -89,6 +89,7 @@
>> #include <linux/err.h>
>> #include <linux/mutex.h>
>> #include <linux/sysfs.h>
>> +#include <linux/interrupt.h>
>>
>> /*
>> * Addresses to scan
>> @@ -1423,6 +1424,18 @@ static void lm90_init_client(struct i2c_client *client)
>> i2c_smbus_write_byte_data(client, LM90_REG_W_CONFIG1, config);
>> }
>>
>> +static void lm90_alert(struct i2c_client *client, unsigned int flag);
>
> Any reason why the implementation of lm90_alert() can't be moved here.
> Granted, it'll make the diff larger but at least it'll allow us to get
> rid of the forward declaration.
Ok, you are right, I will move it.
>
>> +static irqreturn_t lm90_irq_thread(int irq, void *dev_id)
>> +{
>> + struct lm90_data *data = dev_id;
>> + struct i2c_client *client = to_i2c_client(data->hwmon_dev->parent);
>> +
>> + lm90_alert(client, 0);
>> +
>> + return IRQ_HANDLED;
>> +}
>
> Isn't this potentially dangerous, since if the IRQ was shared, IRQ
> processing will always stop after this handler. Shouldn't you check
> whether the device actually triggered an interrupt (by reading the
> interrupt status register)?
Yes, it has potential dangerous, I didn't consider it carefully.
I will check the interrupt status.
>
>> +
>> static int lm90_probe(struct i2c_client *client,
>> const struct i2c_device_id *id)
>> {
>> @@ -1499,6 +1512,18 @@ static int lm90_probe(struct i2c_client *client,
>> goto exit_remove_files;
>> }
>>
>> + if (client->irq >= 0) {
>> + dev_dbg(dev, "lm90 irq: %d\n", client->irq);
>
> Nit: "irq" -> "IRQ"
Ok, got it.
>
> Thierry
>
> * Unknown Key
> * 0x7F3EB3A1
>
WARNING: multiple messages have this Message-ID (diff)
From: Wei Ni <wni@nvidia.com>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org"
<linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
"khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org"
<khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org"
<swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Matthew Longnecker
<MLongnecker-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org"
<lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>,
"linux-kernel-u79uwXL29TZX6JHB/w77yyCwEArCW2h5@public.gmane.org"
<linux-kernel-u79uwXL29TZX6JHB/w77yyCwEArCW2h5@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [lm-sensors] [PATCH 2/3] hwmon: (lm90) add support to handle irq
Date: Tue, 09 Jul 2013 07:58:54 +0000 [thread overview]
Message-ID: <51DBC2BE.6050000@nvidia.com> (raw)
In-Reply-To: <20130709061514.GB17499@mithrandir>
On 07/09/2013 02:15 PM, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Thu, Jul 04, 2013 at 03:57:49PM +0800, Wei Ni wrote:
>> Add support to handle irq. When the temperature touch
>
> Nit: This first sentence can be dropped. It merely repeats the subject.
> And another nit: "irq" -> "IRQ"
Ok, I will update in my next version.
>
>> the limit value, the driver can handle the interrupt.
>>
>> Signed-off-by: Wei Ni <wni@nvidia.com>
>> ---
>> drivers/hwmon/lm90.c | 25 +++++++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>>
>> diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c
>> index 2cb7f8e..fce9dfa 100644
>> --- a/drivers/hwmon/lm90.c
>> +++ b/drivers/hwmon/lm90.c
>> @@ -89,6 +89,7 @@
>> #include <linux/err.h>
>> #include <linux/mutex.h>
>> #include <linux/sysfs.h>
>> +#include <linux/interrupt.h>
>>
>> /*
>> * Addresses to scan
>> @@ -1423,6 +1424,18 @@ static void lm90_init_client(struct i2c_client *client)
>> i2c_smbus_write_byte_data(client, LM90_REG_W_CONFIG1, config);
>> }
>>
>> +static void lm90_alert(struct i2c_client *client, unsigned int flag);
>
> Any reason why the implementation of lm90_alert() can't be moved here.
> Granted, it'll make the diff larger but at least it'll allow us to get
> rid of the forward declaration.
Ok, you are right, I will move it.
>
>> +static irqreturn_t lm90_irq_thread(int irq, void *dev_id)
>> +{
>> + struct lm90_data *data = dev_id;
>> + struct i2c_client *client = to_i2c_client(data->hwmon_dev->parent);
>> +
>> + lm90_alert(client, 0);
>> +
>> + return IRQ_HANDLED;
>> +}
>
> Isn't this potentially dangerous, since if the IRQ was shared, IRQ
> processing will always stop after this handler. Shouldn't you check
> whether the device actually triggered an interrupt (by reading the
> interrupt status register)?
Yes, it has potential dangerous, I didn't consider it carefully.
I will check the interrupt status.
>
>> +
>> static int lm90_probe(struct i2c_client *client,
>> const struct i2c_device_id *id)
>> {
>> @@ -1499,6 +1512,18 @@ static int lm90_probe(struct i2c_client *client,
>> goto exit_remove_files;
>> }
>>
>> + if (client->irq >= 0) {
>> + dev_dbg(dev, "lm90 irq: %d\n", client->irq);
>
> Nit: "irq" -> "IRQ"
Ok, got it.
>
> Thierry
>
> * Unknown Key
> * 0x7F3EB3A1
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2013-07-09 7:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 7:57 [PATCH 0/3] Lm90 Enhancements Wei Ni
2013-07-04 7:57 ` [lm-sensors] " Wei Ni
[not found] ` <1372924670-16355-1-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-07-04 7:57 ` [PATCH 1/3] hwmon: (lm90) split set&show temp as common codes Wei Ni
2013-07-04 7:57 ` [lm-sensors] " Wei Ni
2013-07-04 7:57 ` [PATCH 2/3] hwmon: (lm90) add support to handle irq Wei Ni
2013-07-04 7:57 ` [lm-sensors] " Wei Ni
[not found] ` <1372924670-16355-3-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-07-05 17:35 ` Stephen Warren
2013-07-05 17:35 ` [lm-sensors] " Stephen Warren
[not found] ` <51D703C9.1060607-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-07-05 19:47 ` Guenter Roeck
2013-07-05 19:47 ` [lm-sensors] " Guenter Roeck
[not found] ` <20130705194728.GA24946-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-08 15:46 ` Stephen Warren
2013-07-08 15:46 ` [lm-sensors] " Stephen Warren
[not found] ` <51DADEE1.1030408-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-07-08 20:06 ` Guenter Roeck
2013-07-08 20:06 ` [lm-sensors] " Guenter Roeck
[not found] ` <20130708200623.GA1506-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-09 7:54 ` Wei Ni
2013-07-09 7:54 ` [lm-sensors] " Wei Ni
2013-07-09 6:15 ` Thierry Reding
2013-07-09 6:15 ` [lm-sensors] " Thierry Reding
2013-07-09 6:49 ` Jean Delvare
2013-07-09 6:49 ` [lm-sensors] " Jean Delvare
2013-07-09 7:58 ` Wei Ni [this message]
2013-07-09 7:58 ` Wei Ni
2013-07-04 7:57 ` [PATCH 3/3] hwmon: (lm90) use enums for the indexes of temp8 and temp11 Wei Ni
2013-07-04 7:57 ` [lm-sensors] " Wei Ni
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=51DBC2BE.6050000@nvidia.com \
--to=wni-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=MLongnecker-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TZX6JHB/w77yyCwEArCW2h5@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.