1. 09 Sep, 2017 1 commit
  2. 23 Jun, 2017 1 commit
  3. 22 Jun, 2017 1 commit
    • Frank Rowand's avatar
      of: update ePAPR references to point to Devicetree Specification · 076fb0c4
      Frank Rowand authored
      The Devicetree Specification has superseded the ePAPR as the
      base specification for bindings.  Update files in Documentation
      to reference the new document.
      First reference to ePAPR in Documentation/devicetree/bindings/arm/cci.txt
      is generic, remove it.
      Some files are not updated because there is no hypervisor chapter
      in the Devicetree Specification:
      Signed-off-by: default avatarFrank Rowand <frank.rowand@sony.com>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
  4. 07 Jun, 2017 1 commit
  5. 07 Feb, 2017 1 commit
  6. 28 Nov, 2016 1 commit
    • Martin Blumenstingl's avatar
      Documentation: devicetree: clarify usage of the RGMII phy-modes · e5f3a4a5
      Martin Blumenstingl authored
      RGMII requires special RX and/or TX delays depending on the actual
      hardware circuit/wiring. These delays can be added by the MAC, the PHY
      or the designer of the circuit (the latter means that no delay has to
      be added by PHY or MAC).
      There are 4 RGMII phy-modes used describe where a delay should be
      - rgmii: the RX and TX delays are either added by the MAC (where the
        exact delay is typically configurable, and can be turned off when no
        extra delay is needed) or not needed at all (because the hardware
        wiring adds the delay already). The PHY should neither add the RX nor
        TX delay in this case.
      - rgmii-rxid: configures the PHY to enable the RX delay. The MAC should
        not add the RX delay in this case.
      - rgmii-txid: configures the PHY to enable the TX delay. The MAC should
        not add the TX delay in this case.
      - rgmii-id: combines rgmii-rxid and rgmii-txid and thus configures the
        PHY to enable the RX and TX delays. The MAC should neither add the RX
        nor TX delay in this case.
      Document these cases in the ethernet.txt documentation to make it clear
      when to use each mode.
      If applied incorrectly one might end up with MAC and PHY both enabling
      for example the TX delay, which breaks ethernet TX traffic on 1000Mbit/s
      Signed-off-by: default avatarMartin Blumenstingl <martin.blumenstingl@googlemail.com>
      Reviewed-by: default avatarFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  7. 24 Sep, 2016 1 commit
  8. 21 Jul, 2015 1 commit
    • Stas Sergeev's avatar
      of_mdio: add new DT property 'managed' to specify the PHY management type · 4cba5c21
      Stas Sergeev authored
      Currently the PHY management type is selected by the MAC driver arbitrary.
      The decision is based on the presence of the "fixed-link" node and on a
      will of the driver's authors.
      This caused a regression recently, when mvneta driver suddenly started
      to use the in-band status for auto-negotiation on fixed links.
      It appears the auto-negotiation may not work when expected by the MAC driver.
      Sebastien Rannou explains:
      << Yes, I confirm that my HW does not generate an in-band status. AFAIK, it's
      a PHY that aggregates 4xSGMIIs to 1xQSGMII ; the MAC side of the PHY (with
      inband status) is connected to the switch through QSGMII, and in this context
      we are on the media side of the PHY. >>
      This patch introduces the new string property 'managed' that allows
      the user to set the management type explicitly.
      The supported values are:
      "auto" - default. Uses either MDIO or nothing, depending on the presence
      of the fixed-link node
      "in-band-status" - use in-band status
      Signed-off-by: default avatarStas Sergeev <stsp@users.sourceforge.net>
      CC: Rob Herring <robh+dt@kernel.org>
      CC: Pawel Moll <pawel.moll@arm.com>
      CC: Mark Rutland <mark.rutland@arm.com>
      CC: Ian Campbell <ijc+devicetree@hellion.org.uk>
      CC: Kumar Gala <galak@codeaurora.org>
      CC: Florian Fainelli <f.fainelli@gmail.com>
      CC: Grant Likely <grant.likely@linaro.org>
      CC: devicetree@vger.kernel.org
      CC: linux-kernel@vger.kernel.org
      CC: netdev@vger.kernel.org
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  9. 16 Apr, 2015 1 commit
  10. 16 Apr, 2014 1 commit
  11. 18 Feb, 2014 1 commit
    • Sergei Shtylyov's avatar
      DT: net: document Ethernet bindings in one place · e8f08ee0
      Sergei Shtylyov authored
      This patch is an attempt to gather the Ethernet related bindings in one file,
      like it's done in the MMC and some other subsystems. It should save some of
      the trouble of documenting several properties over and over in each binding
      document, instead only making reference to the main file.
      I have used the Embedded Power Architecture(TM) Platform Requirements (ePAPR)
      standard as a base for the properties description, also documenting some ad-hoc
      properties that have been introduced over time despite having direct analogs in
      Signed-off-by: default avatarSergei Shtylyov <sergei.shtylyov@cogentembedded.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>