devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sharat Masetty <smasetty@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Doug Anderson <dianders@chromium.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Matthias Kaehlcke <mka@chromium.org>,
	dri-devel@freedesktop.org,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	freedreno <freedreno@lists.freedesktop.org>,
	saiprakash.ranjan@codeaurora.org
Subject: Re: [PATCH] dt-bindings: arm-smmu: update the list of clocks
Date: Mon, 2 Mar 2020 12:05:53 +0530	[thread overview]
Message-ID: <3f9ae835-5146-d5db-1caf-01ede5bc9a1f@codeaurora.org> (raw)
In-Reply-To: <CAL_JsqKVNENPZKbCy4FrGRO=D79hBL3keuE-U2tTwDVViCrdPQ@mail.gmail.com>


On 2/26/2020 8:03 PM, Rob Herring wrote:
> On Wed, Feb 26, 2020 at 5:17 AM Sharat Masetty <smasetty@codeaurora.org> wrote:
>>
>> On 2/21/2020 2:05 AM, Rob Herring wrote:
>>> On Thu, 20 Feb 2020 13:42:22 +0530, Sharat Masetty wrote:
>>>> This patch adds a clock definition needed for powering on the GPU TBUs
>>>> and the GPU TCU.
>>>>
>>>> Signed-off-by: Sharat Masetty <smasetty@codeaurora.org>
>>>> ---
>>>>    Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 3 +++
>>>>    1 file changed, 3 insertions(+)
>>>>
>>> My bot found errors running 'make dt_binding_check' on your patch:
>>>
>>> Documentation/devicetree/bindings/display/simple-framebuffer.example.dts:21.16-37.11: Warning (chosen_node_is_root): /example-0/chosen: chosen node must be at root node
>>> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/iommu/arm,smmu.example.dt.yaml: iommu@d00000: clock-names: ['bus', 'iface'] is too short
>>> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/iommu/arm,smmu.example.dt.yaml: iommu@d00000: clocks: [[4294967295, 123], [4294967295, 124]] is too short
>>>
>>> See https://patchwork.ozlabs.org/patch/1241297
>>> Please check and re-submit.
>> Hi Rob, These issues seem to be from the original code and not related
>> to my patch. Are these going to be blocking errors?
> There are no errors in this binding in mainline. You've added a 3rd
> clock when all the existing users have exactly 2 clocks.

Rob,

Adding something like the following seems to be solving the bot errors, 
but I am not certain if this is the right way to address this issue. Can 
you please comment?

    clock-names:
+    minItems: 2
+    maxItems: 3
      items:
        - const: bus
        - const: iface
+      - const: mem_iface_clk

    clocks:
+    minItems: 2
+    maxItems: 3
      items:
        - description: bus clock required for downstream bus access and 
for the
            smmu ptw
        - description: interface clock required to access smmu's registers
            through the TCU's programming interface.
+      - description: core clock required for the GPU SMMU TBUs and the 
GPU TCU.

>
> Rob
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-03-02  6:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  8:12 [PATCH] Update arm,smmu.yaml bindings doc Sharat Masetty
2020-02-20  8:12 ` [PATCH] dt-bindings: arm-smmu: update the list of clocks Sharat Masetty
2020-02-20 20:35   ` Rob Herring
2020-02-26 11:17     ` Sharat Masetty
2020-02-26 14:33       ` Rob Herring
2020-03-02  6:35         ` Sharat Masetty [this message]
2020-02-20 21:02   ` Matthias Kaehlcke
2020-02-26 13:55     ` Robin Murphy

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=3f9ae835-5146-d5db-1caf-01ede5bc9a1f@codeaurora.org \
    --to=smasetty@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=dri-devel@freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=robh@kernel.org \
    --cc=saiprakash.ranjan@codeaurora.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).