From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Taniya Das <tdas@codeaurora.org>
Cc: 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@kernel.org, robh+dt@kernel.org,
Taniya Das <tdas@codeaurora.org>
Subject: Re: [PATCH v3 3/6] clk: qcom: Add graphics clock controller driver for SC7180
Date: Sat, 04 Jan 2020 23:26:15 -0800 [thread overview]
Message-ID: <20200105072616.6A76D21775@mail.kernel.org> (raw)
In-Reply-To: <1577428714-17766-4-git-send-email-tdas@codeaurora.org>
Quoting Taniya Das (2019-12-26 22:38:31)
> Add support for the graphics clock controller found on SC7180
> based devices. This would allow graphics drivers to probe and
> control their clocks.
>
> Signed-off-by: Taniya Das <tdas@codeaurora.org>
> ---
Applied to clk-next
next prev parent reply other threads:[~2020-01-05 7:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 6:38 [PATCH v3 0/6] Add GPU & Video Clock controller driver for SC7180 Taniya Das
2019-12-27 6:38 ` [PATCH v3 1/6] dt-bindings: clock: Add YAML schemas for the QCOM GPUCC clock bindings Taniya Das
2020-01-04 0:33 ` Rob Herring
2020-01-05 7:26 ` Stephen Boyd
2019-12-27 6:38 ` [PATCH v3 2/6] dt-bindings: clock: Introduce QCOM Graphics " Taniya Das
2020-01-05 7:26 ` Stephen Boyd
2019-12-27 6:38 ` [PATCH v3 3/6] clk: qcom: Add graphics clock controller driver for SC7180 Taniya Das
2020-01-05 7:26 ` Stephen Boyd [this message]
2019-12-27 6:38 ` [PATCH v3 4/6] dt-bindings: clock: Add YAML schemas for the QCOM VIDEOCC clock bindings Taniya Das
2020-01-05 7:26 ` Stephen Boyd
2019-12-27 6:38 ` [PATCH v3 5/6] dt-bindings: clock: Introduce SC7180 QCOM Video " Taniya Das
2020-01-05 7:26 ` Stephen Boyd
2019-12-27 6:38 ` [PATCH v3 6/6] clk: qcom: Add video clock controller driver for SC7180 Taniya Das
2019-12-29 17:33 ` Stanimir Varbanov
2020-01-05 7:26 ` Stephen Boyd
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=20200105072616.6A76D21775@mail.kernel.org \
--to=sboyd@kernel.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=tdas@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 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.