From: Bhupesh Sharma <bhupesh.sharma@linaro.org>
To: linux-arm-msm@vger.kernel.org
Cc: bhupesh.sharma@linaro.org, bhupesh.linux@gmail.com,
agross@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, sboyd@kernel.org,
tdas@codeaurora.org, mturquette@baylibre.com,
linux-clk@vger.kernel.org, robh+dt@kernel.org,
bjorn.andersson@linaro.org
Subject: [PATCH v3 3/6] clk: qcom: gcc: Add emac GDSC support for SM8150
Date: Thu, 3 Mar 2022 14:18:21 +0530 [thread overview]
Message-ID: <20220303084824.284946-4-bhupesh.sharma@linaro.org> (raw)
In-Reply-To: <20220303084824.284946-1-bhupesh.sharma@linaro.org>
Add the EMAC GDSC defines and driver structures for SM8150.
Cc: Stephen Boyd <sboyd@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
---
drivers/clk/qcom/gcc-sm8150.c | 10 ++++++++++
include/dt-bindings/clock/qcom,gcc-sm8150.h | 1 +
2 files changed, 11 insertions(+)
diff --git a/drivers/clk/qcom/gcc-sm8150.c b/drivers/clk/qcom/gcc-sm8150.c
index 85a431ac417b..08ba29e3a835 100644
--- a/drivers/clk/qcom/gcc-sm8150.c
+++ b/drivers/clk/qcom/gcc-sm8150.c
@@ -3448,6 +3448,15 @@ static struct clk_branch gcc_video_xo_clk = {
},
};
+static struct gdsc emac_gdsc = {
+ .gdscr = 0x6004,
+ .pd = {
+ .name = "emac_gdsc",
+ },
+ .pwrsts = PWRSTS_OFF_ON,
+ .flags = POLL_CFG_GDSCR,
+};
+
static struct gdsc usb30_prim_gdsc = {
.gdscr = 0xf004,
.pd = {
@@ -3714,6 +3723,7 @@ static const struct qcom_reset_map gcc_sm8150_resets[] = {
};
static struct gdsc *gcc_sm8150_gdscs[] = {
+ [EMAC_GDSC] = &emac_gdsc,
[USB30_PRIM_GDSC] = &usb30_prim_gdsc,
[USB30_SEC_GDSC] = &usb30_sec_gdsc,
};
diff --git a/include/dt-bindings/clock/qcom,gcc-sm8150.h b/include/dt-bindings/clock/qcom,gcc-sm8150.h
index 3e1a91876610..40596b9ded06 100644
--- a/include/dt-bindings/clock/qcom,gcc-sm8150.h
+++ b/include/dt-bindings/clock/qcom,gcc-sm8150.h
@@ -243,5 +243,6 @@
/* GCC GDSCRs */
#define USB30_PRIM_GDSC 4
#define USB30_SEC_GDSC 5
+#define EMAC_GDSC 6
#endif
--
2.35.1
next prev parent reply other threads:[~2022-03-03 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 8:48 [PATCH v3 0/6] Add ethernet support for Qualcomm SA8155p-ADP board Bhupesh Sharma
2022-03-03 8:48 ` [PATCH v3 1/6] dt-bindings: net: qcom,ethqos: Document SM8150 SoC compatible Bhupesh Sharma
2022-03-08 23:11 ` Bjorn Andersson
2022-03-03 8:48 ` [PATCH v3 2/6] clk: qcom: gcc: sm8150: Fix some identation issues Bhupesh Sharma
2022-03-03 8:48 ` Bhupesh Sharma [this message]
2022-03-03 10:33 ` [PATCH v3 3/6] clk: qcom: gcc: Add emac GDSC support for SM8150 Dmitry Baryshkov
2022-03-08 23:09 ` Bjorn Andersson
2022-03-08 23:12 ` Dmitry Baryshkov
2022-03-03 8:48 ` [PATCH v3 4/6] clk: qcom: gcc-sm8150: Use ALWAYS_ON flag as a workaround for emac gdsc Bhupesh Sharma
2022-03-03 8:48 ` [PATCH v3 5/6] arm64: dts: qcom: sm8150: add ethernet node Bhupesh Sharma
2022-03-03 10:34 ` Dmitry Baryshkov
2022-03-03 8:48 ` [PATCH v3 6/6] arm64: dts: qcom: sa8155p-adp: Enable " Bhupesh Sharma
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=20220303084824.284946-4-bhupesh.sharma@linaro.org \
--to=bhupesh.sharma@linaro.org \
--cc=agross@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bjorn.andersson@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=mturquette@baylibre.com \
--cc=robh+dt@kernel.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).