From: Florian Fainelli <f.fainelli@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Marek Vasut <marex@denx.de>,
David Jander <david@protonic.nl>,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/4] dt-bindings: net: phy: Add support for NXP TJA11xx
Date: Wed, 22 Apr 2020 20:15:42 -0700 [thread overview]
Message-ID: <b47f742d-e79a-11c8-6d39-db27dced28b8@gmail.com> (raw)
In-Reply-To: <20200422092456.24281-2-o.rempel@pengutronix.de>
On 4/22/2020 2:24 AM, Oleksij Rempel wrote:
> Document the NXP TJA11xx PHY bindings.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> .../devicetree/bindings/net/nxp,tja11xx.yaml | 61 +++++++++++++++++++
> 1 file changed, 61 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/nxp,tja11xx.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/nxp,tja11xx.yaml b/Documentation/devicetree/bindings/net/nxp,tja11xx.yaml
> new file mode 100644
> index 0000000000000..42be0255512b3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/nxp,tja11xx.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: GPL-2.0+
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/nxp,tja11xx.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP TJA11xx PHY
> +
> +maintainers:
> + - Andrew Lunn <andrew@lunn.ch>
> + - Florian Fainelli <f.fainelli@gmail.com>
> + - Heiner Kallweit <hkallweit1@gmail.com>
I would have expected to have you listed as a maintainer of this
binding, but fair enough.
> +
> +description:
> + Bindings for NXP TJA11xx automotive PHYs
> +
> +allOf:
> + - $ref: ethernet-phy.yaml#
> +
> +patternProperties:
> + "^ethernet-phy@[0-9a-f]+$":
> + type: object
> + description: |
> + Some packages have multiple PHYs. Secondary PHY should be defines as
should be defined as a subnode.
--
Florian
next prev parent reply other threads:[~2020-04-23 3:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 9:24 [PATCH net-next v5 0/4] add TJA1102 support Oleksij Rempel
2020-04-22 9:24 ` [PATCH net-next v5 1/4] dt-bindings: net: phy: Add support for NXP TJA11xx Oleksij Rempel
2020-04-22 13:49 ` Andrew Lunn
2020-04-23 3:15 ` Florian Fainelli [this message]
2020-04-22 9:24 ` [PATCH net-next v5 2/4] net: phy: tja11xx: add initial TJA1102 support Oleksij Rempel
2020-04-22 13:44 ` Andrew Lunn
2020-04-23 3:17 ` Florian Fainelli
2020-04-22 9:24 ` [PATCH net-next v5 3/4] net: mdio: of: export part of of_mdiobus_register_phy() Oleksij Rempel
2020-04-22 13:45 ` Andrew Lunn
2020-04-23 3:18 ` Florian Fainelli
2020-04-22 9:24 ` [PATCH net-next v5 4/4] net: phy: tja11xx: add delayed registration of TJA1102 PHY1 Oleksij Rempel
2020-04-22 13:48 ` Andrew Lunn
2020-04-23 3:21 ` Florian Fainelli
2020-04-23 2:41 ` [PATCH net-next v5 0/4] add TJA1102 support David Miller
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=b47f742d-e79a-11c8-6d39-db27dced28b8@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.