From: Kalle Valo <kvalo@codeaurora.org>
To: Thomas Hebb <tommyhebb@gmail.com>
Cc: ath10k@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath10k: search all IEs for variant before falling back
Date: Thu, 01 Mar 2018 12:11:24 +0200 [thread overview]
Message-ID: <87y3jcp0kz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <d121031bd5eacf212f7ddf49c0440218714f1ae6.1519231419.git.tommyhebb@gmail.com> (Thomas Hebb's message of "Wed, 21 Feb 2018 11:43:39 -0500")
Thomas Hebb <tommyhebb@gmail.com> writes:
> commit f2593cb1b291 ("ath10k: Search SMBIOS for OEM board file
> extension") added a feature to ath10k that allows Board Data File
> (BDF) conflicts between multiple devices that use the same device IDs
> but have different calibration requirements to be resolved by allowing
> a "variant" string to be stored in SMBIOS [and later device tree, added
> by commit d06f26c5c8a4 ("ath10k: search DT for qcom,ath10k-calibration-
> variant")] that gets appended to the ID stored in board-2.bin.
>
> This original patch had a regression, however. Namely that devices with
> a variant present in SMBIOS that didn't need custom BDFs could no longer
> find the default BDF, which has no variant appended. The patch was
> reverted and re-applied with a fix for this issue in commit 1657b8f84ed9
> ("search SMBIOS for OEM board file extension").
>
> But the fix to fall back to a default BDF introduced another issue: the
> driver currently parses IEs in board-2.bin one by one, and for each one
> it first checks to see if it matches the ID with the variant appended.
> If it doesn't, it checks to see if it matches the "fallback" ID with no
> variant. If a matching BDF is found at any point during this search, the
> search is terminated and that BDF is used. The issue is that it's very
> possible (and is currently the case for board-2.bin files present in the
> ath10k-firmware repository) for the default BDF to occur in an earlier
> IE than the variant-specific BDF. In this case, the current code will
> happily choose the default BDF even though a better-matching BDF is
> present later in the file.
>
> This patch fixes the issue by first searching the entire file for the ID
> with variant, and searching for the fallback ID only if that search
> fails. It also includes some code cleanup in the area, as
> ath10k_core_fetch_board_data_api_n() no longer does its own string
> mangling to remove the variant from an ID, instead leaving that job to a
> new flag passed to ath10k_core_create_board_name().
>
> I've tested this patch on a QCA4019 and verified that the driver behaves
> correctly for 1) both fallback and variant BDFs present, 2) only fallback
> BDF present, and 3) no matching BDFs present.
>
> Fixes: 1657b8f84ed9 ("ath10k: search SMBIOS for OEM board file extension")
> Signed-off-by: Thomas Hebb <tommyhebb@gmail.com>
BTW, you forgot to CC linux-wireless so I don't see this in patchwork.
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/submittingpatches
--
Kalle Valo
next prev parent reply other threads:[~2018-03-01 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 16:43 Thomas Hebb
2018-03-01 10:11 ` Kalle Valo [this message]
2018-03-01 10:13 ` Kalle Valo
2018-04-13 14:41 ` 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=87y3jcp0kz.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tommyhebb@gmail.com \
/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
all inboxes | Powered by JetHome®