From: Hector Martin <marcan@marcan.st>
To: Alex Henrie <alexh@vpitech.com>,
linux-i2c@vger.kernel.org, wsa@kernel.org, jdelvare@suse.de
Cc: alexhenrie24@gmail.com
Subject: Re: [PATCH v3] i2c: i801: Safely share SMBus with BIOS/ACPI
Date: Fri, 17 Dec 2021 16:41:05 +0900 [thread overview]
Message-ID: <a5da4d27-f2cc-9018-5266-9f40d74818ad@marcan.st> (raw)
In-Reply-To: <20211216173110.82ae177385322c0992d00126@vpitech.com>
On 17/12/2021 09.31, Alex Henrie wrote:
> Dear kernel developers,
>
> 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.
>
> -Alex
>
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.
--
Hector Martin (marcan@marcan.st)
Public Key: https://mrcn.st/pub
next prev parent reply other threads:[~2021-12-17 7:41 UTC|newest]
Thread overview: 19+ 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 [this message]
2021-12-18 2:51 ` [External] " Alex Henrie
2021-12-18 3:39 ` Hector Martin
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
-- strict thread matches above, loose matches on Subject: below --
2022-12-13 15:10 David Oberhollenzer
2021-06-26 5:41 Hector Martin
2021-11-29 9:00 ` Wolfram Sang
2021-11-30 9:26 ` Jean Delvare
2022-01-19 20:48 ` Alex Henrie
2022-01-24 18:22 ` Alex Henrie
2022-07-20 19:21 ` Ettore Chimenti
2022-12-15 14:26 ` Jean Delvare
2022-12-15 21:09 ` Heiner Kallweit
2022-12-17 13:28 ` Hector Martin
2022-12-18 23:02 ` 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=a5da4d27-f2cc-9018-5266-9f40d74818ad@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).