devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Yuti Amonkar <yamonkar@cadence.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	kishon@ti.com, mark.rutland@arm.com, maxime@cerno.tech,
	jsarha@ti.com, tomi.valkeinen@ti.com, praneeth@ti.com,
	mparab@cadence.com, sjakhade@cadence.com
Subject: Re: [PATCH v3 01/14] dt-bindings: phy: Convert Cadence MHDP PHY bindings to YAML.
Date: Mon, 27 Jan 2020 10:25:33 -0600	[thread overview]
Message-ID: <20200127162533.GA20343@bogus> (raw)
In-Reply-To: <1579689918-7181-2-git-send-email-yamonkar@cadence.com>

On Wed, Jan 22, 2020 at 11:45:05AM +0100, Yuti Amonkar wrote:
> - Convert the MHDP PHY devicetree bindings to yaml schemas.
> - Rename DP PHY to have generic Torrent PHY nomrnclature.
> - Add Torrent PHY reference clock bindings.
> - Rename compatible string from "cdns,dp-phy" to "cdns,torrent-phy".
>   This will not affect ABI as the driver has never been functional,
>   and therefore do not exist in any active use case
> 
> Signed-off-by: Yuti Amonkar <yamonkar@cadence.com>
> ---
>  .../devicetree/bindings/phy/phy-cadence-dp.txt     | 30 --------
>  .../bindings/phy/phy-cadence-torrent.yaml          | 82 ++++++++++++++++++++++
>  2 files changed, 82 insertions(+), 30 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/phy/phy-cadence-dp.txt
>  create mode 100644 Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml

> diff --git a/Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml b/Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml
> new file mode 100644
> index 0000000..eb633d7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml
> @@ -0,0 +1,82 @@

Missing SPDX tag.

As Cadence is the only contributor to the old doc, please relicense to 
dual license:

(GPL-2.0-only OR BSD-2-Clause)

> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/phy/phy-cadence-torrent.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Cadence Torrent SD0801 PHY binding for DisplayPort
> +
> +description:
> +  This binding describes the Cadence SD0801 PHY (also known as Torrent PHY)
> +  hardware included with the Cadence MHDP DisplayPort controller.
> +
> +maintainers:
> +  - Swapnil Jakhade <sjakhade@cadence.com>
> +  - Yuti Amonkar <yamonkar@cadence.com>
> +
> +properties:
> +  compatible:
> +    const: cdns,torrent-phy
> +
> +  clocks:
> +    maxItems: 1
> +    description:
> +      PHY reference clock. Must contain an entry in clock-names.
> +
> +  clock-names:
> +    const: refclk
> +
> +  reg:
> +    minItems: 1
> +    maxItems: 2
> +    items:
> +      - description: Offset of the Torrent PHY configuration registers.
> +      - description: Offset of the DPTX PHY configuration registers.
> +
> +  reg-names:
> +    minItems: 1
> +    maxItems: 2
> +    items:
> +      - const: torrent_phy
> +      - const: dptx_phy
> +
> +  "#phy-cells":
> +    const: 0
> +
> +  num_lanes:

Given you don't care about compatibility, please make this 'num-lanes'.

> +    description:
> +      Number of DisplayPort lanes.
> +    allOf:
> +      - $ref: /schemas/types.yaml#/definitions/uint32
> +      - enum: [1, 2, 4]

If optional, then define a default.

> +
> +  max_bit_rate:

And this 'max-bit-rate-mbps'.

> +    description:
> +      Maximum DisplayPort link bit rate to use, in Mbps
> +    allOf:
> +      - $ref: /schemas/types.yaml#/definitions/uint32
> +      - enum: [2160, 2430, 2700, 3240, 4320, 5400, 8100]

default?

> +
> +required:
> +  - compatible
> +  - clocks
> +  - clock-names
> +  - reg
> +  - reg-names
> +  - "#phy-cells"
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    dp_phy: phy@f0fb500000 {
> +          compatible = "cdns,torrent-phy";
> +          reg = <0xf0 0xfb500000 0x0 0x00100000>,
> +                <0xf0 0xfb030a00 0x0 0x00000040>;
> +          reg-names = "torrent_phy", "dptx_phy";
> +          num_lanes = <4>;
> +          max_bit_rate = <8100>;
> +          #phy-cells = <0>;
> +          clocks = <&ref_clk>;
> +          clock-names = "refclk";
> +    };
> +...
> -- 
> 2.4.5
> 

  reply	other threads:[~2020-01-27 16:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 10:45 [PATCH v3 00/14] PHY: Update Cadence Torrent PHY driver with reconfiguration Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 01/14] dt-bindings: phy: Convert Cadence MHDP PHY bindings to YAML Yuti Amonkar
2020-01-27 16:25   ` Rob Herring [this message]
2020-01-22 10:45 ` [PATCH v3 02/14] phy: cadence-dp: Rename to phy-cadence-torrent Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 03/14] phy: cadence-torrent: Adopt Torrent nomenclature Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 04/14] phy: cadence-torrent: Add wrapper for PHY register access Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 05/14] phy: cadence-torrent: Add wrapper for DPTX " Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 06/14] phy: cadence-torrent: Refactor code for reusability Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 07/14] phy: cadence-torrent: Add 19.2 MHz reference clock support Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 08/14] phy: cadence-torrent: Implement PHY configure APIs Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 09/14] phy: cadence-torrent: Use regmap to read and write Torrent PHY registers Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 10/14] phy: cadence-torrent: Use regmap to read and write DPTX " Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 11/14] dt-bindings: phy: phy-cadence-torrent: Add platform dependent compatible string Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 12/14] phy: cadence-torrent: Add platform dependent initialization structure Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 13/14] dt-bindings: phy: phy-cadence-torrent: Add subnode bindings Yuti Amonkar
2020-01-27 16:42   ` Rob Herring
2020-01-28 10:04     ` Jyri Sarha
2020-01-28 15:40       ` Rob Herring
2020-01-27 16:45   ` Rob Herring
2020-01-22 10:45 ` [PATCH v3 14/14] phy: cadence-torrent: Add support for " Yuti Amonkar

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=20200127162533.GA20343@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jsarha@ti.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime@cerno.tech \
    --cc=mparab@cadence.com \
    --cc=praneeth@ti.com \
    --cc=sjakhade@cadence.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=yamonkar@cadence.com \
    /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).