From: Hector Martin <marcan@marcan.st>
To: Alex Henrie <alexh@vpitech.com>
Cc: linux-i2c@vger.kernel.org, wsa@kernel.org, jdelvare@suse.de,
alexhenrie24@gmail.com
Subject: Re: [External] Re: [PATCH v3] i2c: i801: Safely share SMBus with BIOS/ACPI
Date: Sat, 18 Dec 2021 12:39:11 +0900 [thread overview]
Message-ID: <7fb63895-e8fb-c9c3-c5da-f922ae0c69fd@marcan.st> (raw)
In-Reply-To: <20211217195128.49285f55facfe061655a6279@vpitech.com>
On 18/12/2021 11.51, Alex Henrie wrote:
> On Fri, 17 Dec 2021 16:41:05 +0900
> Hector Martin <marcan@marcan.st> wrote:
>
>> On 17/12/2021 09.31, Alex Henrie wrote:
>>> I am having a similar problem, but unfortunately this patch doesn't
>>> work for me (I get the error "BIOS uses SMBus unsafely"). Would it be
>>> acceptable to add a module parameter to allow access to the SMBus, even
>>> if the BIOS is using it? I realize that this is not a good idea in
>>> general, but I believe it is safe in my particular case, and I don't
>>> see any other way to solve my problem.
>>
>> How is this safe in your case? If the BIOS is using SMBus without
>> locking it, and may do so at any time, then there's no way to safely use
>> it from Linux.
>
> The BIOS appears to access the SMBus during the first few minutes after
> boot, and then it stops using it. So "safe" may not be the right word,
> but in my case, it seems to work OK to use the SMBus as long as the
> uptime is greater than a few minutes.
>
> -Alex
>
Linux will probe the SMBus on startup, so that still seems like a rather
fragile situation. You'd have to blacklist the module and load it
separately a few minutes after boot, or something like that...
--
Hector Martin (marcan@marcan.st)
Public Key: https://mrcn.st/pub
next prev parent reply other threads:[~2021-12-18 3:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 0:31 [PATCH v3] i2c: i801: Safely share SMBus with BIOS/ACPI Alex Henrie
2021-12-17 7:41 ` Hector Martin
2021-12-18 2:51 ` [External] " Alex Henrie
2021-12-18 3:39 ` Hector Martin [this message]
2021-12-20 17:41 ` Alex Henrie
2022-01-05 1:37 ` Alex Henrie
2022-01-08 3:47 ` Hector Martin
2022-01-18 12:53 ` [External] " 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=7fb63895-e8fb-c9c3-c5da-f922ae0c69fd@marcan.st \
--to=marcan@marcan.st \
--cc=alexh@vpitech.com \
--cc=alexhenrie24@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@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 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).