this.
Signed-off-by: Bartosz Markowski bartosz.markow...@tieto.com
---
drivers/net/wireless/ath/ath10k/hw.h | 1 -
drivers/net/wireless/ath/ath10k/pci.c | 4 +++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/hw.h
b/drivers/net/wireless/ath/ath10k/hw.h
index
On 13 October 2014 14:06, voncken cedric.vonc...@acksys.fr wrote:
Have you a benchmark reference with ATH10K ? at this time we can send
around 700 Mbit/s, is it the maximum or we can expected better ?
If this is OTA then this is pretty good. If this is cabled RF w/ attentuator
it should be
On 23 October 2014 17:10, Kalle Valo kv...@qca.qualcomm.com wrote:
Bartosz Markowski bartosz.markow...@tieto.com writes:
Firmware was crashing when we were trying to warm reset it
after suspend. This was due to the fact that target registeres
can be accessed only if the hardware is awaken
From: Michal Kazior michal.kaz...@tieto.com
This event is delivered to host by firmware if it
supports beacon templates only.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/wmi-tlv.c | 50 +++
From: Michal Kazior michal.kaz...@tieto.com
New firmware revisions with beacon templates need
probe templates as well because they don't forward
probe requests to host at all.
This is required for new firmware to work with
direct probe requests (notably required by hidden
ssid AP).
From: Michal Kazior michal.kaz...@tieto.com
New firmware revisions support beacon and probe
response templates instead. This means SWBA events
are no longer delivered for these firmware
revisions.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/mac.c |
From: Michal Kazior michal.kaz...@tieto.com
New firmware revisions may support setting beacon
template. Implement wmi interface for it.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/wmi-ops.h | 23 +++
drivers/net/wireless/ath/ath10k/wmi-tlv.c
This has been missed while adding the QCA6174 support.
As in the last time, without advertising the firmware files
as needed (or optional) for ath10k, these won't be built into
ram disk for instance.
Signed-off-by: Bartosz Markowski bartosz.markow...@tieto.com
---
drivers/net/wireless/ath/ath10k
failed; err=-22 Invalid argument)
wlan0: WPA: Failed to configure IGTK to the driver
wlan0: RSN: Failed to configure IGTK
--
In order to fix this case (PMF: AES-CMAC/IGTK) force the AES_CMAC cipher to
be handled by software.
Signed-off-by: Bartosz Markowski bartosz.markow...@tieto.com
---
drivers/net
failed; err=-22 Invalid argument)
wlan0: WPA: Failed to configure IGTK to the driver
wlan0: RSN: Failed to configure IGTK
--
In order to fix this case (PMF: AES-CMAC/IGTK) force the AES_CMAC cipher to
be handled by software.
Signed-off-by: Bartosz Markowski bartosz.markow...@tieto.com
---
drivers/net
On 10 March 2015 at 14:29, Bartosz Markowski
bartosz.markow...@tieto.com wrote:
While testing with older supplicant, .drv_set_key() was failing due to
higher than ath10k firmware could handle key_index (WMI_MAX_KEY_INDEX == 3).
I've sent a v2 (I forgot the ammend the missing semicolon
On 10 March 2015 at 17:02, Ben Greear gree...@candelatech.com wrote:
On 03/10/2015 06:32 AM, Bartosz Markowski wrote:
While testing with older supplicant, .drv_set_key() was failing due to
higher than ath10k firmware could handle key_index (WMI_MAX_KEY_INDEX == 3
.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
Tested-by: Bartosz Markowski bartosz.markow...@tieto.com
---
drivers/net/wireless/ath/ath10k/mac.c | 45
+++
1 file changed, 24 insertions(+), 21 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/mac.c
after cold
reset: -70
[ 181.688902] ath10k_pci :02:00.0: failed to reset chip: -70
[ 181.689774] ath10k_pci: probe of :02:00.0 failed with error -70
Fix it by updating the address with correct value.
Signed-off-by: Bartosz Markowski bartosz.markow...@tieto.com
---
drivers/net/wireless/ath
)
from QCA61x4 design, so the integration was pretty straightforward.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/core.c | 16
drivers/net/wireless/ath/ath10k/hw.h| 12
drivers/net/wireless/ath/
On 28 October 2015 at 12:51, kbuild test robot <l...@intel.com> wrote:
> Hi Bartosz,
>
> [auto build test WARNING on next-20151022 -- if it's inappropriate base,
> please suggest rules for selecting the more suitable base]
>
> url:
> https://github.com/0day-ci/linu
* Clarifying the naming scheme for QCA9377 targets
* Adding the dev_id mathod (RFC) as a HW identification helper
* updating missing hw_params for 1.1 target
---
Notes:
v2:
* rebase
* fix the whitespace mess in patch 4/4 [Kalle]
Bartosz Markowski (4):
ath10k: fix the currently
When introducing the original QCA9377 support, the chip target
version was wrongly picked. The chip advertising itself with
bmi target value equal to 0x05020001 is in fact a 1.1 revision.
I realized this once I got a real 1.1 hw to play with.
Signed-off-by: Bartosz Markowski <bartosz.mar
On 4 November 2015 at 18:53, Kalle Valo <kv...@qca.qualcomm.com> wrote:
> Bartosz Markowski <bartosz.markow...@tieto.com> writes:
>
>> Add new BMI target version and chip id revision. Register it
>> on supported chips list.
>>
>> Signed-off-by: Bart
The uart_pin was incorrectly configured for QCA9377
and the recently added hw_params were omitted.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wi
Add new BMI target version and chip id revision. Register it
on supported chips list.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/core.c | 18 ++
drivers/net/wireless/ath/ath10k/hw.h | 3 +++
drivers/net/wirele
not overlap with the same chip_id_rev.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/core.c | 27 ++-
drivers/net/wireless/ath/ath10k/core.h | 1 +
drivers/net/wireless/ath/ath10k/hw.h | 6 ++
drivers/net/wirele
Add new BMI target version and chip id revision. Register it
on supported chips list.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/core.c | 18 ++
drivers/net/wireless/ath/ath10k/hw.h | 3 +++
drivers/net/wirele
The uart_pin was incorrectly configured for QCA9377
and the recently added hw_params were omitted.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wi
not overlap with the same chip_id_rev.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/core.c | 27 ++-
drivers/net/wireless/ath/ath10k/core.h | 1 +
drivers/net/wireless/ath/ath10k/hw.h | 6 ++
drivers/net/wirele
When introducing the original QCA9377 support, the chip target
version was wrongly picked. The chip advertising itself with
bmi target value equal to 0x05020001 is in fact a 1.1 revision.
I realized this once I got a real 1.1 hw to play with.
Signed-off-by: Bartosz Markowski <bartosz.mar
* Clarifying the naming scheme for QCA9377 targets
* Adding the dev_id mathod (RFC) as a HW identification helper
* updating missing hw_params for 1.1 target
Bartosz Markowski (4):
ath10k: fix the currently supported QCA9377 target version name
ath10k: update missing hw_params of QCA9377
On 27 August 2015 at 14:47, Michal Kazior michal.kaz...@tieto.com wrote:
From: Bartosz Markowski bartosz.markow...@tieto.com
All beamformee supporting chips have the ability to support
VHT NDP in up to 4 STSs. Change the published beamformee
STS cap accordingly to 3 as it should be Nsts-1
cap accordingly to 3 or to what
the firmware reports.
Assumption so far, it suppose to be the num_rf_chains-1, was
completely wrong.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/mac.c | 22 --
1 file changed, 20 inse
On 28 August 2015 at 14:56, Bartosz Markowski
<bartosz.markow...@tieto.com> wrote:
> On 27 August 2015 at 14:47, Michal Kazior <michal.kaz...@tieto.com> wrote:
>> From: Bartosz Markowski <bartosz.markow...@tieto.com>
>>
>> All beamformee supporting chips
Similarly to the VHT STS, this is supposed to be propagated by firmware.
In case it's not, use the default value, but as last resort.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/mac.c | 21 +++--
1 file changed, 19 inse
On 2 September 2015 at 15:55, Kalle Valo <kv...@qca.qualcomm.com> wrote:
> Bartosz Markowski <bartosz.markow...@tieto.com> writes:
>
>> On 28 August 2015 at 14:56, Bartosz Markowski
>> <bartosz.markow...@tieto.com> wrote:
>>> On 27 August 2015 at
On 1 December 2015 at 09:42, Michal Kazior wrote:
> On 1 December 2015 at 09:38, Bartlomiej Grzeskowiak
> wrote:
>> Hi,
>>
>> I have already tried with backports 4.2.6 and different combinations
>> of firmware.bin / board.bin. With
This overrides whatever regulatory the device
EEPROM contains and uses what the platform says
instead - in this implementation the ACPI driver.
In case the hint is not programmed or corrupted (0x)
the device falls back to the eeprom programmed settings.
Signed-off-by: Bartosz Markowski
From: Michal Kazior <michal.kaz...@tieto.com>
This will be helpful for drivers that can acquire
alpha2 regulatory codes.
Signed-off-by: Michal Kazior <michal.kaz...@tieto.com>
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/regd.c |
.
This has been developed and tested on Skylake (Chromebook) platform, where the
persistent area containing "region" value is called VPD.
Bartosz Markowski (1):
ath10k: add platform regulatory domain support
Michal Kazior (1):
ath: export alpha2 helper
drivers/net/wireless/ath/ath
On 12 September 2016 at 17:35, Valo, Kalle wrote:
[...]
> > +#ifdef CONFIG_ACPI
> > +#define WRD_METHOD "WRDD"
> > +#define WRDD_WIFI (0x07)
> > +
> > +static u32 ath10k_mac_wrdd_get_mcc(struct ath10k *ar, union acpi_object
> > *wrdd)
> > +{
>
> I don't think the ifdef
On 14 September 2016 at 09:06, Valo, Kalle <kv...@qca.qualcomm.com> wrote:
>
> Bartosz Markowski <bartosz.markow...@tieto.com> writes:
>
> > On 12 September 2016 at 17:35, Valo, Kalle <kv...@qca.qualcomm.com> wrote:
> >
> >> > +#ifdef CONFIG_ACP
QCA9377 firmware shall alloc 4 IRAM banks
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.c
b/drivers/net/wireless/ath/ath10k
0x0042BBBC 0x0001
[44]: 0x809FFA45 0x0040EA78 0x0043D3E4 0x0042C2C8
[48]: 0x809FCEF4 0x0040EA98 0x0043D3E4 0x0001
[52]: 0x80911210 0x0040EAE8 0x0010 0x004041D0
[56]: 0x80911154 0x0040EB28 0x0040 0x
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
d
The correct number for QCA9377 chip is 33 VDEVs.
This impacts also QCA6174 chip and it's max VDEV number.
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/hw.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drive
copy engine 5 for HTT messages")
Signed-off-by: Bartosz Markowski <bartosz.markow...@tieto.com>
---
drivers/net/wireless/ath/ath10k/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.c
b/drivers/net/wireless/ath/ath10k/pci.c
in
42 matches
Mail list logo