All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: ath12k@lists.infradead.org,
	 Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>,
	 linux-wireless@vger.kernel.org,
	 Ganesh Babu Jothiram <quic_gjothira@quicinc.com>
Subject: Re: [PATCH v3 12/13] wifi: ath12k: Read board id to support split-PHY QCN9274
Date: Thu, 15 Feb 2024 13:32:41 +0200	[thread overview]
Message-ID: <87bk8inesm.fsf@kernel.org> (raw)
In-Reply-To: <23399810.6Emhk5qWAg@ripper> (Sven Eckelmann's message of "Wed, 14 Feb 2024 15:17:11 +0100")

Sven Eckelmann <sven@narfation.org> writes:

> On Monday, 29 January 2024 07:57:23 CET Raj Kumar Bhagat wrote:
>> diff --git a/drivers/net/wireless/ath/ath12k/fw.c
>> b/drivers/net/wireless/ath/ath12k/fw.c
>> index fbcf40c97792..5be4b2d4a19d 100644
>> --- a/drivers/net/wireless/ath/ath12k/fw.c
>> +++ b/drivers/net/wireless/ath/ath12k/fw.c
>> @@ -119,6 +119,13 @@ static int
>> ath12k_fw_request_firmware_api_n(struct ath12k_base *ab,
> [...]
>> +		case ATH12K_FW_IE_AMSS_DUALMAC_IMAGE:
>> +			ath12k_dbg(ab, ATH12K_DBG_BOOT,
>> +				   "found dualmac fw image ie (%zd B)\n",
>> +				   ie_len);
>> +			ab->fw.amss_dualmac_data = data;
>> +			ab->fw.amss_dualmac_len = ie_len;
>> +			break;
>>  		default:
>>  			ath12k_warn(ab, "Unknown FW IE: %u\n", ie_id);
>>  			break;
>
>> @@ -371,16 +375,43 @@ int ath12k_mhi_register(struct ath12k_pci *ab_pci)
> [...]
>> +	if (dualmac) {
>> +		if (ab->fw.amss_dualmac_data && ab->fw.amss_dualmac_len > 0) {
>> +			/* use MHI firmware file from firmware-N.bin */
>> +			mhi_ctrl->fw_data = ab->fw.amss_dualmac_data;
>> +			mhi_ctrl->fw_sz = ab->fw.amss_dualmac_len;
>> +		} else {
>> + ath12k_warn(ab, "dualmac firmware IE not present in
>> firmware-N.bin\n");
>> +			ret = -ENOENT;
>> +			goto free_controller;
>> +		}
>
> I saw this now already multiple times that the source code was referencing the 
> firmware-N.bin (like we had with ath10k). But they aren't published anywhere. 
> I can't find a single one at:
>
> *
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ath11k
> *
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ath12k
> * https://github.com/kvalo/ath11k-firmware
> * https://github.com/quic/upstream-wifi-fw
>
> So I find it odd that the new code now seems to depend on it without actually 
> providing these files anywhere.

For example, firmware-2.bin will be used for qrtr id to support multiple
devices on the same host.

> Might be good to have these soon in linux-firmware.git.

Yeah, we will but just slowly. We are currently moving
ath1?k-firmware.git repos to a new location, firmware-N.bin files should
start emerging after that.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2024-02-15 11:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29  6:57 [PATCH v3 00/13] wifi: ath12k: QCN9274 dualmac bring up Raj Kumar Bhagat
2024-01-29  6:57 ` [PATCH v3 01/13] wifi: ath12k: indicate NON MBSSID vdev by default during vdev start Raj Kumar Bhagat
2024-01-31 21:04   ` Jeff Johnson
2024-02-02 12:33   ` Kalle Valo
2024-01-29  6:57 ` [PATCH v3 02/13] wifi: ath12k: fetch correct pdev id from WMI_SERVICE_READY_EXT_EVENTID Raj Kumar Bhagat
2024-01-31 21:05   ` Jeff Johnson
2024-01-29  6:57 ` [PATCH v3 03/13] wifi: ath12k: add support for peer meta data version Raj Kumar Bhagat
2024-01-31 21:05   ` Jeff Johnson
2024-01-29  6:57 ` [PATCH v3 04/13] wifi: ath12k: fix fetching MCBC flag for QCN9274 Raj Kumar Bhagat
2024-01-31 21:06   ` Jeff Johnson
2024-01-29  6:57 ` [PATCH v3 05/13] wifi: ath12k: Add logic to write QRTR node id to scratch Raj Kumar Bhagat
2024-01-31 21:06   ` Jeff Johnson
2024-02-02 12:20     ` Kalle Valo
2024-02-02 14:32       ` Raj Kumar Bhagat
2024-01-29  6:57 ` [PATCH v3 06/13] wifi: ath12k: fix firmware assert during insmod in memory segment mode Raj Kumar Bhagat
2024-01-31 21:06   ` Jeff Johnson
2024-01-29  6:57 ` [PATCH v3 07/13] wifi: ath12k: split hal_ops to support RX TLVs word mask compaction Raj Kumar Bhagat
2024-01-31 21:07   ` Jeff Johnson
2024-01-29  6:57 ` [PATCH v3 08/13] wifi: ath12k: remove hal_desc_sz from hw params Raj Kumar Bhagat
2024-01-31 21:07   ` Jeff Johnson
2024-01-29  6:57 ` [PATCH v3 09/13] wifi: ath12k: subscribe required word mask from rx tlv Raj Kumar Bhagat
2024-01-31 21:07   ` Jeff Johnson
2024-02-02 12:27   ` Kalle Valo
2024-02-02 14:28     ` Raj Kumar Bhagat
2024-01-29  6:57 ` [PATCH v3 10/13] wifi: ath12k: add MAC id support in WBM error path Raj Kumar Bhagat
2024-01-31 21:08   ` Jeff Johnson
2024-01-29  6:57 ` [PATCH v3 11/13] wifi: ath12k: fix PCI read and write Raj Kumar Bhagat
2024-01-31 21:08   ` Jeff Johnson
2024-01-29  6:57 ` [PATCH v3 12/13] wifi: ath12k: Read board id to support split-PHY QCN9274 Raj Kumar Bhagat
2024-01-31 21:09   ` Jeff Johnson
2024-02-14 14:17   ` Sven Eckelmann
2024-02-15 11:32     ` Kalle Valo [this message]
2024-01-29  6:57 ` [PATCH v3 13/13] wifi: ath12k: disable QMI PHY capability learn in split-phy QCN9274 Raj Kumar Bhagat
2024-01-30  1:52   ` Jeff Johnson
2024-01-30  3:04     ` Raj Kumar Bhagat
2024-01-31 21:08   ` Jeff Johnson

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=87bk8inesm.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_gjothira@quicinc.com \
    --cc=quic_rajkbhag@quicinc.com \
    --cc=sven@narfation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.