Linux USB
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Elson Roy Serrao <quic_eserrao@quicinc.com>,
	Thinh.Nguyen@synopsys.com, stern@rowland.harvard.edu
Cc: gregkh@linuxfoundation.org, rogerq@kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	quic_wcheng@quicinc.com, quic_jackp@quicinc.com
Subject: Re: [PATCH v3 2/3] dt-bindings: usb: snps,dwc3: Add allow-rtsusp-on-u3 property
Date: Wed, 12 Jul 2023 07:47:10 +0200	[thread overview]
Message-ID: <9425ee08-f714-2833-6c94-a0f15cb608b5@kernel.org> (raw)
In-Reply-To: <20230711174320.24058-3-quic_eserrao@quicinc.com>

On 11/07/2023 19:43, Elson Roy Serrao wrote:
> This property allows dwc3 runtime suspend when bus suspend interrupt
> is received even with cable connected. This would allow the dwc3
> controller to enter low power mode during bus suspend scenario.
> 
> This property would particularly benefit dwc3 IPs where hibernation is
> not enabled and the dwc3 low power mode entry/exit is handled by the
> glue driver. The assumption here is that the platform using this dt
> property is capable of detecting resume events to bring the controller
> out of suspend.

v3 and still ignoring maintainers?

Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

You missed at least DT list (maybe more), so this won't be tested by
automated tooling. Performing review on untested code might be a waste
of time, thus I will skip this patch entirely till you follow the
process allowing the patch to be tested.

Please kindly resend and include all necessary To/Cc entries.


Best regards,
Krzysztof


  parent reply	other threads:[~2023-07-12  5:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 17:43 [PATCH v3 0/3] Support dwc3 runtime suspend during bus suspend Elson Roy Serrao
2023-07-11 17:43 ` [PATCH v3 1/3] usb: function: u_ether: Handle rx requests during suspend/resume Elson Roy Serrao
2023-07-11 17:43 ` [PATCH v3 2/3] dt-bindings: usb: snps,dwc3: Add allow-rtsusp-on-u3 property Elson Roy Serrao
2023-07-11 21:56   ` Thinh Nguyen
2023-07-11 22:38     ` Elson Serrao
2023-07-12 11:53     ` Roger Quadros
2023-07-12 22:34       ` Thinh Nguyen
2023-07-12  5:47   ` Krzysztof Kozlowski [this message]
2023-07-11 17:43 ` [PATCH v3 3/3] usb: dwc3: Modify runtime pm ops to handle bus suspend Elson Roy Serrao
2023-07-11 22:07   ` Thinh Nguyen
2023-07-11 22:51     ` Elson Serrao
2023-07-11 23:22       ` Elson Serrao
2023-07-12 13:46   ` Roger Quadros
2023-07-12 22:57     ` Elson Serrao
2023-07-13 12:56       ` Roger Quadros
2023-07-13 22:31         ` Elson Serrao
2023-07-14 12:23           ` Roger Quadros
2023-07-14 20:34             ` Elson Serrao
2023-07-11 21:58 ` [PATCH v3 0/3] Support dwc3 runtime suspend during " Thinh Nguyen
2023-07-12 12:16 ` Roger Quadros

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=9425ee08-f714-2833-6c94-a0f15cb608b5@kernel.org \
    --to=krzk@kernel.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_eserrao@quicinc.com \
    --cc=quic_jackp@quicinc.com \
    --cc=quic_wcheng@quicinc.com \
    --cc=rogerq@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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