From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sriram Dash <sriram.dash@oss.qualcomm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: jack.pham@oss.qualcomm.com, faisal.hassan@oss.qualcomm.com,
krishna.kurapati@oss.qualcomm.com, andersson@kernel.org,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konradybcio@kernel.org>,
Shazad Hussain <shazad.hussain@oss.qualcomm.com>
Subject: Re: [PATCH 2/2] usb: dwc3: qcom: Support firmware-managed resource states for power management
Date: Thu, 27 Nov 2025 13:14:26 +0100 [thread overview]
Message-ID: <1df4fa7a-4b52-4816-bfa3-39afb5c7ad84@kernel.org> (raw)
In-Reply-To: <20251127-controller_scmi_upstream-v1-2-38bcca513c28@oss.qualcomm.com>
On 27/11/2025 11:31, Sriram Dash wrote:
> Add support for firmware-managed resource states in the
> Qualcomm DWC3 USB controller driver. On platforms
> like sa8255p, where controller resources are abstracted
> and managed collectively by firmware, the driver communicates
> power management transitions using dedicated resource state
> levels via dev_pm_opp_set_level().
>
> Macros are introduced to represent key lifecycle events:
> initialization, system and runtime suspend/resume, and exit.
> The driver sets the appropriate resource state during probe,
> remove, suspend, and resume operations, enabling bulk ON/OFF
> transitions of grouped resources according to the
> controller's operational state.
>
> Signed-off-by: Sriram Dash <sriram.dash@oss.qualcomm.com>
> Co-developed-by: Shazad Hussain <shazad.hussain@oss.qualcomm.com>
> Signed-off-by: Shazad Hussain <shazad.hussain@oss.qualcomm.com>
Messed order of tags. Please read carefully submitting patches, so you
understand what you certify before you actually certify.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-27 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 10:31 [PATCH 0/2] usb: dwc3: qcom: Add support for firmware-managed resources Sriram Dash
2025-11-27 10:31 ` [PATCH 1/2] dt-bindings: usb: qcom,snps-dwc3: " Sriram Dash
2025-11-27 11:29 ` Rob Herring (Arm)
2025-11-27 12:13 ` Krzysztof Kozlowski
2025-11-27 13:56 ` Krzysztof Kozlowski
2025-12-01 11:35 ` Sriram Dash
2025-11-27 10:31 ` [PATCH 2/2] usb: dwc3: qcom: Support firmware-managed resource states for power management Sriram Dash
2025-11-27 12:14 ` Krzysztof Kozlowski [this message]
2025-12-02 5:21 ` Bjorn Andersson
2025-12-02 6:37 ` Sriram Dash
2025-12-02 17:17 ` Bjorn Andersson
2025-12-09 8:48 ` Dan Carpenter
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=1df4fa7a-4b52-4816-bfa3-39afb5c7ad84@kernel.org \
--to=krzk@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=faisal.hassan@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack.pham@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krishna.kurapati@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_wcheng@quicinc.com \
--cc=robh@kernel.org \
--cc=shazad.hussain@oss.qualcomm.com \
--cc=sriram.dash@oss.qualcomm.com \
/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