From: Ping-Ke Shih <pkshih@realtek.com>
To: "Anirudh Srinivasan" <asrinivasan@oss.tenstorrent.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Yixun Lan" <dlan@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Inochi Amaoto" <inochiama@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"spacemit@lists.linux.dev" <spacemit@lists.linux.dev>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 2/2] wifi: rtw89: pci: enable 36-bit DMA on spacemit K3
Date: Thu, 16 Jul 2026 09:22:17 +0000 [thread overview]
Message-ID: <e7a43955e41c4dbdb864e89edc3d9fe6@realtek.com> (raw)
In-Reply-To: <20260715-rtw89-spacemit-k3-v1-2-e577bc63706b@oss.tenstorrent.com>
Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com> wrote:
> The Spacemit K3 Pico ITX Board has a RTL8852BE pcie card behind a PCIe
> root port, but the SoC doesn't have any 32 DMA addreseses which the
> rtw89 seems to use by default. Enable 36 bit DMA ability that the driver
> has when this particular root port is detected so that the driver can
> probe on this SoC.
>
> Signed-off-by: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
This patch looks good to me:
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
But I wonder how this patchset goes via which tree. I'm happy to merge
them into rtw tree and then wireless-next tree if people can ack
patch 1/2.
WARNING: multiple messages have this Message-ID (diff)
From: Ping-Ke Shih <pkshih@realtek.com>
To: "Anirudh Srinivasan" <asrinivasan@oss.tenstorrent.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Yixun Lan" <dlan@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Inochi Amaoto" <inochiama@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"spacemit@lists.linux.dev" <spacemit@lists.linux.dev>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 2/2] wifi: rtw89: pci: enable 36-bit DMA on spacemit K3
Date: Thu, 16 Jul 2026 09:22:17 +0000 [thread overview]
Message-ID: <e7a43955e41c4dbdb864e89edc3d9fe6@realtek.com> (raw)
In-Reply-To: <20260715-rtw89-spacemit-k3-v1-2-e577bc63706b@oss.tenstorrent.com>
Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com> wrote:
> The Spacemit K3 Pico ITX Board has a RTL8852BE pcie card behind a PCIe
> root port, but the SoC doesn't have any 32 DMA addreseses which the
> rtw89 seems to use by default. Enable 36 bit DMA ability that the driver
> has when this particular root port is detected so that the driver can
> probe on this SoC.
>
> Signed-off-by: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
This patch looks good to me:
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
But I wonder how this patchset goes via which tree. I'm happy to merge
them into rtw tree and then wireless-next tree if people can ack
patch 1/2.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-16 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 3:21 [PATCH 0/2] Enable WiFi on Spacemit K3 Pico ITX Anirudh Srinivasan
2026-07-16 3:21 ` Anirudh Srinivasan
2026-07-16 3:21 ` [PATCH 1/2] PCI: Move Spacemit vendor and device ID to linux/pci_Ids.h Anirudh Srinivasan
2026-07-16 3:21 ` Anirudh Srinivasan
2026-07-16 3:21 ` [PATCH 2/2] wifi: rtw89: pci: enable 36-bit DMA on spacemit K3 Anirudh Srinivasan
2026-07-16 3:21 ` Anirudh Srinivasan
2026-07-16 9:22 ` Ping-Ke Shih [this message]
2026-07-16 9:22 ` Ping-Ke Shih
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=e7a43955e41c4dbdb864e89edc3d9fe6@realtek.com \
--to=pkshih@realtek.com \
--cc=asrinivasan@oss.tenstorrent.com \
--cc=bhelgaas@google.com \
--cc=dlan@kernel.org \
--cc=inochiama@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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.