mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sriram Dash <quic_sriramd@quicinc.com>,
	andersson@kernel.org, konrad.dybcio@linaro.org, vkoul@kernel.org,
	kishon@kernel.org, robh@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	gregkh@linuxfoundation.org, quic_wcheng@quicinc.com,
	Thinh.Nguyen@synopsys.com, p.zabel@pengutronix.de,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, quic_psodagud@quicinc.com,
	quic_nkela@quicinc.com, manivannan.sadhasivam@linaro.org,
	ulf.hansson@linaro.org, sudeep.holla@arm.com,
	quic_shazhuss@quicinc.com
Subject: Re: [RFC 1/3] dt-bindings: usb: qcom,dwc3: Add support for multiple power-domains
Date: Tue, 5 Mar 2024 18:07:29 +0100	[thread overview]
Message-ID: <86371fc0-ef49-4dc9-b98c-7c5131cd1227@linaro.org> (raw)
In-Reply-To: <1709657858-8563-2-git-send-email-quic_sriramd@quicinc.com>

On 05/03/2024 17:57, Sriram Dash wrote:
> Some target systems allow multiple resources to be managed by firmware.
> On these targets, tasks related to clocks, regulators, resets, and
> interconnects can be delegated to the firmware, while the remaining
> responsibilities are handled by Linux.
> 
> To support the management of partial resources in Linux and leave the rest
> to firmware, multiple power domains are introduced. Each power domain can
> manage one or more resources, depending on the specific use case.
> 
> These power domains handle SCMI calls to the firmware, enabling the
> activation and deactivation of firmware-managed resources.
> 
> Signed-off-by: Sriram Dash <quic_sriramd@quicinc.com>
> ---
>  .../phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml        | 74 ++++++++++++++++------
>  .../bindings/phy/qcom,usb-snps-femto-v2.yaml       | 49 ++++++++++++--
>  .../devicetree/bindings/usb/qcom,dwc3.yaml         | 37 ++++++++++-
>  3 files changed, 130 insertions(+), 30 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> index 1e2d4dd..53b9ba9 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> @@ -44,7 +44,32 @@ properties:
>      maxItems: 5
>  
>    power-domains:
> -    maxItems: 1
> +    description: specifies a phandle to PM domain provider node

Please drop all redundant descriptions. Adding them is not even related
to this patch.

> +    minItems: 1
> +    maxItems: 2
> +
> +  power-domain-names:
> +    description:
> +      A list of power domain name strings sorted in the same order as the
> +      power-domains property.
> +
> +      For platforms where some resource are firmware managed, the name
> +      corresponding to the index of an SCMI domain provider can be
> +      "usb_core" or "usb_transfer".
> +    items:
> +      - const: usb_core
> +      - const: usb_transfer

How is this related to fw-managed? I fail to see it. Don't mix
independent problems in one patch.

> +
> +  qmp,fw-managed:

Please do not upstream vendor code directly, but perform basic
adjustment to upstream Linux kernel. There is no such company as gmp.

Run this first through your internal review process.

> +    description:
> +      Some targets allow multiple resources to be managed by firmware.

You miss clear mapping between compatibles and this property - allOf
restricting it to specific SoCs.

Is this different property than qcom,controlled-remotely?

Best regards,
Krzysztof


  reply	other threads:[~2024-03-05 17:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 16:57 [RFC 0/3] Enable firmware-managed USB resources on Qcom targets Sriram Dash
2024-03-05 16:57 ` [RFC 1/3] dt-bindings: usb: qcom,dwc3: Add support for multiple power-domains Sriram Dash
2024-03-05 17:07   ` Krzysztof Kozlowski [this message]
2024-03-05 18:03     ` Sriram Dash
2024-03-06  7:03       ` Krzysztof Kozlowski
2024-03-06  7:33         ` Krishna Kurapati PSSNV
2024-03-06 15:49           ` Sriram Dash
2024-03-05 19:03   ` Dmitry Baryshkov
2024-03-06 15:51     ` Sriram Dash
2024-03-06 19:51       ` Dmitry Baryshkov
2024-03-05 16:57 ` [RFC 2/3] USB: dwc3: qcom: Add support for firmware managed resources Sriram Dash
2024-03-05 19:22   ` Bjorn Andersson
2024-03-06 16:21     ` Sriram Dash
2024-03-06  8:45   ` Dmitry Baryshkov
2024-03-06 16:52     ` Sriram Dash
2024-03-06 19:05       ` Dmitry Baryshkov
2024-03-05 16:57 ` [RFC 3/3] arm64: dts: qcom: sa8775p-ride: Enable " Sriram Dash
2024-03-05 17:08   ` Krzysztof Kozlowski
2024-03-05 18:03     ` Sriram Dash
2024-03-05 18:25       ` Sriram Dash
2024-03-05 21:07         ` Konrad Dybcio
2024-03-06 16:03           ` Sriram Dash
2024-03-05 18:47       ` Bjorn Andersson
2024-03-06 15:54         ` Sriram Dash
2024-03-05 17:12 ` [RFC 0/3] Enable firmware-managed USB resources on Qcom targets Krzysztof Kozlowski
2024-03-05 18:04   ` Sriram Dash
2024-03-06  7:04     ` Krzysztof Kozlowski
2024-03-06 16:00       ` Sriram Dash
2024-03-05 21:09 ` Konrad Dybcio
2024-03-06 16:03   ` Sriram Dash
2024-03-12 15:56 ` Trilok Soni
2024-03-19 15:38 ` Sudeep Holla

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=86371fc0-ef49-4dc9-b98c-7c5131cd1227@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=quic_nkela@quicinc.com \
    --cc=quic_psodagud@quicinc.com \
    --cc=quic_shazhuss@quicinc.com \
    --cc=quic_sriramd@quicinc.com \
    --cc=quic_wcheng@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=ulf.hansson@linaro.org \
    --cc=vkoul@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

all inboxes | Powered by JetHome®