From: Anilkumar Kolli <akolli@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Jouni Malinen <jouni@codeaurora.org>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/4] ath11k: add caldata download support from EEPROM
Date: Mon, 27 Sep 2021 10:12:35 +0530 [thread overview]
Message-ID: <53726bfd2c5d7911dc8433e7fd82d238@codeaurora.org> (raw)
In-Reply-To: <875yuqrp4d.fsf@codeaurora.org>
On 2021-09-24 20:34, Kalle Valo wrote:
> Jouni Malinen <jouni@codeaurora.org> writes:
>
>> From: Anilkumar Kolli <akolli@codeaurora.org>
>>
>> Firmware updates EEPROM support capability in QMI FW caps, send QMI
>> BDF
>> download request message with file type EEPROM, to get caldata
>> download
>> from EEPROM. Firmware takes more time to update cal data from EEPROM,
>> so
>> increase QMI timeout.
>
> The commit log would need more explanation how this patch works.
>
FW advertizes calibration data support from EEPROM through
'eeprom_read_timeout' in
QMI FW Capability message. Ath11k sends BDF download request with file
type
'ATH11K_QMI_FILE_TYPE_EEPROM'. FW has logic to read calibration data
from EEPROM and
process the calibration data. FW takes more time to process the
calibration data from
EEPROM so increase QMI timeout to 10msec.
--
- Anil.
next prev parent reply other threads:[~2021-09-27 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 20:19 [PATCH 0/4] ath11k: Add caldata download support from file/EEPROM Jouni Malinen
2021-07-21 20:19 ` [PATCH 1/4] ath11k: use hw_params to access board_size and cal_offset Jouni Malinen
2021-09-24 14:49 ` Kalle Valo
2021-09-27 4:21 ` akolli
2021-09-28 10:50 ` Kalle Valo
2021-07-21 20:19 ` [PATCH 2/4] ath11k: clean up BDF download functions Jouni Malinen
2021-07-21 20:19 ` [PATCH 3/4] ath11k: add caldata file for multiple radios Jouni Malinen
2021-07-21 20:19 ` [PATCH 4/4] ath11k: add caldata download support from EEPROM Jouni Malinen
2021-09-24 15:04 ` Kalle Valo
2021-09-27 4:42 ` Anilkumar Kolli [this message]
2021-09-28 9:24 ` Kalle Valo
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=53726bfd2c5d7911dc8433e7fd82d238@codeaurora.org \
--to=akolli@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=jouni@codeaurora.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).