From: Andrew Lunn <andrew@lunn.ch>
To: 劉偉權 <willy.liu@realtek.com>
Cc: Serge Semin <fancer.lancer@gmail.com>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ryan Kao <ryankao@realtek.com>, Kyle Evans <kevans@FreeBSD.org>,
Joe Hershberger <joe.hershberger@ni.com>,
Peter Robinson <pbrobinson@gmail.com>
Subject: Re: [PATCH] net: phy: realtek: fix rtl8211e rx/tx delay config
Date: Fri, 18 Sep 2020 15:54:03 +0200 [thread overview]
Message-ID: <20200918135403.GC3631014@lunn.ch> (raw)
In-Reply-To: <87c4ebf4b1fe48a7a10b27d0ba0b333c@realtek.com>
On Fri, Sep 18, 2020 at 06:55:16AM +0000, 劉偉權 wrote:
> Hi Serge,
> Thanks for your reply. There is a confidential issue that realtek
> doesn't offer the detail of a full register layout for configuration
> register.
...
> > * 0xa4 extension page (0x7) layout. It can be used to disable/enable
> > * the RX/TX delays otherwise controlled by RXDLY/TXDLY pins. It can
> > * also be used to customize the whole configuration register:
>
> > - * 8:6 = PHY Address, 5:4 = Auto-Negotiation, 3 = Interface Mode Select,
> > - * 2 = RX Delay, 1 = TX Delay, 0 = SELRGV (see original PHY datasheet
> > - * for details).
> > + * 13 = Force Tx RX Delay controlled by bit12 bit11,
> > + * 12 = RX Delay, 11 = TX Delay
>
> Here you've removed the register layout description and replaced itq
> with just three bits info. So from now the text above doesn't really
> corresponds to what follows.
> I might have forgotten something, but AFAIR that register bits
> stateq mapped well to what was available on the corresponding
> external pins.
Hi Willy
So it appears bits 3 to 8 have been reverse engineered. Unless you
know from your confidential datasheet that these are wrong, please
leave the comment alone.
If you confidential datasheet says that the usage of bits 0-2 is
wrong, then please do correct that part.
Andrew
next prev parent reply other threads:[~2020-09-18 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 1:47 [PATCH] net: phy: realtek: fix rtl8211e rx/tx delay config Willy Liu
2020-09-17 10:10 ` Serge Semin
2020-09-18 6:55 ` 劉偉權
2020-09-18 13:54 ` Andrew Lunn [this message]
2020-09-18 15:33 ` Serge Semin
2020-09-21 7:00 ` 劉偉權
2020-09-21 15:12 ` Andrew Lunn
2020-09-22 6:42 ` 劉偉權
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=20200918135403.GC3631014@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=fancer.lancer@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=joe.hershberger@ni.com \
--cc=kevans@FreeBSD.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=ryankao@realtek.com \
--cc=willy.liu@realtek.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;
as well as URLs for NNTP newsgroup(s).