From: Andrew Lunn <andrew@lunn.ch>
To: Shenghao Yang <me@shenghaoyang.info>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com, olteanv@gmail.com,
pavana.sharma@digi.com, ashkan.boldaji@digi.com,
kabel@kernel.org, edumazet@google.com, pabeni@redhat.com,
richardcochran@gmail.com, kuba@kernel.org
Subject: Re: [PATCH net v3 2/3] net: dsa: mv88e6xxx: read cycle counter period from hardware
Date: Sun, 20 Oct 2024 17:47:25 +0200 [thread overview]
Message-ID: <9cc52176-0e9a-48b5-a044-bc13e39d13ec@lunn.ch> (raw)
In-Reply-To: <20241020063833.5425-3-me@shenghaoyang.info>
On Sun, Oct 20, 2024 at 02:38:29PM +0800, Shenghao Yang wrote:
> Instead of relying on a fixed mapping of hardware family to cycle
> counter frequency, pull this information from the
> MV88E6XXX_TAI_CLOCK_PERIOD register.
>
> This lets us support switches whose cycle counter frequencies depend on
> board design.
>
> Fixes: de776d0d316f ("net: dsa: mv88e6xxx: add support for mv88e6393x family")
> Suggested-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Shenghao Yang <me@shenghaoyang.info>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2024-10-20 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 6:38 [PATCH net v3 0/3] net: dsa: mv88e6xxx: fix MV88E6393X PHC frequency on internal clock Shenghao Yang
2024-10-20 6:38 ` [PATCH net v3 1/3] net: dsa: mv88e6xxx: group cycle counter coefficients Shenghao Yang
2024-10-20 6:38 ` [PATCH net v3 2/3] net: dsa: mv88e6xxx: read cycle counter period from hardware Shenghao Yang
2024-10-20 15:47 ` Andrew Lunn [this message]
2024-10-20 6:38 ` [PATCH net v3 3/3] net: dsa: mv88e6xxx: support 4000ps cycle counter period Shenghao Yang
2024-10-24 11:00 ` [PATCH net v3 0/3] net: dsa: mv88e6xxx: fix MV88E6393X PHC frequency on internal clock patchwork-bot+netdevbpf
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=9cc52176-0e9a-48b5-a044-bc13e39d13ec@lunn.ch \
--to=andrew@lunn.ch \
--cc=ashkan.boldaji@digi.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=me@shenghaoyang.info \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pavana.sharma@digi.com \
--cc=richardcochran@gmail.com \
/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