From: Bjorn Andersson <bjorn.andersson@linaro.org> To: Kalle Valo <kvalo@codeaurora.org> Cc: Amit Pundir <amit.pundir@linaro.org>, Rob Herring <robh@kernel.org>, Jeffrey Hugo <jeffrey.l.hugo@gmail.com>, netdev@vger.kernel.org, linux-wireless@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>, ath10k <ath10k@lists.infradead.org>, Konrad Dybcio <konradybcio@gmail.com>, dt <devicetree@vger.kernel.org>, David S Miller <davem@davemloft.net>, John Stultz <john.stultz@linaro.org>, Jakub Kicinski <kuba@kernel.org>, Sumit Semwal <sumit.semwal@linaro.org> Subject: Re: [PATCH] ath10k: Introduce a devicetree quirk to skip host cap QMI requests Date: Mon, 8 Feb 2021 11:48:20 -0600 [thread overview] Message-ID: <YCF5ZC/WMRefTRcQ@builder.lan> (raw) In-Reply-To: <87czxa4grv.fsf@codeaurora.org> On Mon 08 Feb 11:21 CST 2021, Kalle Valo wrote: > Amit Pundir <amit.pundir@linaro.org> writes: > > > Hi Kalle, > > > > On Mon, 7 Dec 2020 at 22:25, Kalle Valo <kvalo@codeaurora.org> wrote: > >> > >> This is firmware version specific, right? There's also enum > >> ath10k_fw_features which is embedded within firmware-N.bin, we could add > >> a new flag there. But that means that a correct firmware-N.bin is needed > >> for each firmware version, not sure if that would work out. Just > >> throwing out ideas here. > > > > Apologies for this late reply. I was out for a while. > > No worries. > > > If by that (the firmware version) you mean "QC_IMAGE_VERSION_STRING", > > then that may be a bit tricky. Pocophone F1 use the same firmware > > family version (WLAN.HL.2.0.XXX), used by Dragonboard 845c (which has > > Wi-Fi working upstream). > > I'm meaning the ath10k firmware meta data we have in firmware-N.bin > (N=2,3,4...) file. A quick summary: > > Every ath10k firmware release should have firmware-N.bin. The file is > created with this tool: > > https://github.com/qca/qca-swiss-army-knife/blob/master/tools/scripts/ath10k/ath10k-fwencoder > > firmware-N.bin contains various metadata, one of those being firmware > feature flags: > > enum ath10k_fw_features { > /* wmi_mgmt_rx_hdr contains extra RSSI information */ > ATH10K_FW_FEATURE_EXT_WMI_MGMT_RX = 0, > > /* Firmware from 10X branch. Deprecated, don't use in new code. */ > ATH10K_FW_FEATURE_WMI_10X = 1, > > [...] > > So what you could is add a new flag enum ath10k_fw_features, create a > new firmware-N.bin for your device and enable the flag on the firmware > releases for your device only. > > I don't know if this is usable, but one solution which came to my mind. It sounds quite reasonable to pass this using firmawre-N.bin instead of DT, however that would imply that we need to find firmware-N.bin in the device-specific directory, where we keep the wlanmdsp.mbn as well - and not under /lib/firmware/ath10k For other devices (e.g. ADSP, modem or wlanmdsp.mbn) we're putting these in e.g. /lib/firmware/qcom/LENOVO/81JL/ and specifies the location using a firmware-name property in DT. Regards, Bjorn > > -- > https://patchwork.kernel.org/project/linux-wireless/list/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2021-02-08 17:49 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-25 18:29 Amit Pundir 2020-09-26 0:00 ` Bjorn Andersson 2020-09-29 19:08 ` Rob Herring 2020-09-30 11:09 ` Amit Pundir 2020-10-29 13:40 ` Bjorn Andersson 2020-11-03 7:48 ` Amit Pundir 2020-11-24 17:51 ` Bjorn Andersson 2020-12-07 16:55 ` Kalle Valo 2021-02-02 11:11 ` Amit Pundir 2021-02-08 17:21 ` Kalle Valo 2021-02-08 17:48 ` Bjorn Andersson [this message] 2021-02-09 8:10 ` Kalle Valo 2021-05-20 11:47 ` Amit Pundir
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=YCF5ZC/WMRefTRcQ@builder.lan \ --to=bjorn.andersson@linaro.org \ --cc=amit.pundir@linaro.org \ --cc=ath10k@lists.infradead.org \ --cc=davem@davemloft.net \ --cc=devicetree@vger.kernel.org \ --cc=jeffrey.l.hugo@gmail.com \ --cc=john.stultz@linaro.org \ --cc=konradybcio@gmail.com \ --cc=kuba@kernel.org \ --cc=kvalo@codeaurora.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-wireless@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=robh@kernel.org \ --cc=sumit.semwal@linaro.org \ --subject='Re: [PATCH] ath10k: Introduce a devicetree quirk to skip host cap QMI requests' \ /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
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).