From: Lars Melin <larsm17@gmail.com>
To: Pawel Laszczak <pawell@cadence.com>, devicetree@vger.kernel.org
Cc: gregkh@linuxfoundation.org, felipe.balbi@linux.intel.com,
mark.rutland@arm.com, linux-usb@vger.kernel.org,
hdegoede@redhat.com, heikki.krogerus@linux.intel.com,
andy.shevchenko@gmail.com, robh+dt@kernel.org, rogerq@ti.com,
linux-kernel@vger.kernel.org, jbergsagel@ti.com, nsekhar@ti.com,
nm@ti.com, sureshp@cadence.com, peter.chen@nxp.com,
kurahul@cadence.com
Subject: Re: [PATCH v6 5/6] usb:cdns3 Add Cadence USB3 DRD Driver
Date: Wed, 10 Apr 2019 17:40:06 +0700 [thread overview]
Message-ID: <f04e98f8-e1d4-55a7-d714-9770961e5fc9@gmail.com> (raw)
In-Reply-To: <1554882504-9010-6-git-send-email-pawell@cadence.com>
On 4/10/2019 14:48, Pawel Laszczak wrote:
> The Cadence USBSS DRD Driver is a highly configurable IP Core which
> can be instantiated as Dual-Role Device (DRD), Peripheral Only and
> Host Only (XHCI)configurations.
The hardware is an IP core, the driver is not.
rgds
Lars
next prev parent reply other threads:[~2019-04-10 10:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 7:48 [PATCH v6 0/6] Introduced new Cadence USBSS DRD Driver Pawel Laszczak
2019-04-10 7:48 ` [PATCH v6 1/6] dt-bindings: add binding for USBSS-DRD controller Pawel Laszczak
2019-04-26 9:21 ` Roger Quadros
2019-04-26 10:39 ` Pawel Laszczak
2019-04-10 7:48 ` [PATCH v6 2/6] usb:common Separated decoding functions from dwc3 driver Pawel Laszczak
2019-04-10 7:48 ` [PATCH v6 3/6] usb:common Patch simplify usb_decode_set_clear_feature function Pawel Laszczak
2019-04-10 7:48 ` [PATCH v6 4/6] usb:common Simplify usb_decode_get_set_descriptor function Pawel Laszczak
2019-04-10 7:48 ` [PATCH v6 5/6] usb:cdns3 Add Cadence USB3 DRD Driver Pawel Laszczak
2019-04-10 10:40 ` Lars Melin [this message]
2019-06-04 7:46 ` Sekhar Nori
2019-06-04 8:17 ` Pawel Laszczak
2019-06-04 8:24 ` Sekhar Nori
2019-06-04 8:38 ` Pawel Laszczak
2019-04-10 7:48 ` [PATCH v6 6/6] usb:cdns3 Fix for stuck packets in on-chip OUT buffer Pawel Laszczak
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=f04e98f8-e1d4-55a7-d714-9770961e5fc9@gmail.com \
--to=larsm17@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jbergsagel@ti.com \
--cc=kurahul@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=pawell@cadence.com \
--cc=peter.chen@nxp.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=sureshp@cadence.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).