From: David Miller <davem@davemloft.net>
To: weifeng.voon@intel.com
Cc: mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, joabreu@synopsys.com,
peppe.cavallaro@st.com, andrew@lunn.ch, alexandre.torgue@st.com,
boon.leong.ong@intel.com
Subject: Re: [net-next,v1, 1/1] net: stmmac: Enable SERDES power up/down sequence
Date: Tue, 21 Apr 2020 15:54:58 -0700 (PDT) [thread overview]
Message-ID: <20200421.155458.2145871366975263658.davem@davemloft.net> (raw)
In-Reply-To: <20200420154252.8000-2-weifeng.voon@intel.com>
From: Voon Weifeng <weifeng.voon@intel.com>
Date: Mon, 20 Apr 2020 23:42:52 +0800
> This patch is to enable Intel SERDES power up/down sequence. The SERDES
> converts 8/10 bits data to SGMII signal. Below is an example of
> HW configuration for SGMII mode. The SERDES is located in the PHY IF
> in the diagram below.
>
> <-----------------GBE Controller---------->|<--External PHY chip-->
> +----------+ +----+ +---+ +----------+
> | EQoS | <-GMII->| DW | < ------ > |PHY| <-SGMII-> | External |
> | MAC | |xPCS| |IF | | PHY |
> +----------+ +----+ +---+ +----------+
> ^ ^ ^ ^
> | | | |
> +---------------------MDIO-------------------------+
>
> PHY IF configuration and status registers are accessible through
> mdio address 0x15 which is defined as mdio_adhoc_addr. During D0,
> The driver will need to power up PHY IF by changing the power state
> to P0. Likewise, for D3, the driver sets PHY IF power state to P3.
>
> Signed-off-by: Voon Weifeng <weifeng.voon@intel.com>
> Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com>
Applied, thanks.
prev parent reply other threads:[~2020-04-21 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 15:42 [net-next,v1, 0/1] Enable SERDES power up/down Voon Weifeng
2020-04-20 15:42 ` [net-next,v1, 1/1] net: stmmac: Enable SERDES power up/down sequence Voon Weifeng
2020-04-21 22:54 ` David Miller [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=20200421.155458.2145871366975263658.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=joabreu@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=weifeng.voon@intel.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
all inboxes | Powered by JetHome®