From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Robert Marko <robimarko@gmail.com>,
agross@kernel.org, andersson@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
mturquette@baylibre.com, sboyd@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 2/3] clk: qcom: ipq6018: add USB GDSCs
Date: Thu, 26 Oct 2023 20:42:54 +0200 [thread overview]
Message-ID: <77314fe2-2936-4f89-a347-4eb288507c47@linaro.org> (raw)
In-Reply-To: <20231025104457.628109-2-robimarko@gmail.com>
On 10/25/23 12:44, Robert Marko wrote:
> IPQ6018 has GDSC-s for each of the USB ports, so lets define them as such
> and drop the curent code that is de-asserting the USB GDSC-s as part of
> the GCC probe.
>
> Signed-off-by: Robert Marko <robimarko@gmail.com>
> ---
Applying patches 1 and 3 without this one breaks usb, no?
Konrad
next prev parent reply other threads:[~2023-10-26 18:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 10:44 [PATCH 1/3] dt-bindings: clock: qcom: ipq6018: add USB GDSCs Robert Marko
2023-10-25 10:44 ` [PATCH 2/3] clk: " Robert Marko
2023-10-26 18:42 ` Konrad Dybcio [this message]
2023-10-26 18:45 ` Konrad Dybcio
2023-10-27 8:48 ` Robert Marko
2023-10-29 11:04 ` Robert Marko
2023-10-30 19:37 ` Konrad Dybcio
2023-10-30 20:37 ` Robert Marko
2023-10-30 21:12 ` Konrad Dybcio
2023-10-31 9:01 ` Robert Marko
2023-11-07 21:51 ` Konrad Dybcio
2023-11-11 11:28 ` Robert Marko
2023-11-13 11:58 ` Konrad Dybcio
2023-11-13 12:50 ` Robert Marko
2023-11-15 16:22 ` Konrad Dybcio
2023-11-28 12:25 ` Robert Marko
2023-11-01 7:57 ` Kathiravan Thirumoorthy
2023-10-25 10:44 ` [PATCH 3/3] arm64: dts: qcom: ipq6018: add USB power domains Robert Marko
2023-10-25 12:44 ` [PATCH 1/3] dt-bindings: clock: qcom: ipq6018: add USB GDSCs Krzysztof Kozlowski
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=77314fe2-2936-4f89-a347-4eb288507c47@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
--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