All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thinh Nguyen <thinh.nguyen@synopsys.com>
To: Felipe Balbi <balbi@kernel.org>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: John Youn <john.youn@synopsys.com>
Subject: [PATCH v2 0/4] usb: dwc3: Introduce refclk lpm
Date: Fri, 7 Dec 2018 18:27:23 -0800	[thread overview]
Message-ID: <cover.1544235317.git.thinhn@synopsys.com> (raw)

This patch series introduce a new feature in DWC_usb31 with more
aggressive low power management using reference clock.

Changes in v2:
- Revise commit messages to correctly describe the feature
- Split previous patch "usb: dwc3: Add reference clock properties" to 2
  separate patches
- Remove reference clock period validation in since DWC_usb3
  can support more periods than DWC_usb31
- Rename property snps,enable-refclk-lpm to snps,enable-refclk-sof


Thinh Nguyen (4):
  usb: dwc3: Add property snps,refclk-period-ns
  usb: dwc3: Set the reference clock period
  usb: dwc3: Add property snps,enable-refclk-sof
  usb: dwc3: Enable frame number tracking based on reference clock

 Documentation/devicetree/bindings/usb/dwc3.txt |  5 +++
 drivers/usb/dwc3/core.c                        | 60 ++++++++++++++++++++++++++
 drivers/usb/dwc3/core.h                        | 16 +++++++
 3 files changed, 81 insertions(+)

-- 
2.11.0

             reply	other threads:[~2018-12-08  2:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08  2:27 Thinh Nguyen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-08  2:27 [v2,1/4] usb: dwc3: Add property snps,refclk-period-ns Thinh Nguyen
2018-12-08  2:27 ` [PATCH v2 1/4] " Thinh Nguyen
2018-12-08  2:27 [v2,3/4] usb: dwc3: Add property snps,enable-refclk-sof Thinh Nguyen
2018-12-08  2:27 ` [PATCH v2 3/4] " Thinh Nguyen
2018-12-18 16:38 [v2,1/4] usb: dwc3: Add property snps,refclk-period-ns Rob Herring
2018-12-18 16:38 ` [PATCH v2 1/4] " Rob Herring
2018-12-18 16:41 [v2,3/4] usb: dwc3: Add property snps,enable-refclk-sof Rob Herring
2018-12-18 16:41 ` [PATCH v2 3/4] " Rob Herring
2018-12-19  0:19 [v2,3/4] " Thinh Nguyen
2018-12-19  0:19 ` [PATCH v2 3/4] " Thinh Nguyen
2018-12-19  0:22 [v2,1/4] usb: dwc3: Add property snps,refclk-period-ns Thinh Nguyen
2018-12-19  0:22 ` [PATCH v2 1/4] " Thinh Nguyen
2018-12-19 13:18 [v2,1/4] " Rob Herring
2018-12-19 13:18 ` [PATCH v2 1/4] " Rob Herring
2018-12-19 21:31 [v2,1/4] " Thinh Nguyen
2018-12-19 21:31 ` [PATCH v2 1/4] " Thinh Nguyen
2018-12-20  6:48 [v2,1/4] " Felipe Balbi
2018-12-20  6:48 ` [PATCH v2 1/4] " Felipe Balbi
2018-12-20  6:52 [v2,3/4] usb: dwc3: Add property snps,enable-refclk-sof Felipe Balbi
2018-12-20  6:52 ` [PATCH v2 3/4] " Felipe Balbi
2018-12-20 15:19 [v2,3/4] " Rob Herring
2018-12-20 15:19 ` [PATCH v2 3/4] " Rob Herring
2018-12-21  0:21 [v2,1/4] usb: dwc3: Add property snps,refclk-period-ns Thinh Nguyen
2018-12-21  0:21 ` [PATCH v2 1/4] " Thinh Nguyen
2018-12-21 17:11 [v2,1/4] " Rob Herring
2018-12-21 17:11 ` [PATCH v2 1/4] " Rob Herring
2018-12-21 19:30 [v2,1/4] " Thinh Nguyen
2018-12-21 19:30 ` [PATCH v2 1/4] " Thinh Nguyen

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=cover.1544235317.git.thinhn@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=balbi@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=john.youn@synopsys.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.