linux-toradex.git/include/linux/phy.h, branch v2.6.38.5

phylib: make local function static

2010-10-24T22:07:11+00:00

The following functions are not used directly by any drivers:
    phy_attach_direct
    phy_device_create
    phy_prepare_link
    genphy_config_advert
    genphy_setup_forced
    phy_config_interrupt
    phy_clear_interrypt
    phy_sanitize_settings
    phy_enable_interrupts
    phy_disable_interrupts

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

net: Improve comments in include/linux/phy.h

2010-09-02T17:12:05+00:00

Correct state range of PHY bus addresses (i.e. 0-31) in comment,
make spelling of PHY consistent in comments.

Signed-off-by: Peter Meerwald 
Signed-off-by: David S. Miller

net: support time stamping in phy devices.

2010-07-19T02:15:26+00:00

This patch adds a new networking option to allow hardware time stamps
from PHY devices. When enabled, likely candidates among incoming and
outgoing network packets are offered to the PHY driver for possible
time stamping. When accepted by the PHY driver, incoming packets are
deferred for later delivery by the driver.

The patch also adds phylib driver methods for the SIOCSHWTSTAMP ioctl
and callbacks for transmit and receive time stamping. Drivers may
optionally implement these functions.

Signed-off-by: Richard Cochran 
Signed-off-by: David S. Miller

net: preserve ifreq parameter when calling generic phy_mii_ioctl().

2010-07-19T02:15:25+00:00

The phy_mii_ioctl() function unnecessarily throws away the original ifreq.
We need access to the ifreq in order to support PHYs that can perform
hardware time stamping.

Two maverick drivers filter the ioctl commands passed to phy_mii_ioctl().
This is unnecessary since phylib will check the command in any case.

Signed-off-by: Richard Cochran 
Signed-off-by: David S. Miller

phylib: Support phy module autoloading

2010-04-02T21:30:39+00:00

We don't use the normal hotplug mechanism because it doesn't work. It will
load the module some time after the device appears, but that's not good
enough for us -- we need the driver loaded _immediately_ because otherwise
the NIC driver may just abort and then the phy 'device' goes away.

[bwh: s/phy/mdio/ in module alias, kerneldoc for struct mdio_device_id]

Signed-off-by: David Woodhouse 
Signed-off-by: Ben Hutchings 
Acked-by: Andy Fleming 
Signed-off-by: David S. Miller

NET: Support clause 45 MDIO commands at the MDIO bus level

2010-03-17T04:23:42+00:00

IEEE 802.3ae clause 45 specifies a somewhat modified MDIO protocol
for use by 10GIGE phys. The main change is a 21 bit address split into
a 5 bit device ID and a 16 bit register offset. The definition is designed
so that normal and extended devices can run on the same MDIO bus.

Extend mdio-bitbang to do the new protocol. At the MDIO bus level the
protocol is requested by or'ing MII_ADDR_C45 into the register offset.

Make phy_read/phy_write/etc pass a full 32 bit register offset.

This does not attempt to make the phy layer support C45 style PHYs, just
to provide the MDIO bus support.

Tested against a Broadcom 10GE phy with ID 0x206034, and several
Broadcom 10/100/1000 Phys in normal mode.

Signed-off-by: Jason Gunthorpe 
Signed-off-by: David S. Miller

libphy: add phy_find_first function

2010-02-04T18:23:02+00:00

Many drivers do this in them manually. Now they can use this function.

Signed-off-by: Jiri Pirko 
Signed-off-by: David S. Miller

phylib: Move workqueue initialization to a proper place

2010-01-19T09:59:02+00:00

commit 541cd3ee00a4fe975b22fac6a3bc846bacef37f7 ("phylib: Fix deadlock
on resume") caused TI DaVinci EMAC ethernet driver to oops upon resume:

 PM: resume of devices complete after 237.098 msecs
 Restarting tasks ... done.
 kernel BUG at kernel/workqueue.c:354!
 Unable to handle kernel NULL pointer dereference at virtual address 00000000
 [...]
 Backtrace:
 [] (__bug+0x0/0x2c) from [] (queue_delayed_work_on+0x74/0xf8)
 [] (queue_delayed_work_on+0x0/0xf8) from [] (queue_delayed_work+0x2c/0x30)

The oops pops up because TI DaVinci EMAC driver detaches PHY on
suspend and attaches it back on resume. Attaching makes phylib call
phy_start_machine() that initializes a workqueue. On the other hand,
PHY's resume routine will call phy_start_machine() again, and that
will cause the oops since we just destroyed the already scheduled
workqueue.

This patch fixes the issue by moving workqueue initialization to
phy_device_create().

p.s. We don't see this oops with ucc_geth and gianfar drivers because
they perform a fine-grained suspend, i.e. they just stop the PHYs
without detaching.

Reported-by: Sekhar Nori 
Signed-off-by: Anton Vorontsov 
Tested-by: Sekhar Nori 
Signed-off-by: David S. Miller

phylib: Properly reinitialize PHYs after hibernation

2009-12-31T06:03:42+00:00

Since hibernation assumes power loss, we should fully reinitialize
PHYs (including platform fixups), as if PHYs were just attached.

This patch factors phy_init_hw() out of phy_attach_direct(), then
converts mdio_bus to dev_pm_ops and adds an appropriate restore()
callback.

Signed-off-by: Anton Vorontsov 
Signed-off-by: David S. Miller

phy: Eliminate references to BUS_ID_SIZE.

2009-05-27T04:16:25+00:00

Just use the constant 20 to keep things working.

If someone is so motivated, this can be converted over to
dynamic strings.  I tried and it's a lot of work.

But for now this is good enough.

Signed-off-by: David S. Miller