From: Wei Ni <wni@nvidia.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: "linux@roeck-us.net" <linux@roeck-us.net>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v4 2/3] hwmon: (lm90) add support to handle IRQ
Date: Mon, 4 Nov 2013 18:05:59 +0800 [thread overview]
Message-ID: <52777187.5010202@nvidia.com> (raw)
In-Reply-To: <20131104103434.5a085e27@endymion.delvare>
On 11/04/2013 05:34 PM, Jean Delvare wrote:
> Hi Wei,
>
> I'm hitting a problem with that patch now...
>
> On Wed, 7 Aug 2013 14:18:25 +0800, Wei Ni wrote:
>> When the temperature exceed the limit range value,
>> the driver can handle the interrupt.
>>
>> Signed-off-by: Wei Ni <wni@nvidia.com>
>> ---
>> drivers/hwmon/lm90.c | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>>
>> diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c
>> index 1da2eff..2e68773 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
>> @@ -1433,6 +1434,16 @@ static bool lm90_is_tripped(struct i2c_client *client)
>> return true;
>> }
>>
>> +static irqreturn_t lm90_irq_thread(int irq, void *dev_id)
>> +{
>> + struct i2c_client *client = dev_id;
>> +
>> + if (lm90_is_tripped(client))
>
> Did you really send the latest version of the patch? lm90_is_tripped()
> takes two arguments now, but here you only pass one.
>
> If you have a more up-to-date version of this patch, please send it
> over quickly.
Hi, Jean
It's so sorry. As you know I resend the "[PATCH RESEND v4 1/3] hwmon:
(lm90) Define status bits" last week, but didn't rebase this patch. I
will rebase it and send it right now.
Wei.
Thanks.
>
>> + return IRQ_HANDLED;
>> + else
>> + return IRQ_NONE;
>> +}
>> +
>> static int lm90_probe(struct i2c_client *client,
>> const struct i2c_device_id *id)
>> {
>> @@ -1509,6 +1520,18 @@ static int lm90_probe(struct i2c_client *client,
>> goto exit_remove_files;
>> }
>>
>> + if (client->irq) {
>> + dev_dbg(dev, "IRQ: %d\n", client->irq);
>> + err = devm_request_threaded_irq(dev, client->irq,
>> + NULL, lm90_irq_thread,
>> + IRQF_TRIGGER_LOW | IRQF_ONESHOT,
>> + "lm90", client);
>> + if (err < 0) {
>> + dev_err(dev, "cannot request IRQ: %d\n", client->irq);
>> + goto exit_remove_files;
>> + }
>> + }
>> +
>> return 0;
>>
>> exit_remove_files:
>
>
next prev parent reply other threads:[~2013-11-04 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 6:18 [PATCH v4 0/3] Lm90 Enhancements Wei Ni
2013-08-07 6:18 ` [PATCH v4 1/3] hwmon: (lm90) Define status bits Wei Ni
2013-10-30 15:41 ` Jean Delvare
2013-10-30 17:03 ` Guenter Roeck
2013-10-31 2:47 ` Wei Ni
2013-10-31 3:09 ` Wei Ni
2013-08-07 6:18 ` [PATCH v4 2/3] hwmon: (lm90) add support to handle IRQ Wei Ni
2013-10-30 15:53 ` Jean Delvare
2013-11-04 9:34 ` Jean Delvare
2013-11-04 10:05 ` Wei Ni [this message]
2013-08-07 6:18 ` [PATCH v4 3/3] hwmon: (lm90) use enums for the indexes of temp8 and temp11 Wei Ni
2013-10-30 16:21 ` Jean Delvare
2013-09-09 6:16 ` [PATCH v4 0/3] Lm90 Enhancements Wei Ni
2013-09-09 7:42 ` 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=52777187.5010202@nvidia.com \
--to=wni@nvidia.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.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;
as well as URLs for NNTP newsgroup(s).