From: Rajendra Nayak <rnayak@codeaurora.org>
To: Amit Kucheria <amit.kucheria@linaro.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
bjorn.andersson@linaro.org, sibis@codeaurora.org,
swboyd@chromium.org, dianders@chromium.org
Cc: devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: cpus: Add kryo468 compatible
Date: Thu, 19 Mar 2020 14:02:54 +0530 [thread overview]
Message-ID: <5bacd2ad-811f-103f-ac5c-fd91522df40d@codeaurora.org> (raw)
In-Reply-To: <cd0f3d35ca0fc2944fd97e030a28318ff82dd5c1.1584516925.git.amit.kucheria@linaro.org>
On 3/18/2020 2:38 PM, Amit Kucheria wrote:
> Kryo468 is found in sc7180, so add it to the list of cpu compatibles
>
> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org>
> ---
Reviewed-by: Rajendra Nayak <rnayak@codeaurora.org>
> Documentation/devicetree/bindings/arm/cpus.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml
> index 7a9c3ce2dbef..57408c773b4d 100644
> --- a/Documentation/devicetree/bindings/arm/cpus.yaml
> +++ b/Documentation/devicetree/bindings/arm/cpus.yaml
> @@ -156,6 +156,7 @@ properties:
> - qcom,krait
> - qcom,kryo
> - qcom,kryo385
> + - qcom,kryo468
> - qcom,kryo485
> - qcom,scorpion
>
>
--
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-03-19 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 9:08 [PATCH 1/2] dt-bindings: arm: cpus: Add kryo468 compatible Amit Kucheria
2020-03-18 9:08 ` [PATCH 2/2] arm64: dts: qcom: sc7180: Fix cpu compatible Amit Kucheria
2020-03-18 17:24 ` Stephen Boyd
2020-03-19 8:33 ` Rajendra Nayak
2020-03-18 17:24 ` [PATCH 1/2] dt-bindings: arm: cpus: Add kryo468 compatible Stephen Boyd
2020-03-19 8:32 ` Rajendra Nayak [this message]
2020-03-30 23:05 ` 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=5bacd2ad-811f-103f-ac5c-fd91522df40d@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=amit.kucheria@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sibis@codeaurora.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).