From: Taniya Das <tdas@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
David Brown <david.brown@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@kernel.org>,
devicetree@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v4 3/5] dt-bindings: clock: Add YAML schemas for the QCOM MSS clock bindings
Date: Wed, 19 Feb 2020 09:35:28 +0530 [thread overview]
Message-ID: <6298769e-09bc-eb69-bf72-5aedd0e87f16@codeaurora.org> (raw)
In-Reply-To: <20200218230026.GA3778@bogus>
Hi Rob,
On 2/19/2020 4:30 AM, Rob Herring wrote:
> On Tue, 18 Feb 2020 23:45:31 +0530, Taniya Das wrote:
>> The Modem Subsystem clock provider have a bunch of generic properties
>> that are needed in a device tree. Add a YAML schemas for those.
>>
>> Signed-off-by: Taniya Das <tdas@codeaurora.org>
>> ---
>> .../devicetree/bindings/clock/qcom,sc7180-mss.yaml | 62 ++++++++++++++++++++++
>> 1 file changed, 62 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7180-mss.yaml
>>
>
> My bot found errors running 'make dt_binding_check' on your patch:
>
> Error: Documentation/devicetree/bindings/clock/qcom,sc7180-mss.example.dts:21.26-27 syntax error
> FATAL ERROR: Unable to parse input tree
> scripts/Makefile.lib:300: recipe for target 'Documentation/devicetree/bindings/clock/qcom,sc7180-mss.example.dt.yaml' failed
> make[1]: *** [Documentation/devicetree/bindings/clock/qcom,sc7180-mss.example.dt.yaml] Error 1
> Makefile:1263: recipe for target 'dt_binding_check' failed
> make: *** [dt_binding_check] Error 2
>
> See https://patchwork.ozlabs.org/patch/1240251
> Please check and re-submit.
>
I did see the same issue and then when I re-ordered by patches
dt-bindings: clock: Add support for Modem clocks in GCC (dependent) on
this binding patch, I no longer encountered the issue.
https://patchwork.kernel.org/patch/11389243/
Please let me know.
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation.
--
next prev parent reply other threads:[~2020-02-19 4:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 18:15 [PATCH v4 0/5] Add modem Clock controller (MSS CC) driver for SC7180 Taniya Das
2020-02-18 18:15 ` [PATCH v4 1/5] dt-bindings: clock: Add support for Modem clocks in GCC Taniya Das
2020-02-18 23:02 ` Rob Herring
2020-02-18 18:15 ` [PATCH v4 2/5] clk: qcom: gcc: Add support for modem " Taniya Das
2020-02-18 18:15 ` [PATCH v4 3/5] dt-bindings: clock: Add YAML schemas for the QCOM MSS clock bindings Taniya Das
2020-02-18 23:00 ` Rob Herring
2020-02-19 4:05 ` Taniya Das [this message]
2020-02-20 11:18 ` Sibi Sankar
2020-02-24 10:37 ` Taniya Das
2020-02-18 18:15 ` [PATCH v4 4/5] dt-bindings: clock: Introduce QCOM Modem " Taniya Das
2020-02-18 18:15 ` [PATCH v4 5/5] clk: qcom: Add modem clock controller driver for SC7180 Taniya Das
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=6298769e-09bc-eb69-bf72-5aedd0e87f16@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=agross@kernel.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@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).