From: Kalle Valo <kvalo@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k vs ar_qrtr?
Date: Wed, 30 Nov 2022 14:42:41 +0200 [thread overview]
Message-ID: <87o7so4nr2.fsf@kernel.org> (raw)
In-Reply-To: <20221130122807.GA31720@lst.de> (Christoph Hellwig's message of "Wed, 30 Nov 2022 13:28:07 +0100")
Hi Christoph,
Christoph Hellwig <hch@lst.de> writes:
> I'm trying to install debian testing on my new Thinkpad T14s, which
> comes with a Qualcomm QCNFA765 wifi adatper that seems to be supported
> by the ath11k driver.
>
> Probing the device fails with a "failed to initialize qmi handle: -517"
> message, which as far as I can tell happens when qmi_sock_create
> fails to create a AF_QIPCRTR socket with a status of -EAFNOSUPPORT,
> which the confusingly gets turned into -EPROBE_DEFER by qmi_handle_init.
>
> The debian installer kernel doesn't seem to come with af_qrtr at all,
> which seems to be required by this call and unless I'm missing something
> is required for support for at least this version of the ath11k
> hardware.
Yeah, ath11k PCI devices require QRTR and we have this in Kconfig:
config ATH11K_PCI
tristate "Atheros ath11k PCI support"
depends on ATH11K && PCI
select MHI_BUS
select QRTR
select QRTR_MHI
> Is there any reson to not have a module dependency so that
> distributions will pick it up automatically?
Sorry, not following you here. Are you saying that "select QRTR" is not
enough and we should add something more?
--
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:[~2022-11-30 12:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 12:28 ath11k vs ar_qrtr? Christoph Hellwig
2022-11-30 12:42 ` Kalle Valo [this message]
2022-11-30 12:52 ` Christoph Hellwig
2022-11-30 13:12 ` Kalle Valo
2022-11-30 13:12 ` Kalle Valo
2022-11-30 13:22 ` Christoph Hellwig
2022-11-30 13:22 ` Christoph Hellwig
2022-11-30 17:18 ` Kalle Valo
2022-11-30 17:18 ` Kalle Valo
2022-11-30 13:30 ` failed to insert STA entry for the AP (error -2) Christoph Hellwig
2022-11-30 13:30 ` Christoph Hellwig
2022-12-02 18:46 ` Kalle Valo
2022-12-02 18:46 ` Kalle Valo
2022-12-03 15:52 ` Christoph Hellwig
2022-12-03 15:52 ` Christoph Hellwig
2022-12-07 12:49 ` Kalle Valo
2022-12-07 12:49 ` Kalle Valo
2022-12-07 13:40 ` Christoph Hellwig
2022-12-07 13:40 ` Christoph Hellwig
2022-12-07 14:24 ` Cyril Brulebois
2022-12-07 14:24 ` Cyril Brulebois
2022-12-08 18:44 ` Kalle Valo
2022-12-08 18:44 ` 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=87o7so4nr2.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=hch@lst.de \
/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.