All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: backports@vger.kernel.org
Subject: [Bug 217925] Backporting ath11k QCN9074 support to kernel 5.10 - no network interface
Date: Tue, 19 Sep 2023 17:29:52 +0000	[thread overview]
Message-ID: <bug-217925-58281-iZxxDFpBBs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217925-58281@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217925

Lakshmanakumar (lakshmanakumar.mohan@celestica.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |trivial
            Summary|Backporting ath11k QCN9074  |Backporting ath11k QCN9074
                   |no network interface        |support to kernel 5.10 - no
                   |                            |network interface

--- Comment #1 from Lakshmanakumar (lakshmanakumar.mohan@celestica.com) ---
I'm trying to port the ath11k driver from kernel 5.15 to kernel 5.10 for
supporting the QCN9074 modules. I have also copied the firmwares from
https://github.com/kvalo/ath11k-firmware/tree/master/QCN9074/hw1.0  
I could see the below logs after loading the ath11k_pci driver. But it does not
proceed after the below state. Therefore the wireless network interface fails
loading.
[  520.582093] cfg80211: Loading compiled-in X.509 certificates for regulatory
database
[  520.594227] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[  520.630560] ath11k_pci 0000:03:00.0: runtime IRQ mapping not provided by
arch
[  520.637930] ath11k_pci 0000:03:00.0: BAR 0: assigned [mem
0xdfa00000-0xdfbfffff 64bit]
[  520.646225] ath11k_pci 0000:03:00.0: qcn9074 hw1.0
[  520.654325] NET: Registered protocol family 42
[  520.714305] mhi 0000:03:00.0: Requested to power ON
[  520.719416] mhi 0000:03:00.0: Power on setup success

PCI list shows the interface as 
root@localhost:/# lspci -v -s 0000:03:00.0
03:00.0 Network controller: Qualcomm Device 1104 (rev 01)
        Subsystem: Qualcomm Device 1104
        Flags: bus master, fast devsel, latency 0, IRQ 77
        Memory at dfa00000 (64-bit, non-prefetchable) [size=2M]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=16/32 Maskable+ 64bit-
        Capabilities: [70] Express Endpoint, MSI 00
        Kernel driver in use: ath11k_pci
        Kernel modules: ath11k_pci

root@localhost:/# tree /sys/bus/pci/devices/0000\:03\:00.0/
0000:03:00.0/             driver/                   rescan
0000:03:00.0_IPCR/        driver_override           reset
0000:03:00.0_LOOPBACK/

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe backports" in

      reply	other threads:[~2023-09-19 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 17:11 [Bug 217925] New: Backporting ath11k QCN9074 no network interface bugzilla-daemon
2023-09-19 17:29 ` bugzilla-daemon [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=bug-217925-58281-iZxxDFpBBs@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=backports@vger.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 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.