'\" t
.\"     Title: genphy_read_status
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\"      Date: May 2018
.\"    Manual: Network device support
.\"    Source: Kernel Hackers Manual 3.16.56
.\"  Language: English
.\"
.TH "GENPHY_READ_STATUS" "9" "May 2018" "Kernel Hackers Manual 3\&.16\&" "Network device support"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
genphy_read_status \- check the link status and update current link state
.SH "SYNOPSIS"
.HP \w'int\ genphy_read_status('u
.BI "int genphy_read_status(struct\ phy_device\ *\ " "phydev" ");"
.SH "ARGUMENTS"
.PP
\fIphydev\fR
.RS 4
target phy_device struct
.RE
.SH "DESCRIPTION"
.PP
Check the link, then figure out the current state by comparing what we advertise with what the link partner advertises\&. Start by checking the gigabit possibilities, then move on to 10/100\&.
.SH "COPYRIGHT"
.br