devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Andy Gross <agross@kernel.org>,
	Stephen Boyd <swboyd@chromium.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Rajendra Nayak <rnayak@codeaurora.org>,
	Rishabh Bhatnagar <rishabhb@codeaurora.org>,
	Doug Anderson <dianders@chromium.org>,
	linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCHv2 0/3] Add LLCC support for SC7180 SoC
Date: Thu, 24 Oct 2019 16:30:21 +0530	[thread overview]
Message-ID: <2fbab8bc38be37fba976d34b2f89e720@codeaurora.org> (raw)
In-Reply-To: <CAL_JsqLzRRQe8UZCxgXArVNhNry7PgMCthAR2aZNcm6CCEpvDA@mail.gmail.com>

Hi Rob,

On 2019-10-24 01:19, Rob Herring wrote:
> On Sun, Oct 20, 2019 at 10:32 PM Bjorn Andersson
> <bjorn.andersson@linaro.org> wrote:
>> 
>> On Sat 19 Oct 04:37 PDT 2019, Sai Prakash Ranjan wrote:
>> 
>> > LLCC behaviour is controlled by the configuration data set
>> > in the llcc-qcom driver, add the same for SC7180 SoC.
>> > Also convert the existing bindings to json-schema and add
>> > the compatible for SC7180 SoC.
>> >
>> 
>> Thanks for the patches and thanks for the review Stephen. Series 
>> applied
> 
> And they break dt_binding_check. Please fix.
> 

I did check this and think that the error log from dt_binding_check is 
not valid because it says cache-level is a required property [1], but 
there is no such property in LLCC bindings.

[1] - http://patchwork.ozlabs.org/patch/1179800/

-Sai

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member
of Code Aurora Forum, hosted by The Linux Foundation

  reply	other threads:[~2019-10-24 11:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-19 11:37 [PATCHv2 0/3] Add LLCC support for SC7180 SoC Sai Prakash Ranjan
2019-10-19 11:37 ` [PATCHv2 1/3] soc: qcom: llcc: Add configuration data for SC7180 Sai Prakash Ranjan
2019-10-20 18:20   ` Stephen Boyd
2019-10-19 11:37 ` [PATCHv2 2/3] dt-bindings: msm: Convert LLCC bindings to YAML Sai Prakash Ranjan
2019-10-20 18:20   ` Stephen Boyd
2019-10-19 11:37 ` [PATCHv2 3/3] dt-bindings: msm: Add LLCC for SC7180 Sai Prakash Ranjan
2019-10-20 18:20   ` Stephen Boyd
2019-10-21  3:32 ` [PATCHv2 0/3] Add LLCC support for SC7180 SoC Bjorn Andersson
2019-10-23 19:49   ` Rob Herring
2019-10-24 11:00     ` Sai Prakash Ranjan [this message]
2019-10-24 22:33       ` Rob Herring
2019-10-25  7:54         ` Sai Prakash Ranjan
2019-11-13 15:00           ` Sai Prakash Ranjan
2019-11-14 16:49             ` Stephen Boyd
2019-11-15 11:24               ` Sai Prakash Ranjan

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=2fbab8bc38be37fba976d34b2f89e720@codeaurora.org \
    --to=saiprakash.ranjan@codeaurora.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=linux-arm-msm-owner@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rishabhb@codeaurora.org \
    --cc=rnayak@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=swboyd@chromium.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).