From: Rob Herring <robh@kernel.org>
To: Govind Singh <govinds@codeaurora.org>
Cc: bjorn.andersson@linaro.org, linux-remoteproc@vger.kernel.org,
sricharan@codeaurora.org, sibis@codeaurora.org,
linux-arm-msm@vger.kernel.org, andy.gross@linaro.org,
david.brown@linaro.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: clock: qcom: Add QCOM WCSS GCC clock bindings
Date: Wed, 17 Oct 2018 15:02:11 -0500 [thread overview]
Message-ID: <20181017200211.GA17394@bogus> (raw)
In-Reply-To: <1539337244-9505-2-git-send-email-govinds@codeaurora.org>
On Fri, 12 Oct 2018 15:10:39 +0530, Govind Singh wrote:
> Add device tree bindings for WiFi QDSP gcc clock controls found in
> QCS404 soc.
>
> Signed-off-by: Govind Singh <govinds@codeaurora.org>
> ---
> include/dt-bindings/clock/qcom,gcc-qcs404.h | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-10-17 20:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 9:40 [PATCH v2 0/6] Add non PAS wcss Q6 support for QCS404 Govind Singh
2018-10-12 9:40 ` [PATCH v2 1/6] dt-bindings: clock: qcom: Add QCOM WCSS GCC clock bindings Govind Singh
2018-10-17 20:02 ` Rob Herring [this message]
2018-10-12 9:40 ` [PATCH v2 2/6] clk: qcom: Add WCSS gcc clock control for QCS404 Govind Singh
2018-10-16 1:01 ` Stephen Boyd
2018-12-15 17:43 ` Govind Singh
2018-10-12 9:40 ` [PATCH v2 3/6] dt-bindings: clock: qcom: Introduce QCOM WCSS Q6DSP clock bindings Govind Singh
2018-10-17 20:05 ` Rob Herring
2018-10-12 9:40 ` [PATCH v2 4/6] clk: qcom: Add WCSS Q6DSP clock controller for QCS404 Govind Singh
2018-10-16 1:00 ` Stephen Boyd
2018-12-15 17:50 ` Govind Singh
2018-10-12 9:40 ` [PATCH v2 5/6] remoteproc: qcom: wcss: populate hardcoded param using driver data Govind Singh
2018-10-12 9:40 ` [PATCH v2 6/6] remoteproc: qcom: wcss: Add non pas wcss Q6 support for QCS404 Govind Singh
2018-10-17 20:08 ` Rob Herring
2018-12-06 16:48 ` Bjorn Andersson
2018-12-15 18:00 ` Govind Singh
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=20181017200211.GA17394@bogus \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=govinds@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=sibis@codeaurora.org \
--cc=sricharan@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).