linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "chiluk@ubuntu.com" <chiluk@ubuntu.com>,
	"Coelho, Luciano" <luciano.coelho@intel.com>
Cc: "regressions@leemhuis.info" <regressions@leemhuis.info>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"marcel@holtmann.org" <marcel@holtmann.org>
Subject: Re: [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211
Date: Thu, 5 Jan 2023 06:15:33 +0000	[thread overview]
Message-ID: <b5e9c8911a46802ddb017554f266c92a7a0b2605.camel@intel.com> (raw)
In-Reply-To: <CAMfi-DTwX2nvP58FRb6NaGMyWO0SBo9W=Fpdtr=XfNRzkqAwHw@mail.gmail.com>

Hi Dave,

On Tue, 2023-01-03 at 11:37 -0600, Dave Chiluk wrote:
> On Thu, Dec 1, 2022 at 5:33 AM Coelho, Luciano <luciano.coelho@intel.com> wrote:
> > 
> > On Thu, 2022-12-01 at 11:14 +0100, Thorsten Leemhuis wrote:
> > > Hi, this is your Linux kernel regression tracker.
> > > 
> > > Luca, I noticed a regression report in bugzilla where I'd like your
> > > advice on. To quote https://bugzilla.kernel.org/show_bug.cgi?id=216753
> > 
> > Hi Thorsten wearing-the-regression-hat, 🙂
> > 
> > I'm not the maintainer of iwlwifi anymore, so I'm adding the new
> > maintainer here, Gregory Greenman.
> > 
> > Gregory, can you take a look?
> > 
> 
> @Gregory Greenman as I'm sure this got buried over the holidays, can
> you take a look at this and advise?  This is definitely a regression,
> but I don't think a lot of people are noticing it or don't yet have
> 6ghz access points.  I can write up a patch removing the offending
> commit (698b166ed), or I can add an iwlwifi option to ignore the 6e
> ACPI bit.  Which would you prefer?
> 
> Dell has been of little help which I pretty much expected.
> 
I'll try to explain, the problem here is not technical. After some
internal checks, it appears that we (wifi driver) aren't allowed to
decide if 6E should be enabled or not. Because of the legal restrictions,
OEM should make this decision and enable/disable 6E in the BIOS. This
commit only gets the value from the BIOS and configures the firmware
accordingly. So, unfortunately, legal restriction is the reason we cannot
revert/overwrite 6E enablement...

> @Luciano, as you were the author of the original change, and I'm not
> familiar enough with ACPI, is the below code reading the enable bits
> from the BIOS ACPI table or is this somehow coming out of the network
> card through some UEFI extensions?  I'm trying to figure out which of
> Dell or Intel need to update their firmware?  I think some Lenovo's
> have similar problems, so I suspect it's a BIOS ACPI table problem.
> 
>  ret = iwl_acpi_get_dsm_u32(mvm->fwrt.dev, 0,
>                                    DSM_FUNC_ENABLE_6E,
>                                    &iwl_guid, &value);

It comes from the BIOS ACPI table.

> 
> Thanks,
> Dave.


  parent reply	other threads:[~2023-01-05  6:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 10:14 [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211 Thorsten Leemhuis
2022-12-01 11:33 ` Coelho, Luciano
2022-12-02 15:37   ` Dave Chiluk
2022-12-02 16:02     ` Thorsten Leemhuis
2022-12-02 16:46       ` Marcel Holtmann
2022-12-02 17:18         ` Dave Chiluk
2022-12-02 17:42           ` Maxime Bizon
2022-12-04  9:37             ` Thorsten Leemhuis
2022-12-20 13:16               ` Maxime Bizon
2023-01-03 19:48               ` Dave Chiluk
2022-12-02 17:46           ` Marcel Holtmann
2022-12-05 16:35             ` Dave Chiluk
2023-01-03 17:37   ` Dave Chiluk
2023-01-04  8:50     ` Coelho, Luciano
2023-01-05  6:15     ` Greenman, Gregory [this message]
2023-01-06 15:37       ` Dave Chiluk
2023-01-19 14:09         ` Greenman, Gregory

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=b5e9c8911a46802ddb017554f266c92a7a0b2605.camel@intel.com \
    --to=gregory.greenman@intel.com \
    --cc=chiluk@ubuntu.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=marcel@holtmann.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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).