From: Amit Nischal <anischal@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>,
Odelu Kukatla <okukatla@codeaurora.org>,
Taniya Das <tdas@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Amit Nischal <anischal@codeaurora.org>
Subject: [PATCH 0/2] Add QCOM camera clock controller driver
Date: Mon, 23 Jul 2018 16:56:31 +0530 [thread overview]
Message-ID: <1532345193-18108-1-git-send-email-anischal@codeaurora.org> (raw)
This patch series adds a driver and device tree documentation binding
for the camera clock controller on some Qualcomm Technologies, Inc, SoCs
such as SDM845. This would allow camera drivers to probe and control their
clocks.
Amit Nischal (2):
dt-bindings: clock: Introduce QCOM Camera clock bindings
clk: qcom: Add camera clock controller driver for SDM845
.../devicetree/bindings/clock/qcom,camcc.txt | 18 +
drivers/clk/qcom/Kconfig | 8 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/camcc-sdm845.c | 1736 ++++++++++++++++++++
include/dt-bindings/clock/qcom,camcc-sdm845.h | 116 ++
5 files changed, 1879 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/qcom,camcc.txt
create mode 100644 drivers/clk/qcom/camcc-sdm845.c
create mode 100644 include/dt-bindings/clock/qcom,camcc-sdm845.h
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2018-07-23 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 11:26 Amit Nischal [this message]
2018-07-23 11:26 ` [PATCH 1/2] dt-bindings: clock: Introduce QCOM Camera clock bindings Amit Nischal
2018-07-26 17:23 ` Stephen Boyd
2018-07-23 11:26 ` [PATCH 2/2] clk: qcom: Add camera clock controller driver for SDM845 Amit Nischal
2018-07-26 17:22 ` Stephen Boyd
2018-07-30 7:20 ` Amit Nischal
2018-08-02 16:57 ` 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=1532345193-18108-1-git-send-email-anischal@codeaurora.org \
--to=anischal@codeaurora.org \
--cc=andy.gross@linaro.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=okukatla@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=sboyd@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 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).