devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Kukjin Kim <kgene@kernel.org>, Maxime Ripard <mripard@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>, Inki Dae <inki.dae@samsung.com>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 4/6] dt-bindings: gpu: samsung-rotator: Add missing properties
Date: Mon, 14 Sep 2020 14:51:05 -0600	[thread overview]
Message-ID: <20200914205105.GA220369@bogus> (raw)
In-Reply-To: <20200903191438.12781-4-krzk@kernel.org>

On Thu, Sep 03, 2020 at 09:14:36PM +0200, Krzysztof Kozlowski wrote:
> Add common properties appearing in DTSes (iommus, power-domains) to fix
> dtbs_check warnings like:
> 
>   arch/arm/boot/dts/exynos4210-i9100.dt.yaml: rotator@12810000:
>     'iommus', 'power-domains' do not match any of the regexes: 'pinctrl-[0-9]+'
> 
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> 
> ---
> 
> Changes since v1:
> 1. Add properties instead of using unevaluated
> ---
>  Documentation/devicetree/bindings/gpu/samsung-rotator.yaml | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/gpu/samsung-rotator.yaml b/Documentation/devicetree/bindings/gpu/samsung-rotator.yaml
> index 665c6e3b31d3..f480174fe0d3 100644
> --- a/Documentation/devicetree/bindings/gpu/samsung-rotator.yaml
> +++ b/Documentation/devicetree/bindings/gpu/samsung-rotator.yaml
> @@ -22,6 +22,9 @@ properties:
>    interrupts:
>      maxItems: 1
>  
> +  iommus: true
> +  power-domains: true

These need to define how many. I assume 1, so 'maxItems: 1'.

> +
>    clocks:
>      maxItems: 1
>  
> -- 
> 2.17.1
> 

  reply	other threads:[~2020-09-14 20:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 19:14 [PATCH v2 1/6] dt-bindings: gpu: arm,mali-midgard: Add missing properties Krzysztof Kozlowski
2020-09-03 19:14 ` [PATCH v2 2/6] dt-bindings: gpu: arm,mali-utgard: " Krzysztof Kozlowski
2020-09-14 20:51   ` [PATCH v2 2/6] dt-bindings: gpu: arm, mali-utgard: " Rob Herring
2020-09-03 19:14 ` [PATCH v2 3/6] dt-bindings: gpu: arm,mali-utgard: Correct Maxime's email Krzysztof Kozlowski
2020-09-14 20:51   ` [PATCH v2 3/6] dt-bindings: gpu: arm, mali-utgard: " Rob Herring
2020-09-03 19:14 ` [PATCH v2 4/6] dt-bindings: gpu: samsung-rotator: Add missing properties Krzysztof Kozlowski
2020-09-14 20:51   ` Rob Herring [this message]
2020-09-03 19:14 ` [PATCH v2 5/6] ARM: dts: exynos: Align OPP table name with dt-schema Krzysztof Kozlowski
2020-09-16 17:12   ` Krzysztof Kozlowski
2020-09-03 19:14 ` [PATCH v2 6/6] arm64: " Krzysztof Kozlowski
2020-09-16 17:13   ` Krzysztof Kozlowski
2020-09-14 20:51 ` [PATCH v2 1/6] dt-bindings: gpu: arm, mali-midgard: Add missing properties 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=20200914205105.GA220369@bogus \
    --to=robh@kernel.org \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=inki.dae@samsung.com \
    --cc=kgene@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mripard@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).