linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
	kishon@ti.com, robh+dt@kernel.org,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 7/9] dt-bindings: phy: meson-g12a-usb3-pcie-phy: convert to yaml
Date: Thu, 8 Aug 2019 21:50:39 +0200	[thread overview]
Message-ID: <CAFBinCBnVdTxWgqmnrPo-5uZ5gxy7p68w0PUa=_42fYxhVrDXQ@mail.gmail.com> (raw)
In-Reply-To: <20190808085139.21438-8-narmstrong@baylibre.com>

On Thu, Aug 8, 2019 at 10:54 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
>
> Now that we have the DT validation in place, let's convert the device tree
> bindings for the Amlogic G12A USB3 + PCIE Combo PHY over to a YAML schemas.
>
> While the original phy bindings specifies phy-supply as required,
> the examples and implementations makes it optional, thus phy-supply
> is not present in the properties and required lists.
nit-pick: the original bindings didn't mention the phy-supply property at all
I'm not sure if you have to re-send it, maybe this can be fixed up
while applying?

> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2019-08-08 19:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  8:51 [PATCH 0/9] dt-bindings: first tentative of conversion to yaml format Neil Armstrong
2019-08-08  8:51 ` [PATCH 1/9] dt-bindings: mailbox: meson-mhu: convert to yaml Neil Armstrong
2019-08-08  8:51 ` [PATCH 2/9] dt-bindings: rng: amlogic,meson-rng: " Neil Armstrong
2019-08-08  8:51 ` [PATCH 3/9] dt-bindings: spi: meson: " Neil Armstrong
2019-08-08  8:51 ` [PATCH 4/9] dt-bindings: reset: amlogic,meson-reset: " Neil Armstrong
2019-08-08  8:51 ` [PATCH 5/9] dt-bindings: arm: amlogic: amlogic, meson-gx-ao-secure: " Neil Armstrong
2019-08-08  8:51 ` [PATCH 6/9] dt-bindings: phy: meson-g12a-usb2-phy: " Neil Armstrong
2019-08-08  8:51 ` [PATCH 7/9] dt-bindings: phy: meson-g12a-usb3-pcie-phy: " Neil Armstrong
2019-08-08 19:50   ` Martin Blumenstingl [this message]
2019-08-09  7:00     ` Neil Armstrong
2019-08-09 19:55       ` Martin Blumenstingl
2019-08-08  8:51 ` [PATCH 8/9] dt-bindings: serial: meson-uart: " Neil Armstrong
2019-08-08  8:51 ` [PATCH 9/9] dt-bindings: watchdog: meson-gxbb-wdt: " Neil Armstrong
2019-08-13 21:19 ` [PATCH 0/9] dt-bindings: first tentative of conversion to yaml format Rob Herring

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='CAFBinCBnVdTxWgqmnrPo-5uZ5gxy7p68w0PUa=_42fYxhVrDXQ@mail.gmail.com' \
    --to=martin.blumenstingl@googlemail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=narmstrong@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@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).