From: Vasanthakumar Thiagarajan <quic_vthiagar@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
"Vasanthakumar Thiagarajan"
<vasanthakumar.thiagarajan@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
<neil.armstrong@linaro.org>,
"Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
Johannes Berg <johannes@sipsolutions.net>,
Jeff Johnson <jjohnson@kernel.org>,
"Aditya Kumar Singh" <quic_adisi@quicinc.com>,
<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 22:53:43 +0530 [thread overview]
Message-ID: <83c71791-dc34-54a5-7d67-9765aa2886e5@quicinc.com> (raw)
In-Reply-To: <hmfvyajygmjoeaaashmddu4rg6ttzn7es4sjls5qvnemykkx2l@zuzixrzkmkgx>
On 3/19/2025 7:03 PM, Dmitry Baryshkov wrote:
> On Wed, Mar 19, 2025 at 06:24:57PM +0530, Vasanthakumar Thiagarajan wrote:
>>
>>
>> On 3/19/2025 5:21 PM, Dmitry Baryshkov wrote:
>>> On Wed, Mar 19, 2025 at 05:02:39PM +0530, Vasanthakumar Thiagarajan wrote:
>>>>
>>>>
>>>> On 3/19/2025 3:57 PM, Krzysztof Kozlowski wrote:
>>>>> On 19/03/2025 10:06, Vasanthakumar Thiagarajan wrote:
>>>>>>>>> ---
>>>>>>>>> base-commit: 7eb172143d5508b4da468ed59ee857c6e5e01da6
>>>>>>>>> change-id: 20250303-topic-ath12k-fix-crash-49e9055c61a1
>>>>>>>>>
>>>>>>>>> Best regards,
>>>>>>>>
>>>>>>>> NAK since this will break QCN
>>>>>>>> There is a series under internal review to address MLO issues for WCN chipsets
>>>>>>>
>>>>>>> ???
>>>>>>>
>>>>>>> The original commit is wrong, this fixes the conversion, nothing else.
>>>>>>
>>>>>> Nope. Driver changes to enable MLO with WCN chipset are not there yet.
>>>>>> Setting the mlo capability flag without having required driver changes
>>>>>> for WCN chipset will likely result in firmware crash. So the recommendation
>>>>>> is to enable MLO (in WCN) only when all the necessary driver changes
>>>>>> (in development, public posting in near future) are in place.
>>>>> Really, these are your answers? There is regression and first reply is
>>>>> upstream should wait for whatever you do internally. Second answer is
>>>>> the same - public posting in near future?
>>>>>
>>>>
>>>> May be I was not clear in my response. I was not telling MLO bug fixes were
>>>> in the development. Actually the MLO feature itself is not enabled
>>>> yet with WCN chip sets. Any code changes enabling it without full feature
>>>> support would result in firmware crashes with the existing firmware binaries
>>>> available in upstream.
>>>
>>> Is there an undocumented change of the behaviour in the commit
>>> 46d16f7e1d14 ("wifi: ath12k: rename mlo_capable_flags to
>>> single_chip_mlo_supp")?
>>>
>>
>> diff --git a/drivers/net/wireless/ath/ath12k/qmi.c b/drivers/net/wireless/ath/ath12k/qmi.c
>>
>> - if (resp.single_chip_mlo_support_valid) {
>> - if (resp.single_chip_mlo_support)
>> - ab->mlo_capable_flags |= ATH12K_INTRA_DEVICE_MLO_SUPPORT;
>> - else
>> - ab->mlo_capable_flags &= ~ATH12K_INTRA_DEVICE_MLO_SUPPORT;
>> - }
>>
>> The above logic seems to keep the initialized intra MLO support even when
>> single_chip_mlo_support_valid is not set. The above code removal is correct as
>> MLO support can not be enabled in host when firmware does not advertise it.
>
> Ack
>
>>
>> diff --git a/drivers/net/wireless/ath/ath12k/core.c b/drivers/net/wireless/ath/ath12k/core.c
>>
>
> You skipped an important chunk:
>
> - ab->mlo_capable_flags = ATH12K_INTRA_DEVICE_MLO_SUPPORT;
>> + ab->single_chip_mlo_supp = false;
>
> Is this an _undocumented_ change? I think it is. If the developer has
> described that the commit disables MLO, there would be no such
> questions.
>
Right. Since MLO was WCN was not supported, this default configuration was
changed to avoid potential issues due to partial MLO configurations with
official upstream firmware binaries.
>> diff --git a/drivers/net/wireless/ath/ath12k/qmi.c b/drivers/net/wireless/ath/ath12k/qmi.c
>>
>> + if (resp.single_chip_mlo_support_valid &&
>> + resp.single_chip_mlo_support)
>> + ab->single_chip_mlo_supp = true;
>>
>> The above code does it in right way. Overriding firmware MLO capability as done
>> in the submitted patch under review is obviously wrong. The firmware used to report
>> the issue seems to have an odd behavior: 1. it does not seem to advertise MLO
>> capability in single_chip_mlo_support bit and 2. expects configurations to enable
>> MLO from host. None of the WCN firmware available in upstream either advertises
>> MLO capability or expects configurations to enable MLO from host.
>
> Additionally, from the commit message:
>
> For the WCN7850 family of chipsets, since the event is not supported,
> assumption is made that single chip MLO is supported.
>
> However the code doesn't contain that change. Instead single chip MLO is
> unconditionally disabled.
>
This text in commit message seems to be a miss. This should have been
removed as the merged patch version completely disables MLO for WCN
chip.
Vasanth
next prev parent reply other threads:[~2025-03-19 17:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 15:00 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
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 [this message]
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=83c71791-dc34-54a5-7d67-9765aa2886e5@quicinc.com \
--to=quic_vthiagar@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk@kernel.org \
--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=vasanthakumar.thiagarajan@oss.qualcomm.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
all inboxes | Powered by JetHome®