From: Rob Herring <robh@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] clk: qcom: mmcc-msm8996: Properly describe GPU_GX gdsc
Date: Wed, 29 Apr 2020 16:35:26 -0500 [thread overview]
Message-ID: <20200429213526.GA6644@bogus> (raw)
In-Reply-To: <20200417070044.1376212-3-bjorn.andersson@linaro.org>
On Fri, 17 Apr 2020 00:00:42 -0700, Bjorn Andersson wrote:
> The GPU_GX GDSC depends on both GPU GDSC being enabled and that the
> VDD_GX rail is powered, so update the description of the node to cover
> these requirements.
>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---
>
> Changes since v1:
> - vdd_gfx -> vdd-gfx
>
> Documentation/devicetree/bindings/clock/qcom,mmcc.yaml | 4 ++++
> drivers/clk/qcom/mmcc-msm8996.c | 2 ++
> 2 files changed, 6 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-04-29 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 7:00 [PATCH v2 0/4] clk: qcom: gdsc: Handle supply regulators Bjorn Andersson
2020-04-17 7:00 ` [PATCH v2 1/4] clk: qcom: gdsc: Handle GDSC regulator supplies Bjorn Andersson
2020-05-14 21:23 ` Stephen Boyd
2020-04-17 7:00 ` [PATCH v2 2/4] clk: qcom: mmcc-msm8996: Properly describe GPU_GX gdsc Bjorn Andersson
2020-04-29 21:35 ` Rob Herring [this message]
2020-05-14 21:24 ` Stephen Boyd
2020-04-17 7:00 ` [PATCH v2 3/4] arm64: dts: qcom: db820c: Add vdd_gfx and tie it into mmcc Bjorn Andersson
2020-04-17 7:00 ` [PATCH v2 4/4] arm64: dts: qcom: msm8996: Make GPU node control GPU_GX GDSC Bjorn Andersson
2020-05-14 17:11 ` [PATCH v2 0/4] clk: qcom: gdsc: Handle supply regulators Vinod Koul
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=20200429213526.GA6644@bogus \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@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=mturquette@baylibre.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.