From: Felipe Balbi <balbi@kernel.org>
To: Artur Petrosyan <Arthur.Petrosyan@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
linux-usb@vger.kernel.org
Cc: John Youn <John.Youn@synopsys.com>,
Artur Petrosyan <Arthur.Petrosyan@synopsys.com>
Subject: Re: [PATCH v2 01/15] usb: dwc2: Fix/update enter/exit partial power down.
Date: Tue, 27 Oct 2020 10:21:23 +0200 [thread overview]
Message-ID: <87d014dqpo.fsf@kernel.org> (raw)
In-Reply-To: <20201011135059.76B73A005E@mailhost.synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 2032 bytes --]
Hi Arthur,
before I review your series, there are few things I'd like to point out:
1. A single patch should do one thing and one thing only
2. Every single patch should compile and work on its own
3. When sending a series, remember to include a cover letter
4. When sending a series, you can rely on git to produce a thread with a
cover letter
git format-patch -o series --cover-letter HEAD~15..
5. Remember to run checkpatch on every patch
6. Please, read https://www.kernel.org/doc/html/latest/process/submit-checklist.html
Artur Petrosyan <Arthur.Petrosyan@synopsys.com> writes:
> - Updated entering and exiting partial power down function
> flow. Before there was a lot of confusions with core
> entering to partial power down in device or host mode.
>
> - Added "rem_wakeup" for host exiting from Partial Power
> Down mode from host remote wakeup flow. According to
> programming guide in host mode, port power must be
> turned on when wakeup is detected.
>
> - Added "in_ppd" flag to indicate the core state after
> entering into Partial Power Down mode.
>
> - Moved setting of lx_state into partial power down
> specific functions.
>
> - Added dev_dbg() messages when entering and exiting from
> partial power down.
>
> - During Partial Power Down exit rely on backuped value of
> "GOTGCTL_CURMODE_HOST" to determine the mode of core
> before entering to PPD.
>
> - Set missing "DCTL_PWRONPRGDONE" bit when exiting device
> partial power down according to programming guide.
>
> - Added missing restore of DCFG register in device mode
> according to programming guide.
From a quick read, it seems like each of these topics deserve a patch of
its own. Could you break this down into smaller patches? Also, you have
colleagues who have been dealing with the community for a long time,
perhaps ask them to do an internal round of review before submitting?
That may help you get your patches merged in a timely manner.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
next parent reply other threads:[~2020-10-27 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201011135059.76B73A005E@mailhost.synopsys.com>
2020-10-27 8:21 ` Felipe Balbi [this message]
2020-10-27 10:26 ` [PATCH v2 01/15] usb: dwc2: Fix/update enter/exit partial power down Artur Petrosyan
2020-10-27 11:01 ` Felipe Balbi
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=87d014dqpo.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=Arthur.Petrosyan@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.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;
as well as URLs for NNTP newsgroup(s).