>
> Add corresponding dependency to ATH10K_SNOC Kconfig entry so that it's
> built as module if QCOM_RPROC_COMMON is built as module too.
>
> Fixes: 747ff7d3d742 ("ath10k: Don't always treat modem stop events as
> crashes")
> Cc: sta...@vger.kernel.org
> Signed-of
Eric Park writes:
> On 5/15/24 5:04 PM, Kalle Valo wrote:
>
>> Eric Park writes:
>>> I'm unsure what to test next, if it can be triaged at all. It's an
>>> outdated card in a really old laptop and I can always work around it
>>> with a USB WiFi adapter
Jeff Johnson writes:
> Historically, prior to being incorporated into the linux-firmware
> project, firmware for kernel.org ath1*k drivers has been first published
> to Kalle's GitHub:
> https://github.com/kvalo/ath10k-firmware
> https://github.com/kvalo/ath11k-firmware
> (ath12k firmware was
triggers.
> Adds also debugfs interface for gpio control.
>
> Signed-off-by: Sebastian Gottschall
> Reviewed-by: Steve deRosier
> [kvalo: major reorg and cleanup]
> Signed-off-by: Kalle Valo
> [ansuel: rebase and small cleanup]
> Signed-off-by: Christian Marangi
>
Eric Park writes:
> On 5/15/2024 12:27 AM, Kalle Valo wrote:
>
>> But James is reporting[1] that 802.11w is working for him. So it doesn't
>> seem to be completely broken even if you are having problems and
>> removing the 802.11w support from the driver doesn't sound ri
Eric Park writes:
> On 5/6/2024 6:04 PM, Kalle Valo wrote:
>
>> (...)
>> This is of course just a theory. I don't know how familiar you are with
>> 802.11 protocols but that is something to investigate. Unfortunately I
>> have very little time for ath10k n
nd it was pointed out that ath11k
> (and ath12k) do not wait for it.
>
> However with so many deployed devices, "might be ok" isn't a strong
> argument for changing the default behavior.
>
> Kalle Valo first suggested setting a bit in firmware-5.bin to trigger
> work-
Jeff Johnson writes:
> On 5/10/2024 7:14 AM, Christian Marangi wrote:
>
>> On Thu, May 09, 2024 at 09:48:08AM -0700, Jeff Johnson wrote:
>>> On 5/9/2024 9:37 AM, Jeff Johnson wrote:
>>>> On 5/8/2024 9:50 PM, Kalle Valo wrote:
>>>>> Sorry for
Jeff Johnson writes:
> On 5/9/2024 9:37 AM, Jeff Johnson wrote:
>> On 5/8/2024 9:50 PM, Kalle Valo wrote:
>>> Sorry for the delay but finally I looked at this again. I decided to
>>> just remove the fixme and otherwise it looks good for me. Please check
&g
Christian Marangi writes:
>>
>> Sorry for the delay but finally I looked at this again. I decided to
>> just remove the fixme and otherwise it looks good for me. Please check
>> my changes:
>>
>>
Ansuel Smith writes:
> Il giorno sab 17 giu 2023 alle ore 19:28 Christian Marangi
> ha scritto:
>
>>
>> On Fri, Jun 16, 2023 at 01:35:04PM +0200, Christian Marangi wrote:
>> > On Fri, Jun 16, 2023 at 08:03:23PM +0300, Kalle Valo wrote:
>> > > Chris
Marc Gonzalez writes:
> On 30/04/2024 06:06, Kalle Valo wrote:
>
>> Bjorn Andersson wrote:
>>
>>> On Mon, Apr 29, 2024 at 04:04:51PM +0200, Marc Gonzalez wrote:
>>>
>>>> The ath10k driver waits for an "MSA_READY" indicator
>>>
Marc Gonzalez writes:
> On 30/04/2024 06:06, Kalle Valo wrote:
>
>> Bjorn Andersson wrote:
>>
>>> On Mon, Apr 29, 2024 at 04:04:51PM +0200, Marc Gonzalez wrote:
>>>
>>>> The ath10k driver waits for an "MSA_READY" indicator
>>>
Eric Park writes:
> I had the opportunity to test the connection with another router (Asus
> RT-AX56U) today and it negotiated with WPA2-PSK, PMF default on, on 5
> GHz. I ran a speedtest and got 20 Mbps both up/down.
>
> I then ran the `nmcli connection modify wifi-sec.pmf 1` and
> after
Kalle Valo wrote:
> Hi,
>
> Please pull, more information in the tag below.
>
> Kalle
>
> The following changes since commit 57a03d83f229126b0aab6f305821358755c7b130:
>
> Merge branch 'mlxsw-preparations-for-improving-performance' (2024-04-03
> 19:5
Jeff Johnson (3):
wifi: ath11k: fix hal_rx_buf_return_buf_manager documentation
wifi: ath12k: fix hal_rx_buf_return_buf_manager documentation
wifi: ath12k: don't use %pK in dmesg format strings
Kalle Valo (2):
Merge branch 'mhi-immutable' of
git://git.kernel.org/pub/scm
t; The feedback I received was "it might be ok to change all ath10k qmi
>> to skip waiting for msa_ready", and it was pointed out that ath11k
>> (and ath12k) do not wait for it.
>>
>> However with so many deployed devices, "might be ok" isn't a st
Eric Park writes:
> On 2024-04-29 14:18, Kalle Valo wrote:
>> If you run wpa_supplicant -dddt (or similar) you get a lot of debug
>> output, I'm sure it will also include the cipher.
>
> Good to know, thank you. Will keep this in mind the next time I'm
> troubleshooti
Eric Park writes:
> On 4/25/24 5:51 AM, Kalle Valo wrote:
>
>> I do not use Network Manager or other connection managers when testing.
>> It's much more reliable to use wpasupplicant directly and you get full
>> control. I usually create a custom config file and then
Conor Dooley writes:
> On Thu, Apr 25, 2024 at 06:42:16PM +0300, Kalle Valo wrote:
>
>> Marc Gonzalez writes:
>>
>> > On 25/04/2024 11:42, Kalle Valo wrote:
>> >
>> >> Marc Gonzalez wrote:
>> >>
>> >>> Do you
Marc Gonzalez writes:
> On 25/04/2024 11:42, Kalle Valo wrote:
>
>> Marc Gonzalez wrote:
>>
>>> Do you prefer:
>>>
>>> Option A = never waiting for the MSA_READY indicator for ANYONE
>>> Option B = not waiting for the MSA_READY ind
Dmitry Baryshkov wrote:
> Specify board data size (and board.bin filename) for the WCN3990
> platform.
>
> Reported-by: Yongqin Liu
> Fixes: 03a72288c546 ("ath10k: wmi: add hw params entry for wcn3990")
> Signed-off-by: Dmitry Baryshkov
> Signed-off-by: Kalle
Eric Park writes:
> Resending as I forgot to CC the mailing list, sorry! I've added some
> more info since the last email.
Thanks. Let's keep the discussion on the list so that others can join.
> On 2024-03-11 11:21, Kalle Valo wrote:
>> But with modern CPUs I would have
Marc Gonzalez writes:
> On 04/04/2024 17:28, Kalle Valo wrote:
>
>> Marc Gonzalez wrote:
>>
>>> On 04/04/2024 13:57, Kalle Valo wrote:
>>>
>>>> Dmitry Baryshkov wrote:
>>>>
>>>>> I'd say, we should take a st
t;ath10k: add debugfs support to get per peer tids log
> via tracing")
> Signed-off-by: Su Hui
> Acked-by: Jeff Johnson
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git, thanks.
c511a9c12674 wifi: ath10k: Fix an error code problem in
ath10k
.
>
> [1] https://lore.kernel.org/all/20240229225910.79e22...@kernel.org/
>
> Signed-off-by: Breno Leitao
> Tested-by: Kalle Valo
I assume this goes via net-next:
Acked-by: Kalle Valo
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
erage alloc_netdev() to allocate the
> net_device object at ath10k_core_create(). The free of the device occurs
> at ath10k_core_destroy().
>
> [1] https://lore.kernel.org/all/20240229225910.79e22...@kernel.org/
>
> Signed-off-by: Breno Leitao
I assume this goes via net-nex
i: qtnfmac: allocate dummy net_device dynamically")
> Signed-off-by: Breno Leitao
I assume this goes via net-next:
Acked-by: Kalle Valo
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Su Hui writes:
> Clang Static Checker (scan-build) Warning:
> drivers/net/wireless/ath/ath10k/debugfs_sta.c:line 429, column 3
> Value stored to 'ret' is never read.
>
> Return 'ret' rather than 'count' when 'ret' stores an error code.
> By the way, remove some useless code.
>
> Fixes:
e wireless drivers.
>
> PS: Due to lack of hardware, unfortunately most these patches are
> compiled tested only, except ath11k that was kindly tested by Kalle Valo.
>
> ---
> Changelog:
>
> v1:
> * https://lore.kernel.org/all/20240327200809.512867-1-lei...@deb
Breno Leitao writes:
> On Tue, Apr 09, 2024 at 01:03:21PM +0300, Kalle Valo wrote:
>
>> Breno Leitao writes:
>>
>> >> > Reading the issue, I am afraid that freeing netdev explicitly
>> >> > (free_netdev()) might not be the best approach at th
Breno Leitao writes:
>> > Reading the issue, I am afraid that freeing netdev explicitly
>> > (free_netdev()) might not be the best approach at the exit path.
>> >
>> > I would like to try to leverage the ->needs_free_netdev netdev
>> > mechanism to do the clean-up, if that makes sense. I've
Breno Leitao writes:
> Hello Kalle,
>
> On Fri, Apr 05, 2024 at 06:15:05PM +0300, Kalle Valo wrote:
>> Breno Leitao writes:
>>
>> > struct net_device shouldn't be embedded into any structure, instead,
>> > the owner should use the private space to
Breno Leitao writes:
> struct net_device shouldn't be embedded into any structure, instead,
> the owner should use the private space to embed their state into
> net_device.
>
> This patch set fixes the problem above for ath10k and ath11k. This also
> fixes the conversion of qtnfmac driver to the
Dmitry Baryshkov writes:
> On Fri, 5 Apr 2024 at 14:57, Kalle Valo wrote:
>
>>
>> Dmitry Baryshkov writes:
>>
>> > On Tue, 30 Jan 2024 at 08:47, Dmitry Baryshkov
>> > wrote:
>> >
>> >>
>> >> The ath10k driver fails
Dmitry Baryshkov writes:
> On Fri, 5 Apr 2024 at 15:01, Kalle Valo wrote:
>
>>
>> Dmitry Baryshkov writes:
>>
>> > On Fri, 8 Mar 2024 at 17:19, Kalle Valo wrote:
>> >>
>> >> Dmitry Baryshkov writes:
>> >>
>>
rzysztof Kozlowski
> Signed-off-by: Dmitry Baryshkov
> Signed-off-by: Kalle Valo
2 patches applied to ath-next branch of ath.git, thanks.
158fff51b4c3 dt-bindings: net: wireless: ath10k: describe firmware-name property
5abf259772df wifi: ath10k: support board-specific firmw
Dmitry Baryshkov writes:
> On Fri, 8 Mar 2024 at 17:19, Kalle Valo wrote:
>>
>> Dmitry Baryshkov writes:
>>
>> >> To be on the safe side using 'qcom-rb1' makes sense but on the other
>> >> hand that means we need to update linux-firmware (basic
Dmitry Baryshkov writes:
> On Tue, 30 Jan 2024 at 08:47, Dmitry Baryshkov
> wrote:
>
>>
>> The ath10k driver fails to properly handle fallback from board-2.bin to
>> board.bin for WCN3990 cards. This happens because the
>> ath10k_hw_params_list doesn't include .fw.board* parameters for the
>>
Krzysztof Kozlowski wrote:
> This driver's initialization functions do not perform any custom code,
> except printing messages. Printing messages on modules
> loading/unloading is discouraged because it pollutes the dmesg
> regardless whether user actually has this device. Core kernel code
>
Marc Gonzalez writes:
> On 04/04/2024 13:57, Kalle Valo wrote:
>
>> Dmitry Baryshkov wrote:
>>
>>> I'd say, we should take a step back and actually verify how this was
>>> handled in the vendor kernel.
>>
>> One comment related to this: usually
Dmitry Baryshkov writes:
>> 3) ADD that compatible to the wifi node in msm8998.dtsi
>>compatible = "qcom,wcn3990-wifi", "qcom,msm8998-wifi";
>> 4) In the driver, set qmi->fake_msa_ready_indicator to true if we
>> detect "qcom,msm8998-wifi"
>>
>> And this approach would be acceptable to both
Jeff Johnson writes:
> On 3/29/2024 9:47 PM, Dmitry Baryshkov wrote:
>
>> On Wed, 6 Mar 2024 at 10:16, Dmitry Baryshkov
>> wrote:
>>>
>>> On WCN3990 platforms actual firmware, wlanmdsp.mbn, is sideloaded to the
>>> modem DSP via the TQFTPserv. These MBN files are signed by the device
>>>
kernel code
> already gives tools to investigate whether module was loaded or not.
>
> Drop the printing messages which allows to replace open-coded
> module_sdio_driver().
>
> Signed-off-by: Krzysztof Kozlowski
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch
Krzysztof Kozlowski writes:
> On 03/04/2024 15:50, Kalle Valo wrote:
>
>> Jeff Johnson writes:
>>
>>> On 3/29/2024 10:10 AM, Krzysztof Kozlowski wrote:
>>>> This driver's initialization functions do not perform any custom code,
>>>> exce
tree:
Acked-by: Kalle Valo
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
his via sdio tree:
Acked-by: Kalle Valo
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
uch as possible. In this patchset I'm
not anticipating any conflicts with wireless trees, so if we can avoid
any conflicts, please take this patchset via the other tree:
Acked-by: Kalle Valo
I'll drop this patchset from my queue. But if I should take these to
wireless trees instead just le
Kalle Valo wrote:
> Hi,
>
> Please pull, more information in the tag below.
>
> Kalle
>
>
> The following changes since commit f654e228ed6b822e87e6e6ad8e889bedccae2e16:
>
> Merge tag 'ath-next-20240305' of
> git://git.kernel.org/pub/scm/linux/kernel/g
obsolete struct wmi_start_scan_arg
wifi: ath11k: remove obsolete struct wmi_start_scan_arg
wifi: ath11k: fix soc_dp_stats debugfs file permission
Kalle Valo (7):
wifi: ath6kl: fix sparse warnings
wifi: wcn36xx: buff_to_be(): fix sparse warnings
wifi: wcn36xx: main: fix
Jakub Kicinski writes:
> On Fri, 22 Mar 2024 07:58:02 -0700 Breno Leitao wrote:
>> > Looks like init_dummy_netdev wipes the netdev structure clean, so I
>> > don't think we can use it directly as the setup function, Breno :(
>>
>> Before my patch, init_dummy_netdev was being also used. The
).
>
> sprintf() will be converted as weel if they have.
>
> Generally, this patch is generated by
> make coccicheck M= MODE=patch \
> COCCI=scripts/coccinelle/api/device_attr_show.cocci
>
> No functional change intended
>
> CC: Kalle Valo
> CC: Jeff Johnson
Jeff Johnson writes:
> On 3/19/2024 3:47 AM, Breno Leitao wrote:
>> Embedding net_device into structures prohibits the usage of flexible
>> arrays in the net_device structure. For more details, see the discussion
>> at [1].
>>
>> Un-embed the net_device from struct ath10k by converting it
>>
Eric Park writes:
> Hello! I have a Samsung NT500R5H-Y53L with the QCA6174 card, and I
> noticed I was getting terrible performance (around 20-30 Mbps)
> compared to other devices on the network (600-700 Mbps), when running
> a speedtest.
>
> I tried modifying some settings and discovered that I
Dmitry Baryshkov writes:
>> To be on the safe side using 'qcom-rb1' makes sense but on the other
>> hand that means we need to update linux-firmware (basically add a new
>> symlink) everytime a new product is added. But are there going to be
>> that many new ath10k based products?
>>
>> Using
.org/linux-wireless/304ce305-fbe6-420e-ac2a-d61ae5e6c...@gmail.com/
> Signed-off-by: Baochen Qiang
> Acked-by: Jeff Johnson
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git, thanks.
e57b7d62a1b2 wifi: ath10k: poll service ready message before failing
--
http
Robert Marko writes:
> On Wed, Mar 6, 2024 at 8:23 PM Jeff Johnson wrote:
>
>>
>> Historically, prior to being incorporated into the linux-firmware
>> project, firmware for kernel.org ath1*k drivers has been first published
>> to Kalle's GitHub:
>> https://github.com/kvalo/ath10k-firmware
>>
Dmitry Baryshkov writes:
> On Wed, 6 Mar 2024 at 11:04, Kalle Valo wrote:
>
>>
>> Dmitry Baryshkov writes:
>>
>> > On WCN3990 platforms actual firmware, wlanmdsp.mbn, is sideloaded to the
>> > modem DSP via the TQFTPserv. These MBN files are signed b
Dmitry Baryshkov writes:
> On WCN3990 platforms actual firmware, wlanmdsp.mbn, is sideloaded to the
> modem DSP via the TQFTPserv. These MBN files are signed by the device
> vendor, can only be used with the particular SoC or device.
>
> Unfortunately different firmware versions come with
Dmitry Baryshkov writes:
> Different Qualcomm platforms using WCN3990 WiFI chip use SoC-specific
> firmware versions with different features. For example firmware for
> SDM845 doesn't use single-chan-info-per-channel feature, while firmware
> for QRB2210 / QRB4210 requires that feature. Allow
Marc Gonzalez writes:
> On 05/03/2024 15:31, Kalle Valo wrote:
>
>> Thanks, this is exactly what I'm proposing.
>
> With your suggestions, the patch becomes much simpler:
Nice, looks good to me.
> I need to build a kernel + rootfs + FW to test the proposed solution,
>
Kalle Valo wrote:
> Hi,
>
> Please pull, more information in the tag below.
>
> Kalle
>
>
> The following changes since commit a4634aa71fee11f5e3e13bf7d80ee1480a64ce70:
>
> bonding: rate-limit bonding driver inspect messages (2024-02-22 19:13:18
> -08
: constify MHI channel and controller configs
Kalle Valo (2):
wifi: ath11k: thermal: don't try to register multiple times
wifi: ath12k: fix license in p2p.c and p2p.h
Kang Yang (1):
wifi: ath12k: add rcu lock for ath12k_wmi_p2p_noa_event()
.../bindings/net/wireless/qcom,ath10k.yaml
Marc Gonzalez writes:
> On 29/02/2024 19:40, Conor Dooley wrote:
>
>> On Wed, Feb 28, 2024 at 06:37:08PM +0200, Kalle Valo wrote:
>>
>>> Marc Gonzalez wrote:
>>>
>>>> As mentioned in my other reply, there are several msm8998-based
>>&g
Conor Dooley writes:
> On Wed, Feb 28, 2024 at 06:37:08PM +0200, Kalle Valo wrote:
>> Marc Gonzalez writes:
>
>> > As mentioned in my other reply, there are several msm8998-based
>> > devices affected by this issue. Is it not appropriate to consider
>> > a
Marc Gonzalez writes:
> On 01/03/2024 09:10, Kalle Valo wrote:
>
>> Marc Gonzalez wrote:
>>
>>> Kalle Valo wrote:
>>>
>>>> Here's one example where in ath10k we use a feature bit as a workaround:
>>>>
>>>>/* Don't trus
Marc Gonzalez writes:
>> Here's one example where in ath10k we use a feature bit as a workaround:
>>
>> /* Don't trust error code from otp.bin */
>> ATH10K_FW_FEATURE_IGNORE_OTP_RESULT = 7,
>>
>>
>>
>> if (!(skip_otp || test_bit(ATH10K_FW_FEATURE_IGNORE_OTP_RESULT,
Dmitry Baryshkov writes:
> Different Qualcomm platforms using WCN3990 WiFI chip use SoC-specific
> firmware versions with different features. For example firmware for
> SDM845 doesn't use single-chan-info-per-channel feature, while firmware
> for QRB2210 / QRB4210 requires that feature. Allow
Baochen Qiang writes:
> Currently host relies on CE interrupts to get notified that
> the service ready message is ready. This results in timeout
> issue if the interrupt is not fired, due to some unknown
> reasons. See below logs:
>
> [76321.937866] ath10k_pci :02:00.0: wmi service ready
Marc Gonzalez writes:
> On 28/02/2024 15:03, Kalle Valo wrote:
>
>> Marc Gonzalez writes:
>>
>>> + qcom,no-msa-ready-indicator:
>>> +type: boolean
>>> +description:
>>> + The driver waits for this indicator before proceed
Marc Gonzalez writes:
> The driver waits for this indicator before proceeding,
> yet some WCNSS firmwares apparently do not send it.
> On those devices, it seems safe to ignore the indicator,
> and continue loading the firmware.
>
> Signed-off-by: Pierre-Hugues Husson
> Signed-off-by: Marc
Baochen Qiang writes:
> Currently host relies on CE interrupts to get notified that
> the service ready message is ready. This results in timeout
> issue if the interrupt is not fired, due to some unknown
> reasons. See below logs:
>
> [76321.937866] ath10k_pci :02:00.0: wmi service ready
Jeff Johnson wrote:
> Add Jeff Johnson as a maintainer of the qcom,ath1*k.yaml files.
>
> Signed-off-by: Jeff Johnson
> Acked-by: Krzysztof Kozlowski
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git, thanks.
1098eb62433c dt-bindings: net: wireles
Kalle Valo writes:
> Hi,
>
> Here's an ath-next pull request to wireless-next. More info below.
>
> Kalle
>
> The following changes since commit 2a71528427c635f0a8bff704b2e62ce81c641d6f:
>
> wifi: brcmfmac: fix copyright year mentioned in platform_data header
&
Hi,
Here's an ath-next pull request to wireless-next. More info below.
Kalle
The following changes since commit 2a71528427c635f0a8bff704b2e62ce81c641d6f:
wifi: brcmfmac: fix copyright year mentioned in platform_data header
(2024-01-31 18:48:06 +0200)
are available in the Git repository at:
Jeff Johnson wrote:
> I now have a @kernel.org e-mail address, so use that for my
> maintenance activities.
>
> Signed-off-by: Jeff Johnson
2 patches applied to wireless.git, thanks.
27dc4c6ee5fe MAINTAINERS: wifi: update Jeff Johnson e-mail address
1b7d9ab3e666 MAINTAINERS: wifi: Add N:
Baochen Qiang writes:
> On 1/31/2024 8:35 PM, Kalle Valo wrote:
>> + ath11k list
>> kernel test robot writes:
>>
>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
>>> pending
>>> head: 2c4
Kalle Valo wrote:
> Hi,
>
> Our ath-next pull request for wireless-next.
>
> Kalle
>
> The following changes since commit c5a3f56fcdb0a48a20772e4c9b8adc6c7256a461:
>
> Merge tag 'ath-next-20231215' of
> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath
+ ath11k list
kernel test robot writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git pending
> head: 2c471f31297856be56f60ef29f2565dea1470800
> commit: 92425f788feede9bf152ecf3fb7a264942ee7719 [47/100] wifi:
> ath11k: fill parameters for vdev set tpc power WMI
-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37 (2024-01-30
19:58:18 +0200)
Kalle Valo (1):
ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37
WHENCE| 2 +-
ath11k
Hi,
Our ath-next pull request for wireless-next.
Kalle
The following changes since commit c5a3f56fcdb0a48a20772e4c9b8adc6c7256a461:
Merge tag 'ath-next-20231215' of
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath (2023-12-17 13:20:18
+0200)
are available in the Git repository at:
ing: Enum value
> 'WMI_10_4_REPORT_AIRTIME' not described in enum 'wmi_10_4_feature_mask'
>
> Update the kernel-doc for enum wmi_10_4_feature_mask to add the
> missing documentation.
>
> No functional changes, compile tested only.
>
> Signed-off-by: Jeff Johnson
> Sig
Karthikeyan Periyasamy wrote:
> ENOTSUPP is not a standard error code, don't use it. Replace with
> EOPNOTSUPP instead.
>
> No functional changes, compile tested only.
>
> Signed-off-by: Karthikeyan Periyasamy
> Acked-by: Jeff Johnson
> Signed-off-by: Kalle Valo
to 17509e53b97baaefeb287b98d3358da8a6e1c199:
ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36 (2023-12-21
16:13:58 +0200)
Kalle Valo (9):
ath12k: add new driver and firmware for WCN7850
ath10k: QCA6174 hw3.0: update
; Reviewed-by: Kees Cook
> Reviewed-by: Gustavo A. R. Silva
> Signed-off-by: Kalle Valo
6 patches applied to ath-next branch of ath.git, thanks.
d2eb318f4b6b wifi: ath10k: use flexible array in struct wmi_host_mem_chunks
72ca7c4073ac wifi: ath10k: use flexible arrays for WMI start scan TLVs
26eb7
ingyuan Mo
> Acked-by: Jeff Johnson
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git, thanks.
ad25ee36f001 wifi: ath10k: fix NULL pointer dereference in
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()
--
https://patchwork.kernel.org/project/linux-wireless/patch/2023120
Kalle Valo wrote:
> Hi,
>
> Now that Jeff is also the ath maintainer we decided to start doing
> proper pull requests. Earlier I was just merging ath-next directly to
> wireless-next. So here's our first pull request, let's see if we got it
> right :)
>
> Kalle
>
&g
Jiri Slaby (SUSE) (1):
wifi: ath5k: remove unused ath5k_eeprom_info::ee_antenna
Justin Stitt (1):
wifi: ath10k: replace deprecated strncpy with memcpy
Kalle Valo (1):
wifi: ath11k: workaround too long expansion sparse warnings
Kang Yang (8):
wifi: ath12k: get msi_data
Dmitry Baryshkov writes:
> We'd like to ask for inclusion of the board file for the Qualcomm
> SDM845 MTP board. It is a hardware development kit manufactured by
> Qualcomm, using the Snapdragon SDM845 SoC and a variant of wcn3990
> BT/WiFi chip.
>
> Following the questions from the ath10k wiki
Erkki hietaranta writes:
> ASUS MAP-AC2200 is IPQ4019 based device with three radios.
> - one QCA40xx radio is used as 2.4GHz radio
> - one QCA40xx radio is used as 5GHz radio
> -- Both allready supported:
> https://www.mail-archive.com/ath10k@lists.infradead.org/msg09696.html
> - one QCA9888
Dmitry Baryshkov writes:
> We'd like to ask for inclusion of the board file for the Qualcomm
> SDM845 MTP board. It is a hardware development kit manufactured by
> Qualcomm, using the Snapdragon SDM845 SoC and a variant of wcn3990
> BT/WiFi chip.
>
> Following the questions from the ath10k wiki
Dylan Van Assche writes:
> I would like to include the board file for the Xiaomi POCOPHONE F1
> smartphone.
> This smartphone is manufactured by Xiaomi and uses the Snapdragon
> SDM845 SoC.
> At postmarketOS, we run the mainline kernel on this phone so shipping
> this board file
> from upstream
Dylan Van Assche writes:
> I would like to include the board file for the SHIFTPHONES SHIFT6mq
> smartphone.
> This smartphone is manufactured by SHIFTPHONES and uses the Snapdragon
> SDM845 SoC.
> At postmarketOS, we run the mainline kernel on this phone so shipping
> this board file
> from
Dmitry Baryshkov writes:
> We'd like to ask for inclusion of the board file for the Qualcomm
> Robotics RB2 platform. It is
> an IOT platform manufactured by Thundercomm, using the Snapdragon QRB4210 SoC.
>
> Following the questions from the ath10k wiki page:
>
> * description for what hardware
Dylan Van Assche writes:
> I would like to include the board file for the Oneplus 6/6T smartphone.
> This smartphone is manufactured by Oneplus and uses the Snapdragon
> SDM845 SoC.
> At postmarketOS, we run the mainline kernel on this phone so shipping
> this board file
> from upstream would be
Dmitry Baryshkov writes:
> Hello Kalle,
>
> We'd like to ask for inclusion of the board file for the Qualcomm
> Robotics RB1 platform. It is
> an IOT platform manufactured by Thundercomm, using the Snapdragon QRB2210 SoC.
>
> Following the questions from the ath10k wiki page:
>
> * description
"Connor Northway" writes:
> Hello,
>
> I am preparing a commit to port OpenWrt to the Eero Cento, and would
> like to provide its board files for inclusion in the official file.
>
> Following the wiki's form:
>
> description for what hardware this is:
>
>- the Eero Cento (model no. J010001)
Yongqin Liu writes:
> On Sat, 1 Jul 2023 at 06:19, Douglas Anderson wrote:
>>
>> As talked about in commit d66d24ac300c ("ath10k: Keep track of which
>> interrupts fired, don't poll them"), if we access the copy engine
>> register at a bad time then ath10k can go boom. However, it's not
>>
Xingyuan Mo writes:
> We should check whether the WMI_TLV_TAG_STRUCT_MGMT_TX_COMPL_EVENT tlv is
> present before accessing it, otherwise a null pointer deference error will
> occur.
I cannot take patches without s-o-b, please read:
"Gustavo A. R. Silva" writes:
> On 12/5/23 09:29, Kalle Valo wrote:
>> Jeff Johnson writes:
>>
>>> On 11/27/2023 8:23 AM, Gustavo A. R. Silva wrote:
>>>
>>>>
>>>>
>>>> On 11/27/23 10:14, Jeff Johnson wrote:
>>
1 - 100 of 2504 matches
Mail list logo