From: Kalle Valo <kvalo@kernel.org>
To: Doug Brewer <brewer.doug@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: QCA9074 problem on rk3568
Date: Thu, 20 Apr 2023 15:16:37 +0300 [thread overview]
Message-ID: <87mt32vjdm.fsf@kernel.org> (raw)
In-Reply-To: <CAG0V13RiyW0HptSbZ6vxoTCmdjzrYZ9MQxCqKuiczJL9znW0-g@mail.gmail.com> (Doug Brewer's message of "Thu, 20 Apr 2023 13:49:40 +0800")
Doug Brewer <brewer.doug@gmail.com> writes:
> I tried to install linux kernel 6.3-rc7 on my rk3568 evb. It seems there's
> a problem about MHI:
>
> [ 11.340558] ath11k_pci 0002:01:00.0: BAR 0: assigned [mem 0x380000000-0x3801f
> ffff 64bit]
> [ 11.341399] ath11k_pci 0002:01:00.0: enabling device (0000 -> 0002)
> [ 11.422849] ath11k_pci 0002:01:00.0: MSI vectors: 16
> [ 11.423335] ath11k_pci 0002:01:00.0: qcn9074 hw1.0
> [ 11.660846] mhi mhi0: Requested to power ON
> [ 11.661271] mhi mhi0: Power on setup success
> [ 31.716289] mhi mhi0: MHI did not load image over BHI, ret: -5
> [ 60.551942] mhi mhi0: Device failed to enter READY state
> [ 60.552544] mhi mhi0: Error moving from PM state: Firmware Download Error to:
> DISABLE
> [ 60.553376] ath11k_pci 0002:01:00.0: failed to power up mhi: -110
> [ 60.553972] ath11k_pci 0002:01:00.0: failed to start mhi: -110
> [ 60.554532] ath11k_pci 0002:01:00.0: failed to power up :-110
> [ 60.567907] ath11k_pci 0002:01:00.0: failed to create soc core:
> -110
> [ 60.568488] ath11k_pci 0002:01:00.0: failed to init core: -110
>
> Any idea how to fix it? Thanks.
I would first check that the firmware files are not corrupted.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2023-04-20 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 5:49 QCA9074 problem on rk3568 Doug Brewer
2023-04-20 12:16 ` Kalle Valo [this message]
2023-04-21 1:35 ` Doug Brewer
2023-04-26 7:28 ` Kalle Valo
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=87mt32vjdm.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=brewer.doug@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.