From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Ansuel Smith <ansuelsmth@gmail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Linus Walleij <linus.walleij@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Abbott Liu <liuwenliang@huawei.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: Enlarge IO_SPACE_LIMIT needed for some SoC
Date: Tue, 11 May 2021 15:54:16 +0100 [thread overview]
Message-ID: <20210511145416.GM1336@shell.armlinux.org.uk> (raw)
In-Reply-To: <YJp1WYTXHsSAA0ES@Ansuel-xps.localdomain>
On Tue, May 11, 2021 at 02:15:21PM +0200, Ansuel Smith wrote:
> 0000:01:00.0 Network controller: Qualcomm Atheros QCA9984 802.11ac Wave 2 Wireless Network Adapter
> Subsystem: Qualcomm Atheros Device cafe
> Device tree node: /sys/firmware/devicetree/base/soc/pci@1b500000/bridge@0,0/wifi@1,0
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 53
> Region 0: Memory at 08000000 (64-bit, non-prefetchable) [size=2M]
It seems this Atheros device does not make any use of I/O, so this
device should be fine.
> 0001:01:00.0 Network controller: Qualcomm Atheros QCA9984 802.11ac Wave 2 Wireless Network Adapter
> Subsystem: Qualcomm Atheros Device cafe
> Device tree node: /sys/firmware/devicetree/base/soc/pci@1b700000/bridge@0,0/wifi@1,0
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 54
> Region 0: Memory at 2e000000 (64-bit, non-prefetchable) [size=2M]
This device also seems to not make use of any I/O.
I don't see any reason probing of these two drivers should fail if
there is no or reduced I/O space.
Please can you share the kernel messages so we can see exactly what is
failing and how?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-05-11 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 2:16 [PATCH] arm: Enlarge IO_SPACE_LIMIT needed for some SoC Ansuel Smith
2021-05-11 2:24 ` Matthew Wilcox
2021-05-11 2:32 ` Ansuel Smith
2021-05-11 4:26 ` Ard Biesheuvel
2021-05-11 12:15 ` Ansuel Smith
2021-05-11 12:30 ` Ard Biesheuvel
2021-05-11 12:37 ` Ansuel Smith
2021-05-11 12:46 ` Ard Biesheuvel
2021-05-11 12:51 ` Ansuel Smith
2021-05-11 14:55 ` Russell King - ARM Linux admin
2021-05-11 14:54 ` Russell King - ARM Linux admin [this message]
2021-05-17 10:26 ` Linus Walleij
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=20210511145416.GM1336@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ansuelsmth@gmail.com \
--cc=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=f.fainelli@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwenliang@huawei.com \
--cc=mcgrof@kernel.org \
--cc=palmerdabbelt@google.com \
--cc=willy@infradead.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).