Does the reg_addr/reg_value reading work?

Sebastian Gottschall s.gottschall at
Mon Jun 8 09:46:28 PDT 2015

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

More information about the ath10k mailing list