Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-12-08 Thread Kalle Valo
Hi, getting back to this old thread, here's the discussion: https://patchwork.kernel.org/patch/9615183/ https://patchwork.kernel.org/patch/9615185/ Sven Eckelmann writes: > On Dienstag, 21. März 2017 21:56:54 CET Rob Herring wrote: > [...] >> Is this always the

Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-22 Thread Sven Eckelmann
On Dienstag, 21. März 2017 21:56:54 CET Rob Herring wrote: [...] > Is this always the case? There's never some variation beyond the > reference design that a BDF difference can't handle? I have no knowledge about anything which isn't handled directly by the BDF variants. But maybe Kalle can

Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-21 Thread Rob Herring
On Tue, Mar 21, 2017 at 9:33 AM, Sven Eckelmann wrote: > On Dienstag, 21. März 2017 08:00:34 CET Rob Herring wrote: > [...] >> > It would then up with something like this as compatibility string: >> > >> > * qcom,ipq4019-wifi-asus-rt-ac58u >> > *

Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-21 Thread Sven Eckelmann
On Dienstag, 21. März 2017 08:00:34 CET Rob Herring wrote: [...] > > It would then up with something like this as compatibility string: > > > > * qcom,ipq4019-wifi-asus-rt-ac58u > > * qcom,ipq4019-wifi-fritzbox-4040 > > * qcom,ipq4019-wifi-netgear-whatever > > *

Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-21 Thread Rob Herring
On Mon, Mar 20, 2017 at 11:28 AM, Sven Eckelmann wrote: > On Montag, 20. März 2017 10:07:33 CET Rob Herring wrote: >> On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote: >> > The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct >> >

Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-21 Thread Sven Eckelmann
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 >

Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-20 Thread Adrian Chadd
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

Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-20 Thread Sven Eckelmann
On Montag, 20. März 2017 10:07:33 CET Rob Herring wrote: > On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote: > > The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct > > board data file on QCA4019 based devices. Multiple different boards share > > the same

Re: [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-20 Thread Rob Herring
On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote: > The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct > board data file on QCA4019 based devices. Multiple different boards share > the same values. Only the original reference designs can currently be >

[PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant

2017-03-10 Thread Sven Eckelmann
The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct board data file on QCA4019 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