From: Simon Horman <simon.horman@corigine•com>
To: Andrew Halaney <ahalaney@redhat•com>
Cc: linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-stm32@st-md-mailman•stormreply.com, netdev@vger•kernel.org,
mcoquelin.stm32@gmail•com, pabeni@redhat•com, kuba@kernel•org,
edumazet@google•com, davem@davemloft•net, joabreu@synopsys•com,
alexandre.torgue@foss•st.com, peppe.cavallaro@st•com,
bhupesh.sharma@linaro•org, vkoul@kernel•org,
linux-arm-msm@vger•kernel.org, jsuraj@qti•qualcomm.com
Subject: Re: [PATCH RFC/RFT net-next 3/3] net: stmmac: Use the max frequency possible for clk_ptp_ref
Date: Thu, 13 Jul 2023 10:58:18 +0100 [thread overview]
Message-ID: <ZK/Kusx3BeCznDoY@corigine.com> (raw)
In-Reply-To: <20230711205732.364954-4-ahalaney@redhat.com>
On Tue, Jul 11, 2023 at 03:35:32PM -0500, Andrew Halaney wrote:
> Using the max frequency allows for the best PTP timestamping resolution,
> so let's default to that.
>
> Signed-off-by: Andrew Halaney <ahalaney@redhat•com>
Reviewed-by: Simon Horman <simon.horman@corigine•com>
prev parent reply other threads:[~2023-07-13 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 20:35 [PATCH RFC/RFT net-next 0/3] net: stmmac: Increase clk_ptp_ref rate Andrew Halaney
2023-07-11 20:35 ` [PATCH RFC/RFT net-next 1/3] net: stmmac: Make ptp_clk_freq_config variable type explicit Andrew Halaney
2023-07-13 9:56 ` Simon Horman
2023-07-11 20:35 ` [PATCH RFC/RFT net-next 2/3] net: stmmac: dwmac-qcom-ethqos: Use max frequency for clk_ptp_ref Andrew Halaney
2023-07-13 9:57 ` Simon Horman
2023-07-11 20:35 ` [PATCH RFC/RFT net-next 3/3] net: stmmac: Use the max frequency possible " Andrew Halaney
2023-07-13 9:58 ` Simon Horman [this message]
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=ZK/Kusx3BeCznDoY@corigine.com \
--to=simon.horman@corigine$(echo .)com \
--cc=ahalaney@redhat$(echo .)com \
--cc=alexandre.torgue@foss$(echo .)st.com \
--cc=bhupesh.sharma@linaro$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=joabreu@synopsys$(echo .)com \
--cc=jsuraj@qti$(echo .)qualcomm.com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=peppe.cavallaro@st$(echo .)com \
--cc=vkoul@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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