public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Frank Rowand" <frowand.list@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	"Chen-Yu Tsai" <wens@csie.org>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@st.com>,
	netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
	"Antoine Ténart" <antoine.tenart@bootlin.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v3 01/16] dt-bindings: net: Add YAML schemas for the generic Ethernet options
Date: Thu, 20 Jun 2019 11:08:57 +0200	[thread overview]
Message-ID: <20190620090857.z6gru4cilq6z7e4w@flea> (raw)
In-Reply-To: <20190619140314.GC18352@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 2740 bytes --]

Hi Andrew,

On Wed, Jun 19, 2019 at 04:03:14PM +0200, Andrew Lunn wrote:
> > +  phy-connection-type:
> > +    description:
> > +      Operation mode of the PHY interface
> > +    enum:
> > +      # There is not a standard bus between the MAC and the PHY,
> > +      # something proprietary is being used to embed the PHY in the
> > +      # MAC.
>
> ...
>
> > +
> > +  phy-mode:
> > +    $ref: "#/properties/phy-connection-type"
> > +    deprecated: true
>
> I don't think phy-mode is actually deprecated. ethernet.txt actually says:
>
> "This is now a de-facto standard property;" and no mentions that is
> should not be used. Looking at actual device trees, phy-mode is by far
> more popular than phy-connection-type.

Looking at the phy-connection-type documentation, I was under this
impression, sorry.

I'll drop it then.

> fwnode_get_phy_mode() first looks for phy-mode and only falls back to
> phy-connection-type if it is not present. The same is true for
> of_get_phy_mode().
>
> > +  fixed-link:
> > +    allOf:
> > +      - if:
> > +          type: array
> > +        then:
> > +          minItems: 1
> > +          maxItems: 1
> > +          items:
> > +            items:
> > +              - minimum: 0
> > +                maximum: 31
> > +                description:
> > +                  Emulated PHY ID, choose any but unique to the all
> > +                  specified fixed-links
> > +
> > +              - enum: [0, 1]
> > +                description:
> > +                  Duplex configuration. 0 for half duplex or 1 for
> > +                  full duplex
> > +
> > +              - enum: [10, 100, 1000]
> > +                description:
> > +                  Link speed in Mbits/sec.
> > +
> > +              - enum: [0, 1]
> > +                description:
> > +                  Pause configuration. 0 for no pause, 1 for pause
> > +
> > +              - enum: [0, 1]
> > +                description:
> > +                  Asymmetric pause configuration. 0 for no asymmetric
> > +                  pause, 1 for asymmetric pause
> > +
>
> This array of 5 values format should be marked as deprecated.

Right, I'll add it.

> > +
> > +      - if:
> > +          type: object
> > +        then:
> > +          properties:
> > +            speed:
> > +              allOf:
> > +                - $ref: /schemas/types.yaml#definitions/uint32
> > +                - enum: [10, 100, 1000]
>
> This recently changed, depending on context. If PHYLINK is being used,
> any speed is allowed. If phylib is used, then only these speeds are
> allowed. And we are starting to see some speeds other than listed
> here.

phylink seems to be described in a separate binding document, maybe we
can adjust that later?

Maxime

      reply	other threads:[~2019-06-20  9:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19  9:47 [PATCH v3 01/16] dt-bindings: net: Add YAML schemas for the generic Ethernet options Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 02/16] dt-bindings: net: Add a YAML schemas for the generic PHY options Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 03/16] dt-bindings: net: Add a YAML schemas for the generic MDIO options Maxime Ripard
2019-06-19 14:17   ` Rob Herring
2019-06-20  9:56     ` Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 04/16] MAINTAINERS: Add Ethernet PHY YAML file Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 05/16] dt-bindings: net: phy: The interrupt property is not mandatory Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 06/16] dt-bindings: net: sun4i-emac: Convert the binding to a schemas Maxime Ripard
2019-06-19 14:46   ` Rob Herring
2019-06-19 20:44     ` Rob Herring
2019-06-19  9:47 ` [PATCH v3 07/16] dt-bindings: net: sun4i-mdio: " Maxime Ripard
2019-06-19 14:19   ` Rob Herring
2019-06-19  9:47 ` [PATCH v3 08/16] dt-bindings: net: stmmac: " Maxime Ripard
2019-06-19 14:12   ` Rob Herring
2019-06-19  9:47 ` [PATCH v3 09/16] dt-bindings: net: sun7i-gmac: " Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 10/16] dt-bindings: net: sun8i-emac: " Maxime Ripard
2019-06-19 14:10   ` Rob Herring
2019-06-19  9:47 ` [PATCH v3 11/16] dt-bindings: net: dwmac: Deprecate the PHY reset properties Maxime Ripard
2019-06-19 14:47   ` Rob Herring
2019-06-19  9:47 ` [PATCH v3 12/16] ARM: dts: sunxi: Switch to the generic PHY properties Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 13/16] ARM: dts: sunxi: Switch from phy to phy-handle Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 14/16] ARM: dts: sunxi: Switch from phy-mode to phy-connection-type Maxime Ripard
2019-06-19 14:11   ` Andrew Lunn
2019-06-19  9:47 ` [PATCH v3 15/16] ARM: dts: sunxi: h3/h5: " Maxime Ripard
2019-06-19  9:47 ` [PATCH v3 16/16] arm64: dts: allwinner: " Maxime Ripard
2019-06-19 14:03 ` [PATCH v3 01/16] dt-bindings: net: Add YAML schemas for the generic Ethernet options Andrew Lunn
2019-06-20  9:08   ` Maxime Ripard [this message]

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=20190620090857.z6gru4cilq6z7e4w@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=alexandre.torgue@st.com \
    --cc=andrew@lunn.ch \
    --cc=antoine.tenart@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=frowand.list@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mark.rutland@arm.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=wens@csie.org \
    /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