From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Taniya Das <tdas@codeaurora.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: clock: qcom,videocc: Add SM8350
Date: Thu, 13 Apr 2023 12:02:20 -0700 [thread overview]
Message-ID: <cbb856f4f7e25b1267c902757e159322.sboyd@kernel.org> (raw)
In-Reply-To: <20230413-topic-lahaina_vidcc-v1-1-134f9b22a5b3@linaro.org>
Quoting Konrad Dybcio (2023-04-13 11:44:58)
> SM8350, like most recent higher-end chips has a separate clock
> controller block just for the Venus IP. Document it.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
> .../devicetree/bindings/clock/qcom,videocc.yaml | 29 +++++++++++++++++-
> include/dt-bindings/clock/qcom,sm8350-videocc.h | 35 ++++++++++++++++++++++
> include/dt-bindings/reset/qcom,sm8350-videocc.h | 18 +++++++++++
Is there any reason to have two files?
next prev parent reply other threads:[~2023-04-13 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 18:44 [PATCH 0/2] SM8350 VIDEOCC Konrad Dybcio
2023-04-13 18:44 ` [PATCH 1/2] dt-bindings: clock: qcom,videocc: Add SM8350 Konrad Dybcio
2023-04-13 19:02 ` Stephen Boyd [this message]
2023-04-13 18:44 ` [PATCH 2/2] clk: qcom: Introduce SM8350 VIDEOCC Konrad Dybcio
2023-04-13 19:04 ` Stephen Boyd
2023-04-14 11:14 ` Konrad Dybcio
2023-04-14 3:27 ` Bjorn Andersson
2023-04-14 11:10 ` Konrad Dybcio
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=cbb856f4f7e25b1267c902757e159322.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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