All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rudolf Marek <r.marek@sh.cvut.cz>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] dme1737 0-002e: Write to register 0x30 failed!
Date: Tue, 23 Oct 2007 21:54:24 +0000	[thread overview]
Message-ID: <471E6D90.9050009@sh.cvut.cz> (raw)
In-Reply-To: <1642847378@web.de>

> etc etc. This appears to be the half-standard ATK0110 implementation
> for which a driver was posted to the lm-sensors list a few months ago.
> Maybe for this motherboard you should use this driver rather than the
> dme1737 driver. Adding Rudolf in Cc, I think he knows more about this
> driver's status.

Hmm dont know more it seems. Perhaps contact original author? Those ACPI 
routines are not called unless the TMP method for thermal stuff is called. So If 
there will be no readings from the acpi thermal sysfs/proc file the method will 
not run (in theory if the code is write like here)

> The DSDT also includes references to the nforce2's SMBus:
> 
>             Device (SMB0)
>             {
>                 Name (_ADR, 0x000A0001)
>                 OperationRegion (SMCF, PCI_Config, 0x48, 0x10)
>                 Field (SMCF, DWordAcc, NoLock, Preserve)
>                 {
>                     SMPM,   4, 
>                     SMT1,   28, 
>                     SMT2,   32
>                 }
> 
>                 OperationRegion (SMCA, PCI_Config, 0x20, 0x08)
>                 Field (SMCA, DWordAcc, NoLock, Preserve)
>                 {
>                     SB1,    32, 
>                     SB2,    32
>                 }
> 
>                 OperationRegion (PDEV, PCI_Config, 0xE8, 0x04)
>                 Scope (\)
>                 {
>                     Field (\_SB.PCI0.SMB0.PDEV, AnyAcc, NoLock, Preserve)
>                     {
>                             ,   12, 
>                         ACIE,   1
>                     }
>                 }
> 
>                 Method (SMBB, 0, NotSerialized)
>                 {
>                     If (PCIA)
>                     {
>                         And (SB1, 0xFFFE, Local0)
>                     }
>                     Else
>                     {
>                         Store (0x4C00, Local0)
>                     }
> 
>                     Return (Local0)
>                 }
>             }
> 
> So at the very least I'd say it's not safe to use the i2c-nforce2 and
> dme1737 drivers when the fan and thermal ACPI drivers are in use. But
> it may even not be safe when these ACPI drivers aren't loaded, I don't
> know.

It depends what methods are called. Imho if you remove the "thermal" support 
from the ACPI it should be ok. If someone gives me the table, I can take a look.

Rudolf

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

  parent reply	other threads:[~2007-10-23 21:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 19:08 [lm-sensors] dme1737 0-002e: Write to register 0x30 failed! Juergen Bausa
2007-10-01 17:44 ` Juerg Haefliger
2007-10-01 19:22 ` Juergen Bausa
2007-10-01 21:39 ` Juerg Haefliger
2007-10-01 21:50 ` Jean Delvare
2007-10-08 18:31 ` Juergen Bausa
2007-10-09  7:03 ` Jean Delvare
2007-10-09 16:08 ` Juerg Haefliger
2007-10-09 19:41 ` Juergen Bausa
2007-10-10 17:12 ` Juerg Haefliger
2007-10-11  7:45 ` Jean Delvare
2007-10-17 18:56 ` Juergen Bausa
2007-10-17 19:43 ` Juerg Haefliger
2007-10-17 21:32 ` Jean Delvare
2007-10-18  4:53 ` Juerg Haefliger
2007-10-19 15:07 ` Jean Delvare
2007-10-20 19:28 ` Juergen Bausa
2007-10-20 19:39 ` Juergen Bausa
2007-10-21 18:40 ` Mark M. Hoffman
2007-10-21 19:14 ` Jean Delvare
2007-10-21 19:37 ` Jean Delvare
2007-10-22 16:02 ` Juerg Haefliger
2007-10-22 16:05 ` Juerg Haefliger
2007-10-23 12:08 ` Jean Delvare
2007-10-23 12:22 ` Jean Delvare
2007-10-23 20:44 ` Juergen Bausa
2007-10-23 21:54 ` Rudolf Marek [this message]
2007-10-24  8:48 ` Jean Delvare
2007-10-29 21:23 ` Rudolf Marek
2007-10-30  2:52 ` Juerg Haefliger
2007-10-31  2:40 ` Juerg Haefliger

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=471E6D90.9050009@sh.cvut.cz \
    --to=r.marek@sh.cvut.cz \
    --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.