All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] PIIX4 and fix_hstcfg
Date: Sat, 01 Apr 2006 15:25:24 +0000	[thread overview]
Message-ID: <442E9B64.50909@sh.cvut.cz> (raw)

Hello all,

We have in the i2-piix4 the fix_hstcfg option and it seems we should move it to pci/quirks.c
The new serverworks chipsets do not need it and because they have bit different interrupt select
field the message about fix_hstcfg will appear. And if the user do it it wont work or freeze.

As to remind I created this modified table with the serverworks int bit in place:

Address Offset:         D2h
Default Value:          00h
Attribute:              Read/Write
    Bit                                               Description
    7:4    Reserved.
    3:1    SMBus Interrupt Select (SMB_INTRSEL)--R/W. Selects the type of interrupt generated by the
           SMBus controller. This field is decoded as follows:
           Bits[3:1]      SMBus Interrupt                Bits[3:1] SMBus Interrupt
              000         SMI#                             100     IRQ9
              001         Serverworks IRQ                  101     Reserved
              010         Reserved                         110     Reserved
              011         Reserved                         111     Reserved
     0     SMBus Controller Host Interface Enable (SMB_HST_EN)--R/W. 1=Enable the SMBus
           Controller Host Interface. 0=Disable.

 if (fix_hstcfg) {
                        dev_info(&PIIX4_dev->dev, "Working around buggy BIOS "
                                        "(I2C)\n");
                        temp &= 0xfd;

So this just cleans bit 1 effectively switching the serverworks IRQ mode to SMI (in fact) (If I remember correctly the motherboard
had some incarnation of serverworks chipset.)

Tom, please can you supply the lspci -v -v -v of that machine so a quirk can be developed?

If you dont have the machine anymore I think we can drop that option anyway because I googled hard and it seemed nobody else had
similar problems.

Regards
Rudolf



             reply	other threads:[~2006-04-01 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01 15:25 Rudolf Marek [this message]
2006-04-01 18:21 ` [lm-sensors] PIIX4 and fix_hstcfg Tom Rini
2006-04-01 18:34 ` Rudolf Marek
2006-04-01 18:54 ` Jean Delvare
2006-04-01 18:57 ` Rudolf Marek
2006-04-01 20:11 ` Tom Rini
2006-04-01 22:03 ` Rudolf Marek
2006-04-02  8:13 ` 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=442E9B64.50909@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.