public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: TY Chang <tychang@realtek.com>
Cc: linux-realtek-soc@lists.infradead.org, afaerber@suse.de,
	linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7] dt-bindings: pinctrl: realtek: Add Realtek DHC SoC rtd1195 and rtd1295.
Date: Thu, 14 May 2020 08:24:39 -0500	[thread overview]
Message-ID: <20200514132439.GB23147@bogus> (raw)
In-Reply-To: <20200514092125.6875-5-tychang@realtek.com>

On Thu, May 14, 2020 at 05:21:22PM +0800, TY Chang wrote:
> Add compatible string for RTD1195 and RTD1295.
> 
> Signed-off-by: TY Chang <tychang@realtek.com>
> ---
>  .../bindings/pinctrl/realtek,rtd-pinctrl.yaml | 59 +++++++++++++++++++
>  1 file changed, 59 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/realtek,rtd-pinctrl.yaml
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/realtek,rtd-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/realtek,rtd-pinctrl.yaml
> new file mode 100644
> index 000000000000..5af5fc8fe633
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/realtek,rtd-pinctrl.yaml
> @@ -0,0 +1,59 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/realtek,rtd-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Realtek DHC pin control
> +
> +maintainers:
> +  - Andreas Farber <afaerber@suse.de>
> +
> +properties:
> +  compatible:
> +    enum:
> +      - realtek,rtd1195-iso-pinctrl
> +      - realtek,rtd1195-crt-pinctrl
> +      - realtek,rtd1295-iso-pinctrl
> +      - realtek,rtd1295-sb2-pinctrl
> +      - realtek,rtd1295-disp-pinctrl
> +      - realtek,rtd1295-cr-pinctrl
> +  reg:
> +    maxItems: 1
> +
> +required:
> +  - compatible
> +  - reg
> +
> +examples:
> +  - |
> +    iso_pinctrl: pinctrl@300 {
> +        compatible = "realtek,rtd1195-iso-pinctrl";
> +        reg = <0x300 0x14>;

Aren't there child nodes with pin settings? They need to be documented.

> +    }
> +  - |
> +    crt_pinctrl: pinctrl@300 {
> +        compatible = "realtek,rtd1195-crt-pinctrl";
> +        reg = <0x300 0x78>;
> +    }
> +  - |
> +    iso_pinctrl: pinctrl@300 {
> +        compatible = "realtek,rtd1295-iso-pinctrl";
> +        reg = <0x300 0x24>;
> +    }
> +  - |
> +    sb2_pinctrl: pinctrl@900 {
> +        compatible = "realtek,rtd1295-sb2-pinctrl";
> +        reg = <0x900 0x100>;
> +    }
> +  - |
> +    disp_pinctrl: pinctrl@4d000 {
> +        compatible = "realtek,rtd1295-disp-pinctrl";
> +        reg = <0x4d000 0x100>;
> +    };
> +  - |
> +    cr_pinctrl: pinctrl@12600 {
> +        compatible = "realtek,rtd1295-cr-pinctrl";
> +        reg = <0x12600 0x100>;
> +    };
> +
> -- 
> 2.26.2
> 

  parent reply	other threads:[~2020-05-14 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14  9:21 [PATCH 0/7] pinctrl: update realtek DHC pinctrl driver TY Chang
2020-05-14  9:21 ` [PATCH 1/7] pinctrl: realtek: rtd1295: Add missed pins TY Chang
2020-05-14  9:21 ` [PATCH 2/7] pinctrl: realtek: rtd1295: Add pin configs TY Chang
2020-05-14  9:21 ` [PATCH 3/7] pinctrl: realtek: rtd1195: Add missed pins and " TY Chang
2020-05-14  9:21 ` [PATCH 4/7] dt-bindings: pinctrl: realtek: Add Realtek DHC SoC rtd1195 and rtd1295 TY Chang
2020-05-14 13:08   ` Rob Herring
2020-05-14 13:24   ` Rob Herring [this message]
2020-05-14  9:21 ` [PATCH 5/7] pinctrl: realtek: DHC: Fix pinctrl driver coding style according to checkpatch.pl TY Chang
2020-05-14  9:21 ` [PATCH 6/7] pinctrl: realtek: DHC: Move pinctrl drivers to realtek directory and rename TY Chang
2020-05-14  9:21 ` [PATCH 7/7] pinctrl: realtek: DHC: Add suspend/resume callback function TY Chang

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=20200514132439.GB23147@bogus \
    --to=robh@kernel.org \
    --cc=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-realtek-soc@lists.infradead.org \
    --cc=tychang@realtek.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