linux-kernel - Re: [PATCH net-next 0/2] net: ipa: fix HOLB timer register use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 03 Jul 2020 14:37:48 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     elder@...aro.org
Cc:     kuba@...nel.org, evgreen@...omium.org, subashab@...eaurora.org,
        cpratapa@...eaurora.org, bjorn.andersson@...aro.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] net: ipa: fix HOLB timer register use

From: Alex Elder <elder@...aro.org>
Date: Fri,  3 Jul 2020 16:23:33 -0500

> 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.

Series applied, thank you.