* Does the reg_addr/reg_value reading work?
@ 2015-06-08 16:11 Ben Greear
2015-06-08 16:46 ` Sebastian Gottschall
0 siblings, 1 reply; 7+ messages in thread
From: Ben Greear @ 2015-06-08 16:11 UTC (permalink / raw)
To: ath10k
I am not getting expected values when I try to read registers
through the ath10k reg_addr/reg_value API.
For instance, I tried reading a particular register 0x80e0
(as defined in the firmware), and I get a zero value. With a different
API that I wrote to dump some specific registers over the WMI API,
I get the expected value.
# echo 0x80e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
# cat /debug/ieee80211/wiphy0/ath10k/reg_value
0x000080e0:0x00000000
# cat /debug/ieee80211/wiphy0/ath10k/fw_regs
ath10k Target Register Dump
=================
MAC-FILTER-ADDR-L32 0xd7ffffff
...
Is there some trick I am missing?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Does the reg_addr/reg_value reading work?
2015-06-08 16:11 Does the reg_addr/reg_value reading work? Ben Greear
@ 2015-06-08 16:46 ` Sebastian Gottschall
2015-06-08 19:45 ` Ben Greear
0 siblings, 1 reply; 7+ messages in thread
From: Sebastian Gottschall @ 2015-06-08 16:46 UTC (permalink / raw)
To: ath10k
Am 08.06.2015 um 18:11 schrieb Ben Greear:
> I am not getting expected values when I try to read registers
> through the ath10k reg_addr/reg_value API.
>
> For instance, I tried reading a particular register 0x80e0
> (as defined in the firmware), and I get a zero value. With a different
> API that I wrote to dump some specific registers over the WMI API,
> I get the expected value.
>
> # echo 0x80e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
> # cat /debug/ieee80211/wiphy0/ath10k/reg_value
> 0x000080e0:0x00000000
> # cat /debug/ieee80211/wiphy0/ath10k/fw_regs
>
> ath10k Target Register Dump
> =================
>
> MAC-FILTER-ADDR-L32 0xd7ffffff
> ...
>
> Is there some trick I am missing?
0x20000 offset makes the voodoo. you will find this offset within your
firmware source too. take a look at the preconfigured register tables.
these contain already the ack,slot etc. settings.
but with a special macro surrounding it which defines that offset
echo 0x2080e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>
> Thanks,
> Ben
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Does the reg_addr/reg_value reading work?
2015-06-08 16:46 ` Sebastian Gottschall
@ 2015-06-08 19:45 ` Ben Greear
2015-06-08 20:02 ` Ben Greear
0 siblings, 1 reply; 7+ messages in thread
From: Ben Greear @ 2015-06-08 19:45 UTC (permalink / raw)
To: Sebastian Gottschall; +Cc: ath10k
On 06/08/2015 09:46 AM, Sebastian Gottschall wrote:
> Am 08.06.2015 um 18:11 schrieb Ben Greear:
>> I am not getting expected values when I try to read registers
>> through the ath10k reg_addr/reg_value API.
>>
>> For instance, I tried reading a particular register 0x80e0
>> (as defined in the firmware), and I get a zero value. With a different
>> API that I wrote to dump some specific registers over the WMI API,
>> I get the expected value.
>>
>> # echo 0x80e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>> # cat /debug/ieee80211/wiphy0/ath10k/reg_value
>> 0x000080e0:0x00000000
>> # cat /debug/ieee80211/wiphy0/ath10k/fw_regs
>>
>> ath10k Target Register Dump
>> =================
>>
>> MAC-FILTER-ADDR-L32 0xd7ffffff
>> ...
>>
>> Is there some trick I am missing?
> 0x20000 offset makes the voodoo. you will find this offset within your firmware source too. take a look at the preconfigured register tables. these contain
> already the ack,slot etc. settings.
> but with a special macro surrounding it which defines that offset
>
> echo 0x2080e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
This crashes my kernel....I instrumented the place that crashed in ath10k/pci.h:
[ 100.676013] ath10k-pci-read32: ar ffff88020279ae20 ar_pci ffff88020279df08 offset: 0x2080e0
[ 100.676016] ar_pci->mem: 0xffffc90019c80000
[ 100.676031] BUG: unable to handle kernel paging request at ffffc90019e880e0
[ 100.681752] IP: [<ffffffff81364ad4>] ioread32+0x9/0x2f
Have you tried this on a 10.1.467 firmware?
And, what kernel? I'm trying 4.0.4+
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Does the reg_addr/reg_value reading work?
2015-06-08 19:45 ` Ben Greear
@ 2015-06-08 20:02 ` Ben Greear
2015-06-08 21:23 ` Sebastian Gottschall
0 siblings, 1 reply; 7+ messages in thread
From: Ben Greear @ 2015-06-08 20:02 UTC (permalink / raw)
To: Sebastian Gottschall; +Cc: ath10k
On 06/08/2015 12:45 PM, Ben Greear wrote:
> On 06/08/2015 09:46 AM, Sebastian Gottschall wrote:
>> Am 08.06.2015 um 18:11 schrieb Ben Greear:
>>> I am not getting expected values when I try to read registers
>>> through the ath10k reg_addr/reg_value API.
>>>
>>> For instance, I tried reading a particular register 0x80e0
>>> (as defined in the firmware), and I get a zero value. With a different
>>> API that I wrote to dump some specific registers over the WMI API,
>>> I get the expected value.
>>>
>>> # echo 0x80e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>>> # cat /debug/ieee80211/wiphy0/ath10k/reg_value
>>> 0x000080e0:0x00000000
>>> # cat /debug/ieee80211/wiphy0/ath10k/fw_regs
>>>
>>> ath10k Target Register Dump
>>> =================
>>>
>>> MAC-FILTER-ADDR-L32 0xd7ffffff
>>> ...
>>>
>>> Is there some trick I am missing?
>> 0x20000 offset makes the voodoo. you will find this offset within your firmware source too. take a look at the preconfigured register tables. these contain
>> already the ack,slot etc. settings.
>> but with a special macro surrounding it which defines that offset
>>
>> echo 0x2080e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>
> This crashes my kernel....I instrumented the place that crashed in ath10k/pci.h:
>
> [ 100.676013] ath10k-pci-read32: ar ffff88020279ae20 ar_pci ffff88020279df08 offset: 0x2080e0
> [ 100.676016] ar_pci->mem: 0xffffc90019c80000
> [ 100.676031] BUG: unable to handle kernel paging request at ffffc90019e880e0
> [ 100.681752] IP: [<ffffffff81364ad4>] ioread32+0x9/0x2f
>
> Have you tried this on a 10.1.467 firmware?
>
> And, what kernel? I'm trying 4.0.4+
I was using the wrong address value..it should be 0x280e0. Maybe the driver should still keep us from
crashing the whole kernel (while holding locks!), but at least it works when I put in
the right value.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Does the reg_addr/reg_value reading work?
2015-06-08 20:02 ` Ben Greear
@ 2015-06-08 21:23 ` Sebastian Gottschall
2015-06-08 21:28 ` Ben Greear
0 siblings, 1 reply; 7+ messages in thread
From: Sebastian Gottschall @ 2015-06-08 21:23 UTC (permalink / raw)
To: Ben Greear; +Cc: ath10k
Am 08.06.2015 um 22:02 schrieb Ben Greear:
> On 06/08/2015 12:45 PM, Ben Greear wrote:
>> On 06/08/2015 09:46 AM, Sebastian Gottschall wrote:
>>> Am 08.06.2015 um 18:11 schrieb Ben Greear:
>>>> I am not getting expected values when I try to read registers
>>>> through the ath10k reg_addr/reg_value API.
>>>>
>>>> For instance, I tried reading a particular register 0x80e0
>>>> (as defined in the firmware), and I get a zero value. With a different
>>>> API that I wrote to dump some specific registers over the WMI API,
>>>> I get the expected value.
>>>>
>>>> # echo 0x80e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>>>> # cat /debug/ieee80211/wiphy0/ath10k/reg_value
>>>> 0x000080e0:0x00000000
>>>> # cat /debug/ieee80211/wiphy0/ath10k/fw_regs
>>>>
>>>> ath10k Target Register Dump
>>>> =================
>>>>
>>>> MAC-FILTER-ADDR-L32 0xd7ffffff
>>>> ...
>>>>
>>>> Is there some trick I am missing?
>>> 0x20000 offset makes the voodoo. you will find this offset within your firmware source too. take a look at the preconfigured register tables. these contain
>>> already the ack,slot etc. settings.
>>> but with a special macro surrounding it which defines that offset
>>>
>>> echo 0x2080e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>> This crashes my kernel....I instrumented the place that crashed in ath10k/pci.h:
>>
>> [ 100.676013] ath10k-pci-read32: ar ffff88020279ae20 ar_pci ffff88020279df08 offset: 0x2080e0
>> [ 100.676016] ar_pci->mem: 0xffffc90019c80000
>> [ 100.676031] BUG: unable to handle kernel paging request at ffffc90019e880e0
>> [ 100.681752] IP: [<ffffffff81364ad4>] ioread32+0x9/0x2f
>>
>> Have you tried this on a 10.1.467 firmware?
>>
>> And, what kernel? I'm trying 4.0.4+
> I was using the wrong address value..it should be 0x280e0. Maybe the driver should still keep us from
> crashing the whole kernel (while holding locks!), but at least it works when I put in
> the right value.
now that you say it. i see it too. but playing direct register writes
can always lead to problematic scenarios. its a debug register. from my
oppinion, a debug register should allow
whatever is possible. even crashing something. its like using /dev/kmem
>
> Thanks,
> Ben
>
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Does the reg_addr/reg_value reading work?
2015-06-08 21:23 ` Sebastian Gottschall
@ 2015-06-08 21:28 ` Ben Greear
2015-06-11 7:45 ` Michal Kazior
0 siblings, 1 reply; 7+ messages in thread
From: Ben Greear @ 2015-06-08 21:28 UTC (permalink / raw)
To: Sebastian Gottschall; +Cc: ath10k
On 06/08/2015 02:23 PM, Sebastian Gottschall wrote:
> Am 08.06.2015 um 22:02 schrieb Ben Greear:
>> On 06/08/2015 12:45 PM, Ben Greear wrote:
>>> On 06/08/2015 09:46 AM, Sebastian Gottschall wrote:
>>>> Am 08.06.2015 um 18:11 schrieb Ben Greear:
>>>>> I am not getting expected values when I try to read registers
>>>>> through the ath10k reg_addr/reg_value API.
>>>>>
>>>>> For instance, I tried reading a particular register 0x80e0
>>>>> (as defined in the firmware), and I get a zero value. With a different
>>>>> API that I wrote to dump some specific registers over the WMI API,
>>>>> I get the expected value.
>>>>>
>>>>> # echo 0x80e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>>>>> # cat /debug/ieee80211/wiphy0/ath10k/reg_value
>>>>> 0x000080e0:0x00000000
>>>>> # cat /debug/ieee80211/wiphy0/ath10k/fw_regs
>>>>>
>>>>> ath10k Target Register Dump
>>>>> =================
>>>>>
>>>>> MAC-FILTER-ADDR-L32 0xd7ffffff
>>>>> ...
>>>>>
>>>>> Is there some trick I am missing?
>>>> 0x20000 offset makes the voodoo. you will find this offset within your firmware source too. take a look at the preconfigured register tables. these contain
>>>> already the ack,slot etc. settings.
>>>> but with a special macro surrounding it which defines that offset
>>>>
>>>> echo 0x2080e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>>> This crashes my kernel....I instrumented the place that crashed in ath10k/pci.h:
>>>
>>> [ 100.676013] ath10k-pci-read32: ar ffff88020279ae20 ar_pci ffff88020279df08 offset: 0x2080e0
>>> [ 100.676016] ar_pci->mem: 0xffffc90019c80000
>>> [ 100.676031] BUG: unable to handle kernel paging request at ffffc90019e880e0
>>> [ 100.681752] IP: [<ffffffff81364ad4>] ioread32+0x9/0x2f
>>>
>>> Have you tried this on a 10.1.467 firmware?
>>>
>>> And, what kernel? I'm trying 4.0.4+
>> I was using the wrong address value..it should be 0x280e0. Maybe the driver should still keep us from
>> crashing the whole kernel (while holding locks!), but at least it works when I put in
>> the right value.
> now that you say it. i see it too. but playing direct register writes can always lead to problematic scenarios. its a debug register. from my oppinion, a debug
> register should allow
> whatever is possible. even crashing something. its like using /dev/kmem
I am guessing the driver knows the pci address space that is available..it could probably
just limit any access outside those bounds since they can never work anyway.
Anyway, I'll let someone else deal with it if they want.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Does the reg_addr/reg_value reading work?
2015-06-08 21:28 ` Ben Greear
@ 2015-06-11 7:45 ` Michal Kazior
0 siblings, 0 replies; 7+ messages in thread
From: Michal Kazior @ 2015-06-11 7:45 UTC (permalink / raw)
To: Ben Greear; +Cc: ath10k@lists.infradead.org, Sebastian Gottschall
On 8 June 2015 at 23:28, Ben Greear <greearb@candelatech.com> wrote:
> On 06/08/2015 02:23 PM, Sebastian Gottschall wrote:
>> Am 08.06.2015 um 22:02 schrieb Ben Greear:
>>> On 06/08/2015 12:45 PM, Ben Greear wrote:
>>>> On 06/08/2015 09:46 AM, Sebastian Gottschall wrote:
[...]
>>>>> echo 0x2080e0 > /debug/ieee80211/wiphy0/ath10k/reg_addr
>>>> This crashes my kernel....I instrumented the place that crashed in ath10k/pci.h:
>>>>
>>>> [ 100.676013] ath10k-pci-read32: ar ffff88020279ae20 ar_pci ffff88020279df08 offset: 0x2080e0
>>>> [ 100.676016] ar_pci->mem: 0xffffc90019c80000
>>>> [ 100.676031] BUG: unable to handle kernel paging request at ffffc90019e880e0
>>>> [ 100.681752] IP: [<ffffffff81364ad4>] ioread32+0x9/0x2f
>>>>
>>>> Have you tried this on a 10.1.467 firmware?
>>>>
>>>> And, what kernel? I'm trying 4.0.4+
>>> I was using the wrong address value..it should be 0x280e0. Maybe the driver should still keep us from
>>> crashing the whole kernel (while holding locks!), but at least it works when I put in
>>> the right value.
>> now that you say it. i see it too. but playing direct register writes can always lead to problematic scenarios. its a debug register. from my oppinion, a debug
>> register should allow
>> whatever is possible. even crashing something. its like using /dev/kmem
>
> I am guessing the driver knows the pci address space that is available..it could probably
> just limit any access outside those bounds since they can never work anyway.
>
> Anyway, I'll let someone else deal with it if they want.
Yep. I've just sent a patch for review which introduces a sanity check
to prevent out of bounds MMIO access.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2015-06-11 7:45 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-08 16:11 Does the reg_addr/reg_value reading work? Ben Greear
2015-06-08 16:46 ` Sebastian Gottschall
2015-06-08 19:45 ` Ben Greear
2015-06-08 20:02 ` Ben Greear
2015-06-08 21:23 ` Sebastian Gottschall
2015-06-08 21:28 ` Ben Greear
2015-06-11 7:45 ` Michal Kazior
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.