From: ulli.kroll@googlemail.com (Hans Ulli Kroll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5 v3] usb: host: fotg2: add Gemini-specific handling
Date: Mon, 24 Apr 2017 19:06:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1704241853240.15211@T420s> (raw)
In-Reply-To: <20170421204058.6206-4-linus.walleij@linaro.org>
Hi Linus
On Fri, 21 Apr 2017, Linus Walleij wrote:
> The Cortina Systems Gemini has bolted on a PHY inside the
> silicon that can be handled by six bits in a MISC register in
> the system controller.
>
> If we are running on Gemini, look up a syscon regmap through
> a phandle and enable VBUS and optionally the Mini-B connector.
>
> If the device is flagged as "wakeup-source" using the standard
> DT bindings, we also enable this in the global controller for
> respective port.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> drivers/usb/host/Kconfig | 1 +
> drivers/usb/host/fotg210-hcd.c | 76 ++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 77 insertions(+)
>
please wait for a while, I'm working on some glue code to support both
host and device mode on FOTG.
Hans Ulli Kroll
next prev parent reply other threads:[~2017-04-24 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 20:40 [PATCH 1/5 v3] usb: host: add DT bindings for faraday fotg2 Linus Walleij
2017-04-21 20:40 ` [PATCH 2/5 v3] usb: host: fotg2: add device tree probing Linus Walleij
2017-04-21 20:40 ` [PATCH 3/5 v3] usb: host: fotg2: add silicon clock handling Linus Walleij
2017-04-21 20:40 ` [PATCH 4/5 v3] usb: host: fotg2: add Gemini-specific handling Linus Walleij
2017-04-24 17:06 ` Hans Ulli Kroll [this message]
2017-04-25 8:15 ` Linus Walleij
2017-04-21 20:40 ` [PATCH 5/5 v3] ARM: dts: Add the FOTG210 USB host to Gemini Linus Walleij
2017-04-22 2:52 ` kbuild test robot
2017-04-24 16:53 ` [PATCH 1/5 v3] usb: host: add DT bindings for faraday fotg2 Hans Ulli Kroll
2017-04-25 8:12 ` Linus Walleij
2017-04-25 19:07 ` Hans Ulli Kroll
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=alpine.LNX.2.00.1704241853240.15211@T420s \
--to=ulli.kroll@googlemail.com \
--cc=linux-arm-kernel@lists.infradead.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