diff options
author | David S. Miller <davem@davemloft.net> | 2020-07-03 14:37:33 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2020-07-03 14:37:33 -0700 |
commit | a2116491c8bc47810c74768739e8146401cf8359 (patch) | |
tree | c286faac4ddf9238379a865e60c312bdf8e03284 /kernel/bpf/stackmap.c | |
parent | cd8700e45e73c5e5c32260ebc3092e50c1853e5d (diff) | |
parent | f13a8c3189d7e31b6cb70333ee61365d66974399 (diff) | |
download | linux-a2116491c8bc47810c74768739e8146401cf8359.tar.gz linux-a2116491c8bc47810c74768739e8146401cf8359.tar.bz2 linux-a2116491c8bc47810c74768739e8146401cf8359.zip |
Merge branch 'net-ipa-fix-HOLB-timer-register-use'
Alex Elder says:
====================
net: ipa: fix HOLB timer register use
The function ipa_reg_init_hol_block_timer_val() generates the value
to write into the HOL_BLOCK_TIMER endpoint configuration register,
to represent a given timeout value (in microseconds). It only
supports a timer value of 0 though, in part because that's
sufficient, but mainly because there was some confusion about
how the register is formatted in newer hardware.
I got clarification about the register format, so this series fixes
ipa_reg_init_hol_block_timer_val() to work for any supported delay
value.
The delay is based on the IPA core clock, so determining the value
to write for a given period requires access to the current core
clock rate. So the first patch just creates a new function to
provide that.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel/bpf/stackmap.c')
0 files changed, 0 insertions, 0 deletions