From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: "'Andrew Lunn'" <andrew@lunn.ch>
Cc: <netdev@vger.kernel.org>, <chris.packham@alliedtelesis.co.nz>,
<daniel@makrotopia.org>,
"'Jonas Jelonek'" <jonas.jelonek@protonmail.ch>
Subject: AW: Realtek Otto PHY hardware polling
Date: Mon, 8 Jun 2026 19:29:27 +0200 [thread overview]
Message-ID: <05d401dcf76c$5e474550$1ad5cff0$@gmx.de> (raw)
In-Reply-To: <1a025904-4518-4e48-bbe1-c203e409ee4d@lunn.ch>
> Von: Andrew Lunn <andrew@lunn.ch>
> Gesendet: Sonntag, 7. Juni 2026 08:39
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Cc: netdev@vger.kernel.org; chris.packham@alliedtelesis.co.nz;
daniel@makrotopia.org; 'Jonas Jelonek' <jonas.jelonek@protonmail.ch>
> Betreff: Re: Realtek Otto PHY hardware polling
>
> > Basically there is no need to disable/enable polling for an access.
> > We are running OpenWrt with polling enabled all the time without
> > major issues.
>
> > - It is only used for special functions (fiber, EEE, hard reset, SerDes
> > calibration).
>
> One obvious question is, why are these special? Hard reset i can
> understand, you need to know the reset is complete before trying to
> use the registers. But the others?
>
> Either we need some documentation from Realtek, or we need to reverse
> engineer the hardware to understand what it does.
Just out of curiosity I ordered a logic analyzer. Lets see
if it tells us more.
Markus
prev parent reply other threads:[~2026-06-08 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 16:48 Realtek Otto PHY hardware polling Markus Stockhausen
2026-06-07 6:39 ` Andrew Lunn
2026-06-08 17:29 ` Markus Stockhausen [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='05d401dcf76c$5e474550$1ad5cff0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=daniel@makrotopia.org \
--cc=jonas.jelonek@protonmail.ch \
--cc=netdev@vger.kernel.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