From: Alex Elder <elder@linaro.org>
To: davem@davemloft.net, kuba@kernel.org
Cc: evgreen@chromium.org, subashab@codeaurora.org,
cpratapa@codeaurora.org, bjorn.andersson@linaro.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] net: ipa: fix HOLB timer register use
Date: Fri, 3 Jul 2020 16:23:33 -0500 [thread overview]
Message-ID: <20200703212335.465355-1-elder@linaro.org> (raw)
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.
-Alex
Alex Elder (2):
net: ipa: introduce ipa_clock_rate()
net: ipa: fix HOLB timer calculation
drivers/net/ipa/ipa_clock.c | 6 +++
drivers/net/ipa/ipa_clock.h | 8 ++++
drivers/net/ipa/ipa_endpoint.c | 78 +++++++++++++++++++---------------
3 files changed, 57 insertions(+), 35 deletions(-)
--
2.25.1
next reply other threads:[~2020-07-03 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 21:23 Alex Elder [this message]
2020-07-03 21:23 ` [PATCH net-next 1/2] net: ipa: introduce ipa_clock_rate() Alex Elder
2020-07-03 21:23 ` [PATCH net-next 2/2] net: ipa: fix HOLB timer calculation Alex Elder
2020-07-03 21:37 ` [PATCH net-next 0/2] net: ipa: fix HOLB timer register use David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200703212335.465355-1-elder@linaro.org \
--to=elder@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®