linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: piix4_smbus: How to deal with conflicting ACPI regions?
Date: Tue, 16 Jul 2013 01:04:13 +0200	[thread overview]
Message-ID: <1373929453.12205.1.camel@mattotaupa> (raw)

[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]

Dear Linux folks,


using coreboot on the ASRock E350M1, the ACPI table contains the
following [1].

        $ more src/mainboard/asrock/e350m1/acpi/smbus.asl
        […]
        /* SMBUS Support */
        Mutex (SBX0, 0x00)
        OperationRegion (SMB0, SystemIO, 0xB00, 0x0C)
        	Field (SMB0, ByteAcc, NoLock, Preserve) {
        		HSTS,   8,  /* SMBUS status */
        		SSTS,   8,  /* SMBUS slave status */
        		HCNT,   8,  /* SMBUS control */
        		HCMD,   8,  /* SMBUS host cmd */
        		HADD,   8,  /* SMBUS address */
        		DAT0,   8,  /* SMBUS data0 */
        		DAT1,   8,  /* SMBUS data1 */
        		BLKD,   8,  /* SMBUS block data */
        		SCNT,   8,  /* SMBUS slave control */
        		SCMD,   8,  /* SMBUS shaow cmd */
        		SEVT,   8,  /* SMBUS slave event */
        		SDAT,   8   /* SMBUS slave data */
        }
        
        Method (WCLR, 0, NotSerialized) { /* clear SMBUS status register */
        	Store (0x1E, HSTS)
        	Store (0xFA, Local0)
        	While (LAnd (LNotEqual (And (HSTS, 0x1E), Zero), LGreater (Local0, Zero))) {
        		Stall (0x64)
        		Decrement (Local0)
        	}
        
        	Return (Local0)
        }

This causes a conflict later with piix4_smbus.

        ACPI: resource piix4_smbus [io  0x0b00-0x0b07] conflicts with ACPI region SMB0 [io 0xb00-0xb0b]

And the log message tells me to use an ACPI driver, if available.

Is there such a driver? I ask, because I was not able to find one. Would
that work with `decode-dimms`?

If the above is not possible, would the workaround be to remove the ACPI
SMBus configuration?


Thanks,

Paul


[1] http://review.coreboot.org/gitweb?p=coreboot.git;a=blob;f=src/mainboard/asrock/e350m1/acpi/e350m1/acpi/smbus.asl;h=e4ccfe3467c1b49edbf21b11add62872286684ed;hb=HEAD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2013-07-15 23:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1373929453.12205.1.camel@mattotaupa \
    --to=paulepanter-rn4veauk+akrv+lv9mx5uipxlwaovq5f@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 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).