From: Taniya Das <tdas@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: Andy Gross <andy.gross@linaro.org>,
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,
chandanu@codeaurora.org, Taniya Das <tdas@codeaurora.org>
Subject: [PATCH v1 0/2] Add support for display port clocks and clock ops
Date: Tue, 9 Oct 2018 19:27:45 +0530 [thread overview]
Message-ID: <1539093467-12123-1-git-send-email-tdas@codeaurora.org> (raw)
New display port clock ops supported for display port clocks.
Also add support for the display port related branches and RCGs.
Taniya Das (2):
clk: qcom: rcg2: Add support for display port clock ops
clk: qcom : dispcc: Add support for display port clocks
drivers/clk/qcom/clk-rcg.h | 1 +
drivers/clk/qcom/clk-rcg2.c | 86 +++++++++
drivers/clk/qcom/dispcc-sdm845.c | 232 +++++++++++++++++++++++++
include/dt-bindings/clock/qcom,dispcc-sdm845.h | 11 ++
4 files changed, 330 insertions(+)
--
Qualcomm INDIA, on behalf of Qualcomm Innovation Center, Inc.is a member
of the Code Aurora Forum, hosted by the Linux Foundation.
next reply other threads:[~2018-10-09 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 13:57 Taniya Das [this message]
2018-10-09 13:57 ` [PATCH v1 1/2] clk: qcom: rcg2: Add support for display port clock ops Taniya Das
2018-10-09 20:46 ` Stephen Boyd
2018-10-19 10:31 ` Taniya Das
2018-10-09 13:57 ` [PATCH v1 2/2] clk: qcom : dispcc: Add support for display port clocks Taniya Das
2018-10-09 20:34 ` Stephen Boyd
2018-10-19 10:34 ` Taniya Das
2018-10-28 10:34 ` Taniya Das
2018-10-29 18:43 ` Stephen Boyd
2018-10-30 6:01 ` Taniya Das
2018-10-30 16:33 ` Stephen Boyd
2018-11-01 5:02 ` Taniya Das
2018-11-06 17:08 ` Stephen Boyd
2018-11-12 3:41 ` chandanu
2019-02-02 0:05 ` chandanu
2019-07-15 22:59 ` 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=1539093467-12123-1-git-send-email-tdas@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=chandanu@codeaurora.org \
--cc=david.brown@linaro.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=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).