linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Masami Hiramatsu <masami.hiramatsu@linaro.org>,
	Jassi Brar <jaswinder.singh@linaro.org>,
	Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Subject: [PATCH 0/2] reset: uniphier: add USB3 controller reset support
Date: Fri, 29 Jun 2018 17:11:29 +0900	[thread overview]
Message-ID: <1530259891-18822-1-git-send-email-hayashi.kunihiko@socionext.com> (raw)

This series add new USB3 reset control support for UniPhier SoCs.
This reset lines is included in USB3 glue layer.

Kunihiko Hayashi (2):
  dt-bindings: reset: uniphier: add USB3 controller reset support
  reset: uniphier: add USB3 controller reset control

 .../devicetree/bindings/reset/uniphier-reset.txt   |  45 +++++
 drivers/reset/Kconfig                              |  10 ++
 drivers/reset/Makefile                             |   1 +
 drivers/reset/reset-uniphier-usb3.c                | 183 +++++++++++++++++++++
 4 files changed, 239 insertions(+)
 create mode 100644 drivers/reset/reset-uniphier-usb3.c

-- 
2.7.4


             reply	other threads:[~2018-06-29  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  8:11 Kunihiko Hayashi [this message]
2018-06-29  8:11 ` [PATCH 1/2] dt-bindings: reset: uniphier: add USB3 controller reset support Kunihiko Hayashi
2018-06-29  9:57   ` Philipp Zabel
2018-07-03 23:37   ` Rob Herring
2018-07-04  1:09     ` Kunihiko Hayashi
2018-06-29  8:11 ` [PATCH 2/2] reset: uniphier: add USB3 controller reset control Kunihiko Hayashi
2018-06-29  9:51   ` kbuild test robot
2018-06-29  9:55   ` Philipp Zabel
2018-06-29 10:53     ` Kunihiko Hayashi

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=1530259891-18822-1-git-send-email-hayashi.kunihiko@socionext.com \
    --to=hayashi.kunihiko@socionext.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masami.hiramatsu@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).