From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 2/7] ath10k: add ATH10K_FW_IE_WMI_OP_VERSION
Date: Tue, 2 Dec 2014 10:48:46 +0200 [thread overview]
Message-ID: <8761duphch.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQ=mx2PSX2uDKrN6pk+YN0e8s8Q1xGZpe0yG-4rT+Hn25Q@mail.gmail.com> (Michal Kazior's message of "Tue, 2 Dec 2014 09:28:34 +0100")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 1 December 2014 at 15:45, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> [...]
>> diff --git a/drivers/net/wireless/ath/ath10k/core.h b/drivers/net/wireless/ath/ath10k/core.h
>> index 514c219263a5..92b04fe73151 100644
>> --- a/drivers/net/wireless/ath/ath10k/core.h
>> +++ b/drivers/net/wireless/ath/ath10k/core.h
>> @@ -120,6 +120,7 @@ struct ath10k_mem_chunk {
>> };
>>
>> struct ath10k_wmi {
>> + unsigned int op_version;
>
> I wonder - can't we have this as `enum ath10k_fw_wmi_op_version op_version;` ?
Oh yes, I was even planning to change it but apparently forgot. Will fix
in v4.
>> @@ -378,8 +379,9 @@ enum ath10k_fw_features {
>> /* Firmware does not support P2P */
>> ATH10K_FW_FEATURE_NO_P2P = 3,
>>
>> - /* Firmware 10.2 feature bit. The ATH10K_FW_FEATURE_WMI_10X feature bit
>> - * is required to be set as well.
>> + /* Firmware 10.2 feature bit. The ATH10K_FW_FEATURE_WMI_10X feature
>> + * bit is required to be set as well. Deprecated, don't use in new
>> + * code.
>
> Just out of curiosity - any plans how long this is going to be
> depracated until removed/replaced?
So there are two parts:
1) In the driver we should not use these deprated flags with new code,
and preferably remove existing uses bit by bit. But for backwards
compatibility we will keep the flags in
ath10k_core_init_firmware_features() so that we can set correct
wmi.op_version when using firmware images which don't have
ATH10K_FW_IE_WMI_OP_VERSION.
2) In firmware images we will continue use the deprecated flags with
main, 10.1 and 10.2 firmware branches, at least for the time being.
This makes it possible to have new firmware releases working on older
drivers.
>> diff --git a/drivers/net/wireless/ath/ath10k/hw.h b/drivers/net/wireless/ath/ath10k/hw.h
>> index dfedfd0e0f34..04aaf9af3ca0 100644
>> --- a/drivers/net/wireless/ath/ath10k/hw.h
>> +++ b/drivers/net/wireless/ath/ath10k/hw.h
>> @@ -58,6 +58,16 @@ enum ath10k_fw_ie_type {
>> ATH10K_FW_IE_FEATURES = 2,
>> ATH10K_FW_IE_FW_IMAGE = 3,
>> ATH10K_FW_IE_OTP_IMAGE = 4,
>> +
>> + /* WMI "operations" interface version, 32 bit value. Supported from
>> + * FW API 4 and above. */
>> + ATH10K_FW_IE_WMI_OP_VERSION = 5,
>
> Hmm.. shouldn't we bump up the firmware filename from -3 to -4 and try
> loading 4..3..2..1?
I was thinking that we add FW API 4 only once we have all necessary
changes for the new hw. For example, in case we need HTT changes as
well.
--
Kalle Valo
next prev parent reply other threads:[~2014-12-02 8:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 14:44 [PATCH v3 0/7] ath10k: add support for new wmi-tlv backend Kalle Valo
2014-12-01 14:44 ` [PATCH v3 1/7] ath10k: create ath10k_core_init_features() Kalle Valo
2014-12-02 6:58 ` Michal Kazior
2014-12-02 7:09 ` Kalle Valo
2014-12-01 14:45 ` [PATCH v3 2/7] ath10k: add ATH10K_FW_IE_WMI_OP_VERSION Kalle Valo
2014-12-02 8:28 ` Michal Kazior
2014-12-02 8:48 ` Kalle Valo [this message]
2014-12-02 11:51 ` Michal Kazior
2014-12-03 6:32 ` Kalle Valo
2014-12-02 12:16 ` Michal Kazior
2014-12-03 6:30 ` Kalle Valo
2014-12-01 14:45 ` [PATCH v3 3/7] ath10k: set max_num_pending_tx in ath10k_core_init_firmware_features() Kalle Valo
2014-12-01 14:45 ` [PATCH v3 4/7] ath10k: implement intermediate event args Kalle Valo
2014-12-01 14:46 ` [PATCH v3 5/7] ath10k: introduce wmi ops Kalle Valo
2014-12-01 14:46 ` [PATCH v3 6/7] ath10k: make some wmi functions public Kalle Valo
2014-12-01 14:46 ` [PATCH v3 7/7] ath10k: implement wmi-tlv backend Kalle Valo
2014-12-02 6:38 ` Michal Kazior
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=8761duphch.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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;
as well as URLs for NNTP newsgroup(s).