• Home
  • History
  • Annotate
  • Raw
  • Download
  • only in /netgear-R7000-V1.0.7.12_1.2.5/components/opensource/linux/linux-2.6.36/drivers/net/igb/

Lines Matching defs:link

463  *  igb_check_for_copper_link - Check for link (Copper)
466 * Checks to see of the link status of the hardware has changed. If a
467 * change in link status has been detected, then we read the PHY registers
468 * to get the current speed/duplex if link exists.
474 bool link;
478 * has completed and/or if our link status has changed. The
489 * link. If so, then we want to get the current speed/duplex
492 ret_val = igb_phy_has_link(hw, 1, 0, &link);
496 if (!link)
497 goto out; /* No link detected */
503 * immediately after link-up
509 * we have already determined whether we have link or not.
527 * different link partner.
538 * igb_setup_link - Setup flow control and link settings
542 * control. Calls the appropriate media-specific link configuration
543 * function. Assuming the adapter has a valid link partner, a valid link
552 * In the case of the phy reset being blocked, we already have a link.
577 /* Call the necessary media_type subroutine to configure the link. */
606 * during link setup. Currently no func pointer exists and all
708 * also configure these bits when link is forced on a fiber connection.
718 * Because we didn't get link via the internal auto-negotiation
719 * mechanism (we either forced link or we got link via PHY
765 * igb_config_fc_after_link_up - Configures flow control after link
768 * Checks the status of auto-negotiation after link up to ensure that the
769 * speed and duplex were not forced. If the link needed to be forced, then
771 * and did not fail, then we configure flow control based on our link
783 * so we had to force link. In this case, we need to force the
802 * has completed, and if so, how the PHY and link partner has
846 * for both the PHY and the link partner. The following
928 * desired flow control, but can be forced on the link
932 * and the link partner advertised none, we will configure
934 * this safely for two reasons: If the link partner really
937 * anyway. If the intent on the link partner was to have
943 * our link partner to pause transmission of frames.
962 hw_dbg("Error getting link speed and duplex\n");