ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: w.wadepohl@posteo.de
To: Bastian Krause <bst@pengutronix.de>
Cc: "Lukas F. Hartmann" <lukas@mntre.com>,
	Gary Bisson <bisson.gary@gmail.com>,
	Kalle Valo <kvalo@kernel.org>,
	ath10k@lists.infradead.org, gary.bisson@boundarydevices.com,
	kernel@pengutronix.de
Subject: Re: Problems with QCA9377 SDIO on NXP i.MX8MPlus SOM
Date: Tue, 05 Sep 2023 05:58:21 +0000	[thread overview]
Message-ID: <6b7a87b601e60052120d8fbb3567df1b@posteo.de> (raw)
In-Reply-To: <c22e2867-5ebb-4337-a9c9-be95621b3e78@pengutronix.de>

We are using a QCA9377 based device (8devices Redbean) with the ath10k 
over SDIO together with kernel 5.10. It works well. We also use qcacld 
for regulative testing purpose. All our patches are mainlined.

Am 04.09.2023 16:28 schrieb Bastian Krause:
> Hi Lukas and everybody else,
> 
> On 6/13/23 17:35, Lukas F. Hartmann wrote:
>> Gary Bisson <bisson.gary@gmail.com> writes:
>> 
>>>> Trying significantly older ath10k from an older kernel is something 
>>>> to
>>>> try in case there are recent regressions in ath10k.
>>>> 
>>>> I don't have an ath10k SDIO device myself so I don't know the state 
>>>> of
>>>> SDIO support in ath10k. Does anyone else from the list know?
>>> 
>>> FYI we have a branch in our repo with the firmware that worked on 
>>> ath10k
>>> at some point [2].
>> 
>> Thanks, I looked at this FW now and it is exactly the same as the
>> "untested" in the ath10k-firmware repo
>> https://github.com/kvalo/ath10k-firmware/tree/master/QCA9377/hw1.0/untested
>> 
>> So if that worked with ath10k several years ago (when?) I could try to
>> reconstruct an older version and try to bisect for a regression, 
>> though
>> I imagine it will be complicated to make these old versions work with
>> APIs that have changed in the meantime in Linux.
> 
> I just wanted to check if I understood this correctly and whether this
> is still the latest information: The QCA9377 connected via SDIO won't
> work with the ath10k driver right now, correct? Neither with [1] nor
> with any other known firmware, right?
> 
> Thanks for the previous information, by the way. I'm also stuck with a
> QCA9377 (Telit module) connected via SDIO and I'm not too keen on using
> the qcacld driver. With Kernel 6.5, I see basically the same output as
> pasted here [2] with slightly different register dumps.
> 
> Regards,
> Bastian
> 
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ath10k/QCA9377/hw1.0
> [2] https://gist.github.com/mntmn/7d18cba485572bf0690267f37647cacb

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2023-09-05  5:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 19:59 Problems with QCA9377 SDIO on NXP i.MX8MPlus SOM Lukas F. Hartmann
2023-06-13  8:05 ` Kalle Valo
2023-06-13  8:26   ` Gary Bisson
2023-06-13 15:35     ` Lukas F. Hartmann
2023-09-04 14:28       ` Bastian Krause
2023-09-05  5:58         ` w.wadepohl [this message]

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=6b7a87b601e60052120d8fbb3567df1b@posteo.de \
    --to=w.wadepohl@posteo.de \
    --cc=ath10k@lists.infradead.org \
    --cc=bisson.gary@gmail.com \
    --cc=bst@pengutronix.de \
    --cc=gary.bisson@boundarydevices.com \
    --cc=kernel@pengutronix.de \
    --cc=kvalo@kernel.org \
    --cc=lukas@mntre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox