From: Rob Herring <robh@kernel.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: vkoul@kernel.org, kishon@ti.com,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: phy: add Amlogic G12A Analog MIPI D-PHY bindings
Date: Mon, 7 Dec 2020 16:47:36 -0600 [thread overview]
Message-ID: <20201207224736.GB978231@robh.at.kernel.org> (raw)
In-Reply-To: <20201123145157.300456-2-narmstrong@baylibre.com>
On Mon, Nov 23, 2020 at 03:51:56PM +0100, Neil Armstrong wrote:
> The Amlogic G12A SoCs embeds an Analog MIPI D-PHY to communicate with DSI
> panels, this adds the bindings.
>
> This Analog D-PHY works with a separate Digital MIPI D-PHY.
>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> .../phy/amlogic,g12a-mipi-dphy-analog.yaml | 40 +++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/amlogic,g12a-mipi-dphy-analog.yaml
>
> diff --git a/Documentation/devicetree/bindings/phy/amlogic,g12a-mipi-dphy-analog.yaml b/Documentation/devicetree/bindings/phy/amlogic,g12a-mipi-dphy-analog.yaml
> new file mode 100644
> index 000000000000..28663552f05b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/amlogic,g12a-mipi-dphy-analog.yaml
> @@ -0,0 +1,40 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/phy/amlogic,g12a-mipi-dphy-analog.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Amlogic G12A MIPI analog PHY
> +
> +maintainers:
> + - Neil Armstrong <narmstrong@baylibre.com>
> +
> +description: |+
> + The Everything-Else Power Domains node should be the child of a syscon
> + node with the required property:
> +
> + - compatible: Should be the following:
> + "amlogic,meson-gx-hhi-sysctrl", "simple-mfd", "syscon"
> +
> + Refer to the the bindings described in
> + Documentation/devicetree/bindings/mfd/syscon.yaml
This schema should be referenced from the parent schema and if you have
child nodes, you shouldn't be using syscon.yaml.
> +
> +properties:
> + compatible:
> + const: amlogic,g12a-mipi-dphy-analog
> +
> + "#phy-cells":
> + const: 0
> +
> +required:
> + - compatible
> + - "#phy-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + mpphy: phy {
> + compatible = "amlogic,g12a-mipi-dphy-analog";
> + #phy-cells = <0>;
Looks like a dedicated subset of registers, add 'reg' even if Linux
doesn't use it (currently).
> + };
> --
> 2.25.1
>
next prev parent reply other threads:[~2020-12-07 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 14:51 [PATCH 0/2] phy: amlogic: Add support for the G12A Analog MIPI D-PHY Neil Armstrong
2020-11-23 14:51 ` [PATCH 1/2] dt-bindings: phy: add Amlogic G12A Analog MIPI D-PHY bindings Neil Armstrong
2020-12-05 8:04 ` Vinod Koul
2020-12-07 9:50 ` Neil Armstrong
2020-12-07 22:44 ` Rob Herring
2020-12-08 7:52 ` Neil Armstrong
2020-12-07 22:47 ` Rob Herring [this message]
2020-11-23 14:51 ` [PATCH 2/2] phy: amlogic: Add G12A Analog MIPI D-PHY driver Neil Armstrong
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=20201207224736.GB978231@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--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).