From: Alex Henrie <alexh@vpitech.com>
To: Hector Martin <marcan@marcan.st>, Jean Delvare <jdelvare@suse.de>
Cc: linux-i2c@vger.kernel.org, wsa@kernel.org, alexhenrie24@gmail.com
Subject: Re: [PATCH] i2c: i801: Add module parameter to inhibit BIOS access
Date: Wed, 19 Jan 2022 11:01:56 -0700 [thread overview]
Message-ID: <20220119110156.574ae2d96af6b8a722c8c9ba@vpitech.com> (raw)
In-Reply-To: <dc6c3b38-dbc1-3d86-fd87-607a2d6a6685@marcan.st>
On Thu, 20 Jan 2022 02:32:02 +0900
Hector Martin <marcan@marcan.st> wrote:
> On 20/01/2022 01.49, Alex Henrie wrote:
> > I think Hector's patch to share the SMBus is a great idea; my patch was
> > meant to complement his, not replace it. The problem is that when I
> > tried Hector's patch, I got the message "BIOS left SMBus locked". So I
> > didn't want to let the BIOS touch the SMBus at all because once it had
> > the lock, it seemed to never let go. However, today I tried v2 of
> > Hector's patch [1] instead of v3 [2], and v2 worked perfectly! My guess
> > is that despite the text of the error message, it's Linux that's
> > leaving the SMBus locked, not the BIOS.
> >
> > The only difference between v2 and v3 is that v2 called
> > outb_p(SMBHSTSTS_INUSE_STS, SMBHSTSTS(priv)) at the end of i801_access.
> > Hector, can you clarify why you removed that call in v3?
>
> Well that solves the mystery.
>
> That line was split off and submitted separately in another patch, as it
> fixes the immediate breakage that I was trying to address with my patch,
> namely that *linux* left the SMBus locked and that broke BIOS accesses.
> The full patch implements proper sharing logic; that line alone is
> enough to unbork the backlight on iMacs (among other things) which was
> the immediate regression I had encountered. The rest of the patch breaks
> horribly without that line, as you'd expect, since it's trying to work
> around a broken BIOS when Linux itself is broken.
>
> That patch was posted in June 2021 and CC'd stable [1], and was merged
> into the stable 5.10 and 5.12 trees as well as released in 5.13. So, you
> must be running an old kernel :-).
>
> [1]
> https://lore.kernel.org/linux-i2c/cefbeb76-5f7f-036b-fa0e-1e339d261c35@gmail.com/
Excellent! Thank you so much Hector. Indeed, this system is currently
using a custom-built 5.4 kernel.
Jean, please feel free to disregard my patch and to commit Hector's
with "Tested-by: Alex Henrie <alexh@vpitech.com>".
-Alex
next prev parent reply other threads:[~2022-01-19 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 23:31 [PATCH] i2c: i801: Add module parameter to inhibit BIOS access Alex Henrie
2022-01-18 12:47 ` Jean Delvare
2022-01-19 16:49 ` Alex Henrie
2022-01-19 17:32 ` Hector Martin
2022-01-19 18:01 ` Alex Henrie [this message]
2022-01-19 18:43 ` Wolfram Sang
2022-01-19 19:24 ` [External] " Alex Henrie
2022-01-19 20:22 ` Wolfram Sang
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=20220119110156.574ae2d96af6b8a722c8c9ba@vpitech.com \
--to=alexh@vpitech.com \
--cc=alexhenrie24@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=marcan@marcan.st \
--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).