From: Rob Herring <robh@kernel.org>
To: Abhishek Kumar <kuabhs@chromium.org>
Cc: devicetree@vger.kernel.org, netdev@vger.kernel.org,
pillair@codeaurora.org, Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
dianders@chromium.org, kvalo@codeaurora.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt: bindings: add dt entry for ath10k default BDF name
Date: Tue, 11 Jan 2022 20:21:03 -0600 [thread overview]
Message-ID: <Yd47D9GjbAFaWXEo@robh.at.kernel.org> (raw)
In-Reply-To: <20220110231255.v2.2.Ia0365467994f8f9085c86b5674b57ff507c669f8@changeid>
On Mon, 10 Jan 2022 23:14:15 +0000, Abhishek Kumar wrote:
> 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>
> ---
>
> Changes in v2:
> - Changes in v2: none
>
> .../devicetree/bindings/net/wireless/qcom,ath10k.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Abhishek Kumar <kuabhs@chromium.org>
Cc: devicetree@vger.kernel.org, netdev@vger.kernel.org,
pillair@codeaurora.org, Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
dianders@chromium.org, kvalo@codeaurora.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt: bindings: add dt entry for ath10k default BDF name
Date: Tue, 11 Jan 2022 20:21:03 -0600 [thread overview]
Message-ID: <Yd47D9GjbAFaWXEo@robh.at.kernel.org> (raw)
In-Reply-To: <20220110231255.v2.2.Ia0365467994f8f9085c86b5674b57ff507c669f8@changeid>
On Mon, 10 Jan 2022 23:14:15 +0000, Abhishek Kumar wrote:
> 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>
> ---
>
> Changes in v2:
> - Changes in v2: none
>
> .../devicetree/bindings/net/wireless/qcom,ath10k.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-01-12 2:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 23:14 [PATCH v2 1/2] ath10k: search for default BDF name provided in DT Abhishek Kumar
2022-01-10 23:14 ` Abhishek Kumar
2022-01-10 23:14 ` [PATCH v2 2/2] dt: bindings: add dt entry for ath10k default BDF name Abhishek Kumar
2022-01-10 23:14 ` Abhishek Kumar
2022-01-12 2:21 ` Rob Herring [this message]
2022-01-12 2:21 ` Rob Herring
2022-01-11 0:51 ` [PATCH v2 1/2] ath10k: search for default BDF name provided in DT Doug Anderson
2022-01-11 0:51 ` Doug Anderson
2022-01-14 6:50 ` Abhishek Kumar
2022-01-14 6:50 ` Abhishek Kumar
2022-01-11 1:07 ` kernel test robot
2022-01-11 1:07 ` kernel test robot
2022-01-11 1:07 ` kernel test robot
2022-01-14 6:47 ` Abhishek Kumar
2022-01-14 6:47 ` Abhishek Kumar
2022-01-14 6:47 ` Abhishek Kumar
2022-01-14 14:46 ` Kalle Valo
2022-01-14 14:46 ` Kalle Valo
2022-01-14 14:46 ` Kalle Valo
2022-03-08 0:50 ` Doug Anderson
2022-03-08 0:50 ` Doug Anderson
2022-03-08 0:50 ` Doug Anderson
2022-03-10 10:07 ` Kalle Valo
2022-03-10 10:07 ` Kalle Valo
2022-03-10 10:07 ` 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=Yd47D9GjbAFaWXEo@robh.at.kernel.org \
--to=robh@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=kvalo@codeaurora.org \
--cc=kvalo@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 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.