linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Antonio Terceiro <antonio.terceiro@linaro.org>
Cc: Robin Murphy <robin.murphy@arm.com>, 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 16:03:10 -0300	[thread overview]
Message-ID: <ZPjM7op/B/CGCF/N@geday> (raw)
In-Reply-To: <ZPjGuCdmPgqznc5t@linaro.org>

On Wed, Sep 06, 2023 at 03:36:40PM -0300, Antonio Terceiro wrote:
> On Wed, Sep 06, 2023 at 01:49:16PM +0100, Robin Murphy wrote:
> > On 2023-09-06 07:10, Takashi Iwai wrote:
> > > On Wed, 06 Sep 2023 00:01:01 +0200,
> > > Antonio Terceiro wrote:
> > > > 
> > > > Hi,
> > > > 

Hi Antonio, my 2 cents:

> > > > I'm using an arm64 workstation, and wanted to add a sound card to it. I bought
> > > > one who was pretty popular around where I live, and it is supported by the
> > > > snd-cmipci driver.

Specifically, which arm64 workstation? I'm guessing Compute Module 4 IO
Board + Raspbery Pi CM4? This detail is important because the stack
trace you provided only references generic PCI calls and there's a need
to know exactly which PCIe driver could be failing. Is it pcie-brcmstb?

Thanks,
Geraldo Nascimento


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-09-06 19:03 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 [this message]
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
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=ZPjM7op/B/CGCF/N@geday \
    --to=geraldogabriel@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=antonio.terceiro@linaro.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;
as well as URLs for NNTP newsgroup(s).