From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Martin Mokrejs
<mmokrejs-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org>
Cc: mhoffman-xQSgfq/1h4JiLUuM0BA3LQ@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: i801_smbus: ... you should use it instead of the native driver
Date: Wed, 27 Jun 2012 11:33:30 +0200 [thread overview]
Message-ID: <20120627113330.1efc1862@endymion.delvare> (raw)
In-Reply-To: <4F7085DD.7050303-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org>
Dobry den Martine,
Sorry for the late reply.
On Mon, 26 Mar 2012 17:06:05 +0200, Martin Mokrejs wrote:
> Hi,
> I have the following message logged through syslog on a 2.6.32.59 kernel:
>
> Mar 26 11:21:55 vostro kernel: i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
> Mar 26 11:21:55 vostro kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>
>
> And here the relevant line from lspci:
> 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
>
> 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
> Subsystem: Dell Device 04b3
> Flags: medium devsel, IRQ 18
> Memory at f7f05000 (64-bit, non-prefetchable) [size=256]
> I/O ports at f040 [size=32]
> Kernel modules: i2c-i801
>
>
> So what driver should I use instead? This is a Dell Vostro 3550 laptop with Core i7 on
> a SandyBridge.
Unfortunately, in most cases there's nothing that can be done. The ACPI
BIOS has requested the SMBus controller for its own use. You can
disassemble your DSDT to see if it has good reasons for that.
Unfortunately most BIOSes that do this don't bother implementing a
standard ACPI interface to the SMBus controller for the operating
system's benefit. We have drivers for these standards (i2c-scmi and
sbshc), but it only helps on the rare machines which implement them.
So, as a summary, if your ACPI BIOS implements any device in ACPI0001,
ACPI0005 or SMBUS01, you may get SMBus to work, otherwise you won't,
sorry. Feel free to bring up the issue to your hardware vendor if this
bothers you.
--
Jean Delvare
prev parent reply other threads:[~2012-06-27 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 15:06 i801_smbus: ... you should use it instead of the native driver Martin Mokrejs
[not found] ` <4F7085DD.7050303-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org>
2012-06-27 9:33 ` Jean Delvare [this message]
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=20120627113330.1efc1862@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mhoffman-xQSgfq/1h4JiLUuM0BA3LQ@public.gmane.org \
--cc=mmokrejs-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@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).