linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Rob Herring <robh@kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Waldemar Rymarkiewicz <ext.waldemar.rymarkiewicz@tieto.com>,
	Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant
Date: Tue, 21 Mar 2017 08:29:59 +0100	[thread overview]
Message-ID: <6837301.TG6zjU3t3l@bentobox> (raw)
In-Reply-To: <CAJ-Vmok=6Tcvr4NE9+KMSQ4OSd80e1DSkgbOqFcWnFT3A1ikgw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 648 bytes --]

On Montag, 20. März 2017 09:42:05 CET Adrian Chadd wrote:
> Vendors using ath10k will like this. I mean, I'm using ath10k, and I
> really like this moving forward. This will make life so much easier in
> the long run.
> 
> Everyone else isn't using board-2.bin; they're just copying
> calibration/board data files over so the reference driver can assemble
> a board data file based on wifi0/wifi1/etc probe order, and use that.

Thanks for the feedback. But I am not sure what you mean by "this". Do you 
mean the "qcom,ath10k-calibration-variant" entry or the "qcom,ipq4019-
$vendorstring" compatiblity string?

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-03-21  7:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  8:06 [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant Sven Eckelmann
2017-03-10  8:06 ` [PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant Sven Eckelmann
2017-03-10 18:20   ` Christian Lamparter
2017-03-15  8:04     ` Sven Eckelmann
2017-08-21  7:11     ` Sven Eckelmann
2017-10-27  9:34       ` [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant Kalle Valo
2017-12-08  9:50     ` Kalle Valo
2018-01-29 20:09       ` Asus RT-AC58U boardfile (was Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant) Christian Lamparter
2018-10-08  8:21         ` Kalle Valo
2018-04-19 14:56     ` [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant Kalle Valo
2018-04-20 19:50       ` Christian Lamparter
2017-12-08  9:27   ` [PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant Kalle Valo
2017-03-20 15:07 ` [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant Rob Herring
2017-03-20 16:28   ` Sven Eckelmann
2017-03-20 16:42     ` Adrian Chadd
2017-03-21  7:29       ` Sven Eckelmann [this message]
2017-03-21 13:00     ` Rob Herring
2017-03-21 14:33       ` Sven Eckelmann
2017-03-22  2:56         ` Rob Herring
2017-03-22  7:20           ` Sven Eckelmann
2017-12-08  9:22             ` 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=6837301.TG6zjU3t3l@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ext.waldemar.rymarkiewicz@tieto.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).