From: Voon Weifeng <weifeng.voon@intel.com>
To: "David S . Miller" <davem@davemloft.net>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jose Abreu <joabreu@synopsys.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Andrew Lunn <andrew@lunn.ch>,
Alexandre Torgue <alexandre.torgue@st.com>,
Ong Boon Leong <boon.leong.ong@intel.com>,
Voon Weifeng <weifeng.voon@intel.com>
Subject: [net-next,v1, 0/1] Enable SERDES power up/down
Date: Mon, 20 Apr 2020 23:42:51 +0800 [thread overview]
Message-ID: <20200420154252.8000-1-weifeng.voon@intel.com> (raw)
This patch is to enable Intel SERDES power up/down sequence. The SERDES
converts 8/10 bits data to SGMII signal.
1.Introduced 2 new BSP callbacks ->serdes_powerup() and ->serdes_powerdown().
2.The 2 new BSP callbacks is called in stmmac_dvr_probe() and
stmmac_resume() for SERDER powerup; stmmac_dvr_remove() and
stmmac_suspend() for SERDES powerdown.
3.Intel platform specific SERDES powerup and powerdown sequence functions
are added in dwmac-intel.c.
4.Since configuring the SERDES is through mdio, mdio communication is
needed to be up before powerup sequence. As for SERDES power-down
sequence, it must be configured after all dma stop and before unregister
the mdio bus.
5.New file dwmac-intel.h is created for register definition.
Voon Weifeng (1):
net: stmmac: Enable SERDES power up/down sequence
.../net/ethernet/stmicro/stmmac/dwmac-intel.c | 189 ++++++++++++++++++
.../net/ethernet/stmicro/stmmac/dwmac-intel.h | 23 +++
.../net/ethernet/stmicro/stmmac/stmmac_main.c | 23 +++
include/linux/stmmac.h | 2 +
4 files changed, 237 insertions(+)
create mode 100644 drivers/net/ethernet/stmicro/stmmac/dwmac-intel.h
--
2.17.1
next reply other threads:[~2020-04-20 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 15:42 Voon Weifeng [this message]
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
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=20200420154252.8000-1-weifeng.voon@intel.com \
--to=weifeng.voon@intel.com \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--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 \
/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
Powered by JetHome