From: Rob Herring <robh@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt: bindings: add new dt entry for ath11k calibration variant
Date: Mon, 19 Oct 2020 16:18:50 -0500 [thread overview]
Message-ID: <20201019211850.GA3619287@bogus> (raw)
In-Reply-To: <20201015131501.1939685-1-sven@narfation.org>
On Thu, 15 Oct 2020 15:15:00 +0200, Sven Eckelmann wrote:
> The bus + qmi-chip-id + qmi-board-id is not enough to identify the correct
> board data file on IPQ6018 based devices. Multiple different boards share
> the same values. Only the original reference designs can currently be
> identified and loaded from the board-2.bin. But these will not result in
> the correct calibration data when combined with the pre-calibration data
> from the device.
>
> An additional "variant" information has to be provided to select the
> correct board data for a design which was modified by an ODM. This follows
> the same approach as ath10k.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
> .../devicetree/bindings/net/wireless/qcom,ath11k.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-10-19 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 13:15 [PATCH 1/2] dt: bindings: add new dt entry for ath11k calibration variant Sven Eckelmann
2020-10-15 13:15 ` [PATCH 2/2] ath11k: search DT for qcom,ath11k-calibration-variant Sven Eckelmann
2020-10-19 21:18 ` Rob Herring [this message]
2020-11-07 8:01 ` [PATCH 1/2] dt: bindings: add new dt entry for ath11k calibration variant 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=20201019211850.GA3619287@bogus \
--to=robh@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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 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).