All of lore.kernel.org
 help / color / mirror / Atom feed
From: "richardvoigt@gmail.com" <richardvoigt@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] (no subject)
Date: Wed, 11 Jul 2012 15:26:30 +0000	[thread overview]
Message-ID: <CAO_2OxXdVraavs-Lwo4XYaq5m5Uk8t466ZQ_LAKVH=6SfkZ3+g@mail.gmail.com> (raw)
In-Reply-To: <200703231349.l2NDnj1q025087@whb1.seed.net.tw>

If the purpose is to clear a single bit, wouldn't code of the form

    old & ~bit

be better?

On Wed, Jul 11, 2012 at 9:45 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> On Wed, Jul 11, 2012 at 04:16:21PM +0200, Stevie Trujillo wrote:
> [ ... ]
>>
>> > If that works, then please unload the driver and reload with write=2.
>> > This will log every register write right before it happens. So the last
>> > message logged is likely to point to a register write which is
>> > inappropriate for your device/board.
>>
>> I only see these lines:
>> [  265.408976] it87: Found IT8728F chip at 0xa30, revision 1
>> [  265.410655] it87: Beeping is supported
>> [  265.411583] it87: Writing value 0x37 to register 0x0c
>> [  265.423124] it87: Writing value 0x13 to register 0x00
>>
> Jean,
>
> it87_write_value(data, IT87_REG_CONFIG,
>                  (it87_read_value(data, IT87_REG_CONFIG) & 0x36)
>                         | (update_vbat ? 0x41 : 0x01));
>
> Unless I am missing something, the above code enables interrupts by clearing
> bit 3. In combination with having bit 1 set, this means that SMI# interrupts
> will be enabled. Default value for the register, at least for IT8721F and
> IT8718F, is 0x18. Replacing the 0x36 mask above with 0x3e might possibly solve
> the problem.
>
> Guenter
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2012-07-11 15:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703231349.l2NDnj1q025087@whb1.seed.net.tw>
2007-07-24 14:40 ` [lm-sensors] (no subject) cilly
2009-11-09  3:39 ` jack
2012-02-29  9:23 ` sravan vasu
2012-02-29 14:40 ` Guenter Roeck
2012-04-23 20:35 ` Crunchy Toast
2012-04-25  7:18 ` Mr. Tux
2012-07-11 14:16 ` Stevie Trujillo
2012-07-11 14:45 ` Guenter Roeck
2012-07-11 15:26 ` richardvoigt [this message]
2005-05-29 14:39 John WICKS
2008-09-23 13:29 ` gaming
2011-05-04  7:03 ` Jeremy Harmon
2011-05-06 18:52 ` Nat Gurumoorthy
2011-05-06 19:13   ` Guenter Roeck
2011-05-06 20:00     ` Natarajan Gurumoorthy
2011-05-10 18:53 ` Jeremy Harmon
2011-11-26 18:26 ` su_pyrow
2011-12-08 18:31 ` Guenter Roeck
2011-12-08 18:36 ` Guenter Roeck
2012-11-07 20:09 ` 郭�园
2012-12-04  7:22 ` Dok Sander
2013-08-23 23:53 ` Robert Hinson
2013-10-29 17:51 ` morgan chong

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='CAO_2OxXdVraavs-Lwo4XYaq5m5Uk8t466ZQ_LAKVH=6SfkZ3+g@mail.gmail.com' \
    --to=richardvoigt@gmail.com \
    --cc=lm-sensors@vger.kernel.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.