From: Vitor Soares <ivitro@gmail.com>
To: Kang Yang <kang.yang@oss.qualcomm.com>,
Jeff Johnson <jjohnson@kernel.org>
Cc: Vitor Soares <vitor.soares@toradex.com>,
linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org, baochen.qiang@oss.qualcomm.com
Subject: Re: [PATCH ath-next v3] wifi: ath12k: advertise interface MAC address pool
Date: Tue, 22 Sep 2026 10:29:53 +0100 [thread overview]
Message-ID: <c30b21e218bfb00a1eb3c52ea0b7c9f0dc828592.camel@gmail.com> (raw)
In-Reply-To: <974e540d-d6e2-4ebf-8714-98e4056083d9@oss.qualcomm.com>
On Tue, 2026-09-22 at 14:13 +0800, Kang Yang wrote:
>
>
> On 9/22/2026 1:30 AM, Vitor Soares wrote:
> > From: Vitor Soares <vitor.soares@toradex.com>
> >
> > ath12k supports creating vdevs with addresses provided by mac80211.
> > Userspace can already make concurrent interfaces work by explicitly
> > assigning different locally administered addresses.
> >
> > However, ath12k does not advertise an address list, so when a second
> > interface is created without an explicit address, mac80211 has nothing
> > to pick from and falls back to the permanent address. If the first
> > interface is already running with that address, bringing up the second
> > one fails with -ENOTUNIQ.
> >
> > As in ath11k, provide a list of usable addresses so
> > ieee80211_assign_perm_addr() can hand each new interface an unused one.
> > Keep the first entry as the wiphy's permanent MAC address. Generate the
> > remaining entries as locally administered variants by changing only the
> > upper nibble of the first octet, which naturally limits the pool to 16
> > unique addresses.
> >
> > The cfg80211 definition of wiphy->addresses does not specify where the
> > addresses must come from. Some ath12k platforms use it as an interface
> > MAC address pool, while others use it for firmware-provided per-radio
> > addresses. Gate the generated address pool behind
> > advertise_iface_mac_pool and enable it for WCN7850 and QCC2072.
> >
> > Other platforms keep the existing behavior.
> >
> > Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c7-00108-
> > QCAHMTSWPL_V1.0_V2.0_SILICONZ_UPSTREAM-3
> >
>
>
>
> I just did test on QCC2072:
>
> root@yk-Mayan:/home/yk# sudo iw dev wlo1 interface add wlo2 type station
> root@yk-Mayan:/home/yk# sudo iw dev wlo1 interface add wlo3 type station
> phy#0
> Interface wlo3
> ifindex 6
> wdev 0x3
> addr 22:03:7f:12:be:cd
> type managed
>
> Interface wlo2
> ifindex 5
> wdev 0x2
> addr 12:03:7f:12:be:cd
> type managed
>
> Interface wlo1
> ifindex 4
> wdev 0x1
> addr 00:03:7f:12:be:cd
> type managed
>
>
>
>
> Tested-on: QCC2072 hw1.0 PCI
> WLAN.COL.1.0.c2-00074-QCACOLSWPL_V1_TO_SILICONZ-1
>
Thanks for testing this on QCC2072.
I've added the QCC2072 Tested-on line for v4. Could you reply with your Tested-
by so I can pick it up?
Best regards,
Vitor
next prev parent reply other threads:[~2026-09-22 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 17:30 [PATCH ath-next v3] wifi: ath12k: advertise interface MAC address pool Vitor Soares
2026-09-22 6:13 ` Kang Yang
2026-09-22 9:29 ` Vitor Soares [this message]
2026-09-22 10:34 ` Kang Yang
2026-09-22 6:47 ` Baochen Qiang
2026-09-23 8:50 ` Baochen Qiang
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=c30b21e218bfb00a1eb3c52ea0b7c9f0dc828592.camel@gmail.com \
--to=ivitro@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kang.yang@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vitor.soares@toradex.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.