From: Kalle Valo <kvalo@kernel.org>
To: Abhishek Kumar <kuabhs@chromium.org>
Cc: dianders@chromium.org, pillair@codeaurora.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, netdev@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Re: [PATCH 2/2] dt: bindings: add dt entry for ath10k default BDF name
Date: Mon, 10 Jan 2022 12:18:08 +0200 [thread overview]
Message-ID: <87pmozvqqn.fsf@kernel.org> (raw)
In-Reply-To: <20220107200417.2.Ia0365467994f8f9085c86b5674b57ff507c669f8@changeid> (Abhishek Kumar's message of "Fri, 7 Jan 2022 20:04:31 +0000")
Abhishek Kumar <kuabhs@chromium.org> writes:
> It is possible that BDF name with board-id+chip-id+variant
> combination is not found in the board-2.bin. Such cases can
> cause wlan probe to fail and completely break wifi. In such
> case there can be an optional property to define a default
> BDF name to search for in the board-2.bin file when none of
> the combinations (board-id,chip-id,variant) match.
> To address the above concern provide an optional proptery:
> qcom,ath10k-default-bdf
>
> Signed-off-by: Abhishek Kumar <kuabhs@chromium.org>
> ---
>
> .../devicetree/bindings/net/wireless/qcom,ath10k.txt | 4 ++++
> 1 file changed, 4 insertions(+)
Please CC ath10k list on all ath10k related patches.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-01-10 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 20:04 [PATCH 1/2] ath10k: search for default BDF name provided in DT Abhishek Kumar
2022-01-07 20:04 ` [PATCH 2/2] dt: bindings: add dt entry for ath10k default BDF name Abhishek Kumar
2022-01-10 10:18 ` Kalle Valo [this message]
2022-01-07 21:22 ` [PATCH 1/2] ath10k: search for default BDF name provided in DT Doug Anderson
2022-03-10 10:05 ` Kalle Valo
2022-03-11 0:27 ` Doug Anderson
2022-04-11 23:25 ` Abhishek Kumar
2022-04-12 10:46 ` Kalle Valo
2022-04-20 0:43 ` Abhishek Kumar
2022-01-08 3:14 ` kernel test robot
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=87pmozvqqn.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kuabhs@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pillair@codeaurora.org \
--cc=robh+dt@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).