From: Rob Herring <robh@kernel.org>
To: "Marek Behún" <kabel@kernel.org>
Cc: devicetree@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com>,
Holger Brunck <holger.brunck@hitachienergy.com>,
Andrew Lunn <andrew@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-phy@lists.infradead.org, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH devicetree 1/2] dt-bindings: phy: Convert generic PHY provider binding to YAML
Date: Wed, 15 Dec 2021 15:41:04 -0600 [thread overview]
Message-ID: <Ybpg8OpVCmWqNOL2@robh.at.kernel.org> (raw)
In-Reply-To: <20211214233432.22580-2-kabel@kernel.org>
On Wed, Dec 15, 2021 at 12:34:31AM +0100, Marek Behún wrote:
> Convert phy-bindings.txt to YAML. This creates binding only for PHY
> provider, since PHY consumer binding is in dtschema. Consumer binding
> example is provided.
>
> Signed-off-by: Marek Behún <kabel@kernel.org>
> ---
> .../devicetree/bindings/phy/phy-bindings.txt | 73 +------------------
> .../devicetree/bindings/phy/phy.yaml | 59 +++++++++++++++
> 2 files changed, 60 insertions(+), 72 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/phy/phy.yaml
We already have phy-provider.yaml and phy-consumer.yaml in dtschema
repo. Add what's missing there (anything copied from here will need to
be relicensed).
Rob
next prev parent reply other threads:[~2021-12-15 21:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 23:34 [PATCH devicetree 0/2] Common PHY to YAML + tx-amplitude property Marek Behún
2021-12-14 23:34 ` [PATCH devicetree 1/2] dt-bindings: phy: Convert generic PHY provider binding to YAML Marek Behún
2021-12-15 21:41 ` Rob Herring [this message]
2021-12-14 23:34 ` [PATCH devicetree 2/2] dt-bindings: phy: Add `tx-amplitude-microvolt` property binding Marek Behún
2021-12-15 10:55 ` Andrew Lunn
2021-12-15 17:22 ` Marek Behún
2021-12-15 17:29 ` Andrew Lunn
2021-12-15 22:01 ` Rob Herring
2021-12-15 21:58 ` Rob Herring
2022-01-12 17:29 ` Marek Behún
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=Ybpg8OpVCmWqNOL2@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=holger.brunck@hitachienergy.com \
--cc=kabel@kernel.org \
--cc=kishon@ti.com \
--cc=linux-phy@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=vkoul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).