From: Antonio Terceiro <antonio.terceiro@linaro.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: snd-cmipci oops during probe on arm64 (current mainline, pre-6.6-rc1)
Date: Wed, 6 Sep 2023 21:41:05 -0300 [thread overview]
Message-ID: <ZPkcIayHbYJopT6n@linaro.org> (raw)
In-Reply-To: <43632d9d-722c-b14f-336a-eac402ef9362@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
On Wed, Sep 06, 2023 at 08:52:40PM +0100, Robin Murphy wrote:
> On 2023-09-06 19:36, Antonio Terceiro wrote:
> > I'm pretty sure I saw reports of people using PCI GPUs on this machine,
> > but I would need to confirm.
>
> GPUs and any other PCIe devices will be fine, since they will use memory
> BARs - I/O space is pretty much deprecated in PCIe, and as mentioned some
> systems don't even support it at all. I found a datasheet for CMI8738, and
> they seem to be right at the other end of the scale as legacy PCI chips with
> *only* an I/O BAR (and so I guess your card includes a PCIe-PCI bridge as
> well), so are definitely going to be hitting paths that are less
> well-exercised on arm64 in general.
OK, that makes sense. So If I'm able to find a card that is genuinely
PCIe¹, then it should work?
¹ this one has a connector that looks like a PCIe x1, but it's not
really PCIe as the chipset was designed for legacy PCI?
> > What info would I need to gather from the machine in order to figure
> > this out?
>
> The first thing I'd try is rebuilding the kernel with CONFIG_INDIRECT_PIO
> disabled and see what difference that makes. I'm not too familiar with that
> area of the code, so the finer details of how to debug broken I/O space
> beyond that would be more of a linux-pci question.
Tried that, didn't help.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-07 0:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 22:01 snd-cmipci oops during probe on arm64 (current mainline, pre-6.6-rc1) Antonio Terceiro
2023-09-06 6:10 ` Takashi Iwai
2023-09-06 12:49 ` Robin Murphy
2023-09-06 18:36 ` Antonio Terceiro
2023-09-06 19:03 ` Geraldo Nascimento
2023-09-06 20:37 ` Robin Murphy
2023-09-06 21:00 ` Geraldo Nascimento
2023-09-06 19:52 ` Robin Murphy
2023-09-07 0:41 ` Antonio Terceiro [this message]
2023-09-07 12:22 ` Robin Murphy
2023-09-07 2:29 ` Geraldo Nascimento
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=ZPkcIayHbYJopT6n@linaro.org \
--to=antonio.terceiro@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robin.murphy@arm.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=will@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