mirror of https://lore.kernel.org/ath12k/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>,
	neil.armstrong@linaro.org,
	Vasanthakumar Thiagarajan <quic_vthiagar@quicinc.com>,
	Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Jeff Johnson <jjohnson@kernel.org>,
	Aditya Kumar Singh <quic_adisi@quicinc.com>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH net] wifi: ath12k: properly set single_chip_mlo_supp to true in ath12k_core_alloc()
Date: Wed, 19 Mar 2025 11:29:18 +0100	[thread overview]
Message-ID: <91a5a1f7-6eef-4ea0-bcde-350640984a7b@kernel.org> (raw)
In-Reply-To: <38cd738c-1a2a-4382-80f8-d57feb7c829d@quicinc.com>

On 19/03/2025 10:46, Baochen Qiang wrote:
> 
> 
> On 3/19/2025 5:12 PM, neil.armstrong@linaro.org wrote:
>> Hi,
>>
>> On 19/03/2025 10:06, Vasanthakumar Thiagarajan wrote:
>>>
>>>
>>> On 3/19/2025 1:34 PM, Neil Armstrong wrote:
>>>> On 18/03/2025 17:35, Jeff Johnson wrote:
>>>>> On 3/3/2025 7:00 AM, Neil Armstrong wrote:
>>>>>> In commit 46d16f7e1d14 ("wifi: ath12k: rename mlo_capable_flags to
>>>>>> single_chip_mlo_supp")
>>>>>> the line:
>>>>>>     ab->mlo_capable_flags = ATH12K_INTRA_DEVICE_MLO_SUPPORT;
>>>>>> was incorrectly updated to:
>>>>>>     ab->single_chip_mlo_supp = false;
>>>>>> leading to always disabling INTRA_DEVICE_MLO even if the device supports it.
>>>>>>
>>>>>> The firmware "WLAN.HMT.1.1.c5-00156-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1"
>>>>>> crashes on driver initialization with:
>>>>>>   ath12k_pci 0000:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0x3d soc_id 0x40170200
>>>>>>   ath12k_pci 0000:01:00.0: fw_version 0x110f009c fw_build_timestamp 2024-05-30 11:35
>>>>>> fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c5-00156-
>>>>>> QCAHMTSWPL_V1.0_V2.0_SILICONZ-1
> 
> this FW version is not upstream yet, why are you testing with it?
> 
> Generally we only support upstrmea driver + upstream FW.
FW does not have to be upstream. We work, here in upstream, with all
sort of vendors and all sorts of devices, for which vendors might not
send yet their FW or we are unclear about licensing rules.

Regression is still regression and stop deflecting the discussion -
third response now! - what you internally want to achieve.

Upstream does not care about your internal processes.


Best regards,
Krzysztof


  parent reply	other threads:[~2025-03-19 10:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 15:00 [PATCH net] wifi: ath12k: properly set single_chip_mlo_supp to true in ath12k_core_alloc() Neil Armstrong
2025-03-18 16:35 ` Jeff Johnson
2025-03-19  8:04   ` Neil Armstrong
2025-03-19  9:06     ` Vasanthakumar Thiagarajan
2025-03-19  9:12       ` neil.armstrong
2025-03-19  9:46         ` Baochen Qiang
2025-03-19 10:00           ` neil.armstrong
2025-03-19 10:18             ` Dmitry Baryshkov
2025-03-19 10:21               ` neil.armstrong
2025-03-19 10:23                 ` Dmitry Baryshkov
2025-03-19 10:33               ` Krzysztof Kozlowski
2025-03-19 11:22                 ` Dmitry Baryshkov
2025-03-19 11:31             ` Dmitry Baryshkov
2025-03-19 10:29           ` Krzysztof Kozlowski [this message]
2025-03-19 11:25             ` Dmitry Baryshkov
2025-03-20  7:21               ` Krzysztof Kozlowski
2025-03-19 18:24           ` Jeff Johnson
2025-03-19 10:27       ` Krzysztof Kozlowski
2025-03-19 11:32         ` Vasanthakumar Thiagarajan
2025-03-19 11:51           ` Dmitry Baryshkov
2025-03-19 12:54             ` Vasanthakumar Thiagarajan
2025-03-19 13:33               ` Dmitry Baryshkov
2025-03-19 17:23                 ` Vasanthakumar Thiagarajan
2025-03-20  7:23                 ` Vasanthakumar Thiagarajan
2025-03-20 10:06                   ` neil.armstrong
2025-03-19 18:32         ` Jeff Johnson
2025-03-20 10:14           ` neil.armstrong

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=91a5a1f7-6eef-4ea0-bcde-350640984a7b@kernel.org \
    --to=krzk@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_adisi@quicinc.com \
    --cc=quic_bqiang@quicinc.com \
    --cc=quic_vthiagar@quicinc.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