mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: "Rob Herring (Arm)" <robh@kernel.org>,
	Ernest Van Hoecke <ernestvanhoecke@gmail.com>
Cc: linux-kernel@vger.kernel.org, ath12k@lists.infradead.org,
	Conor Dooley <conor+dt@kernel.org>,
	linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	Andrew LaMarche <andrewjlamarche@gmail.com>,
	devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Jeff Johnson <jjohnson@kernel.org>,
	Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
Subject: Re: [PATCH v2] dt-bindings: wireless: ath12k: allow calibration variant for WCN7850
Date: Fri, 30 Oct 2026 14:09:23 -0700	[thread overview]
Message-ID: <44bc6f1b-6f04-46ee-8578-caff30ab25e8@oss.qualcomm.com> (raw)
In-Reply-To: <179337193753.3936464.10436179036151297295.robh@kernel.org>

On 10/30/2026 7:53 AM, Rob Herring (Arm) wrote:
> 
> On Mon, 07 Sep 2026 16:17:20 +0200, Ernest Van Hoecke wrote:
>> From: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
>>
>> qcom,calibration-variant is the generic Qualcomm Wi-Fi DT property for
>> selecting board-specific calibration data when the device identity alone
>> is ambiguous.
>>
>> Commit 06cca100ad08 ("wifi: ath12k: support calibration-variant from
>> device tree") implemented support for this property in the ath12k
>> driver.
>>
>> WCN7850 can be used in systems where the PCI device ID and machine
>> compatible are identical across product variants, or across regions with
>> different regulations. For regulatory changes, the hardware description
>> does not change, but the vendor-provided calibration data can differ. In
>> that case neither the PCI identity nor the machine compatible can
>> identify the required data, so DT needs an explicit calibration variant.
>>
>> The ath10k, ath11k and ath12k WSI bindings already allow this generic
>> property for the same class of board-data selection. Allow it for
>> WCN7850 PCIe devices as well.
>>
>> Signed-off-by: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
>> ---
>> Changes in v2:
>> - Rebased
>> - Updated commit message
>> - Link to v1: https://lore.kernel.org/r/20260701-ath12k-calibration-variant-v1-1-d3eddaabf026@toradex.com
>> ---
>>  Documentation/devicetree/bindings/net/wireless/qcom,ath12k.yaml | 6 ++++++
>>  1 file changed, 6 insertions(+)
>>
> 
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> 
> Sorry, not sure why this wasn't showing up for me. You may want to 
> resend it in case it is not in wireless queue.
> 
> Rob

It's in my queue, will pick it up now.

/jeff

  reply	other threads:[~2026-10-30 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 14:17 Ernest Van Hoecke
2026-10-26 10:51 ` Ernest Van Hoecke
2026-10-30 14:53 ` Rob Herring (Arm)
2026-10-30 21:09   ` Jeff Johnson [this message]
2026-10-30 22:41 ` Jeff Johnson

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=44bc6f1b-6f04-46ee-8578-caff30ab25e8@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=andrewjlamarche@gmail.com \
    --cc=ath12k@lists.infradead.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ernest.vanhoecke@toradex.com \
    --cc=ernestvanhoecke@gmail.com \
    --cc=jjohnson@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=robh@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

all inboxes | Powered by JetHome®