From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux-usb@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: Multiple generic PHY instances for DWC3 USB IP
Date: Wed, 04 Apr 2018 11:00:54 +0300 [thread overview]
Message-ID: <87woxns8nd.fsf@linux.intel.com> (raw)
In-Reply-To: <CAK7LNATpFZYK-f4j7sJpur-u43bK1gsz_eS1wurTq7C+n6pHAw@mail.gmail.com>
Hi,
Masahiro Yamada <yamada.masahiro@socionext.com> writes:
>>> Each DWC3 instance is connected with
>>> multiple HS PHYs and multiple SS PHYs,
>>> depending on the number of ports.
>>
>> in that case, you shouldn't need dwc3 at all. A Host-only dwc3 is xHCI
>> compliant. If you really don't have the gadget block, there's no need
>> for you to use dwc3. Just use xhci-plat directly.
>
> Sorry, I was misunderstanding.
>
> Some of our SoCs support gadget,
> so we need to use the dwc3 driver.
fair enough. Now we need to figure out how to pass multiply PHYs to a
multi-port dwc3 instance.
Kishon, any ideas? How do you think DT should look like?
--
balbi
next prev parent reply other threads:[~2018-04-04 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 13:31 Multiple generic PHY instances for DWC3 USB IP Masahiro Yamada
2018-04-04 5:36 ` Felipe Balbi
2018-04-04 5:56 ` Masahiro Yamada
2018-04-04 6:04 ` Felipe Balbi
2018-04-04 7:31 ` Masahiro Yamada
2018-04-04 8:00 ` Felipe Balbi [this message]
2018-04-04 8:43 ` Arnd Bergmann
2018-04-04 10:33 ` Masahiro Yamada
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=87woxns8nd.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=kishon@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=mathias.nyman@linux.intel.com \
--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).