From: Bjorn Helgaas <helgaas@kernel.org>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "thierry.reding@kernel.org" <thierry.reding@kernel.org>,
"lukas@wunner.de" <lukas@wunner.de>,
"mmaddireddy@nvidia.com" <mmaddireddy@nvidia.com>,
"sashiko-reviews@lists.linux.dev"
<sashiko-reviews@lists.linux.dev>,
"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>,
"treding@nvidia.com" <treding@nvidia.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: Disable NoSnoop and Relaxed ordering for Intel wireless BE200
Date: Tue, 28 Jul 2026 14:24:10 -0500 [thread overview]
Message-ID: <20260728192410.GA1387466@bhelgaas> (raw)
In-Reply-To: <a1934c51592fc56c65232b1379680c52c6d0cea3.camel@intel.com>
On Tue, Jul 28, 2026 at 06:21:23PM +0000, Grumbach, Emmanuel wrote:
> On Tue, 2026-07-28 at 13:03 -0500, Bjorn Helgaas wrote:
> ...
> > AFAICS we still don't know why Tegra264 would set NoSnoop and/or
> > RlxdOrd in the MMIO read.
>
> Me neither but... I can't comment on that. And de-facto, once it does
> that, the BE200 replies with the NoSnoop and RlxOrd clear in the TLP
> which is then considered as a malformed TLP.
>
> > Unless iwlwifi asked for NoSnoop and/or RlxdOrd to be set, I think
> > it's a potential problem for drivers if Tegra264 sets them.
>
> I ... don't think we would do that. The driver would certainly not do
> that... Regarding the hardware itself, I can't comment, but I can check
> internally.
Forgot to ask, can you collect the output of "sudo lspci -vv", at
least for the RP and the BE200?
And maybe the dmesg log when booted with "log_buf_len=16M
pci=earlydump" as well, so we can see if attributes were enabled by a
bootloader?
next prev parent reply other threads:[~2026-07-28 19:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 6:54 [PATCH] PCI: Disable NoSnoop and Relaxed ordering for Intel wireless BE200 Emmanuel Grumbach
2026-06-21 7:12 ` sashiko-bot
2026-06-21 7:30 ` Grumbach, Emmanuel
2026-07-22 14:56 ` Bjorn Helgaas
2026-07-22 15:14 ` Grumbach, Emmanuel
2026-07-22 17:04 ` Bjorn Helgaas
[not found] ` <204d9dab-96de-45fb-867d-20defc0b79e6@nvidia.com>
[not found] ` <534363f87b37ba6f1449d0524400bcfd7fdf5b3e.camel@intel.com>
2026-07-24 10:54 ` Manikanta Maddireddy
2026-07-28 18:03 ` Bjorn Helgaas
2026-07-28 18:21 ` Grumbach, Emmanuel
2026-07-28 19:11 ` Bjorn Helgaas
2026-07-28 19:16 ` Grumbach, Emmanuel
2026-07-28 19:24 ` Bjorn Helgaas [this message]
2026-07-28 19:47 ` Grumbach, Emmanuel
2026-07-28 20:18 ` Bjorn Helgaas
2026-07-29 6:49 ` Grumbach, Emmanuel
2026-07-30 4:51 ` Manikanta Maddireddy
2026-07-30 17:28 ` Bjorn Helgaas
2026-07-30 18:45 ` Grumbach, Emmanuel
2026-07-30 20:08 ` Bjorn Helgaas
2026-07-30 20:16 ` Grumbach, Emmanuel
2026-07-31 15:24 ` Bjorn Helgaas
2026-07-23 6:47 ` Lukas Wunner
2026-06-21 8:10 ` Lukas Wunner
2026-06-21 8:28 ` Grumbach, Emmanuel
2026-07-22 11:01 ` Grumbach, Emmanuel
2026-07-22 14:36 ` Lukas Wunner
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=20260728192410.GA1387466@bhelgaas \
--to=helgaas@kernel.org \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=miriam.rachel.korenblit@intel.com \
--cc=mmaddireddy@nvidia.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=thierry.reding@kernel.org \
--cc=treding@nvidia.com \
/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