usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/**
|
|
|
|
* gadget.c - DesignWare USB3 DRD Controller Gadget Framework Link
|
|
|
|
*
|
|
|
|
* Copyright (C) 2010-2011 Texas Instruments Incorporated - http://www.ti.com
|
|
|
|
*
|
|
|
|
* Authors: Felipe Balbi <balbi@ti.com>,
|
|
|
|
* Sebastian Andrzej Siewior <bigeasy@linutronix.de>
|
|
|
|
*
|
2013-06-30 14:15:11 +03:00
|
|
|
* This program is free software: you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License version 2 of
|
|
|
|
* the License as published by the Free Software Foundation.
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*
|
2013-06-30 14:15:11 +03:00
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/spinlock.h>
|
|
|
|
#include <linux/platform_device.h>
|
|
|
|
#include <linux/pm_runtime.h>
|
2013-06-05 16:15:01 +05:30
|
|
|
#include <linux/ratelimit.h>
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/io.h>
|
|
|
|
#include <linux/list.h>
|
|
|
|
#include <linux/dma-mapping.h>
|
|
|
|
|
|
|
|
#include <linux/usb/ch9.h>
|
2015-04-20 22:49:35 -07:00
|
|
|
#include <linux/usb/composite.h>
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
#include <linux/usb/gadget.h>
|
|
|
|
|
2014-08-19 16:37:22 -05:00
|
|
|
#include "debug.h"
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
#include "core.h"
|
|
|
|
#include "gadget.h"
|
2013-02-14 16:33:30 +05:30
|
|
|
#include "debug.h"
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
#include "io.h"
|
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
static void dwc3_gadget_wakeup_interrupt(struct dwc3 *dwc, bool remote_wakeup);
|
2014-05-13 15:45:00 +03:00
|
|
|
static int dwc3_gadget_wakeup_int(struct dwc3 *dwc);
|
2014-03-27 23:41:09 +02:00
|
|
|
|
2012-01-02 18:25:43 +02:00
|
|
|
/**
|
|
|
|
* dwc3_gadget_set_test_mode - Enables USB2 Test Modes
|
|
|
|
* @dwc: pointer to our context structure
|
|
|
|
* @mode: the mode to set (J, K SE0 NAK, Force Enable)
|
|
|
|
*
|
|
|
|
* Caller should take care of locking. This function will
|
|
|
|
* return 0 on success or -EINVAL if wrong Test Selector
|
|
|
|
* is passed
|
|
|
|
*/
|
|
|
|
int dwc3_gadget_set_test_mode(struct dwc3 *dwc, int mode)
|
|
|
|
{
|
|
|
|
u32 reg;
|
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
reg &= ~DWC3_DCTL_TSTCTRL_MASK;
|
|
|
|
|
|
|
|
switch (mode) {
|
|
|
|
case TEST_J:
|
|
|
|
case TEST_K:
|
|
|
|
case TEST_SE0_NAK:
|
|
|
|
case TEST_PACKET:
|
|
|
|
case TEST_FORCE_EN:
|
|
|
|
reg |= mode << 1;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-04-27 13:35:15 +03:00
|
|
|
/**
|
|
|
|
* dwc3_gadget_get_link_state - Gets current state of USB Link
|
|
|
|
* @dwc: pointer to our context structure
|
|
|
|
*
|
|
|
|
* Caller should take care of locking. This function will
|
|
|
|
* return the link state on success (>= 0) or -ETIMEDOUT.
|
|
|
|
*/
|
|
|
|
int dwc3_gadget_get_link_state(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
u32 reg;
|
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DSTS);
|
|
|
|
|
|
|
|
return DWC3_DSTS_USBLNKST(reg);
|
|
|
|
}
|
|
|
|
|
2012-01-02 18:55:57 +02:00
|
|
|
/**
|
|
|
|
* dwc3_gadget_set_link_state - Sets USB Link to a particular State
|
|
|
|
* @dwc: pointer to our context structure
|
|
|
|
* @state: the state to put link into
|
|
|
|
*
|
|
|
|
* Caller should take care of locking. This function will
|
2012-02-24 17:32:15 -08:00
|
|
|
* return 0 on success or -ETIMEDOUT.
|
2012-01-02 18:55:57 +02:00
|
|
|
*/
|
|
|
|
int dwc3_gadget_set_link_state(struct dwc3 *dwc, enum dwc3_link_state state)
|
|
|
|
{
|
2012-02-24 17:32:15 -08:00
|
|
|
int retries = 10000;
|
2012-01-02 18:55:57 +02:00
|
|
|
u32 reg;
|
|
|
|
|
2012-04-27 13:10:52 +03:00
|
|
|
/*
|
|
|
|
* Wait until device controller is ready. Only applies to 1.94a and
|
|
|
|
* later RTL.
|
|
|
|
*/
|
|
|
|
if (dwc->revision >= DWC3_REVISION_194A) {
|
|
|
|
while (--retries) {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DSTS);
|
|
|
|
if (reg & DWC3_DSTS_DCNRD)
|
|
|
|
udelay(5);
|
|
|
|
else
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (retries <= 0)
|
|
|
|
return -ETIMEDOUT;
|
|
|
|
}
|
|
|
|
|
2012-01-02 18:55:57 +02:00
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
reg &= ~DWC3_DCTL_ULSTCHNGREQ_MASK;
|
|
|
|
|
|
|
|
/* set requested state */
|
|
|
|
reg |= DWC3_DCTL_ULSTCHNGREQ(state);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
|
2012-04-27 13:10:52 +03:00
|
|
|
/*
|
|
|
|
* The following code is racy when called from dwc3_gadget_wakeup,
|
|
|
|
* and is not needed, at least on newer versions
|
|
|
|
*/
|
|
|
|
if (dwc->revision >= DWC3_REVISION_194A)
|
|
|
|
return 0;
|
|
|
|
|
2012-01-02 18:55:57 +02:00
|
|
|
/* wait for a change in DSTS */
|
2012-04-27 12:52:01 +03:00
|
|
|
retries = 10000;
|
2012-01-02 18:55:57 +02:00
|
|
|
while (--retries) {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DSTS);
|
|
|
|
|
|
|
|
if (DWC3_DSTS_USBLNKST(reg) == state)
|
|
|
|
return 0;
|
|
|
|
|
2012-02-24 17:32:15 -08:00
|
|
|
udelay(5);
|
2012-01-02 18:55:57 +02:00
|
|
|
}
|
|
|
|
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"link state change request timed out");
|
2012-01-02 18:55:57 +02:00
|
|
|
|
|
|
|
return -ETIMEDOUT;
|
|
|
|
}
|
|
|
|
|
2012-01-18 18:04:09 +02:00
|
|
|
/**
|
|
|
|
* dwc3_gadget_resize_tx_fifos - reallocate fifo spaces for current use-case
|
|
|
|
* @dwc: pointer to our context structure
|
|
|
|
*
|
|
|
|
* This function will a best effort FIFO allocation in order
|
|
|
|
* to improve FIFO usage and throughput, while still allowing
|
|
|
|
* us to enable as many endpoints as possible.
|
|
|
|
*
|
|
|
|
* Keep in mind that this operation will be highly dependent
|
|
|
|
* on the configured size for RAM1 - which contains TxFifo -,
|
|
|
|
* the amount of endpoints enabled on coreConsultant tool, and
|
|
|
|
* the width of the Master Bus.
|
|
|
|
*
|
|
|
|
* In the ideal world, we would always be able to satisfy the
|
|
|
|
* following equation:
|
|
|
|
*
|
|
|
|
* ((512 + 2 * MDWIDTH-Bytes) + (Number of IN Endpoints - 1) * \
|
|
|
|
* (3 * (1024 + MDWIDTH-Bytes) + MDWIDTH-Bytes)) / MDWIDTH-Bytes
|
|
|
|
*
|
|
|
|
* Unfortunately, due to many variables that's not always the case.
|
|
|
|
*/
|
|
|
|
int dwc3_gadget_resize_tx_fifos(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
int last_fifo_depth = 0;
|
|
|
|
int ram1_depth;
|
|
|
|
int fifo_size;
|
|
|
|
int mdwidth;
|
|
|
|
int num;
|
2015-04-20 22:49:35 -07:00
|
|
|
int num_eps;
|
2015-06-29 12:05:45 -07:00
|
|
|
int max_packet = 1024;
|
2015-04-20 22:49:35 -07:00
|
|
|
struct usb_composite_dev *cdev = get_gadget_data(&dwc->gadget);
|
2012-01-18 18:04:09 +02:00
|
|
|
|
2014-10-30 11:43:35 -07:00
|
|
|
if (!(cdev && cdev->config) || !dwc->needs_fifo_resize)
|
2012-01-18 18:04:09 +02:00
|
|
|
return 0;
|
|
|
|
|
2016-05-19 14:22:37 -07:00
|
|
|
num_eps = dwc->num_in_eps;
|
2012-01-18 18:04:09 +02:00
|
|
|
ram1_depth = DWC3_RAM1_DEPTH(dwc->hwparams.hwparams7);
|
|
|
|
mdwidth = DWC3_MDWIDTH(dwc->hwparams.hwparams0);
|
|
|
|
|
|
|
|
/* MDWIDTH is represented in bits, we need it in bytes */
|
|
|
|
mdwidth >>= 3;
|
2015-06-01 19:45:17 -07:00
|
|
|
last_fifo_depth = (dwc3_readl(dwc->regs, DWC3_GTXFIFOSIZ(0)) & 0xFFFF);
|
|
|
|
dev_dbg(dwc->dev, "%s: num eps:%d max_packet:%d last_fifo_depth:%04x\n",
|
|
|
|
__func__, num_eps, max_packet, last_fifo_depth);
|
|
|
|
|
|
|
|
/* Don't resize ep0IN TxFIFO, start with ep1IN only. */
|
|
|
|
for (num = 1; num < num_eps; num++) {
|
2014-03-26 10:31:44 -07:00
|
|
|
/* bit0 indicates direction; 1 means IN ep */
|
|
|
|
struct dwc3_ep *dep = dwc->eps[(num << 1) | 1];
|
2012-02-02 13:01:12 +02:00
|
|
|
int mult = 1;
|
2012-01-18 18:04:09 +02:00
|
|
|
int tmp;
|
|
|
|
|
2016-06-14 16:45:24 -07:00
|
|
|
tmp = max_packet + mdwidth;
|
|
|
|
/*
|
|
|
|
* Interfaces like MBIM or ECM is having multiple data
|
|
|
|
* interfaces. SET_CONFIG() happens before set_alt with
|
|
|
|
* data interface 1 which results into calling this API
|
|
|
|
* before GSI endpoint enabled. This results no txfifo
|
|
|
|
* resize with GSI endpoint causing low throughput. Hence
|
|
|
|
* use mult as 3 for GSI IN endpoint always irrespective
|
|
|
|
* USB speed.
|
|
|
|
*/
|
2016-09-21 12:21:01 -07:00
|
|
|
if (dep->endpoint.ep_type == EP_TYPE_GSI ||
|
|
|
|
dep->endpoint.endless)
|
2016-06-14 16:45:24 -07:00
|
|
|
mult = 3;
|
|
|
|
|
2015-04-20 22:49:35 -07:00
|
|
|
if (!(dep->flags & DWC3_EP_ENABLED)) {
|
2016-05-19 14:22:37 -07:00
|
|
|
dev_dbg(dwc->dev, "ep%dIn not enabled", num);
|
2015-04-20 22:49:35 -07:00
|
|
|
goto resize_fifo;
|
|
|
|
}
|
2012-01-18 18:04:09 +02:00
|
|
|
|
2015-04-20 22:49:35 -07:00
|
|
|
if (((dep->endpoint.maxburst > 1) &&
|
|
|
|
usb_endpoint_xfer_bulk(dep->endpoint.desc))
|
2012-03-12 20:25:24 +02:00
|
|
|
|| usb_endpoint_xfer_isoc(dep->endpoint.desc))
|
2012-02-02 13:01:12 +02:00
|
|
|
mult = 3;
|
2015-06-01 19:45:17 -07:00
|
|
|
|
2015-04-20 22:49:35 -07:00
|
|
|
resize_fifo:
|
2016-06-14 16:45:24 -07:00
|
|
|
tmp *= mult;
|
2012-01-18 18:04:09 +02:00
|
|
|
tmp += mdwidth;
|
|
|
|
|
|
|
|
fifo_size = DIV_ROUND_UP(tmp, mdwidth);
|
2012-02-02 13:01:12 +02:00
|
|
|
|
2012-01-18 18:04:09 +02:00
|
|
|
fifo_size |= (last_fifo_depth << 16);
|
|
|
|
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "%s: Fifo Addr %04x Size %d",
|
2012-01-18 18:04:09 +02:00
|
|
|
dep->name, last_fifo_depth, fifo_size & 0xffff);
|
|
|
|
|
2015-04-20 22:49:35 -07:00
|
|
|
last_fifo_depth += (fifo_size & 0xffff);
|
|
|
|
if (dwc->tx_fifo_size &&
|
|
|
|
(last_fifo_depth >= dwc->tx_fifo_size)) {
|
|
|
|
/*
|
|
|
|
* Fifo size allocated exceeded available RAM size.
|
|
|
|
* Hence return error.
|
|
|
|
*/
|
|
|
|
dev_err(dwc->dev, "Fifosize(%d) > available RAM(%d)\n",
|
|
|
|
last_fifo_depth, dwc->tx_fifo_size);
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
2014-03-26 10:31:44 -07:00
|
|
|
dwc3_writel(dwc->regs, DWC3_GTXFIFOSIZ(num), fifo_size);
|
2012-01-18 18:04:09 +02:00
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
void dwc3_gadget_giveback(struct dwc3_ep *dep, struct dwc3_request *req,
|
|
|
|
int status)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
2017-03-13 14:11:32 +02:00
|
|
|
unsigned int unmap_after_complete = false;
|
2013-01-14 15:59:37 +05:30
|
|
|
int i;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
if (req->queued) {
|
2013-01-14 15:59:37 +05:30
|
|
|
i = 0;
|
|
|
|
do {
|
2011-11-28 12:46:59 +02:00
|
|
|
dep->busy_slot++;
|
2013-01-14 15:59:37 +05:30
|
|
|
/*
|
|
|
|
* Skip LINK TRB. We can't use req->trb and check for
|
|
|
|
* DWC3_TRBCTL_LINK_TRB because it points the TRB we
|
|
|
|
* just completed (not the LINK TRB).
|
|
|
|
*/
|
|
|
|
if (((dep->busy_slot & DWC3_TRB_MASK) ==
|
|
|
|
DWC3_TRB_NUM- 1) &&
|
2012-03-12 20:25:24 +02:00
|
|
|
usb_endpoint_xfer_isoc(dep->endpoint.desc))
|
2013-01-14 15:59:37 +05:30
|
|
|
dep->busy_slot++;
|
|
|
|
} while(++i < req->request.num_mapped_sgs);
|
2013-01-14 15:59:38 +05:30
|
|
|
req->queued = false;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
list_del(&req->list);
|
2011-11-28 12:46:59 +02:00
|
|
|
req->trb = NULL;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
if (req->request.status == -EINPROGRESS)
|
|
|
|
req->request.status = status;
|
|
|
|
|
2017-03-13 14:11:32 +02:00
|
|
|
/*
|
|
|
|
* NOTICE we don't want to unmap before calling ->complete() if we're
|
|
|
|
* dealing with a bounced ep0 request. If we unmap it here, we would end
|
|
|
|
* up overwritting the contents of req->buf and this could confuse the
|
|
|
|
* gadget driver.
|
|
|
|
*/
|
|
|
|
if (dwc->ep0_bounced && dep->number <= 1) {
|
2012-08-10 13:42:16 +05:30
|
|
|
dwc->ep0_bounced = false;
|
2017-03-13 14:11:32 +02:00
|
|
|
unmap_after_complete = true;
|
|
|
|
} else {
|
|
|
|
usb_gadget_unmap_request(&dwc->gadget,
|
|
|
|
&req->request, req->direction);
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-11-03 17:15:41 -07:00
|
|
|
dev_dbg(dwc->dev, "request %pK from %s completed %d/%d ===> %d\n",
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
req, dep->name, req->request.actual,
|
|
|
|
req->request.length, status);
|
2014-04-30 17:45:10 -05:00
|
|
|
trace_dwc3_gadget_giveback(req);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_done(dep->number, req->request.actual, req->request.status);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_unlock(&dwc->lock);
|
2014-09-24 22:43:19 +02:00
|
|
|
usb_gadget_giveback_request(&dep->endpoint, &req->request);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_lock(&dwc->lock);
|
2017-03-13 14:11:32 +02:00
|
|
|
|
|
|
|
if (unmap_after_complete)
|
|
|
|
usb_gadget_unmap_request(&dwc->gadget,
|
|
|
|
&req->request, req->direction);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2014-09-05 09:47:44 -05:00
|
|
|
int dwc3_send_gadget_generic_command(struct dwc3 *dwc, unsigned cmd, u32 param)
|
2012-04-24 16:19:11 +03:00
|
|
|
{
|
|
|
|
u32 timeout = 500;
|
|
|
|
u32 reg;
|
|
|
|
|
2014-04-30 17:45:10 -05:00
|
|
|
trace_dwc3_gadget_generic_cmd(cmd, param);
|
2014-04-25 14:14:14 -05:00
|
|
|
|
2012-04-24 16:19:11 +03:00
|
|
|
dwc3_writel(dwc->regs, DWC3_DGCMDPAR, param);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DGCMD, cmd | DWC3_DGCMD_CMDACT);
|
|
|
|
|
|
|
|
do {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DGCMD);
|
|
|
|
if (!(reg & DWC3_DGCMD_CMDACT)) {
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"Command Complete --> %d",
|
2012-04-24 16:19:11 +03:00
|
|
|
DWC3_DGCMD_STATUS(reg));
|
2015-05-21 15:46:47 +05:30
|
|
|
if (DWC3_DGCMD_STATUS(reg))
|
|
|
|
return -EINVAL;
|
2012-04-24 16:19:11 +03:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We can't sleep here, because it's also called from
|
|
|
|
* interrupt context.
|
|
|
|
*/
|
|
|
|
timeout--;
|
2015-01-27 13:48:14 -06:00
|
|
|
if (!timeout) {
|
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"Command Timed Out");
|
2012-04-24 16:19:11 +03:00
|
|
|
return -ETIMEDOUT;
|
2015-01-27 13:48:14 -06:00
|
|
|
}
|
2012-04-24 16:19:11 +03:00
|
|
|
udelay(1);
|
|
|
|
} while (1);
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
int dwc3_send_gadget_ep_cmd(struct dwc3 *dwc, unsigned ep,
|
|
|
|
unsigned cmd, struct dwc3_gadget_ep_cmd_params *params)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep = dwc->eps[ep];
|
2016-08-25 16:17:48 -07:00
|
|
|
u32 timeout = 3000;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
u32 reg;
|
|
|
|
|
2014-04-30 17:45:10 -05:00
|
|
|
trace_dwc3_gadget_ep_cmd(dep, cmd, params);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-09-30 10:58:51 +03:00
|
|
|
dwc3_writel(dwc->regs, DWC3_DEPCMDPAR0(ep), params->param0);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEPCMDPAR1(ep), params->param1);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEPCMDPAR2(ep), params->param2);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEPCMD(ep), cmd | DWC3_DEPCMD_CMDACT);
|
|
|
|
do {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DEPCMD(ep));
|
|
|
|
if (!(reg & DWC3_DEPCMD_CMDACT)) {
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"Command Complete --> %d",
|
2011-08-27 20:29:58 +03:00
|
|
|
DWC3_DEPCMD_STATUS(reg));
|
2013-01-30 17:35:45 +05:30
|
|
|
|
|
|
|
/* SW issues START TRANSFER command to isochronous ep
|
|
|
|
* with future frame interval. If future interval time
|
|
|
|
* has already passed when core recieves command, core
|
|
|
|
* will respond with an error(bit13 in Command complete
|
|
|
|
* event. Hence return error in this case.
|
|
|
|
*/
|
|
|
|
if (reg & 0x2000)
|
|
|
|
return -EAGAIN;
|
|
|
|
else if (DWC3_DEPCMD_STATUS(reg))
|
2015-05-21 15:46:48 +05:30
|
|
|
return -EINVAL;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We can't sleep here, because it is also called from
|
|
|
|
* interrupt context.
|
|
|
|
*/
|
|
|
|
timeout--;
|
2015-01-27 13:48:14 -06:00
|
|
|
if (!timeout) {
|
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"Command Timed Out");
|
2014-07-07 17:07:16 -07:00
|
|
|
dev_err(dwc->dev, "%s command timeout for %s\n",
|
|
|
|
dwc3_gadget_ep_cmd_string(cmd), dep->name);
|
2016-08-25 16:17:48 -07:00
|
|
|
if (!(cmd & DWC3_DEPCMD_ENDTRANSFER)) {
|
|
|
|
dwc->ep_cmd_timeout_cnt++;
|
|
|
|
dwc3_notify_event(dwc,
|
2016-01-29 21:14:24 +05:30
|
|
|
DWC3_CONTROLLER_RESTART_USB_SESSION, 0);
|
2016-08-25 16:17:48 -07:00
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return -ETIMEDOUT;
|
2015-01-27 13:48:14 -06:00
|
|
|
}
|
2017-03-16 17:38:49 -07:00
|
|
|
if ((cmd & DWC3_DEPCMD_SETTRANSFRESOURCE))
|
|
|
|
udelay(20);
|
|
|
|
else
|
|
|
|
udelay(1);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
} while (1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_alloc_trb_pool(struct dwc3_ep *dep)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
2016-07-13 12:05:40 -07:00
|
|
|
u32 num_trbs = DWC3_TRB_NUM;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
if (dep->trb_pool)
|
|
|
|
return 0;
|
|
|
|
|
2015-05-18 18:27:53 -07:00
|
|
|
dep->trb_pool = dma_zalloc_coherent(dwc->dev,
|
2016-07-13 12:05:40 -07:00
|
|
|
sizeof(struct dwc3_trb) * num_trbs,
|
2016-02-16 11:38:23 -08:00
|
|
|
&dep->trb_pool_dma, GFP_KERNEL);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (!dep->trb_pool) {
|
|
|
|
dev_err(dep->dwc->dev, "failed to allocate trb pool for %s\n",
|
|
|
|
dep->name);
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
2016-07-13 12:05:40 -07:00
|
|
|
dep->num_trbs = num_trbs;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_free_trb_pool(struct dwc3_ep *dep)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
|
2015-10-09 19:36:21 -07:00
|
|
|
/* Freeing of GSI EP TRBs are handled by GSI EP ops. */
|
|
|
|
if (dep->endpoint.ep_type == EP_TYPE_GSI)
|
|
|
|
return;
|
|
|
|
|
2016-10-05 09:43:05 -07:00
|
|
|
/*
|
|
|
|
* Clean up ep ring to avoid getting xferInProgress due to stale trbs
|
|
|
|
* with HWO bit set from previous composition when update transfer cmd
|
|
|
|
* is issued.
|
|
|
|
*/
|
|
|
|
if (dep->number > 1 && dep->trb_pool && dep->trb_pool_dma) {
|
|
|
|
memset(&dep->trb_pool[0], 0,
|
|
|
|
sizeof(struct dwc3_trb) * dep->num_trbs);
|
|
|
|
dbg_event(dep->number, "Clr_TRB", 0);
|
|
|
|
|
2015-10-09 19:36:21 -07:00
|
|
|
dma_free_coherent(dwc->dev,
|
|
|
|
sizeof(struct dwc3_trb) * DWC3_TRB_NUM, dep->trb_pool,
|
|
|
|
dep->trb_pool_dma);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2015-10-09 19:36:21 -07:00
|
|
|
dep->trb_pool = NULL;
|
|
|
|
dep->trb_pool_dma = 0;
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2016-02-16 20:10:53 -08:00
|
|
|
static int dwc3_gadget_set_xfer_resource(struct dwc3 *dwc, struct dwc3_ep *dep);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dwc3_gadget_start_config - Configure EP resources
|
|
|
|
* @dwc: pointer to our controller context structure
|
|
|
|
* @dep: endpoint that is being enabled
|
|
|
|
*
|
|
|
|
* The assignment of transfer resources cannot perfectly follow the
|
|
|
|
* data book due to the fact that the controller driver does not have
|
|
|
|
* all knowledge of the configuration in advance. It is given this
|
|
|
|
* information piecemeal by the composite gadget framework after every
|
|
|
|
* SET_CONFIGURATION and SET_INTERFACE. Trying to follow the databook
|
|
|
|
* programming model in this scenario can cause errors. For two
|
|
|
|
* reasons:
|
|
|
|
*
|
|
|
|
* 1) The databook says to do DEPSTARTCFG for every SET_CONFIGURATION
|
|
|
|
* and SET_INTERFACE (8.1.5). This is incorrect in the scenario of
|
|
|
|
* multiple interfaces.
|
|
|
|
*
|
|
|
|
* 2) The databook does not mention doing more DEPXFERCFG for new
|
|
|
|
* endpoint on alt setting (8.1.6).
|
|
|
|
*
|
|
|
|
* The following simplified method is used instead:
|
|
|
|
*
|
|
|
|
* All hardware endpoints can be assigned a transfer resource and this
|
|
|
|
* setting will stay persistent until either a core reset or
|
|
|
|
* hibernation. So whenever we do a DEPSTARTCFG(0) we can go ahead and
|
|
|
|
* do DEPXFERCFG for every hardware endpoint as well. We are
|
|
|
|
* guaranteed that there are as many transfer resources as endpoints.
|
|
|
|
*
|
|
|
|
* This function is called for each endpoint when it is being enabled
|
|
|
|
* but is triggered only when called for EP0-out, which always happens
|
|
|
|
* first, and which should only happen in one of the above conditions.
|
|
|
|
*/
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
static int dwc3_gadget_start_config(struct dwc3 *dwc, struct dwc3_ep *dep)
|
|
|
|
{
|
|
|
|
struct dwc3_gadget_ep_cmd_params params;
|
|
|
|
u32 cmd;
|
2016-02-16 20:10:53 -08:00
|
|
|
int i;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (dep->number)
|
|
|
|
return 0;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
memset(¶ms, 0x00, sizeof(params));
|
2016-02-16 20:10:53 -08:00
|
|
|
cmd = DWC3_DEPCMD_DEPSTARTCFG;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-02-16 20:10:53 -08:00
|
|
|
ret = dwc3_send_gadget_ep_cmd(dwc, 0, cmd, ¶ms);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-02-16 20:10:53 -08:00
|
|
|
for (i = 0; i < DWC3_ENDPOINTS_NUM; i++) {
|
|
|
|
struct dwc3_ep *dep = dwc->eps[i];
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-02-16 20:10:53 -08:00
|
|
|
if (!dep)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
ret = dwc3_gadget_set_xfer_resource(dwc, dep);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_gadget_set_ep_config(struct dwc3 *dwc, struct dwc3_ep *dep,
|
2011-11-29 13:11:21 +02:00
|
|
|
const struct usb_endpoint_descriptor *desc,
|
2012-07-16 14:08:16 +03:00
|
|
|
const struct usb_ss_ep_comp_descriptor *comp_desc,
|
2013-12-19 12:38:49 -06:00
|
|
|
bool ignore, bool restore)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3_gadget_ep_cmd_params params;
|
|
|
|
|
|
|
|
memset(¶ms, 0x00, sizeof(params));
|
|
|
|
|
2011-09-30 10:58:51 +03:00
|
|
|
params.param0 = DWC3_DEPCFG_EP_TYPE(usb_endpoint_type(desc))
|
2012-08-31 16:54:07 +09:00
|
|
|
| DWC3_DEPCFG_MAX_PACKET_SIZE(usb_endpoint_maxp(desc));
|
|
|
|
|
|
|
|
/* Burst size is only needed in SuperSpeed mode */
|
|
|
|
if (dwc->gadget.speed == USB_SPEED_SUPER) {
|
|
|
|
u32 burst = dep->endpoint.maxburst - 1;
|
|
|
|
|
|
|
|
params.param0 |= DWC3_DEPCFG_BURST_SIZE(burst);
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-07-16 14:08:16 +03:00
|
|
|
if (ignore)
|
|
|
|
params.param0 |= DWC3_DEPCFG_IGN_SEQ_NUM;
|
|
|
|
|
2013-12-19 12:38:49 -06:00
|
|
|
if (restore) {
|
|
|
|
params.param0 |= DWC3_DEPCFG_ACTION_RESTORE;
|
|
|
|
params.param2 |= dep->saved_state;
|
|
|
|
}
|
|
|
|
|
2014-02-13 20:04:03 -08:00
|
|
|
if (!dep->endpoint.endless) {
|
|
|
|
pr_debug("%s(): enable xfer_complete_int for %s\n",
|
|
|
|
__func__, dep->endpoint.name);
|
|
|
|
params.param1 = DWC3_DEPCFG_XFER_COMPLETE_EN
|
|
|
|
| DWC3_DEPCFG_XFER_NOT_READY_EN;
|
|
|
|
} else {
|
|
|
|
pr_debug("%s(): disable xfer_complete_int for %s\n",
|
|
|
|
__func__, dep->endpoint.name);
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-01-02 13:35:41 +02:00
|
|
|
if (usb_ss_max_streams(comp_desc) && usb_endpoint_xfer_bulk(desc)) {
|
2011-09-30 10:58:51 +03:00
|
|
|
params.param1 |= DWC3_DEPCFG_STREAM_CAPABLE
|
|
|
|
| DWC3_DEPCFG_STREAM_EVENT_EN;
|
2011-09-30 10:58:47 +03:00
|
|
|
dep->stream_capable = true;
|
|
|
|
}
|
|
|
|
|
2015-09-28 20:01:21 -07:00
|
|
|
if (usb_endpoint_xfer_isoc(desc))
|
2011-09-30 10:58:51 +03:00
|
|
|
params.param1 |= DWC3_DEPCFG_XFER_IN_PROGRESS_EN;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* We are doing 1:1 mapping for endpoints, meaning
|
|
|
|
* Physical Endpoints 2 maps to Logical Endpoint 2 and
|
|
|
|
* so on. We consider the direction bit as part of the physical
|
|
|
|
* endpoint number. So USB endpoint 0x81 is 0x03.
|
|
|
|
*/
|
2011-09-30 10:58:51 +03:00
|
|
|
params.param1 |= DWC3_DEPCFG_EP_NUMBER(dep->number);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* We must use the lower 16 TX FIFOs even though
|
|
|
|
* HW might have more
|
|
|
|
*/
|
|
|
|
if (dep->direction)
|
2011-09-30 10:58:51 +03:00
|
|
|
params.param0 |= DWC3_DEPCFG_FIFO_NUMBER(dep->number >> 1);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
if (desc->bInterval) {
|
2011-09-30 10:58:51 +03:00
|
|
|
params.param1 |= DWC3_DEPCFG_BINTERVAL_M1(desc->bInterval - 1);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->interval = 1 << (desc->bInterval - 1);
|
|
|
|
}
|
|
|
|
|
|
|
|
return dwc3_send_gadget_ep_cmd(dwc, dep->number,
|
|
|
|
DWC3_DEPCMD_SETEPCONFIG, ¶ms);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_gadget_set_xfer_resource(struct dwc3 *dwc, struct dwc3_ep *dep)
|
|
|
|
{
|
|
|
|
struct dwc3_gadget_ep_cmd_params params;
|
|
|
|
|
|
|
|
memset(¶ms, 0x00, sizeof(params));
|
|
|
|
|
2011-09-30 10:58:51 +03:00
|
|
|
params.param0 = DWC3_DEPXFERCFG_NUM_XFER_RES(1);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
return dwc3_send_gadget_ep_cmd(dwc, dep->number,
|
|
|
|
DWC3_DEPCMD_SETTRANSFRESOURCE, ¶ms);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* __dwc3_gadget_ep_enable - Initializes a HW endpoint
|
|
|
|
* @dep: endpoint to be initialized
|
|
|
|
* @desc: USB Endpoint Descriptor
|
|
|
|
*
|
|
|
|
* Caller should take care of locking
|
|
|
|
*/
|
|
|
|
static int __dwc3_gadget_ep_enable(struct dwc3_ep *dep,
|
2011-11-29 13:11:21 +02:00
|
|
|
const struct usb_endpoint_descriptor *desc,
|
2012-07-16 14:08:16 +03:00
|
|
|
const struct usb_ss_ep_comp_descriptor *comp_desc,
|
2013-12-19 12:38:49 -06:00
|
|
|
bool ignore, bool restore)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
u32 reg;
|
2014-05-15 15:53:32 +03:00
|
|
|
int ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "Enabling %s", dep->name);
|
2013-07-12 19:09:39 +03:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (!(dep->flags & DWC3_EP_ENABLED)) {
|
|
|
|
ret = dwc3_gadget_start_config(dwc, dep);
|
2014-07-07 17:07:16 -07:00
|
|
|
if (ret) {
|
|
|
|
dev_err(dwc->dev, "start_config() failed for %s\n",
|
|
|
|
dep->name);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return ret;
|
2014-07-07 17:07:16 -07:00
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2013-12-19 12:38:49 -06:00
|
|
|
ret = dwc3_gadget_set_ep_config(dwc, dep, desc, comp_desc, ignore,
|
|
|
|
restore);
|
2014-07-07 17:07:16 -07:00
|
|
|
if (ret) {
|
|
|
|
dev_err(dwc->dev, "set_ep_config() failed for %s\n", dep->name);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return ret;
|
2014-07-07 17:07:16 -07:00
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
if (!(dep->flags & DWC3_EP_ENABLED)) {
|
2012-02-06 11:04:53 +02:00
|
|
|
struct dwc3_trb *trb_st_hw;
|
|
|
|
struct dwc3_trb *trb_link;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-03-12 20:25:24 +02:00
|
|
|
dep->endpoint.desc = desc;
|
2011-11-29 13:11:21 +02:00
|
|
|
dep->comp_desc = comp_desc;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->type = usb_endpoint_type(desc);
|
|
|
|
dep->flags |= DWC3_EP_ENABLED;
|
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DALEPENA);
|
|
|
|
reg |= DWC3_DALEPENA_EP(dep->number);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DALEPENA, reg);
|
|
|
|
|
|
|
|
if (!usb_endpoint_xfer_isoc(desc))
|
|
|
|
return 0;
|
|
|
|
|
2012-02-15 18:56:56 -08:00
|
|
|
/* Link TRB for ISOC. The HWO bit is never reset */
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
trb_st_hw = &dep->trb_pool[0];
|
|
|
|
|
2012-02-06 11:04:53 +02:00
|
|
|
trb_link = &dep->trb_pool[DWC3_TRB_NUM - 1];
|
2014-10-21 16:31:10 -07:00
|
|
|
memset(trb_link, 0, sizeof(*trb_link));
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-02-06 11:04:53 +02:00
|
|
|
trb_link->bpl = lower_32_bits(dwc3_trb_dma_offset(dep, trb_st_hw));
|
|
|
|
trb_link->bph = upper_32_bits(dwc3_trb_dma_offset(dep, trb_st_hw));
|
|
|
|
trb_link->ctrl |= DWC3_TRBCTL_LINK_TRB;
|
|
|
|
trb_link->ctrl |= DWC3_TRB_CTRL_HWO;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2015-07-20 14:48:13 -05:00
|
|
|
switch (usb_endpoint_type(desc)) {
|
|
|
|
case USB_ENDPOINT_XFER_CONTROL:
|
|
|
|
strlcat(dep->name, "-control", sizeof(dep->name));
|
|
|
|
break;
|
|
|
|
case USB_ENDPOINT_XFER_ISOC:
|
|
|
|
strlcat(dep->name, "-isoc", sizeof(dep->name));
|
|
|
|
break;
|
|
|
|
case USB_ENDPOINT_XFER_BULK:
|
|
|
|
strlcat(dep->name, "-bulk", sizeof(dep->name));
|
|
|
|
break;
|
|
|
|
case USB_ENDPOINT_XFER_INT:
|
|
|
|
strlcat(dep->name, "-int", sizeof(dep->name));
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
dev_err(dwc->dev, "invalid endpoint transfer type\n");
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2011-08-29 13:56:37 +02:00
|
|
|
static void dwc3_remove_requests(struct dwc3 *dwc, struct dwc3_ep *dep)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3_request *req;
|
|
|
|
|
2012-02-17 12:10:04 +02:00
|
|
|
if (!list_empty(&dep->req_queued)) {
|
2012-04-27 14:17:35 +03:00
|
|
|
dwc3_stop_active_transfer(dwc, dep->number, true);
|
2011-08-29 13:56:37 +02:00
|
|
|
|
2012-07-06 15:19:10 +05:30
|
|
|
/* - giveback all requests to gadget driver */
|
2012-06-15 11:54:36 +05:30
|
|
|
while (!list_empty(&dep->req_queued)) {
|
|
|
|
req = next_request(&dep->req_queued);
|
|
|
|
|
|
|
|
dwc3_gadget_giveback(dep, req, -ESHUTDOWN);
|
|
|
|
}
|
2012-02-17 12:10:04 +02:00
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
while (!list_empty(&dep->request_list)) {
|
|
|
|
req = next_request(&dep->request_list);
|
|
|
|
|
2011-08-29 13:56:37 +02:00
|
|
|
dwc3_gadget_giveback(dep, req, -ESHUTDOWN);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* __dwc3_gadget_ep_disable - Disables a HW endpoint
|
|
|
|
* @dep: the endpoint to disable
|
|
|
|
*
|
2011-08-29 13:56:37 +02:00
|
|
|
* This function also removes requests which are currently processed ny the
|
|
|
|
* hardware and those which are not yet scheduled.
|
|
|
|
* Caller should take care of locking.
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*/
|
|
|
|
static int __dwc3_gadget_ep_disable(struct dwc3_ep *dep)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
u32 reg;
|
|
|
|
|
2015-07-20 14:46:15 -05:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "Disabling %s", dep->name);
|
|
|
|
|
2015-10-09 19:36:21 -07:00
|
|
|
if (dep->endpoint.ep_type == EP_TYPE_NORMAL)
|
|
|
|
dwc3_remove_requests(dwc, dep);
|
|
|
|
else if (dep->endpoint.ep_type == EP_TYPE_GSI)
|
|
|
|
dwc3_stop_active_transfer(dwc, dep->number, true);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2014-04-16 10:30:33 -05:00
|
|
|
/* make sure HW endpoint isn't stalled */
|
|
|
|
if (dep->flags & DWC3_EP_STALL)
|
2014-09-24 14:19:52 -05:00
|
|
|
__dwc3_gadget_ep_set_halt(dep, 0, false);
|
2014-04-16 10:30:33 -05:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DALEPENA);
|
|
|
|
reg &= ~DWC3_DALEPENA_EP(dep->number);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DALEPENA, reg);
|
|
|
|
|
2011-09-30 10:58:47 +03:00
|
|
|
dep->stream_capable = false;
|
2012-02-08 13:56:48 +02:00
|
|
|
dep->endpoint.desc = NULL;
|
2011-11-29 13:11:21 +02:00
|
|
|
dep->comp_desc = NULL;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->type = 0;
|
2011-09-30 10:58:47 +03:00
|
|
|
dep->flags = 0;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-05-10 15:23:00 -07:00
|
|
|
/* Keep GSI ep names with "-gsi" suffix */
|
|
|
|
if (!strnstr(dep->name, "gsi", 10)) {
|
|
|
|
snprintf(dep->name, sizeof(dep->name), "ep%d%s",
|
2015-07-20 14:48:13 -05:00
|
|
|
dep->number >> 1,
|
|
|
|
(dep->number & 1) ? "in" : "out");
|
2016-05-10 15:23:00 -07:00
|
|
|
}
|
2015-07-20 14:48:13 -05:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* -------------------------------------------------------------------------- */
|
|
|
|
|
|
|
|
static int dwc3_gadget_ep0_enable(struct usb_ep *ep,
|
|
|
|
const struct usb_endpoint_descriptor *desc)
|
|
|
|
{
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_gadget_ep0_disable(struct usb_ep *ep)
|
|
|
|
{
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* -------------------------------------------------------------------------- */
|
|
|
|
|
|
|
|
static int dwc3_gadget_ep_enable(struct usb_ep *ep,
|
|
|
|
const struct usb_endpoint_descriptor *desc)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
struct dwc3 *dwc;
|
|
|
|
unsigned long flags;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (!ep || !desc || desc->bDescriptorType != USB_DT_ENDPOINT) {
|
2016-11-03 17:15:41 -07:00
|
|
|
pr_debug("dwc3: invalid parameters. ep=%pK, desc=%pK, DT=%d\n",
|
2014-05-22 16:11:58 +03:00
|
|
|
ep, desc, desc ? desc->bDescriptorType : 0);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!desc->wMaxPacketSize) {
|
|
|
|
pr_debug("dwc3: missing wMaxPacketSize\n");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
dep = to_dwc3_ep(ep);
|
|
|
|
dwc = dep->dwc;
|
|
|
|
|
2012-08-15 12:28:29 +03:00
|
|
|
if (dep->flags & DWC3_EP_ENABLED) {
|
|
|
|
dev_WARN_ONCE(dwc->dev, true, "%s is already enabled\n",
|
|
|
|
dep->name);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
2013-12-19 12:38:49 -06:00
|
|
|
ret = __dwc3_gadget_ep_enable(dep, desc, ep->comp_desc, false, false);
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(dep->number, "ENABLE", ret);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_gadget_ep_disable(struct usb_ep *ep)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
struct dwc3 *dwc;
|
|
|
|
unsigned long flags;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (!ep) {
|
|
|
|
pr_debug("dwc3: invalid parameters\n");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
dep = to_dwc3_ep(ep);
|
|
|
|
dwc = dep->dwc;
|
|
|
|
|
|
|
|
if (!(dep->flags & DWC3_EP_ENABLED)) {
|
2014-10-30 16:21:03 -07:00
|
|
|
dev_dbg(dwc->dev, "%s is already disabled\n", dep->name);
|
|
|
|
dbg_event(dep->number, "ALRDY DISABLED", dep->flags);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
|
|
|
ret = __dwc3_gadget_ep_disable(dep);
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(dep->number, "DISABLE", ret);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct usb_request *dwc3_gadget_ep_alloc_request(struct usb_ep *ep,
|
|
|
|
gfp_t gfp_flags)
|
|
|
|
{
|
|
|
|
struct dwc3_request *req;
|
|
|
|
struct dwc3_ep *dep = to_dwc3_ep(ep);
|
|
|
|
|
|
|
|
req = kzalloc(sizeof(*req), gfp_flags);
|
2014-07-17 12:45:11 +09:00
|
|
|
if (!req)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return NULL;
|
|
|
|
|
|
|
|
req->epnum = dep->number;
|
|
|
|
req->dep = dep;
|
2014-06-28 00:36:38 -07:00
|
|
|
req->request.dma = DMA_ERROR_CODE;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2014-04-30 17:45:10 -05:00
|
|
|
trace_dwc3_alloc_request(req);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return &req->request;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_gadget_ep_free_request(struct usb_ep *ep,
|
|
|
|
struct usb_request *request)
|
|
|
|
{
|
|
|
|
struct dwc3_request *req = to_dwc3_request(request);
|
|
|
|
|
2014-04-30 17:45:10 -05:00
|
|
|
trace_dwc3_free_request(req);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
kfree(req);
|
|
|
|
}
|
|
|
|
|
2011-11-22 11:37:34 +02:00
|
|
|
/**
|
|
|
|
* dwc3_prepare_one_trb - setup one TRB from one request
|
|
|
|
* @dep: endpoint for which this request is prepared
|
|
|
|
* @req: dwc3_request pointer
|
|
|
|
*/
|
2011-11-28 12:25:01 +02:00
|
|
|
static void dwc3_prepare_one_trb(struct dwc3_ep *dep,
|
2011-11-28 12:46:59 +02:00
|
|
|
struct dwc3_request *req, dma_addr_t dma,
|
2013-01-14 15:59:37 +05:30
|
|
|
unsigned length, unsigned last, unsigned chain, unsigned node)
|
2011-11-22 11:37:34 +02:00
|
|
|
{
|
2012-02-06 11:04:53 +02:00
|
|
|
struct dwc3_trb *trb;
|
2011-11-22 11:37:34 +02:00
|
|
|
|
2016-11-03 17:15:41 -07:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "%s: req %pK dma %08llx length %d%s%s",
|
2011-11-28 12:46:59 +02:00
|
|
|
dep->name, req, (unsigned long long) dma,
|
|
|
|
length, last ? " last" : "",
|
|
|
|
chain ? " chain" : "");
|
|
|
|
|
2013-01-14 15:59:35 +05:30
|
|
|
|
|
|
|
trb = &dep->trb_pool[dep->free_slot & DWC3_TRB_MASK];
|
2011-11-22 11:37:34 +02:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
if (!req->trb) {
|
|
|
|
dwc3_gadget_move_request_queued(req);
|
2012-02-06 11:04:53 +02:00
|
|
|
req->trb = trb;
|
|
|
|
req->trb_dma = dwc3_trb_dma_offset(dep, trb);
|
2013-01-14 15:59:37 +05:30
|
|
|
req->start_slot = dep->free_slot & DWC3_TRB_MASK;
|
2011-11-28 12:46:59 +02:00
|
|
|
}
|
2011-11-22 11:37:34 +02:00
|
|
|
|
2013-01-14 15:59:37 +05:30
|
|
|
dep->free_slot++;
|
2014-05-16 05:57:57 +08:00
|
|
|
/* Skip the LINK-TRB on ISOC */
|
|
|
|
if (((dep->free_slot & DWC3_TRB_MASK) == DWC3_TRB_NUM - 1) &&
|
|
|
|
usb_endpoint_xfer_isoc(dep->endpoint.desc))
|
|
|
|
dep->free_slot++;
|
2013-01-14 15:59:37 +05:30
|
|
|
|
2012-02-06 11:04:53 +02:00
|
|
|
trb->size = DWC3_TRB_SIZE_LENGTH(length);
|
|
|
|
trb->bpl = lower_32_bits(dma);
|
|
|
|
trb->bph = upper_32_bits(dma);
|
2011-11-22 11:37:34 +02:00
|
|
|
|
2012-03-12 20:25:24 +02:00
|
|
|
switch (usb_endpoint_type(dep->endpoint.desc)) {
|
2011-11-22 11:37:34 +02:00
|
|
|
case USB_ENDPOINT_XFER_CONTROL:
|
2012-02-06 11:04:53 +02:00
|
|
|
trb->ctrl = DWC3_TRBCTL_CONTROL_SETUP;
|
2011-11-22 11:37:34 +02:00
|
|
|
break;
|
|
|
|
|
|
|
|
case USB_ENDPOINT_XFER_ISOC:
|
2013-01-14 15:59:37 +05:30
|
|
|
if (!node)
|
|
|
|
trb->ctrl = DWC3_TRBCTL_ISOCHRONOUS_FIRST;
|
|
|
|
else
|
|
|
|
trb->ctrl = DWC3_TRBCTL_ISOCHRONOUS;
|
2015-06-27 14:54:14 -07:00
|
|
|
|
|
|
|
if (!req->request.no_interrupt && !chain)
|
|
|
|
trb->ctrl |= DWC3_TRB_CTRL_IOC;
|
2011-11-22 11:37:34 +02:00
|
|
|
break;
|
|
|
|
|
|
|
|
case USB_ENDPOINT_XFER_BULK:
|
|
|
|
case USB_ENDPOINT_XFER_INT:
|
2012-02-06 11:04:53 +02:00
|
|
|
trb->ctrl = DWC3_TRBCTL_NORMAL;
|
2015-06-27 14:54:14 -07:00
|
|
|
if (req->request.num_mapped_sgs > 0) {
|
|
|
|
if (!last && !chain &&
|
|
|
|
!req->request.no_interrupt)
|
|
|
|
trb->ctrl |= DWC3_TRB_CTRL_IOC;
|
|
|
|
}
|
2011-11-22 11:37:34 +02:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
/*
|
|
|
|
* This is only possible with faulty memory because we
|
|
|
|
* checked it already :)
|
|
|
|
*/
|
|
|
|
BUG();
|
|
|
|
}
|
|
|
|
|
2012-03-12 20:25:24 +02:00
|
|
|
if (usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
2012-02-06 11:04:53 +02:00
|
|
|
trb->ctrl |= DWC3_TRB_CTRL_ISP_IMI;
|
|
|
|
trb->ctrl |= DWC3_TRB_CTRL_CSP;
|
2013-01-14 15:59:37 +05:30
|
|
|
} else if (last) {
|
|
|
|
trb->ctrl |= DWC3_TRB_CTRL_LST;
|
2012-02-06 11:04:53 +02:00
|
|
|
}
|
2011-11-22 11:37:34 +02:00
|
|
|
|
2013-01-14 15:59:37 +05:30
|
|
|
if (chain)
|
|
|
|
trb->ctrl |= DWC3_TRB_CTRL_CHN;
|
|
|
|
|
2012-03-12 20:25:24 +02:00
|
|
|
if (usb_endpoint_xfer_bulk(dep->endpoint.desc) && dep->stream_capable)
|
2012-02-06 11:04:53 +02:00
|
|
|
trb->ctrl |= DWC3_TRB_CTRL_SID_SOFN(req->request.stream_id);
|
2011-11-22 11:37:34 +02:00
|
|
|
|
2012-02-06 11:04:53 +02:00
|
|
|
trb->ctrl |= DWC3_TRB_CTRL_HWO;
|
2014-04-30 17:45:10 -05:00
|
|
|
|
|
|
|
trace_dwc3_prepare_trb(dep, trb);
|
2011-11-22 11:37:34 +02:00
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/*
|
|
|
|
* dwc3_prepare_trbs - setup TRBs from requests
|
|
|
|
* @dep: endpoint for which requests are being prepared
|
|
|
|
* @starting: true if the endpoint is idle and no requests are queued.
|
|
|
|
*
|
2012-02-15 18:56:56 -08:00
|
|
|
* The function goes through the requests list and sets up TRBs for the
|
|
|
|
* transfers. The function returns once there are no more TRBs available or
|
|
|
|
* it runs out of requests.
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*/
|
2011-11-28 12:25:01 +02:00
|
|
|
static void dwc3_prepare_trbs(struct dwc3_ep *dep, bool starting)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
2011-11-28 12:25:01 +02:00
|
|
|
struct dwc3_request *req, *n;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
u32 trbs_left;
|
2012-02-15 13:35:06 +02:00
|
|
|
u32 max;
|
2011-11-22 11:37:34 +02:00
|
|
|
unsigned int last_one = 0;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
BUILD_BUG_ON_NOT_POWER_OF_2(DWC3_TRB_NUM);
|
|
|
|
|
|
|
|
/* the first request must not be queued */
|
|
|
|
trbs_left = (dep->busy_slot - dep->free_slot) & DWC3_TRB_MASK;
|
2011-11-22 11:37:34 +02:00
|
|
|
|
2012-02-15 13:35:06 +02:00
|
|
|
/* Can't wrap around on a non-isoc EP since there's no link TRB */
|
2012-03-12 20:25:24 +02:00
|
|
|
if (!usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
2012-02-15 13:35:06 +02:00
|
|
|
max = DWC3_TRB_NUM - (dep->free_slot & DWC3_TRB_MASK);
|
|
|
|
if (trbs_left > max)
|
|
|
|
trbs_left = max;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/*
|
2012-02-15 18:56:56 -08:00
|
|
|
* If busy & slot are equal than it is either full or empty. If we are
|
|
|
|
* starting to process requests then we are empty. Otherwise we are
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
* full and don't do anything
|
|
|
|
*/
|
|
|
|
if (!trbs_left) {
|
|
|
|
if (!starting)
|
2011-11-28 12:25:01 +02:00
|
|
|
return;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
trbs_left = DWC3_TRB_NUM;
|
|
|
|
/*
|
|
|
|
* In case we start from scratch, we queue the ISOC requests
|
|
|
|
* starting from slot 1. This is done because we use ring
|
|
|
|
* buffer and have no LST bit to stop us. Instead, we place
|
2012-02-15 18:56:56 -08:00
|
|
|
* IOC bit every TRB_NUM/4. We try to avoid having an interrupt
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
* after the first request so we start at slot 1 and have
|
|
|
|
* 7 requests proceed before we hit the first IOC.
|
|
|
|
* Other transfer types don't use the ring buffer and are
|
|
|
|
* processed from the first TRB until the last one. Since we
|
|
|
|
* don't wrap around we have to start at the beginning.
|
|
|
|
*/
|
2012-03-12 20:25:24 +02:00
|
|
|
if (usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->busy_slot = 1;
|
|
|
|
dep->free_slot = 1;
|
|
|
|
} else {
|
|
|
|
dep->busy_slot = 0;
|
|
|
|
dep->free_slot = 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* The last TRB is a link TRB, not used for xfer */
|
2012-03-12 20:25:24 +02:00
|
|
|
if ((trbs_left <= 1) && usb_endpoint_xfer_isoc(dep->endpoint.desc))
|
2011-11-28 12:25:01 +02:00
|
|
|
return;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
list_for_each_entry_safe(req, n, &dep->request_list, list) {
|
2011-11-28 12:46:59 +02:00
|
|
|
unsigned length;
|
|
|
|
dma_addr_t dma;
|
2013-01-14 15:59:37 +05:30
|
|
|
last_one = false;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
if (req->request.num_mapped_sgs > 0) {
|
|
|
|
struct usb_request *request = &req->request;
|
|
|
|
struct scatterlist *sg = request->sg;
|
|
|
|
struct scatterlist *s;
|
|
|
|
int i;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
for_each_sg(sg, s, request->num_mapped_sgs, i) {
|
|
|
|
unsigned chain = true;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
length = sg_dma_len(s);
|
|
|
|
dma = sg_dma_address(s);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-02-15 18:56:56 -08:00
|
|
|
if (i == (request->num_mapped_sgs - 1) ||
|
|
|
|
sg_is_last(s)) {
|
2015-01-13 14:27:20 +05:30
|
|
|
if (list_empty(&dep->request_list))
|
2013-01-14 15:59:37 +05:30
|
|
|
last_one = true;
|
2011-11-28 12:46:59 +02:00
|
|
|
chain = false;
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
trbs_left--;
|
|
|
|
if (!trbs_left)
|
|
|
|
last_one = true;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
if (last_one)
|
|
|
|
chain = false;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
dwc3_prepare_one_trb(dep, req, dma, length,
|
2013-01-14 15:59:37 +05:30
|
|
|
last_one, chain, i);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
if (last_one)
|
|
|
|
break;
|
|
|
|
}
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_queue(dep->number, &req->request, trbs_left);
|
2015-01-13 14:27:21 +05:30
|
|
|
|
|
|
|
if (last_one)
|
|
|
|
break;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
} else {
|
2011-11-28 12:46:59 +02:00
|
|
|
dma = req->request.dma;
|
|
|
|
length = req->request.length;
|
|
|
|
trbs_left--;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
if (!trbs_left)
|
|
|
|
last_one = 1;
|
2011-09-30 10:58:47 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
/* Is this the last request? */
|
|
|
|
if (list_is_last(&req->list, &dep->request_list))
|
|
|
|
last_one = 1;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-11-28 12:46:59 +02:00
|
|
|
dwc3_prepare_one_trb(dep, req, dma, length,
|
2013-01-14 15:59:37 +05:30
|
|
|
last_one, false, 0);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_queue(dep->number, &req->request, 0);
|
2011-11-28 12:46:59 +02:00
|
|
|
if (last_one)
|
|
|
|
break;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static int __dwc3_gadget_kick_transfer(struct dwc3_ep *dep, u16 cmd_param,
|
|
|
|
int start_new)
|
|
|
|
{
|
|
|
|
struct dwc3_gadget_ep_cmd_params params;
|
2013-01-30 17:35:45 +05:30
|
|
|
struct dwc3_request *req, *req1, *n;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
int ret;
|
|
|
|
u32 cmd;
|
|
|
|
|
|
|
|
if (start_new && (dep->flags & DWC3_EP_BUSY)) {
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "%s: endpoint busy", dep->name);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return -EBUSY;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If we are getting here after a short-out-packet we don't enqueue any
|
|
|
|
* new requests as we try to set the IOC bit only on the last request.
|
|
|
|
*/
|
|
|
|
if (start_new) {
|
|
|
|
if (list_empty(&dep->req_queued))
|
|
|
|
dwc3_prepare_trbs(dep, start_new);
|
|
|
|
|
|
|
|
/* req points to the first request which will be sent */
|
|
|
|
req = next_request(&dep->req_queued);
|
|
|
|
} else {
|
2011-11-28 12:25:01 +02:00
|
|
|
dwc3_prepare_trbs(dep, start_new);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/*
|
2012-02-15 18:56:56 -08:00
|
|
|
* req points to the first request where HWO changed from 0 to 1
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*/
|
2011-11-28 12:25:01 +02:00
|
|
|
req = next_request(&dep->req_queued);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
if (!req) {
|
|
|
|
dep->flags |= DWC3_EP_PENDING_REQUEST;
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(dep->number, "NO REQ", 0);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
memset(¶ms, 0, sizeof(params));
|
|
|
|
|
2013-01-14 15:59:36 +05:30
|
|
|
if (start_new) {
|
|
|
|
params.param0 = upper_32_bits(req->trb_dma);
|
|
|
|
params.param1 = lower_32_bits(req->trb_dma);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
cmd = DWC3_DEPCMD_STARTTRANSFER;
|
2013-01-14 15:59:36 +05:30
|
|
|
} else {
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
cmd = DWC3_DEPCMD_UPDATETRANSFER;
|
2013-01-14 15:59:36 +05:30
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
cmd |= DWC3_DEPCMD_PARAM(cmd_param);
|
|
|
|
ret = dwc3_send_gadget_ep_cmd(dwc, dep->number, cmd, ¶ms);
|
|
|
|
if (ret < 0) {
|
|
|
|
dev_dbg(dwc->dev, "failed to send STARTTRANSFER command\n");
|
|
|
|
|
2013-01-30 17:35:45 +05:30
|
|
|
if ((ret == -EAGAIN) && start_new &&
|
|
|
|
usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
|
|
|
/* If bit13 in Command complete event is set, software
|
|
|
|
* must issue ENDTRANSFER command and wait for
|
|
|
|
* Xfernotready event to queue the requests again.
|
|
|
|
*/
|
|
|
|
if (!dep->resource_index) {
|
|
|
|
dep->resource_index =
|
|
|
|
dwc3_gadget_ep_get_transfer_index(dwc,
|
|
|
|
dep->number);
|
|
|
|
WARN_ON_ONCE(!dep->resource_index);
|
|
|
|
}
|
|
|
|
dwc3_stop_active_transfer(dwc, dep->number, true);
|
|
|
|
list_for_each_entry_safe_reverse(req1, n,
|
|
|
|
&dep->req_queued, list) {
|
|
|
|
req1->trb = NULL;
|
|
|
|
dwc3_gadget_move_request_list_front(req1);
|
|
|
|
if (req->request.num_mapped_sgs)
|
|
|
|
dep->busy_slot +=
|
|
|
|
req->request.num_mapped_sgs;
|
|
|
|
else
|
|
|
|
dep->busy_slot++;
|
|
|
|
if ((dep->busy_slot & DWC3_TRB_MASK) ==
|
|
|
|
DWC3_TRB_NUM - 1)
|
|
|
|
dep->busy_slot++;
|
|
|
|
}
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/*
|
|
|
|
* FIXME we need to iterate over the list of requests
|
|
|
|
* here and stop, unmap, free and del each of the linked
|
2012-02-15 18:56:56 -08:00
|
|
|
* requests instead of what we do now.
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*/
|
2011-12-19 11:32:34 +02:00
|
|
|
usb_gadget_unmap_request(&dwc->gadget, &req->request,
|
|
|
|
req->direction);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
list_del(&req->list);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
dep->flags |= DWC3_EP_BUSY;
|
2011-11-04 12:32:47 +02:00
|
|
|
|
2012-03-29 18:16:54 +00:00
|
|
|
if (start_new) {
|
2012-06-06 12:04:13 +03:00
|
|
|
dep->resource_index = dwc3_gadget_ep_get_transfer_index(dwc,
|
2012-03-29 18:16:54 +00:00
|
|
|
dep->number);
|
2012-06-06 12:04:13 +03:00
|
|
|
WARN_ON_ONCE(!dep->resource_index);
|
2012-03-29 18:16:54 +00:00
|
|
|
}
|
2011-11-04 12:32:47 +02:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-05-25 18:54:56 +05:30
|
|
|
static void __dwc3_gadget_start_isoc(struct dwc3 *dwc,
|
|
|
|
struct dwc3_ep *dep, u32 cur_uf)
|
|
|
|
{
|
|
|
|
u32 uf;
|
2013-02-14 16:33:30 +05:30
|
|
|
int ret;
|
2012-05-25 18:54:56 +05:30
|
|
|
|
2013-01-30 17:35:45 +05:30
|
|
|
dep->current_uf = cur_uf;
|
|
|
|
|
2012-05-25 18:54:56 +05:30
|
|
|
if (list_empty(&dep->request_list)) {
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"ISOC ep %s run out for requests",
|
|
|
|
dep->name);
|
2012-08-30 12:21:43 +05:30
|
|
|
dep->flags |= DWC3_EP_PENDING_REQUEST;
|
2012-05-25 18:54:56 +05:30
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* 4 micro frames in the future */
|
|
|
|
uf = cur_uf + dep->interval * 4;
|
|
|
|
|
2013-02-14 16:33:30 +05:30
|
|
|
ret = __dwc3_gadget_kick_transfer(dep, uf, 1);
|
|
|
|
if (ret < 0)
|
|
|
|
dbg_event(dep->number, "ISOC QUEUE", ret);
|
2012-05-25 18:54:56 +05:30
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_gadget_start_isoc(struct dwc3 *dwc,
|
|
|
|
struct dwc3_ep *dep, const struct dwc3_event_depevt *event)
|
|
|
|
{
|
|
|
|
u32 cur_uf, mask;
|
|
|
|
|
|
|
|
mask = ~(dep->interval - 1);
|
|
|
|
cur_uf = event->parameters & mask;
|
|
|
|
|
|
|
|
__dwc3_gadget_start_isoc(dwc, dep, cur_uf);
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
static int __dwc3_gadget_ep_queue(struct dwc3_ep *dep, struct dwc3_request *req)
|
|
|
|
{
|
2011-12-19 11:32:34 +02:00
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
int ret;
|
|
|
|
|
2013-02-11 15:53:34 +05:30
|
|
|
if (req->request.status == -EINPROGRESS) {
|
|
|
|
ret = -EBUSY;
|
2016-11-03 17:15:41 -07:00
|
|
|
dev_err(dwc->dev, "%s: %pK request already in queue",
|
2013-02-11 15:53:34 +05:30
|
|
|
dep->name, req);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
req->request.actual = 0;
|
|
|
|
req->request.status = -EINPROGRESS;
|
|
|
|
req->direction = dep->direction;
|
|
|
|
req->epnum = dep->number;
|
|
|
|
|
2015-09-01 09:01:38 -05:00
|
|
|
trace_dwc3_ep_queue(req);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/*
|
|
|
|
* We only add to our list of requests now and
|
|
|
|
* start consuming the list once we get XferNotReady
|
|
|
|
* IRQ.
|
|
|
|
*
|
|
|
|
* That way, we avoid doing anything that we don't need
|
|
|
|
* to do now and defer it until the point we receive a
|
|
|
|
* particular token from the Host side.
|
|
|
|
*
|
|
|
|
* This will also avoid Host cancelling URBs due to too
|
2012-02-15 18:56:56 -08:00
|
|
|
* many NAKs.
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*/
|
2011-12-19 11:32:34 +02:00
|
|
|
ret = usb_gadget_map_request(&dwc->gadget, &req->request,
|
|
|
|
dep->direction);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
list_add_tail(&req->list, &dep->request_list);
|
|
|
|
|
|
|
|
/*
|
2012-06-06 12:00:50 +03:00
|
|
|
* There are a few special cases:
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*
|
2012-03-29 18:16:54 +00:00
|
|
|
* 1. XferNotReady with empty list of requests. We need to kick the
|
|
|
|
* transfer here in that situation, otherwise we will be NAKing
|
|
|
|
* forever. If we get XferNotReady before gadget driver has a
|
|
|
|
* chance to queue a request, we will ACK the IRQ but won't be
|
|
|
|
* able to receive the data until the next request is queued.
|
|
|
|
* The following code is handling exactly that.
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*
|
|
|
|
*/
|
|
|
|
if (dep->flags & DWC3_EP_PENDING_REQUEST) {
|
2012-08-30 12:21:43 +05:30
|
|
|
/*
|
|
|
|
* If xfernotready is already elapsed and it is a case
|
|
|
|
* of isoc transfer, then issue END TRANSFER, so that
|
|
|
|
* you can receive xfernotready again and can have
|
|
|
|
* notion of current microframe.
|
|
|
|
*/
|
|
|
|
if (usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
2013-01-30 17:35:45 +05:30
|
|
|
/* If xfernotready event is recieved before issuing
|
|
|
|
* START TRANSFER command, don't issue END TRANSFER.
|
|
|
|
* Rather start queueing the requests by issuing START
|
|
|
|
* TRANSFER command.
|
|
|
|
*/
|
|
|
|
if (list_empty(&dep->req_queued) && dep->resource_index)
|
2012-04-27 14:17:35 +03:00
|
|
|
dwc3_stop_active_transfer(dwc, dep->number, true);
|
2013-01-30 17:35:45 +05:30
|
|
|
else
|
|
|
|
__dwc3_gadget_start_isoc(dwc, dep,
|
|
|
|
dep->current_uf);
|
|
|
|
dep->flags &= ~DWC3_EP_PENDING_REQUEST;
|
2012-08-30 12:21:43 +05:30
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-06-06 12:00:50 +03:00
|
|
|
ret = __dwc3_gadget_kick_transfer(dep, 0, true);
|
2015-09-15 09:49:14 -05:00
|
|
|
if (!ret)
|
|
|
|
dep->flags &= ~DWC3_EP_PENDING_REQUEST;
|
2013-02-14 16:33:30 +05:30
|
|
|
else if (ret != -EBUSY)
|
|
|
|
dbg_event(dep->number, "XfNR QUEUE", ret);
|
2015-09-15 09:49:14 -05:00
|
|
|
|
2015-09-16 10:40:07 -05:00
|
|
|
goto out;
|
2012-06-06 12:00:50 +03:00
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-06-06 12:00:50 +03:00
|
|
|
/*
|
|
|
|
* 2. XferInProgress on Isoc EP with an active transfer. We need to
|
|
|
|
* kick the transfer here after queuing a request, otherwise the
|
|
|
|
* core may not see the modified TRB(s).
|
|
|
|
*/
|
|
|
|
if (usb_endpoint_xfer_isoc(dep->endpoint.desc) &&
|
2012-08-07 16:54:18 +05:30
|
|
|
(dep->flags & DWC3_EP_BUSY) &&
|
|
|
|
!(dep->flags & DWC3_EP_MISSED_ISOC)) {
|
2012-06-06 12:04:13 +03:00
|
|
|
WARN_ON_ONCE(!dep->resource_index);
|
|
|
|
ret = __dwc3_gadget_kick_transfer(dep, dep->resource_index,
|
2012-06-06 12:00:50 +03:00
|
|
|
false);
|
2013-02-14 16:33:30 +05:30
|
|
|
if (ret && ret != -EBUSY)
|
|
|
|
dbg_event(dep->number, "XfIP QUEUE", ret);
|
2015-09-16 10:40:07 -05:00
|
|
|
goto out;
|
2012-05-22 10:24:11 +03:00
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-07-26 13:26:50 +03:00
|
|
|
/*
|
|
|
|
* 4. Stream Capable Bulk Endpoints. We need to start the transfer
|
|
|
|
* right away, otherwise host will not know we have streams to be
|
|
|
|
* handled.
|
|
|
|
*/
|
2015-09-16 10:40:07 -05:00
|
|
|
if (dep->stream_capable)
|
2012-07-26 13:26:50 +03:00
|
|
|
ret = __dwc3_gadget_kick_transfer(dep, 0, true);
|
|
|
|
|
2015-09-16 10:40:07 -05:00
|
|
|
out:
|
2013-02-14 16:33:30 +05:30
|
|
|
if (ret && ret != -EBUSY) {
|
|
|
|
dbg_event(dep->number, "QUEUE err", ret);
|
2015-09-16 10:40:07 -05:00
|
|
|
dev_dbg(dwc->dev, "%s: failed to kick transfers\n",
|
|
|
|
dep->name);
|
2013-02-14 16:33:30 +05:30
|
|
|
}
|
2015-09-16 10:40:07 -05:00
|
|
|
if (ret == -EBUSY)
|
|
|
|
ret = 0;
|
|
|
|
|
|
|
|
return ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2014-05-13 15:45:00 +03:00
|
|
|
static int dwc3_gadget_wakeup(struct usb_gadget *g)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
|
|
|
|
2016-01-29 11:46:05 -08:00
|
|
|
schedule_work(&dwc->wakeup_work);
|
|
|
|
return 0;
|
2014-05-13 15:45:00 +03:00
|
|
|
}
|
|
|
|
|
2014-06-17 15:22:45 +03:00
|
|
|
static bool dwc3_gadget_is_suspended(struct dwc3 *dwc)
|
|
|
|
{
|
2014-10-24 19:18:58 -07:00
|
|
|
if (atomic_read(&dwc->in_lpm) ||
|
|
|
|
dwc->link_state == DWC3_LINK_STATE_U3)
|
2014-06-17 15:22:45 +03:00
|
|
|
return true;
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2015-12-02 10:06:45 -06:00
|
|
|
static void __dwc3_gadget_ep_zlp_complete(struct usb_ep *ep,
|
|
|
|
struct usb_request *request)
|
|
|
|
{
|
|
|
|
dwc3_gadget_ep_free_request(ep, request);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int __dwc3_gadget_ep_queue_zlp(struct dwc3 *dwc, struct dwc3_ep *dep)
|
|
|
|
{
|
|
|
|
struct dwc3_request *req;
|
|
|
|
struct usb_request *request;
|
|
|
|
struct usb_ep *ep = &dep->endpoint;
|
|
|
|
|
|
|
|
dwc3_trace(trace_dwc3_gadget, "queueing ZLP\n");
|
|
|
|
request = dwc3_gadget_ep_alloc_request(ep, GFP_ATOMIC);
|
|
|
|
if (!request)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
request->length = 0;
|
|
|
|
request->buf = dwc->zlp_buf;
|
|
|
|
request->complete = __dwc3_gadget_ep_zlp_complete;
|
|
|
|
|
|
|
|
req = to_dwc3_request(request);
|
|
|
|
|
|
|
|
return __dwc3_gadget_ep_queue(dep, req);
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
static int dwc3_gadget_ep_queue(struct usb_ep *ep, struct usb_request *request,
|
|
|
|
gfp_t gfp_flags)
|
|
|
|
{
|
|
|
|
struct dwc3_request *req = to_dwc3_request(request);
|
|
|
|
struct dwc3_ep *dep = to_dwc3_ep(ep);
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
|
|
|
|
unsigned long flags;
|
|
|
|
int ret;
|
|
|
|
|
2014-09-03 14:26:34 +08:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
2012-03-12 20:25:24 +02:00
|
|
|
if (!dep->endpoint.desc) {
|
2016-11-03 17:15:41 -07:00
|
|
|
dev_dbg(dwc->dev, "trying to queue request %pK to disabled %s\n",
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
request, ep->name);
|
2014-10-13 15:36:16 -05:00
|
|
|
ret = -ESHUTDOWN;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2016-11-03 17:15:41 -07:00
|
|
|
if (WARN(req->dep != dep, "request %pK belongs to '%s'\n",
|
2014-10-13 15:36:16 -05:00
|
|
|
request, req->dep->name)) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto out;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2016-04-28 11:35:50 +05:30
|
|
|
/*
|
|
|
|
* Queuing endless request to USB endpoint through generic ep queue
|
|
|
|
* API should not be allowed.
|
|
|
|
*/
|
|
|
|
if (dep->endpoint.endless) {
|
|
|
|
dev_dbg(dwc->dev, "trying to queue endless request %p to %s\n",
|
|
|
|
request, ep->name);
|
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
return -EPERM;
|
|
|
|
}
|
|
|
|
|
2014-06-17 15:22:45 +03:00
|
|
|
if (dwc3_gadget_is_suspended(dwc)) {
|
|
|
|
if (dwc->gadget.remote_wakeup)
|
|
|
|
dwc3_gadget_wakeup(&dwc->gadget);
|
|
|
|
ret = dwc->gadget.remote_wakeup ? -EAGAIN : -ENOTSUPP;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2012-10-05 13:16:00 +05:30
|
|
|
WARN(!dep->direction && (request->length % ep->desc->wMaxPacketSize),
|
|
|
|
"trying to queue unaligned request (%d)\n", request->length);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
ret = __dwc3_gadget_ep_queue(dep, req);
|
2014-10-13 15:36:16 -05:00
|
|
|
|
2015-12-02 10:06:45 -06:00
|
|
|
/*
|
|
|
|
* Okay, here's the thing, if gadget driver has requested for a ZLP by
|
|
|
|
* setting request->zero, instead of doing magic, we will just queue an
|
|
|
|
* extra usb_request ourselves so that it gets handled the same way as
|
|
|
|
* any other request.
|
|
|
|
*/
|
2015-12-22 12:23:20 -08:00
|
|
|
if (ret == 0 && request->zero && request->length &&
|
|
|
|
(request->length % ep->maxpacket == 0))
|
2015-12-02 10:06:45 -06:00
|
|
|
ret = __dwc3_gadget_ep_queue_zlp(dwc, dep);
|
|
|
|
|
2014-10-13 15:36:16 -05:00
|
|
|
out:
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_gadget_ep_dequeue(struct usb_ep *ep,
|
|
|
|
struct usb_request *request)
|
|
|
|
{
|
|
|
|
struct dwc3_request *req = to_dwc3_request(request);
|
|
|
|
struct dwc3_request *r = NULL;
|
|
|
|
|
|
|
|
struct dwc3_ep *dep = to_dwc3_ep(ep);
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
|
|
|
|
unsigned long flags;
|
|
|
|
int ret = 0;
|
|
|
|
|
2015-04-11 00:56:27 -07:00
|
|
|
if (atomic_read(&dwc->in_lpm)) {
|
|
|
|
dev_err(dwc->dev, "Unable to dequeue while in LPM\n");
|
|
|
|
return -EAGAIN;
|
|
|
|
}
|
|
|
|
|
2014-04-30 17:45:10 -05:00
|
|
|
trace_dwc3_ep_dequeue(req);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
|
|
|
|
|
|
|
list_for_each_entry(r, &dep->request_list, list) {
|
|
|
|
if (r == req)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (r != req) {
|
|
|
|
list_for_each_entry(r, &dep->req_queued, list) {
|
|
|
|
if (r == req)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
if (r == req) {
|
|
|
|
/* wait until it is processed */
|
2012-04-27 14:17:35 +03:00
|
|
|
dwc3_stop_active_transfer(dwc, dep->number, true);
|
2012-06-15 11:54:00 +05:30
|
|
|
goto out1;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
2016-11-03 17:15:41 -07:00
|
|
|
dev_err(dwc->dev, "request %pK was not queued to %s\n",
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
request, ep->name);
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto out0;
|
|
|
|
}
|
|
|
|
|
2012-06-15 11:54:00 +05:30
|
|
|
out1:
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(dep->number, "DEQUEUE", 0);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/* giveback the request */
|
|
|
|
dwc3_gadget_giveback(dep, req, -ECONNRESET);
|
|
|
|
|
|
|
|
out0:
|
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2014-09-24 14:19:52 -05:00
|
|
|
int __dwc3_gadget_ep_set_halt(struct dwc3_ep *dep, int value, int protocol)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3_gadget_ep_cmd_params params;
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
memset(¶ms, 0x00, sizeof(params));
|
|
|
|
|
|
|
|
if (value) {
|
2014-09-24 14:19:52 -05:00
|
|
|
if (!protocol && ((dep->direction && dep->flags & DWC3_EP_BUSY) ||
|
|
|
|
(!list_empty(&dep->req_queued) ||
|
|
|
|
!list_empty(&dep->request_list)))) {
|
|
|
|
dev_dbg(dwc->dev, "%s: pending request, cannot halt\n",
|
|
|
|
dep->name);
|
|
|
|
return -EAGAIN;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
ret = dwc3_send_gadget_ep_cmd(dwc, dep->number,
|
|
|
|
DWC3_DEPCMD_SETSTALL, ¶ms);
|
|
|
|
if (ret)
|
2014-03-07 14:20:22 +03:00
|
|
|
dev_err(dwc->dev, "failed to set STALL on %s\n",
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->name);
|
|
|
|
else
|
|
|
|
dep->flags |= DWC3_EP_STALL;
|
|
|
|
} else {
|
|
|
|
ret = dwc3_send_gadget_ep_cmd(dwc, dep->number,
|
|
|
|
DWC3_DEPCMD_CLEARSTALL, ¶ms);
|
|
|
|
if (ret)
|
2014-03-07 14:20:22 +03:00
|
|
|
dev_err(dwc->dev, "failed to clear STALL on %s\n",
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->name);
|
|
|
|
else
|
2013-11-01 12:05:12 -04:00
|
|
|
dep->flags &= ~(DWC3_EP_STALL | DWC3_EP_WEDGE);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
2011-09-30 10:58:44 +03:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_gadget_ep_set_halt(struct usb_ep *ep, int value)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep = to_dwc3_ep(ep);
|
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
int ret;
|
|
|
|
|
2015-04-28 10:39:56 -07:00
|
|
|
if (!ep->desc) {
|
|
|
|
dev_err(dwc->dev, "(%s)'s desc is NULL.\n", dep->name);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(dep->number, "HALT", value);
|
2015-10-27 20:28:51 -07:00
|
|
|
if (usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
|
|
|
dev_err(dwc->dev, "%s is of Isochronous type\n", dep->name);
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2014-09-24 14:19:52 -05:00
|
|
|
ret = __dwc3_gadget_ep_set_halt(dep, value, false);
|
2015-10-27 20:28:51 -07:00
|
|
|
out:
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_gadget_ep_set_wedge(struct usb_ep *ep)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep = to_dwc3_ep(ep);
|
2012-02-24 17:32:16 -08:00
|
|
|
struct dwc3 *dwc = dep->dwc;
|
|
|
|
unsigned long flags;
|
2014-09-24 10:50:14 -05:00
|
|
|
int ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-02-24 17:32:16 -08:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(dep->number, "WEDGE", 0);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->flags |= DWC3_EP_WEDGE;
|
|
|
|
|
2012-06-25 22:40:43 +05:30
|
|
|
if (dep->number == 0 || dep->number == 1)
|
2014-09-24 10:50:14 -05:00
|
|
|
ret = __dwc3_gadget_ep0_set_halt(ep, 1);
|
2012-06-25 22:40:43 +05:30
|
|
|
else
|
2014-09-24 14:19:52 -05:00
|
|
|
ret = __dwc3_gadget_ep_set_halt(dep, 1, false);
|
2014-09-24 10:50:14 -05:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
|
|
|
|
return ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* -------------------------------------------------------------------------- */
|
|
|
|
|
|
|
|
static struct usb_endpoint_descriptor dwc3_gadget_ep0_desc = {
|
|
|
|
.bLength = USB_DT_ENDPOINT_SIZE,
|
|
|
|
.bDescriptorType = USB_DT_ENDPOINT,
|
|
|
|
.bmAttributes = USB_ENDPOINT_XFER_CONTROL,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct usb_ep_ops dwc3_gadget_ep0_ops = {
|
|
|
|
.enable = dwc3_gadget_ep0_enable,
|
|
|
|
.disable = dwc3_gadget_ep0_disable,
|
|
|
|
.alloc_request = dwc3_gadget_ep_alloc_request,
|
|
|
|
.free_request = dwc3_gadget_ep_free_request,
|
|
|
|
.queue = dwc3_gadget_ep0_queue,
|
|
|
|
.dequeue = dwc3_gadget_ep_dequeue,
|
2012-06-25 22:40:43 +05:30
|
|
|
.set_halt = dwc3_gadget_ep0_set_halt,
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
.set_wedge = dwc3_gadget_ep_set_wedge,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct usb_ep_ops dwc3_gadget_ep_ops = {
|
|
|
|
.enable = dwc3_gadget_ep_enable,
|
|
|
|
.disable = dwc3_gadget_ep_disable,
|
|
|
|
.alloc_request = dwc3_gadget_ep_alloc_request,
|
|
|
|
.free_request = dwc3_gadget_ep_free_request,
|
|
|
|
.queue = dwc3_gadget_ep_queue,
|
|
|
|
.dequeue = dwc3_gadget_ep_dequeue,
|
|
|
|
.set_halt = dwc3_gadget_ep_set_halt,
|
|
|
|
.set_wedge = dwc3_gadget_ep_set_wedge,
|
|
|
|
};
|
|
|
|
|
|
|
|
/* -------------------------------------------------------------------------- */
|
|
|
|
|
|
|
|
static int dwc3_gadget_get_frame(struct usb_gadget *g)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
|
|
|
u32 reg;
|
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DSTS);
|
|
|
|
return DWC3_DSTS_SOFFN(reg);
|
|
|
|
}
|
|
|
|
|
2015-06-10 19:28:49 +05:30
|
|
|
#define DWC3_PM_RESUME_RETRIES 20 /* Max Number of retries */
|
|
|
|
#define DWC3_PM_RESUME_DELAY 100 /* 100 msec */
|
|
|
|
|
2014-05-13 15:45:00 +03:00
|
|
|
static void dwc3_gadget_wakeup_work(struct work_struct *w)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
2014-05-13 15:45:00 +03:00
|
|
|
struct dwc3 *dwc;
|
|
|
|
int ret;
|
2015-06-10 19:28:49 +05:30
|
|
|
static int retry_count;
|
2014-05-13 15:45:00 +03:00
|
|
|
|
|
|
|
dwc = container_of(w, struct dwc3, wakeup_work);
|
|
|
|
|
2015-06-10 19:28:49 +05:30
|
|
|
ret = pm_runtime_get_sync(dwc->dev);
|
|
|
|
if (ret) {
|
|
|
|
/* pm_runtime_get_sync returns -EACCES error between
|
|
|
|
* late_suspend and early_resume, wait for system resume to
|
|
|
|
* finish and queue work again
|
|
|
|
*/
|
|
|
|
pr_debug("PM runtime get sync failed, ret %d\n", ret);
|
|
|
|
if (ret == -EACCES) {
|
|
|
|
pm_runtime_put_noidle(dwc->dev);
|
|
|
|
if (retry_count == DWC3_PM_RESUME_RETRIES) {
|
|
|
|
retry_count = 0;
|
|
|
|
pr_err("pm_runtime_get_sync timed out\n");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
msleep(DWC3_PM_RESUME_DELAY);
|
|
|
|
retry_count++;
|
|
|
|
schedule_work(&dwc->wakeup_work);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
retry_count = 0;
|
2015-04-27 15:09:23 -07:00
|
|
|
dbg_event(0xFF, "Gdgwake gsyn",
|
|
|
|
atomic_read(&dwc->dev->power.usage_count));
|
2014-05-13 15:45:00 +03:00
|
|
|
|
|
|
|
ret = dwc3_gadget_wakeup_int(dwc);
|
|
|
|
|
|
|
|
if (ret)
|
|
|
|
pr_err("Remote wakeup failed. ret = %d.\n", ret);
|
|
|
|
else
|
|
|
|
pr_debug("Remote wakeup succeeded.\n");
|
2015-04-27 15:09:23 -07:00
|
|
|
|
|
|
|
pm_runtime_put_noidle(dwc->dev);
|
|
|
|
dbg_event(0xFF, "Gdgwake put",
|
|
|
|
atomic_read(&dwc->dev->power.usage_count));
|
2014-05-13 15:45:00 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_gadget_wakeup_int(struct dwc3 *dwc)
|
|
|
|
{
|
2014-05-19 11:18:01 +03:00
|
|
|
bool link_recover_only = false;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
u32 reg;
|
|
|
|
int ret = 0;
|
|
|
|
u8 link_state;
|
2014-11-25 15:29:58 -08:00
|
|
|
unsigned long flags;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
pr_debug("%s(): Entry\n", __func__);
|
|
|
|
disable_irq(dwc->irq);
|
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/*
|
|
|
|
* According to the Databook Remote wakeup request should
|
|
|
|
* be issued only when the device is in early suspend state.
|
|
|
|
*
|
|
|
|
* We can check that via USB Link State bits in DSTS register.
|
|
|
|
*/
|
2014-05-13 15:45:00 +03:00
|
|
|
link_state = dwc3_get_link_state(dwc);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
switch (link_state) {
|
|
|
|
case DWC3_LINK_STATE_RX_DET: /* in HS, means Early Suspend */
|
|
|
|
case DWC3_LINK_STATE_U3: /* in HS, means SUSPEND */
|
|
|
|
break;
|
2014-05-19 11:18:01 +03:00
|
|
|
case DWC3_LINK_STATE_U1:
|
|
|
|
if (dwc->gadget.speed != USB_SPEED_SUPER) {
|
|
|
|
link_recover_only = true;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
/* Intentional fallthrough */
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
default:
|
|
|
|
dev_dbg(dwc->dev, "can't wakeup from link state %d\n",
|
|
|
|
link_state);
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
/* Enable LINK STATUS change event */
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DEVTEN);
|
|
|
|
reg |= DWC3_DEVTEN_ULSTCNGEN;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEVTEN, reg);
|
|
|
|
/*
|
|
|
|
* memory barrier is required to make sure that required events
|
|
|
|
* with core is enabled before performing RECOVERY mechnism.
|
|
|
|
*/
|
|
|
|
mb();
|
|
|
|
|
2012-01-02 18:55:57 +02:00
|
|
|
ret = dwc3_gadget_set_link_state(dwc, DWC3_LINK_STATE_RECOV);
|
|
|
|
if (ret < 0) {
|
|
|
|
dev_err(dwc->dev, "failed to put link in Recovery\n");
|
2014-11-25 15:29:58 -08:00
|
|
|
/* Disable LINK STATUS change */
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DEVTEN);
|
|
|
|
reg &= ~DWC3_DEVTEN_ULSTCNGEN;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEVTEN, reg);
|
|
|
|
/* Required to complete this operation before returning */
|
|
|
|
mb();
|
2012-01-02 18:55:57 +02:00
|
|
|
goto out;
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-04-27 13:10:52 +03:00
|
|
|
/* Recent versions do this automatically */
|
|
|
|
if (dwc->revision < DWC3_REVISION_194A) {
|
|
|
|
/* write zeroes to Link Change Request */
|
2012-05-24 10:27:56 +03:00
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
2012-04-27 13:10:52 +03:00
|
|
|
reg &= ~DWC3_DCTL_ULSTCHNGREQ_MASK;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
enable_irq(dwc->irq);
|
2015-03-06 17:30:03 -08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Have bigger value (16 sec) for timeout since some host PCs driving
|
|
|
|
* resume for very long time (e.g. 8 sec)
|
|
|
|
*/
|
2014-11-25 15:29:58 -08:00
|
|
|
ret = wait_event_interruptible_timeout(dwc->wait_linkstate,
|
|
|
|
(dwc->link_state < DWC3_LINK_STATE_U3) ||
|
|
|
|
(dwc->link_state == DWC3_LINK_STATE_SS_DIS),
|
2015-03-06 17:30:03 -08:00
|
|
|
msecs_to_jiffies(16000));
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
|
|
|
/* Disable link status change event */
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DEVTEN);
|
|
|
|
reg &= ~DWC3_DEVTEN_ULSTCNGEN;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEVTEN, reg);
|
|
|
|
/*
|
|
|
|
* Complete this write before we go ahead and perform resume
|
|
|
|
* as we don't need link status change notificaiton anymore.
|
|
|
|
*/
|
|
|
|
mb();
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
if (!ret) {
|
|
|
|
dev_dbg(dwc->dev, "Timeout moving into state(%d)\n",
|
|
|
|
dwc->link_state);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
ret = -EINVAL;
|
2014-11-25 15:29:58 -08:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
goto out1;
|
|
|
|
} else {
|
|
|
|
ret = 0;
|
|
|
|
/*
|
|
|
|
* If USB is disconnected OR received RESET from host,
|
|
|
|
* don't perform resume
|
|
|
|
*/
|
|
|
|
if (dwc->link_state == DWC3_LINK_STATE_SS_DIS ||
|
|
|
|
dwc->gadget.state == USB_STATE_DEFAULT)
|
|
|
|
link_recover_only = true;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2014-03-27 23:41:09 +02:00
|
|
|
/*
|
|
|
|
* According to DWC3 databook, the controller does not
|
|
|
|
* trigger a wakeup event when remote-wakeup is used.
|
|
|
|
* Hence, after remote-wakeup sequence is complete, and
|
|
|
|
* the device is back at U0 state, it is required that
|
|
|
|
* the resume sequence is initiated by SW.
|
|
|
|
*/
|
2014-05-19 11:18:01 +03:00
|
|
|
if (!link_recover_only)
|
2014-11-25 15:29:58 -08:00
|
|
|
dwc3_gadget_wakeup_interrupt(dwc, true);
|
|
|
|
|
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
pr_debug("%s: Exit\n", __func__);
|
|
|
|
return ret;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
out:
|
2014-11-25 15:29:58 -08:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
enable_irq(dwc->irq);
|
|
|
|
|
|
|
|
out1:
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2014-05-22 16:11:58 +03:00
|
|
|
static int dwc_gadget_func_wakeup(struct usb_gadget *g, int interface_id)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
|
|
|
|
|
|
|
if (!g || (g->speed != USB_SPEED_SUPER))
|
|
|
|
return -ENOTSUPP;
|
|
|
|
|
2014-06-17 15:22:45 +03:00
|
|
|
if (dwc3_gadget_is_suspended(dwc)) {
|
|
|
|
pr_debug("USB bus is suspended. Scheduling wakeup and returning -EAGAIN.\n");
|
|
|
|
dwc3_gadget_wakeup(&dwc->gadget);
|
|
|
|
return -EAGAIN;
|
|
|
|
}
|
|
|
|
|
2014-08-14 10:20:49 +03:00
|
|
|
if (dwc->revision < DWC3_REVISION_220A) {
|
|
|
|
ret = dwc3_send_gadget_generic_command(dwc,
|
|
|
|
DWC3_DGCMD_XMIT_FUNCTION, interface_id);
|
|
|
|
} else {
|
|
|
|
ret = dwc3_send_gadget_generic_command(dwc,
|
|
|
|
DWC3_DGCMD_XMIT_DEV, 0x1 | (interface_id << 4));
|
|
|
|
}
|
2014-05-22 16:11:58 +03:00
|
|
|
|
2016-01-29 11:46:05 -08:00
|
|
|
if (ret)
|
|
|
|
pr_err("Function wakeup HW command failed.\n");
|
|
|
|
else
|
|
|
|
pr_debug("Function wakeup HW command succeeded.\n");
|
|
|
|
|
2014-05-22 16:11:58 +03:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
static int dwc3_gadget_set_selfpowered(struct usb_gadget *g,
|
|
|
|
int is_selfpowered)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
2012-02-24 17:32:16 -08:00
|
|
|
unsigned long flags;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2012-02-24 17:32:16 -08:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
2015-01-28 16:32:40 +08:00
|
|
|
g->is_selfpowered = !!is_selfpowered;
|
2012-02-24 17:32:16 -08:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-06-05 16:15:01 +05:30
|
|
|
#define DWC3_SOFT_RESET_TIMEOUT 10 /* 10 msec */
|
2013-12-19 13:43:19 -06:00
|
|
|
static int dwc3_gadget_run_stop(struct dwc3 *dwc, int is_on, int suspend)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
u32 reg;
|
2011-08-29 16:46:38 +02:00
|
|
|
u32 timeout = 500;
|
2013-06-05 16:15:01 +05:30
|
|
|
ktime_t start, diff;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
2012-01-18 18:32:29 +02:00
|
|
|
if (is_on) {
|
2016-07-15 11:45:14 -07:00
|
|
|
dbg_event(0xFF, "Pullup_enable", is_on);
|
2012-04-27 13:10:52 +03:00
|
|
|
if (dwc->revision <= DWC3_REVISION_187A) {
|
|
|
|
reg &= ~DWC3_DCTL_TRGTULST_MASK;
|
|
|
|
reg |= DWC3_DCTL_TRGTULST_RX_DET;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (dwc->revision >= DWC3_REVISION_194A)
|
|
|
|
reg &= ~DWC3_DCTL_KEEP_CONNECT;
|
2013-06-05 16:15:01 +05:30
|
|
|
|
|
|
|
start = ktime_get();
|
|
|
|
/* issue device SoftReset */
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg | DWC3_DCTL_CSFTRST);
|
|
|
|
do {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
if (!(reg & DWC3_DCTL_CSFTRST))
|
|
|
|
break;
|
|
|
|
|
|
|
|
diff = ktime_sub(ktime_get(), start);
|
|
|
|
/* poll for max. 10ms */
|
|
|
|
if (ktime_to_ms(diff) > DWC3_SOFT_RESET_TIMEOUT) {
|
|
|
|
printk_ratelimited(KERN_ERR
|
|
|
|
"%s:core Reset Timed Out\n", __func__);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
cpu_relax();
|
|
|
|
} while (true);
|
|
|
|
|
|
|
|
|
|
|
|
dwc3_event_buffers_setup(dwc);
|
|
|
|
dwc3_gadget_restart(dwc);
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
2012-04-27 13:10:52 +03:00
|
|
|
reg |= DWC3_DCTL_RUN_STOP;
|
2013-12-19 13:43:19 -06:00
|
|
|
|
|
|
|
if (dwc->has_hibernation)
|
|
|
|
reg |= DWC3_DCTL_KEEP_CONNECT;
|
|
|
|
|
2013-02-08 17:55:58 +02:00
|
|
|
dwc->pullups_connected = true;
|
2012-01-18 18:32:29 +02:00
|
|
|
} else {
|
2016-07-15 11:45:14 -07:00
|
|
|
dbg_event(0xFF, "Pullup_disable", is_on);
|
2015-10-21 12:50:15 -07:00
|
|
|
dwc3_gadget_disable_irq(dwc);
|
|
|
|
__dwc3_gadget_ep_disable(dwc->eps[0]);
|
|
|
|
__dwc3_gadget_ep_disable(dwc->eps[1]);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
reg &= ~DWC3_DCTL_RUN_STOP;
|
2013-12-19 13:43:19 -06:00
|
|
|
|
|
|
|
if (dwc->has_hibernation && !suspend)
|
|
|
|
reg &= ~DWC3_DCTL_KEEP_CONNECT;
|
|
|
|
|
2013-02-08 17:55:58 +02:00
|
|
|
dwc->pullups_connected = false;
|
2014-05-04 11:34:45 +03:00
|
|
|
usb_gadget_set_state(&dwc->gadget, USB_STATE_NOTATTACHED);
|
2012-01-18 18:32:29 +02:00
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
|
|
|
|
do {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DSTS);
|
|
|
|
if (is_on) {
|
|
|
|
if (!(reg & DWC3_DSTS_DEVCTRLHLT))
|
|
|
|
break;
|
|
|
|
} else {
|
|
|
|
if (reg & DWC3_DSTS_DEVCTRLHLT)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
timeout--;
|
2016-07-15 11:45:14 -07:00
|
|
|
if (!timeout) {
|
|
|
|
dev_err(dwc->dev, "failed to %s controller\n",
|
|
|
|
is_on ? "start" : "stop");
|
|
|
|
if (is_on)
|
|
|
|
dbg_event(0xFF, "STARTTOUT", reg);
|
|
|
|
else
|
|
|
|
dbg_event(0xFF, "STOPTOUT", reg);
|
2012-07-02 10:21:55 +05:30
|
|
|
return -ETIMEDOUT;
|
2016-07-15 11:45:14 -07:00
|
|
|
}
|
2011-08-29 16:46:38 +02:00
|
|
|
udelay(1);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
} while (1);
|
|
|
|
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "gadget %s data soft-%s",
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc->gadget_driver
|
|
|
|
? dwc->gadget_driver->function : "no-function",
|
|
|
|
is_on ? "connect" : "disconnect");
|
2012-07-02 10:21:55 +05:30
|
|
|
|
|
|
|
return 0;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
static int dwc3_gadget_vbus_draw(struct usb_gadget *g, unsigned mA)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
|
|
|
|
|
|
|
dwc->vbus_draw = mA;
|
|
|
|
dev_dbg(dwc->dev, "Notify controller from %s. mA = %d\n", __func__, mA);
|
2016-01-29 21:14:24 +05:30
|
|
|
dwc3_notify_event(dwc, DWC3_CONTROLLER_SET_CURRENT_DRAW_EVENT, 0);
|
2016-02-02 12:57:37 -08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
|
|
|
unsigned long flags;
|
2012-07-02 10:21:55 +05:30
|
|
|
int ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
is_on = !!is_on;
|
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
dwc->softconnect = is_on;
|
|
|
|
|
|
|
|
if ((dwc->is_drd && !dwc->vbus_active) || !dwc->gadget_driver) {
|
|
|
|
/*
|
|
|
|
* Need to wait for vbus_session(on) from otg driver or to
|
|
|
|
* the udc_start.
|
|
|
|
*/
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2015-04-11 00:56:27 -07:00
|
|
|
pm_runtime_get_sync(dwc->dev);
|
|
|
|
dbg_event(0xFF, "Pullup gsync",
|
|
|
|
atomic_read(&dwc->dev->power.usage_count));
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
2015-04-11 00:56:27 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If we are here after bus suspend notify otg state machine to
|
|
|
|
* increment pm usage count of dwc to prevent pm_runtime_suspend
|
|
|
|
* during enumeration.
|
|
|
|
*/
|
|
|
|
dev_dbg(dwc->dev, "Notify OTG from %s\n", __func__);
|
|
|
|
dwc->b_suspend = false;
|
2016-01-29 21:14:24 +05:30
|
|
|
dwc3_notify_event(dwc, DWC3_CONTROLLER_NOTIFY_OTG_EVENT, 0);
|
2015-04-11 00:56:27 -07:00
|
|
|
|
2013-12-19 13:43:19 -06:00
|
|
|
ret = dwc3_gadget_run_stop(dwc, is_on, false);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
|
2016-03-11 17:38:51 -08:00
|
|
|
pm_runtime_mark_last_busy(dwc->dev);
|
|
|
|
pm_runtime_put_autosuspend(dwc->dev);
|
2015-04-11 00:56:27 -07:00
|
|
|
dbg_event(0xFF, "Pullup put",
|
|
|
|
atomic_read(&dwc->dev->power.usage_count));
|
|
|
|
|
2012-07-02 10:21:55 +05:30
|
|
|
return ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2014-08-29 15:21:03 -07:00
|
|
|
void dwc3_gadget_enable_irq(struct dwc3 *dwc)
|
2013-02-08 15:24:04 +02:00
|
|
|
{
|
|
|
|
u32 reg;
|
|
|
|
|
|
|
|
/* Enable all but Start and End of Frame IRQs */
|
|
|
|
reg = (DWC3_DEVTEN_VNDRDEVTSTRCVEDEN |
|
|
|
|
DWC3_DEVTEN_EVNTOVERFLOWEN |
|
|
|
|
DWC3_DEVTEN_CMDCMPLTEN |
|
|
|
|
DWC3_DEVTEN_ERRTICERREN |
|
|
|
|
DWC3_DEVTEN_WKUPEVTEN |
|
|
|
|
DWC3_DEVTEN_CONNECTDONEEN |
|
|
|
|
DWC3_DEVTEN_USBRSTEN |
|
|
|
|
DWC3_DEVTEN_DISCONNEVTEN);
|
|
|
|
|
2014-03-10 15:24:52 -07:00
|
|
|
/*
|
|
|
|
* Enable SUSPENDEVENT(BIT:6) for version 230A and above
|
|
|
|
* else enable USB Link change event (BIT:3) for older version
|
|
|
|
*/
|
|
|
|
if (dwc->revision < DWC3_REVISION_230A)
|
|
|
|
reg |= DWC3_DEVTEN_ULSTCNGEN;
|
|
|
|
else
|
|
|
|
reg |= DWC3_DEVTEN_SUSPEND;
|
|
|
|
|
2013-02-08 15:24:04 +02:00
|
|
|
dwc3_writel(dwc->regs, DWC3_DEVTEN, reg);
|
|
|
|
}
|
|
|
|
|
2014-08-29 15:21:03 -07:00
|
|
|
void dwc3_gadget_disable_irq(struct dwc3 *dwc)
|
2013-02-08 15:24:04 +02:00
|
|
|
{
|
|
|
|
/* mask all interrupts */
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEVTEN, 0x00);
|
|
|
|
}
|
|
|
|
|
2011-06-30 16:57:15 +03:00
|
|
|
static irqreturn_t dwc3_thread_interrupt(int irq, void *_dwc);
|
2016-02-02 12:57:37 -08:00
|
|
|
static void dwc3_gadget_disconnect_interrupt(struct dwc3 *dwc);
|
2013-02-08 15:24:04 +02:00
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
static int dwc3_gadget_vbus_session(struct usb_gadget *_gadget, int is_active)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
2016-02-02 12:57:37 -08:00
|
|
|
struct dwc3 *dwc = gadget_to_dwc(_gadget);
|
|
|
|
unsigned long flags;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
if (!dwc->is_drd)
|
|
|
|
return -EPERM;
|
|
|
|
|
|
|
|
is_active = !!is_active;
|
2013-06-27 10:00:18 +03:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
/* Mark that the vbus was powered */
|
|
|
|
dwc->vbus_active = is_active;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Check if upper level usb_gadget_driver was already registerd with
|
|
|
|
* this udc controller driver (if dwc3_gadget_start was called)
|
|
|
|
*/
|
|
|
|
if (dwc->gadget_driver && dwc->softconnect) {
|
|
|
|
if (dwc->vbus_active) {
|
|
|
|
/*
|
|
|
|
* Both vbus was activated by otg and pullup was
|
|
|
|
* signaled by the gadget driver.
|
|
|
|
*/
|
|
|
|
dwc3_gadget_run_stop(dwc, 1, false);
|
|
|
|
} else {
|
|
|
|
dwc3_gadget_run_stop(dwc, 0, false);
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
/*
|
|
|
|
* Clearing run/stop bit might occur before disconnect event is seen.
|
|
|
|
* Make sure to let gadget driver know in that case.
|
|
|
|
*/
|
|
|
|
if (!dwc->vbus_active) {
|
|
|
|
dev_dbg(dwc->dev, "calling disconnect from %s\n", __func__);
|
|
|
|
dwc3_gadget_disconnect_interrupt(dwc);
|
|
|
|
}
|
|
|
|
|
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int __dwc3_gadget_start(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
int ret = 0;
|
|
|
|
u32 reg;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-11-14 12:32:43 -08:00
|
|
|
/*
|
|
|
|
* Use IMOD if enabled via dwc->imod_interval. Otherwise, if
|
|
|
|
* the core supports IMOD, disable it.
|
|
|
|
*/
|
|
|
|
if (dwc->imod_interval) {
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEV_IMOD(0), dwc->imod_interval);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_GEVNTCOUNT(0), DWC3_GEVNTCOUNT_EHB);
|
|
|
|
} else if (dwc3_has_imod(dwc)) {
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DEV_IMOD(0), 0);
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCFG);
|
|
|
|
reg &= ~(DWC3_DCFG_SPEED_MASK);
|
2012-03-23 12:20:31 +02:00
|
|
|
|
|
|
|
/**
|
|
|
|
* WORKAROUND: DWC3 revision < 2.20a have an issue
|
|
|
|
* which would cause metastability state on Run/Stop
|
|
|
|
* bit if we try to force the IP to USB2-only mode.
|
|
|
|
*
|
|
|
|
* Because of that, we cannot configure the IP to any
|
|
|
|
* speed other than the SuperSpeed
|
|
|
|
*
|
|
|
|
* Refers to:
|
|
|
|
*
|
|
|
|
* STAR#9000525659: Clock Domain Crossing on DCTL in
|
|
|
|
* USB 2.0 Mode
|
|
|
|
*/
|
2013-06-30 14:29:51 +03:00
|
|
|
if (dwc->revision < DWC3_REVISION_220A) {
|
2012-03-23 12:20:31 +02:00
|
|
|
reg |= DWC3_DCFG_SUPERSPEED;
|
2013-06-30 14:29:51 +03:00
|
|
|
} else {
|
|
|
|
switch (dwc->maximum_speed) {
|
|
|
|
case USB_SPEED_LOW:
|
|
|
|
reg |= DWC3_DSTS_LOWSPEED;
|
|
|
|
break;
|
|
|
|
case USB_SPEED_FULL:
|
|
|
|
reg |= DWC3_DSTS_FULLSPEED1;
|
|
|
|
break;
|
|
|
|
case USB_SPEED_HIGH:
|
|
|
|
reg |= DWC3_DSTS_HIGHSPEED;
|
|
|
|
break;
|
|
|
|
case USB_SPEED_SUPER: /* FALLTHROUGH */
|
|
|
|
case USB_SPEED_UNKNOWN: /* FALTHROUGH */
|
|
|
|
default:
|
|
|
|
reg |= DWC3_DSTS_SUPERSPEED;
|
|
|
|
}
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc3_writel(dwc->regs, DWC3_DCFG, reg);
|
|
|
|
|
2015-04-20 23:25:16 -07:00
|
|
|
/* Programs the number of outstanding pipelined transfer requests
|
|
|
|
* the AXI master pushes to the AXI slave.
|
|
|
|
*/
|
|
|
|
if (dwc->revision >= DWC3_REVISION_270A) {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_GSBUSCFG1);
|
|
|
|
reg &= ~DWC3_GSBUSCFG1_PIPETRANSLIMIT_MASK;
|
|
|
|
reg |= DWC3_GSBUSCFG1_PIPETRANSLIMIT(0xe);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_GSBUSCFG1, reg);
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/* Start with SuperSpeed Default */
|
|
|
|
dwc3_gadget_ep0_desc.wMaxPacketSize = cpu_to_le16(512);
|
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
dwc->delayed_status = false;
|
|
|
|
/* reinitialize physical ep0-1 */
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep = dwc->eps[0];
|
2016-02-02 12:57:37 -08:00
|
|
|
dep->flags = 0;
|
|
|
|
dep->endpoint.maxburst = 1;
|
2013-12-19 12:38:49 -06:00
|
|
|
ret = __dwc3_gadget_ep_enable(dep, &dwc3_gadget_ep0_desc, NULL, false,
|
|
|
|
false);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (ret) {
|
|
|
|
dev_err(dwc->dev, "failed to enable %s\n", dep->name);
|
2016-02-02 12:57:37 -08:00
|
|
|
return ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
dep = dwc->eps[1];
|
2016-02-02 12:57:37 -08:00
|
|
|
dep->flags = 0;
|
|
|
|
dep->endpoint.maxburst = 1;
|
2013-12-19 12:38:49 -06:00
|
|
|
ret = __dwc3_gadget_ep_enable(dep, &dwc3_gadget_ep0_desc, NULL, false,
|
|
|
|
false);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (ret) {
|
|
|
|
dev_err(dwc->dev, "failed to enable %s\n", dep->name);
|
2016-02-02 12:57:37 -08:00
|
|
|
__dwc3_gadget_ep_disable(dwc->eps[0]);
|
|
|
|
return ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* begin to receive SETUP packets */
|
2011-08-27 22:28:36 +03:00
|
|
|
dwc->ep0state = EP0_SETUP_PHASE;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc3_ep0_out_start(dwc);
|
|
|
|
|
2013-02-08 15:24:04 +02:00
|
|
|
dwc3_gadget_enable_irq(dwc);
|
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
return ret;
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
/* Required gadget re-initialization before switching to gadget in OTG mode */
|
|
|
|
void dwc3_gadget_restart(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
__dwc3_gadget_start(dwc);
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
static int dwc3_gadget_start(struct usb_gadget *g,
|
|
|
|
struct usb_gadget_driver *driver)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
|
|
|
unsigned long flags;
|
|
|
|
int ret = 0;
|
2013-06-27 10:00:18 +03:00
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
|
|
|
|
|
|
|
if (dwc->gadget_driver) {
|
|
|
|
dev_err(dwc->dev, "%s is already bound to %s\n",
|
|
|
|
dwc->gadget.name,
|
|
|
|
dwc->gadget_driver->driver.name);
|
|
|
|
ret = -EBUSY;
|
2016-04-14 15:57:10 -07:00
|
|
|
goto err0;
|
2016-02-02 12:57:37 -08:00
|
|
|
}
|
|
|
|
|
|
|
|
dwc->gadget_driver = driver;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* For DRD, this might get called by gadget driver during bootup
|
|
|
|
* even though host mode might be active. Don't actually perform
|
|
|
|
* device-specific initialization until device mode is activated.
|
|
|
|
* In that case dwc3_gadget_restart() will handle it.
|
|
|
|
*/
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
2016-02-02 12:57:37 -08:00
|
|
|
return 0;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2013-06-27 10:00:18 +03:00
|
|
|
err0:
|
2016-04-14 15:57:10 -07:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2014-10-17 12:05:12 -05:00
|
|
|
static int dwc3_gadget_stop(struct usb_gadget *g)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
|
|
|
unsigned long flags;
|
|
|
|
|
2015-08-04 18:45:57 -07:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
|
|
|
dwc->gadget_driver = NULL;
|
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2012-04-27 13:10:52 +03:00
|
|
|
|
2015-08-26 17:18:36 -07:00
|
|
|
static int dwc3_gadget_restart_usb_session(struct usb_gadget *g)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = gadget_to_dwc(g);
|
|
|
|
|
2016-01-29 21:14:24 +05:30
|
|
|
return dwc3_notify_event(dwc, DWC3_CONTROLLER_RESTART_USB_SESSION, 0);
|
2015-08-26 17:18:36 -07:00
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
static const struct usb_gadget_ops dwc3_gadget_ops = {
|
|
|
|
.get_frame = dwc3_gadget_get_frame,
|
|
|
|
.wakeup = dwc3_gadget_wakeup,
|
2014-05-22 16:11:58 +03:00
|
|
|
.func_wakeup = dwc_gadget_func_wakeup,
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
.set_selfpowered = dwc3_gadget_set_selfpowered,
|
2016-02-02 12:57:37 -08:00
|
|
|
.vbus_session = dwc3_gadget_vbus_session,
|
|
|
|
.vbus_draw = dwc3_gadget_vbus_draw,
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
.pullup = dwc3_gadget_pullup,
|
|
|
|
.udc_start = dwc3_gadget_start,
|
|
|
|
.udc_stop = dwc3_gadget_stop,
|
2015-08-26 17:18:36 -07:00
|
|
|
.restart = dwc3_gadget_restart_usb_session,
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
};
|
|
|
|
|
|
|
|
/* -------------------------------------------------------------------------- */
|
|
|
|
|
2016-01-25 12:50:22 -08:00
|
|
|
#define NUM_GSI_OUT_EPS 1
|
|
|
|
#define NUM_GSI_IN_EPS 2
|
|
|
|
|
2011-05-05 16:21:59 +03:00
|
|
|
static int dwc3_gadget_init_hw_endpoints(struct dwc3 *dwc,
|
|
|
|
u8 num, u32 direction)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
2016-01-25 12:50:22 -08:00
|
|
|
u8 i, gsi_ep_count, gsi_ep_index = 0;
|
|
|
|
|
|
|
|
/* Read number of event buffers to check if we need
|
|
|
|
* to update gsi_ep_count. For non GSI targets this
|
|
|
|
* will be 0 and we will skip reservation of GSI eps.
|
|
|
|
* There is one event buffer for each GSI EP.
|
|
|
|
*/
|
|
|
|
gsi_ep_count = dwc->num_gsi_event_buffers;
|
|
|
|
/* OUT GSI EPs based on direction field */
|
|
|
|
if (gsi_ep_count && !direction)
|
|
|
|
gsi_ep_count = NUM_GSI_OUT_EPS;
|
|
|
|
/* IN GSI EPs */
|
|
|
|
else if (gsi_ep_count && direction)
|
|
|
|
gsi_ep_count = NUM_GSI_IN_EPS;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-05-05 16:21:59 +03:00
|
|
|
for (i = 0; i < num; i++) {
|
|
|
|
u8 epnum = (i << 1) | (!!direction);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
dep = kzalloc(sizeof(*dep), GFP_KERNEL);
|
2014-07-17 12:45:11 +09:00
|
|
|
if (!dep)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
dep->dwc = dwc;
|
|
|
|
dep->number = epnum;
|
2013-07-12 19:10:59 +03:00
|
|
|
dep->direction = !!direction;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc->eps[epnum] = dep;
|
|
|
|
|
2016-01-25 12:50:22 -08:00
|
|
|
/* Reserve EPs at the end for GSI based on gsi_ep_count */
|
|
|
|
if ((gsi_ep_index < gsi_ep_count) &&
|
|
|
|
(i > (num - 1 - gsi_ep_count))) {
|
|
|
|
gsi_ep_index++;
|
|
|
|
/* For GSI EPs, name eps as "gsi-epin" or "gsi-epout" */
|
|
|
|
snprintf(dep->name, sizeof(dep->name), "%s",
|
|
|
|
(epnum & 1) ? "gsi-epin" : "gsi-epout");
|
|
|
|
/* Set ep type as GSI */
|
|
|
|
dep->endpoint.ep_type = EP_TYPE_GSI;
|
|
|
|
} else {
|
|
|
|
snprintf(dep->name, sizeof(dep->name), "ep%d%s",
|
|
|
|
epnum >> 1, (epnum & 1) ? "in" : "out");
|
|
|
|
}
|
2011-05-05 16:21:59 +03:00
|
|
|
|
2016-01-25 12:50:22 -08:00
|
|
|
dep->endpoint.ep_num = epnum >> 1;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->endpoint.name = dep->name;
|
|
|
|
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "initializing %s", dep->name);
|
2013-07-12 19:11:57 +03:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (epnum == 0 || epnum == 1) {
|
2013-12-13 12:23:38 +01:00
|
|
|
usb_ep_set_maxpacket_limit(&dep->endpoint, 512);
|
2013-01-18 16:53:56 +05:30
|
|
|
dep->endpoint.maxburst = 1;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->endpoint.ops = &dwc3_gadget_ep0_ops;
|
|
|
|
if (!epnum)
|
|
|
|
dwc->gadget.ep0 = &dep->endpoint;
|
|
|
|
} else {
|
2016-02-16 11:38:23 -08:00
|
|
|
int ret;
|
|
|
|
|
2013-12-13 12:23:38 +01:00
|
|
|
usb_ep_set_maxpacket_limit(&dep->endpoint, 1024);
|
2011-11-03 20:27:50 +01:00
|
|
|
dep->endpoint.max_streams = 15;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->endpoint.ops = &dwc3_gadget_ep_ops;
|
|
|
|
list_add_tail(&dep->endpoint.ep_list,
|
|
|
|
&dwc->gadget.ep_list);
|
2016-02-16 11:38:23 -08:00
|
|
|
|
|
|
|
ret = dwc3_alloc_trb_pool(dep);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
2011-11-04 12:32:47 +02:00
|
|
|
|
2015-07-31 16:00:19 +02:00
|
|
|
if (epnum == 0 || epnum == 1) {
|
|
|
|
dep->endpoint.caps.type_control = true;
|
|
|
|
} else {
|
|
|
|
dep->endpoint.caps.type_iso = true;
|
|
|
|
dep->endpoint.caps.type_bulk = true;
|
|
|
|
dep->endpoint.caps.type_int = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
dep->endpoint.caps.dir_in = !!direction;
|
|
|
|
dep->endpoint.caps.dir_out = !direction;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
INIT_LIST_HEAD(&dep->request_list);
|
|
|
|
INIT_LIST_HEAD(&dep->req_queued);
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2011-05-05 16:21:59 +03:00
|
|
|
static int dwc3_gadget_init_endpoints(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
INIT_LIST_HEAD(&dwc->gadget.ep_list);
|
|
|
|
|
|
|
|
ret = dwc3_gadget_init_hw_endpoints(dwc, dwc->num_out_eps, 0);
|
|
|
|
if (ret < 0) {
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"failed to allocate OUT endpoints");
|
2011-05-05 16:21:59 +03:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = dwc3_gadget_init_hw_endpoints(dwc, dwc->num_in_eps, 1);
|
|
|
|
if (ret < 0) {
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"failed to allocate IN endpoints");
|
2011-05-05 16:21:59 +03:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
static void dwc3_gadget_free_endpoints(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
u8 epnum;
|
|
|
|
|
|
|
|
for (epnum = 0; epnum < DWC3_ENDPOINTS_NUM; epnum++) {
|
|
|
|
dep = dwc->eps[epnum];
|
2011-05-05 16:21:59 +03:00
|
|
|
if (!dep)
|
|
|
|
continue;
|
2013-05-27 14:35:49 +05:30
|
|
|
/*
|
|
|
|
* Physical endpoints 0 and 1 are special; they form the
|
|
|
|
* bi-directional USB endpoint 0.
|
|
|
|
*
|
|
|
|
* For those two physical endpoints, we don't allocate a TRB
|
|
|
|
* pool nor do we add them the endpoints list. Due to that, we
|
|
|
|
* shouldn't do these two operations otherwise we would end up
|
|
|
|
* with all sorts of bugs when removing dwc3.ko.
|
|
|
|
*/
|
|
|
|
if (epnum != 0 && epnum != 1) {
|
2016-02-16 11:38:23 -08:00
|
|
|
dwc3_free_trb_pool(dep);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
list_del(&dep->endpoint.ep_list);
|
2013-05-27 14:35:49 +05:30
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
kfree(dep);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* -------------------------------------------------------------------------- */
|
2013-02-26 15:11:05 +02:00
|
|
|
|
2013-01-14 15:59:37 +05:30
|
|
|
static int __dwc3_cleanup_done_trbs(struct dwc3 *dwc, struct dwc3_ep *dep,
|
2015-03-06 17:58:21 -08:00
|
|
|
struct dwc3_request *req, struct dwc3_trb *trb, unsigned length,
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
const struct dwc3_event_depevt *event, int status)
|
|
|
|
{
|
|
|
|
unsigned int count;
|
|
|
|
unsigned int s_pkt = 0;
|
2012-05-25 18:54:56 +05:30
|
|
|
unsigned int trb_status;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2014-04-30 17:45:10 -05:00
|
|
|
trace_dwc3_complete_trb(dep, trb);
|
|
|
|
|
2013-01-14 15:59:37 +05:30
|
|
|
if ((trb->ctrl & DWC3_TRB_CTRL_HWO) && status != -ESHUTDOWN)
|
|
|
|
/*
|
|
|
|
* We continue despite the error. There is not much we
|
|
|
|
* can do. If we don't clean it up we loop forever. If
|
|
|
|
* we skip the TRB then it gets overwritten after a
|
|
|
|
* while since we use them in a ring buffer. A BUG()
|
|
|
|
* would help. Lets hope that if this occurs, someone
|
|
|
|
* fixes the root cause instead of looking away :)
|
|
|
|
*/
|
2016-11-03 17:15:41 -07:00
|
|
|
dev_err(dwc->dev, "%s's TRB (%pK) still owned by HW\n",
|
2013-01-14 15:59:37 +05:30
|
|
|
dep->name, trb);
|
|
|
|
count = trb->size & DWC3_TRB_SIZE_MASK;
|
|
|
|
|
|
|
|
if (dep->direction) {
|
|
|
|
if (count) {
|
|
|
|
trb_status = DWC3_TRB_SIZE_TRBSTS(trb->size);
|
|
|
|
if (trb_status == DWC3_TRBSTS_MISSED_ISOC) {
|
|
|
|
dev_dbg(dwc->dev, "incomplete IN transfer %s\n",
|
|
|
|
dep->name);
|
|
|
|
/*
|
|
|
|
* If missed isoc occurred and there is
|
|
|
|
* no request queued then issue END
|
|
|
|
* TRANSFER, so that core generates
|
|
|
|
* next xfernotready and we will issue
|
|
|
|
* a fresh START TRANSFER.
|
|
|
|
* If there are still queued request
|
|
|
|
* then wait, do not issue either END
|
|
|
|
* or UPDATE TRANSFER, just attach next
|
|
|
|
* request in request_list during
|
|
|
|
* giveback.If any future queued request
|
|
|
|
* is successfully transferred then we
|
|
|
|
* will issue UPDATE TRANSFER for all
|
|
|
|
* request in the request_list.
|
|
|
|
*/
|
|
|
|
dep->flags |= DWC3_EP_MISSED_ISOC;
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(dep->number, "MISSED ISOC", status);
|
2013-01-14 15:59:37 +05:30
|
|
|
} else {
|
|
|
|
dev_err(dwc->dev, "incomplete IN transfer %s\n",
|
|
|
|
dep->name);
|
|
|
|
status = -ECONNRESET;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
dep->flags &= ~DWC3_EP_MISSED_ISOC;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
if (count && (event->status & DEPEVT_STATUS_SHORT))
|
|
|
|
s_pkt = 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We assume here we will always receive the entire data block
|
|
|
|
* which we should receive. Meaning, if we program RX to
|
|
|
|
* receive 4K but we receive only 2K, we assume that's all we
|
|
|
|
* should receive and we simply bounce the request back to the
|
|
|
|
* gadget driver for further processing.
|
|
|
|
*/
|
2015-03-06 17:58:21 -08:00
|
|
|
req->request.actual += length - count;
|
2013-01-14 15:59:37 +05:30
|
|
|
if (s_pkt)
|
|
|
|
return 1;
|
|
|
|
if ((event->status & DEPEVT_STATUS_LST) &&
|
|
|
|
(trb->ctrl & (DWC3_TRB_CTRL_LST |
|
|
|
|
DWC3_TRB_CTRL_HWO)))
|
|
|
|
return 1;
|
|
|
|
if ((event->status & DEPEVT_STATUS_IOC) &&
|
|
|
|
(trb->ctrl & DWC3_TRB_CTRL_IOC))
|
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int dwc3_cleanup_done_reqs(struct dwc3 *dwc, struct dwc3_ep *dep,
|
|
|
|
const struct dwc3_event_depevt *event, int status)
|
|
|
|
{
|
|
|
|
struct dwc3_request *req;
|
|
|
|
struct dwc3_trb *trb;
|
|
|
|
unsigned int slot;
|
|
|
|
unsigned int i;
|
2015-03-06 17:58:21 -08:00
|
|
|
unsigned int trb_len;
|
2013-01-14 15:59:37 +05:30
|
|
|
int ret;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
do {
|
2015-08-31 19:48:28 +03:00
|
|
|
req = next_request(&dep->req_queued);
|
|
|
|
if (!req) {
|
2014-10-31 14:04:04 -07:00
|
|
|
dev_err(dwc->dev, "%s: evt sts %x for no req queued",
|
|
|
|
dep->name, event->status);
|
2015-08-31 19:48:28 +03:00
|
|
|
return 1;
|
|
|
|
}
|
2015-06-27 18:39:18 -07:00
|
|
|
|
|
|
|
/* Make sure that not to queue any TRB if HWO bit is set. */
|
|
|
|
if (req->trb->ctrl & DWC3_TRB_CTRL_HWO)
|
|
|
|
return 0;
|
|
|
|
|
2015-08-31 19:48:28 +03:00
|
|
|
i = 0;
|
|
|
|
do {
|
|
|
|
slot = req->start_slot + i;
|
|
|
|
if ((slot == DWC3_TRB_NUM - 1) &&
|
2013-01-14 15:59:37 +05:30
|
|
|
usb_endpoint_xfer_isoc(dep->endpoint.desc))
|
2015-08-31 19:48:28 +03:00
|
|
|
slot++;
|
|
|
|
slot %= DWC3_TRB_NUM;
|
|
|
|
trb = &dep->trb_pool[slot];
|
|
|
|
|
2015-03-06 17:58:21 -08:00
|
|
|
if (req->request.num_mapped_sgs)
|
|
|
|
trb_len = sg_dma_len(&req->request.sg[i]);
|
|
|
|
else
|
|
|
|
trb_len = req->request.length;
|
|
|
|
|
2015-08-31 19:48:28 +03:00
|
|
|
ret = __dwc3_cleanup_done_trbs(dwc, dep, req, trb,
|
2015-03-06 17:58:21 -08:00
|
|
|
trb_len, event, status);
|
2015-08-31 19:48:28 +03:00
|
|
|
if (ret)
|
|
|
|
break;
|
|
|
|
} while (++i < req->request.num_mapped_sgs);
|
|
|
|
|
|
|
|
dwc3_gadget_giveback(dep, req, status);
|
2013-01-14 15:59:37 +05:30
|
|
|
|
2014-03-10 23:40:58 -07:00
|
|
|
/* EP possibly disabled during giveback? */
|
|
|
|
if (!(dep->flags & DWC3_EP_ENABLED)) {
|
|
|
|
dev_dbg(dwc->dev, "%s disabled while handling ep event\n",
|
|
|
|
dep->name);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-01-14 15:59:37 +05:30
|
|
|
if (ret)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
2015-08-31 19:48:28 +03:00
|
|
|
} while (1);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2013-01-14 15:59:34 +05:30
|
|
|
if (usb_endpoint_xfer_isoc(dep->endpoint.desc) &&
|
|
|
|
list_empty(&dep->req_queued)) {
|
2013-01-30 17:35:45 +05:30
|
|
|
if (list_empty(&dep->request_list))
|
2013-01-14 15:59:34 +05:30
|
|
|
/*
|
|
|
|
* If there is no entry in request list then do
|
|
|
|
* not issue END TRANSFER now. Just set PENDING
|
|
|
|
* flag, so that END TRANSFER is issued when an
|
|
|
|
* entry is added into request list.
|
|
|
|
*/
|
2013-01-30 17:35:45 +05:30
|
|
|
dep->flags |= DWC3_EP_PENDING_REQUEST;
|
|
|
|
else
|
2012-04-27 14:17:35 +03:00
|
|
|
dwc3_stop_active_transfer(dwc, dep->number, true);
|
2013-01-30 17:35:45 +05:30
|
|
|
dep->flags &= ~DWC3_EP_MISSED_ISOC;
|
2013-01-14 15:59:32 +05:30
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2015-06-27 14:54:14 -07:00
|
|
|
if ((event->status & DEPEVT_STATUS_IOC) &&
|
|
|
|
(trb->ctrl & DWC3_TRB_CTRL_IOC))
|
|
|
|
return 0;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_endpoint_transfer_complete(struct dwc3 *dwc,
|
2014-07-04 15:00:51 +09:00
|
|
|
struct dwc3_ep *dep, const struct dwc3_event_depevt *event)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
unsigned status = 0;
|
|
|
|
int clean_busy;
|
2015-05-29 10:06:38 -05:00
|
|
|
u32 is_xfer_complete;
|
|
|
|
|
|
|
|
is_xfer_complete = (event->endpoint_event == DWC3_DEPEVT_XFERCOMPLETE);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
if (event->status & DEPEVT_STATUS_BUSERR)
|
|
|
|
status = -ECONNRESET;
|
|
|
|
|
2012-02-15 18:56:56 -08:00
|
|
|
clean_busy = dwc3_cleanup_done_reqs(dwc, dep, event, status);
|
2015-05-29 10:06:38 -05:00
|
|
|
if (clean_busy && (is_xfer_complete ||
|
|
|
|
usb_endpoint_xfer_isoc(dep->endpoint.desc)))
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep->flags &= ~DWC3_EP_BUSY;
|
2011-10-14 13:00:30 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* WORKAROUND: This is the 2nd half of U1/U2 -> U0 workaround.
|
|
|
|
* See dwc3_gadget_linksts_change_interrupt() for 1st half.
|
|
|
|
*/
|
|
|
|
if (dwc->revision < DWC3_REVISION_183A) {
|
|
|
|
u32 reg;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < DWC3_ENDPOINTS_NUM; i++) {
|
2012-08-01 14:08:30 -05:00
|
|
|
dep = dwc->eps[i];
|
2011-10-14 13:00:30 +03:00
|
|
|
|
|
|
|
if (!(dep->flags & DWC3_EP_ENABLED))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
if (!list_empty(&dep->req_queued))
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
reg |= dwc->u1u2;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
|
|
|
|
dwc->u1u2 = 0;
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_endpoint_interrupt(struct dwc3 *dwc,
|
|
|
|
const struct dwc3_event_depevt *event)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
u8 epnum = event->endpoint_number;
|
|
|
|
|
|
|
|
dep = dwc->eps[epnum];
|
|
|
|
|
2012-06-06 09:19:35 +03:00
|
|
|
if (!(dep->flags & DWC3_EP_ENABLED))
|
|
|
|
return;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (epnum == 0 || epnum == 1) {
|
|
|
|
dwc3_ep0_interrupt(dwc, event);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2014-02-28 11:04:38 -08:00
|
|
|
dep->dbg_ep_events.total++;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
switch (event->endpoint_event) {
|
|
|
|
case DWC3_DEPEVT_XFERCOMPLETE:
|
2012-06-06 12:04:13 +03:00
|
|
|
dep->resource_index = 0;
|
2014-02-28 11:04:38 -08:00
|
|
|
dep->dbg_ep_events.xfercomplete++;
|
2012-02-24 17:32:18 -08:00
|
|
|
|
2012-03-12 20:25:24 +02:00
|
|
|
if (usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dev_dbg(dwc->dev, "%s is an Isochronous endpoint\n",
|
|
|
|
dep->name);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2014-07-04 15:00:51 +09:00
|
|
|
dwc3_endpoint_transfer_complete(dwc, dep, event);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEPEVT_XFERINPROGRESS:
|
2014-02-28 11:04:38 -08:00
|
|
|
dep->dbg_ep_events.xferinprogress++;
|
2015-09-28 20:01:21 -07:00
|
|
|
if (!usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
|
|
|
dev_dbg(dwc->dev, "%s is not an Isochronous endpoint\n",
|
|
|
|
dep->name);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2014-07-04 15:00:51 +09:00
|
|
|
dwc3_endpoint_transfer_complete(dwc, dep, event);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEPEVT_XFERNOTREADY:
|
2014-02-28 11:04:38 -08:00
|
|
|
dep->dbg_ep_events.xfernotready++;
|
2012-03-12 20:25:24 +02:00
|
|
|
if (usb_endpoint_xfer_isoc(dep->endpoint.desc)) {
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc3_gadget_start_isoc(dwc, dep, event);
|
|
|
|
} else {
|
|
|
|
int ret;
|
|
|
|
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "%s: reason %s",
|
2016-09-09 18:17:51 -07:00
|
|
|
dep->name, event->status &
|
|
|
|
DEPEVT_STATUS_TRANSFER_ACTIVE
|
|
|
|
? "Transfer Active"
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
: "Transfer Not Active");
|
|
|
|
|
2015-06-27 19:02:44 -07:00
|
|
|
/*
|
|
|
|
* If XFERNOTREADY interrupt is received with event
|
|
|
|
* status as TRANSFER ACTIVE, don't kick next transfer.
|
|
|
|
* otherwise data stall is seen on that endpoint.
|
|
|
|
*/
|
|
|
|
if (event->status & DEPEVT_STATUS_TRANSFER_ACTIVE)
|
|
|
|
return;
|
|
|
|
|
2016-09-09 18:17:51 -07:00
|
|
|
ret = __dwc3_gadget_kick_transfer(dep, 0, 1);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (!ret || ret == -EBUSY)
|
|
|
|
return;
|
|
|
|
|
|
|
|
dev_dbg(dwc->dev, "%s: failed to kick transfers\n",
|
|
|
|
dep->name);
|
|
|
|
}
|
|
|
|
|
2011-09-30 10:58:47 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEPEVT_STREAMEVT:
|
2014-02-28 11:04:38 -08:00
|
|
|
dep->dbg_ep_events.streamevent++;
|
2012-03-12 20:25:24 +02:00
|
|
|
if (!usb_endpoint_xfer_bulk(dep->endpoint.desc)) {
|
2011-09-30 10:58:47 +03:00
|
|
|
dev_err(dwc->dev, "Stream event for non-Bulk %s\n",
|
|
|
|
dep->name);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (event->status) {
|
|
|
|
case DEPEVT_STREAMEVT_FOUND:
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"Stream %d found and started",
|
2011-09-30 10:58:47 +03:00
|
|
|
event->parameters);
|
|
|
|
|
|
|
|
break;
|
|
|
|
case DEPEVT_STREAMEVT_NOTFOUND:
|
|
|
|
/* FALLTHROUGH */
|
|
|
|
default:
|
|
|
|
dev_dbg(dwc->dev, "Couldn't find suitable stream\n");
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEPEVT_RXTXFIFOEVT:
|
|
|
|
dev_dbg(dwc->dev, "%s FIFO Overrun\n", dep->name);
|
2014-02-28 11:04:38 -08:00
|
|
|
dep->dbg_ep_events.rxtxfifoevent++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEPEVT_EPCMDCMPLT:
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "Endpoint Command Complete");
|
2014-02-28 11:04:38 -08:00
|
|
|
dep->dbg_ep_events.epcmdcomplete++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_disconnect_gadget(struct dwc3 *dwc)
|
|
|
|
{
|
2017-11-15 09:57:15 -08:00
|
|
|
struct usb_gadget_driver *gadget_driver;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (dwc->gadget_driver && dwc->gadget_driver->disconnect) {
|
2017-11-15 09:57:15 -08:00
|
|
|
gadget_driver = dwc->gadget_driver;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_unlock(&dwc->lock);
|
2017-11-15 09:57:15 -08:00
|
|
|
dbg_event(0xFF, "DISCONNECT", 0);
|
|
|
|
gadget_driver->disconnect(&dwc->gadget);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
spin_lock(&dwc->lock);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-26 10:17:07 -06:00
|
|
|
static void dwc3_suspend_gadget(struct dwc3 *dwc)
|
|
|
|
{
|
2017-11-15 09:57:15 -08:00
|
|
|
struct usb_gadget_driver *gadget_driver;
|
|
|
|
|
2014-03-07 14:19:57 +03:00
|
|
|
if (dwc->gadget_driver && dwc->gadget_driver->suspend) {
|
2017-11-15 09:57:15 -08:00
|
|
|
gadget_driver = dwc->gadget_driver;
|
2014-02-26 10:17:07 -06:00
|
|
|
spin_unlock(&dwc->lock);
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(0xFF, "SUSPEND", 0);
|
2017-11-15 09:57:15 -08:00
|
|
|
gadget_driver->suspend(&dwc->gadget);
|
2014-02-26 10:17:07 -06:00
|
|
|
spin_lock(&dwc->lock);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_resume_gadget(struct dwc3 *dwc)
|
|
|
|
{
|
2017-11-15 09:57:15 -08:00
|
|
|
struct usb_gadget_driver *gadget_driver;
|
|
|
|
|
2014-03-07 14:19:57 +03:00
|
|
|
if (dwc->gadget_driver && dwc->gadget_driver->resume) {
|
2017-11-15 09:57:15 -08:00
|
|
|
gadget_driver = dwc->gadget_driver;
|
2014-02-26 10:17:07 -06:00
|
|
|
spin_unlock(&dwc->lock);
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(0xFF, "RESUME", 0);
|
2017-11-15 09:57:15 -08:00
|
|
|
gadget_driver->resume(&dwc->gadget);
|
2015-01-29 10:29:18 -06:00
|
|
|
spin_lock(&dwc->lock);
|
2014-11-06 14:27:53 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_reset_gadget(struct dwc3 *dwc)
|
|
|
|
{
|
2017-11-15 09:57:15 -08:00
|
|
|
struct usb_gadget_driver *gadget_driver;
|
|
|
|
|
2014-11-06 14:27:53 +08:00
|
|
|
if (!dwc->gadget_driver)
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (dwc->gadget.speed != USB_SPEED_UNKNOWN) {
|
2017-11-15 09:57:15 -08:00
|
|
|
gadget_driver = dwc->gadget_driver;
|
2014-11-06 14:27:53 +08:00
|
|
|
spin_unlock(&dwc->lock);
|
2017-11-15 09:57:15 -08:00
|
|
|
dbg_event(0xFF, "UDC RESET", 0);
|
|
|
|
usb_gadget_udc_reset(&dwc->gadget, gadget_driver);
|
2014-02-26 10:17:07 -06:00
|
|
|
spin_lock(&dwc->lock);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-10-09 19:36:21 -07:00
|
|
|
void dwc3_stop_active_transfer(struct dwc3 *dwc, u32 epnum, bool force)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
struct dwc3_gadget_ep_cmd_params params;
|
|
|
|
u32 cmd;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
dep = dwc->eps[epnum];
|
|
|
|
|
2012-06-06 12:04:13 +03:00
|
|
|
if (!dep->resource_index)
|
2012-06-23 02:23:08 +05:30
|
|
|
return;
|
|
|
|
|
2016-01-29 21:14:24 +05:30
|
|
|
if (dep->endpoint.endless)
|
|
|
|
dwc3_notify_event(dwc, DWC3_CONTROLLER_NOTIFY_DISABLE_UPDXFER,
|
|
|
|
dep->number);
|
|
|
|
|
2012-07-06 15:19:10 +05:30
|
|
|
/*
|
|
|
|
* NOTICE: We are violating what the Databook says about the
|
|
|
|
* EndTransfer command. Ideally we would _always_ wait for the
|
|
|
|
* EndTransfer Command Completion IRQ, but that's causing too
|
|
|
|
* much trouble synchronizing between us and gadget driver.
|
|
|
|
*
|
|
|
|
* We have discussed this with the IP Provider and it was
|
|
|
|
* suggested to giveback all requests here, but give HW some
|
|
|
|
* extra time to synchronize with the interconnect. We're using
|
2014-12-23 17:34:43 +01:00
|
|
|
* an arbitrary 100us delay for that.
|
2012-07-06 15:19:10 +05:30
|
|
|
*
|
|
|
|
* Note also that a similar handling was tested by Synopsys
|
|
|
|
* (thanks a lot Paul) and nothing bad has come out of it.
|
|
|
|
* In short, what we're doing is:
|
|
|
|
*
|
|
|
|
* - Issue EndTransfer WITH CMDIOC bit set
|
|
|
|
* - Wait 100us
|
|
|
|
*/
|
|
|
|
|
2012-06-23 02:23:08 +05:30
|
|
|
cmd = DWC3_DEPCMD_ENDTRANSFER;
|
2012-04-27 14:17:35 +03:00
|
|
|
cmd |= force ? DWC3_DEPCMD_HIPRI_FORCERM : 0;
|
|
|
|
cmd |= DWC3_DEPCMD_CMDIOC;
|
2012-06-06 12:04:13 +03:00
|
|
|
cmd |= DWC3_DEPCMD_PARAM(dep->resource_index);
|
2012-06-23 02:23:08 +05:30
|
|
|
memset(¶ms, 0, sizeof(params));
|
|
|
|
ret = dwc3_send_gadget_ep_cmd(dwc, dep->number, cmd, ¶ms);
|
|
|
|
WARN_ON_ONCE(ret);
|
2012-06-06 12:04:13 +03:00
|
|
|
dep->resource_index = 0;
|
2012-10-04 11:58:00 +03:00
|
|
|
dep->flags &= ~DWC3_EP_BUSY;
|
2012-07-06 15:19:10 +05:30
|
|
|
udelay(100);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_stop_active_transfers(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
u32 epnum;
|
|
|
|
|
|
|
|
for (epnum = 2; epnum < DWC3_ENDPOINTS_NUM; epnum++) {
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
|
|
|
|
dep = dwc->eps[epnum];
|
2011-05-05 16:21:59 +03:00
|
|
|
if (!dep)
|
|
|
|
continue;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (!(dep->flags & DWC3_EP_ENABLED))
|
|
|
|
continue;
|
|
|
|
|
2011-08-29 13:56:37 +02:00
|
|
|
dwc3_remove_requests(dwc, dep);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_clear_stall_all_ep(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
u32 epnum;
|
|
|
|
|
|
|
|
for (epnum = 1; epnum < DWC3_ENDPOINTS_NUM; epnum++) {
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
struct dwc3_gadget_ep_cmd_params params;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
dep = dwc->eps[epnum];
|
2011-05-05 16:21:59 +03:00
|
|
|
if (!dep)
|
|
|
|
continue;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
if (!(dep->flags & DWC3_EP_STALL))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
dep->flags &= ~DWC3_EP_STALL;
|
|
|
|
|
|
|
|
memset(¶ms, 0, sizeof(params));
|
|
|
|
ret = dwc3_send_gadget_ep_cmd(dwc, dep->number,
|
|
|
|
DWC3_DEPCMD_CLEARSTALL, ¶ms);
|
2014-10-31 14:04:04 -07:00
|
|
|
if (ret) {
|
|
|
|
dev_dbg(dwc->dev, "%s; send ep cmd CLEARSTALL failed",
|
|
|
|
dep->name);
|
|
|
|
dbg_event(dep->number, "ECLRSTALL", ret);
|
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_gadget_disconnect_interrupt(struct dwc3 *dwc)
|
|
|
|
{
|
2012-05-24 10:30:01 +03:00
|
|
|
int reg;
|
|
|
|
|
2015-04-11 00:56:27 -07:00
|
|
|
dev_dbg(dwc->dev, "Notify OTG from %s\n", __func__);
|
|
|
|
dwc->b_suspend = false;
|
2016-01-29 21:14:24 +05:30
|
|
|
dwc3_notify_event(dwc, DWC3_CONTROLLER_NOTIFY_OTG_EVENT, 0);
|
2015-04-11 00:56:27 -07:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
reg &= ~DWC3_DCTL_INITU1ENA;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
|
|
|
|
reg &= ~DWC3_DCTL_INITU2ENA;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(0xFF, "DISCONNECT", 0);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc3_disconnect_gadget(dwc);
|
|
|
|
|
|
|
|
dwc->gadget.speed = USB_SPEED_UNKNOWN;
|
2011-10-14 15:11:49 +03:00
|
|
|
dwc->setup_packet_pending = false;
|
2014-10-24 19:18:58 -07:00
|
|
|
dwc->link_state = DWC3_LINK_STATE_SS_DIS;
|
2014-10-10 15:24:00 -05:00
|
|
|
usb_gadget_set_state(&dwc->gadget, USB_STATE_NOTATTACHED);
|
2014-11-25 15:29:58 -08:00
|
|
|
wake_up_interruptible(&dwc->wait_linkstate);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_gadget_reset_interrupt(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
u32 reg;
|
|
|
|
|
2011-10-14 15:11:49 +03:00
|
|
|
/*
|
|
|
|
* WORKAROUND: DWC3 revisions <1.88a have an issue which
|
|
|
|
* would cause a missing Disconnect Event if there's a
|
|
|
|
* pending Setup Packet in the FIFO.
|
|
|
|
*
|
|
|
|
* There's no suggested workaround on the official Bug
|
|
|
|
* report, which states that "unless the driver/application
|
|
|
|
* is doing any special handling of a disconnect event,
|
|
|
|
* there is no functional issue".
|
|
|
|
*
|
|
|
|
* Unfortunately, it turns out that we _do_ some special
|
|
|
|
* handling of a disconnect event, namely complete all
|
|
|
|
* pending transfers, notify gadget driver of the
|
|
|
|
* disconnection, and so on.
|
|
|
|
*
|
|
|
|
* Our suggested workaround is to follow the Disconnect
|
|
|
|
* Event steps here, instead, based on a setup_packet_pending
|
|
|
|
* flag. Such flag gets set whenever we have a XferNotReady
|
|
|
|
* event on EP0 and gets cleared on XferComplete for the
|
|
|
|
* same endpoint.
|
|
|
|
*
|
|
|
|
* Refers to:
|
|
|
|
*
|
|
|
|
* STAR#9000466709: RTL: Device : Disconnect event not
|
|
|
|
* generated if setup packet pending in FIFO
|
|
|
|
*/
|
|
|
|
if (dwc->revision < DWC3_REVISION_188A) {
|
|
|
|
if (dwc->setup_packet_pending)
|
|
|
|
dwc3_gadget_disconnect_interrupt(dwc);
|
|
|
|
}
|
|
|
|
|
2015-04-11 00:56:27 -07:00
|
|
|
dev_dbg(dwc->dev, "Notify OTG from %s\n", __func__);
|
|
|
|
dwc->b_suspend = false;
|
2016-01-29 21:14:24 +05:30
|
|
|
dwc3_notify_event(dwc, DWC3_CONTROLLER_NOTIFY_OTG_EVENT, 0);
|
2015-04-11 00:56:27 -07:00
|
|
|
|
2016-02-01 23:48:15 -08:00
|
|
|
dwc3_usb3_phy_suspend(dwc, false);
|
|
|
|
|
2014-11-06 14:27:53 +08:00
|
|
|
dwc3_reset_gadget(dwc);
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(0xFF, "BUS RST", 0);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
reg &= ~DWC3_DCTL_TSTCTRL_MASK;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
2012-02-10 12:21:18 +02:00
|
|
|
dwc->test_mode = false;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2017-11-16 17:00:09 +05:30
|
|
|
/*
|
|
|
|
* From SNPS databook section 8.1.2
|
|
|
|
* the EP0 should be in setup phase. So ensure
|
|
|
|
* that EP0 is in setup phase by issuing a stall
|
|
|
|
* and restart if EP0 is not in setup phase.
|
|
|
|
*/
|
|
|
|
if (dwc->ep0state != EP0_SETUP_PHASE)
|
|
|
|
dwc3_ep0_stall_and_restart(dwc);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc3_stop_active_transfers(dwc);
|
|
|
|
dwc3_clear_stall_all_ep(dwc);
|
|
|
|
|
2014-10-30 11:43:35 -07:00
|
|
|
/* bus reset issued due to missing status stage of a control transfer */
|
|
|
|
dwc->resize_fifos = 0;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/* Reset device address to zero */
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCFG);
|
|
|
|
reg &= ~(DWC3_DCFG_DEVADDR_MASK);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCFG, reg);
|
2014-08-28 16:47:51 -07:00
|
|
|
dwc->gadget.speed = USB_SPEED_UNKNOWN;
|
2014-10-24 19:18:58 -07:00
|
|
|
dwc->link_state = DWC3_LINK_STATE_U0;
|
2014-11-25 15:29:58 -08:00
|
|
|
wake_up_interruptible(&dwc->wait_linkstate);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_update_ram_clk_sel(struct dwc3 *dwc, u32 speed)
|
|
|
|
{
|
|
|
|
u32 reg;
|
|
|
|
u32 usb30_clock = DWC3_GCTL_CLK_BUS;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We change the clock only at SS but I dunno why I would want to do
|
|
|
|
* this. Maybe it becomes part of the power saving plan.
|
|
|
|
*/
|
|
|
|
|
|
|
|
if (speed != DWC3_DSTS_SUPERSPEED)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* RAMClkSel is reset to 0 after USB reset, so it must be reprogrammed
|
|
|
|
* each time on Connect Done.
|
|
|
|
*/
|
|
|
|
if (!usb30_clock)
|
|
|
|
return;
|
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_GCTL);
|
|
|
|
reg |= DWC3_GCTL_RAMCLKSEL(usb30_clock);
|
|
|
|
dwc3_writel(dwc->regs, DWC3_GCTL, reg);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_gadget_conndone_interrupt(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
int ret;
|
|
|
|
u32 reg;
|
|
|
|
u8 speed;
|
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DSTS);
|
|
|
|
speed = reg & DWC3_DSTS_CONNECTSPD;
|
|
|
|
dwc->speed = speed;
|
|
|
|
|
|
|
|
dwc3_update_ram_clk_sel(dwc, speed);
|
|
|
|
|
|
|
|
switch (speed) {
|
|
|
|
case DWC3_DCFG_SUPERSPEED:
|
2011-10-14 14:51:38 +03:00
|
|
|
/*
|
|
|
|
* WORKAROUND: DWC3 revisions <1.90a have an issue which
|
|
|
|
* would cause a missing USB3 Reset event.
|
|
|
|
*
|
|
|
|
* In such situations, we should force a USB3 Reset
|
|
|
|
* event by calling our dwc3_gadget_reset_interrupt()
|
|
|
|
* routine.
|
|
|
|
*
|
|
|
|
* Refers to:
|
|
|
|
*
|
|
|
|
* STAR#9000483510: RTL: SS : USB3 reset event may
|
|
|
|
* not be generated always when the link enters poll
|
|
|
|
*/
|
|
|
|
if (dwc->revision < DWC3_REVISION_190A)
|
|
|
|
dwc3_gadget_reset_interrupt(dwc);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc3_gadget_ep0_desc.wMaxPacketSize = cpu_to_le16(512);
|
|
|
|
dwc->gadget.ep0->maxpacket = 512;
|
|
|
|
dwc->gadget.speed = USB_SPEED_SUPER;
|
|
|
|
break;
|
|
|
|
case DWC3_DCFG_HIGHSPEED:
|
|
|
|
dwc3_gadget_ep0_desc.wMaxPacketSize = cpu_to_le16(64);
|
|
|
|
dwc->gadget.ep0->maxpacket = 64;
|
|
|
|
dwc->gadget.speed = USB_SPEED_HIGH;
|
|
|
|
break;
|
|
|
|
case DWC3_DCFG_FULLSPEED2:
|
|
|
|
case DWC3_DCFG_FULLSPEED1:
|
|
|
|
dwc3_gadget_ep0_desc.wMaxPacketSize = cpu_to_le16(64);
|
|
|
|
dwc->gadget.ep0->maxpacket = 64;
|
|
|
|
dwc->gadget.speed = USB_SPEED_FULL;
|
|
|
|
break;
|
|
|
|
case DWC3_DCFG_LOWSPEED:
|
|
|
|
dwc3_gadget_ep0_desc.wMaxPacketSize = cpu_to_le16(8);
|
|
|
|
dwc->gadget.ep0->maxpacket = 8;
|
|
|
|
dwc->gadget.speed = USB_SPEED_LOW;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2018-01-12 18:18:05 -08:00
|
|
|
dwc->eps[1]->endpoint.maxpacket = dwc->gadget.ep0->maxpacket;
|
|
|
|
|
2013-01-14 15:59:31 +05:30
|
|
|
/* Enable USB2 LPM Capability */
|
|
|
|
|
|
|
|
if ((dwc->revision > DWC3_REVISION_194A)
|
|
|
|
&& (speed != DWC3_DCFG_SUPERSPEED)) {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCFG);
|
|
|
|
reg |= DWC3_DCFG_LPM_CAP;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCFG, reg);
|
|
|
|
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
reg &= ~(DWC3_DCTL_HIRD_THRES_MASK | DWC3_DCTL_L1_HIBER_EN);
|
|
|
|
|
2014-10-31 11:11:18 +08:00
|
|
|
reg |= DWC3_DCTL_HIRD_THRES(dwc->hird_threshold);
|
2013-01-14 15:59:31 +05:30
|
|
|
|
2014-10-28 19:54:26 +08:00
|
|
|
/*
|
|
|
|
* When dwc3 revisions >= 2.40a, LPM Erratum is enabled and
|
|
|
|
* DCFG.LPMCap is set, core responses with an ACK and the
|
|
|
|
* BESL value in the LPM token is less than or equal to LPM
|
|
|
|
* NYET threshold.
|
|
|
|
*/
|
|
|
|
WARN_ONCE(dwc->revision < DWC3_REVISION_240A
|
|
|
|
&& dwc->has_lpm_erratum,
|
|
|
|
"LPM Erratum not available on dwc3 revisisions < 2.40a\n");
|
|
|
|
|
|
|
|
if (dwc->has_lpm_erratum && dwc->revision >= DWC3_REVISION_240A)
|
|
|
|
reg |= DWC3_DCTL_LPM_ERRATA(dwc->lpm_nyet_threshold);
|
|
|
|
|
2013-12-19 16:37:05 -06:00
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
} else {
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
reg &= ~DWC3_DCTL_HIRD_THRES_MASK;
|
2013-01-14 15:59:31 +05:30
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
}
|
|
|
|
|
2016-02-01 23:48:15 -08:00
|
|
|
/*
|
|
|
|
* In HS mode this allows SS phy suspend. In SS mode this allows ss phy
|
|
|
|
* suspend in P3 state and generates IN_P3 power event irq.
|
|
|
|
*/
|
|
|
|
dwc3_usb3_phy_suspend(dwc, true);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dep = dwc->eps[0];
|
2013-12-19 12:38:49 -06:00
|
|
|
ret = __dwc3_gadget_ep_enable(dep, &dwc3_gadget_ep0_desc, NULL, true,
|
|
|
|
false);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (ret) {
|
|
|
|
dev_err(dwc->dev, "failed to enable %s\n", dep->name);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
dep = dwc->eps[1];
|
2013-12-19 12:38:49 -06:00
|
|
|
ret = __dwc3_gadget_ep_enable(dep, &dwc3_gadget_ep0_desc, NULL, true,
|
|
|
|
false);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (ret) {
|
|
|
|
dev_err(dwc->dev, "failed to enable %s\n", dep->name);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2016-01-29 21:14:24 +05:30
|
|
|
dwc3_notify_event(dwc, DWC3_CONTROLLER_CONNDONE_EVENT, 0);
|
2015-04-11 00:56:27 -07:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/*
|
|
|
|
* Configure PHY via GUSB3PIPECTLn if required.
|
|
|
|
*
|
|
|
|
* Update GTXFIFOSIZn
|
|
|
|
*
|
|
|
|
* In both cases reset values should be sufficient.
|
|
|
|
*/
|
|
|
|
}
|
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
static void dwc3_gadget_wakeup_interrupt(struct dwc3 *dwc, bool remote_wakeup)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
2014-11-25 15:29:58 -08:00
|
|
|
bool perform_resume = true;
|
|
|
|
|
2014-10-24 19:18:58 -07:00
|
|
|
dev_dbg(dwc->dev, "%s\n", __func__);
|
2015-04-11 00:56:27 -07:00
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
/*
|
|
|
|
* Identify if it is called from wakeup_interrupt() context for bus
|
|
|
|
* resume or as part of remote wakeup. And based on that check for
|
|
|
|
* U3 state. as we need to handle case of L1 resume i.e. where we
|
|
|
|
* don't want to perform resume.
|
|
|
|
*/
|
|
|
|
if (!remote_wakeup && dwc->link_state != DWC3_LINK_STATE_U3)
|
|
|
|
perform_resume = false;
|
|
|
|
|
2014-10-24 19:18:58 -07:00
|
|
|
/* Only perform resume from L2 or Early Suspend states */
|
2014-11-25 15:29:58 -08:00
|
|
|
if (perform_resume) {
|
2014-10-24 19:18:58 -07:00
|
|
|
dbg_event(0xFF, "WAKEUP", 0);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* In case of remote wake up dwc3_gadget_wakeup_work()
|
|
|
|
* is doing pm_runtime_get_sync().
|
|
|
|
*/
|
|
|
|
dev_dbg(dwc->dev, "Notify OTG from %s\n", __func__);
|
|
|
|
dwc->b_suspend = false;
|
2016-01-29 21:14:24 +05:30
|
|
|
dwc3_notify_event(dwc,
|
|
|
|
DWC3_CONTROLLER_NOTIFY_OTG_EVENT, 0);
|
2014-10-24 19:18:58 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* set state to U0 as function level resume is trying to queue
|
|
|
|
* notification over USB interrupt endpoint which would fail
|
|
|
|
* due to state is not being updated.
|
|
|
|
*/
|
|
|
|
dwc->link_state = DWC3_LINK_STATE_U0;
|
|
|
|
dwc3_resume_gadget(dwc);
|
|
|
|
return;
|
|
|
|
}
|
2015-04-11 00:56:27 -07:00
|
|
|
|
2014-10-24 19:18:58 -07:00
|
|
|
dwc->link_state = DWC3_LINK_STATE_U0;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_gadget_linksts_change_interrupt(struct dwc3 *dwc,
|
|
|
|
unsigned int evtinfo)
|
|
|
|
{
|
2011-10-14 13:00:30 +03:00
|
|
|
enum dwc3_link_state next = evtinfo & DWC3_LINK_STATE_MASK;
|
2012-09-18 21:39:24 +03:00
|
|
|
unsigned int pwropt;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* WORKAROUND: DWC3 < 2.50a have an issue when configured without
|
|
|
|
* Hibernation mode enabled which would show up when device detects
|
|
|
|
* host-initiated U3 exit.
|
|
|
|
*
|
|
|
|
* In that case, device will generate a Link State Change Interrupt
|
|
|
|
* from U3 to RESUME which is only necessary if Hibernation is
|
|
|
|
* configured in.
|
|
|
|
*
|
|
|
|
* There are no functional changes due to such spurious event and we
|
|
|
|
* just need to ignore it.
|
|
|
|
*
|
|
|
|
* Refers to:
|
|
|
|
*
|
|
|
|
* STAR#9000570034 RTL: SS Resume event generated in non-Hibernation
|
|
|
|
* operational mode
|
|
|
|
*/
|
|
|
|
pwropt = DWC3_GHWPARAMS1_EN_PWROPT(dwc->hwparams.hwparams1);
|
|
|
|
if ((dwc->revision < DWC3_REVISION_250A) &&
|
|
|
|
(pwropt != DWC3_GHWPARAMS1_EN_PWROPT_HIB)) {
|
|
|
|
if ((dwc->link_state == DWC3_LINK_STATE_U3) &&
|
|
|
|
(next == DWC3_LINK_STATE_RESUME)) {
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"ignoring transition U3 -> Resume");
|
2012-09-18 21:39:24 +03:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
2011-10-14 13:00:30 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* WORKAROUND: DWC3 Revisions <1.83a have an issue which, depending
|
|
|
|
* on the link partner, the USB session might do multiple entry/exit
|
|
|
|
* of low power states before a transfer takes place.
|
|
|
|
*
|
|
|
|
* Due to this problem, we might experience lower throughput. The
|
|
|
|
* suggested workaround is to disable DCTL[12:9] bits if we're
|
|
|
|
* transitioning from U1/U2 to U0 and enable those bits again
|
|
|
|
* after a transfer completes and there are no pending transfers
|
|
|
|
* on any of the enabled endpoints.
|
|
|
|
*
|
|
|
|
* This is the first half of that workaround.
|
|
|
|
*
|
|
|
|
* Refers to:
|
|
|
|
*
|
|
|
|
* STAR#9000446952: RTL: Device SS : if U1/U2 ->U0 takes >128us
|
|
|
|
* core send LGO_Ux entering U0
|
|
|
|
*/
|
|
|
|
if (dwc->revision < DWC3_REVISION_183A) {
|
|
|
|
if (next == DWC3_LINK_STATE_U0) {
|
|
|
|
u32 u1u2;
|
|
|
|
u32 reg;
|
|
|
|
|
|
|
|
switch (dwc->link_state) {
|
|
|
|
case DWC3_LINK_STATE_U1:
|
|
|
|
case DWC3_LINK_STATE_U2:
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_DCTL);
|
|
|
|
u1u2 = reg & (DWC3_DCTL_INITU2ENA
|
|
|
|
| DWC3_DCTL_ACCEPTU2ENA
|
|
|
|
| DWC3_DCTL_INITU1ENA
|
|
|
|
| DWC3_DCTL_ACCEPTU1ENA);
|
|
|
|
|
|
|
|
if (!dwc->u1u2)
|
|
|
|
dwc->u1u2 = reg & u1u2;
|
|
|
|
|
|
|
|
reg &= ~u1u2;
|
|
|
|
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCTL, reg);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
/* do nothing */
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-26 10:17:07 -06:00
|
|
|
switch (next) {
|
|
|
|
case DWC3_LINK_STATE_U1:
|
|
|
|
if (dwc->speed == USB_SPEED_SUPER)
|
|
|
|
dwc3_suspend_gadget(dwc);
|
|
|
|
break;
|
|
|
|
case DWC3_LINK_STATE_U2:
|
|
|
|
case DWC3_LINK_STATE_U3:
|
|
|
|
dwc3_suspend_gadget(dwc);
|
|
|
|
break;
|
|
|
|
case DWC3_LINK_STATE_RESUME:
|
|
|
|
dwc3_resume_gadget(dwc);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
/* do nothing */
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2014-11-25 15:29:58 -08:00
|
|
|
dev_dbg(dwc->dev, "Going from (%d)--->(%d)\n", dwc->link_state, next);
|
2014-04-22 13:20:12 -05:00
|
|
|
dwc->link_state = next;
|
2014-11-25 15:29:58 -08:00
|
|
|
wake_up_interruptible(&dwc->wait_linkstate);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2014-02-25 14:47:54 -06:00
|
|
|
static void dwc3_gadget_hibernation_interrupt(struct dwc3 *dwc,
|
|
|
|
unsigned int evtinfo)
|
|
|
|
{
|
|
|
|
unsigned int is_ss = evtinfo & BIT(4);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* WORKAROUND: DWC3 revison 2.20a with hibernation support
|
|
|
|
* have a known issue which can cause USB CV TD.9.23 to fail
|
|
|
|
* randomly.
|
|
|
|
*
|
|
|
|
* Because of this issue, core could generate bogus hibernation
|
|
|
|
* events which SW needs to ignore.
|
|
|
|
*
|
|
|
|
* Refers to:
|
|
|
|
*
|
|
|
|
* STAR#9000546576: Device Mode Hibernation: Issue in USB 2.0
|
|
|
|
* Device Fallback from SuperSpeed
|
|
|
|
*/
|
|
|
|
if (is_ss ^ (dwc->speed == USB_SPEED_SUPER))
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* enter hibernation here */
|
|
|
|
}
|
|
|
|
|
2014-03-10 15:24:52 -07:00
|
|
|
static void dwc3_gadget_suspend_interrupt(struct dwc3 *dwc,
|
|
|
|
unsigned int evtinfo)
|
|
|
|
{
|
|
|
|
enum dwc3_link_state next = evtinfo & DWC3_LINK_STATE_MASK;
|
|
|
|
|
2015-03-31 12:27:43 -07:00
|
|
|
dev_dbg(dwc->dev, "%s Entry to %d\n", __func__, next);
|
|
|
|
|
|
|
|
if (dwc->link_state != next && next == DWC3_LINK_STATE_U3) {
|
2014-05-04 11:34:45 +03:00
|
|
|
/*
|
|
|
|
* When first connecting the cable, even before the initial
|
|
|
|
* DWC3_DEVICE_EVENT_RESET or DWC3_DEVICE_EVENT_CONNECT_DONE
|
|
|
|
* events, the controller sees a DWC3_DEVICE_EVENT_SUSPEND
|
|
|
|
* event. In such a case, ignore.
|
2014-08-29 14:36:05 -07:00
|
|
|
* Ignore suspend event until device side usb is not into
|
|
|
|
* CONFIGURED state.
|
2014-05-04 11:34:45 +03:00
|
|
|
*/
|
2014-08-29 14:36:05 -07:00
|
|
|
if (dwc->gadget.state != USB_STATE_CONFIGURED) {
|
|
|
|
pr_err("%s(): state:%d. Ignore SUSPEND.\n",
|
|
|
|
__func__, dwc->gadget.state);
|
2014-05-04 11:34:45 +03:00
|
|
|
return;
|
2014-08-29 14:36:05 -07:00
|
|
|
}
|
2014-05-04 11:34:45 +03:00
|
|
|
|
2014-03-10 15:24:52 -07:00
|
|
|
dwc3_suspend_gadget(dwc);
|
2015-04-11 00:56:27 -07:00
|
|
|
|
|
|
|
dev_dbg(dwc->dev, "Notify OTG from %s\n", __func__);
|
|
|
|
dwc->b_suspend = true;
|
2016-01-29 21:14:24 +05:30
|
|
|
dwc3_notify_event(dwc, DWC3_CONTROLLER_NOTIFY_OTG_EVENT, 0);
|
2014-05-04 11:34:45 +03:00
|
|
|
}
|
2014-03-10 15:24:52 -07:00
|
|
|
|
|
|
|
dwc->link_state = next;
|
|
|
|
dwc3_trace(trace_dwc3_gadget, "link state %d", dwc->link_state);
|
|
|
|
}
|
|
|
|
|
2013-02-14 16:33:30 +05:30
|
|
|
static void dwc3_dump_reg_info(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
dbg_event(0xFF, "REGDUMP", 0);
|
|
|
|
|
|
|
|
dbg_print_reg("GUSB3PIPCTL", dwc3_readl(dwc->regs,
|
|
|
|
DWC3_GUSB3PIPECTL(0)));
|
|
|
|
dbg_print_reg("GUSB2PHYCONFIG", dwc3_readl(dwc->regs,
|
|
|
|
DWC3_GUSB2PHYCFG(0)));
|
|
|
|
dbg_print_reg("GCTL", dwc3_readl(dwc->regs, DWC3_GCTL));
|
|
|
|
dbg_print_reg("GUCTL", dwc3_readl(dwc->regs, DWC3_GUCTL));
|
|
|
|
dbg_print_reg("GDBGLTSSM", dwc3_readl(dwc->regs, DWC3_GDBGLTSSM));
|
|
|
|
dbg_print_reg("DCFG", dwc3_readl(dwc->regs, DWC3_DCFG));
|
|
|
|
dbg_print_reg("DCTL", dwc3_readl(dwc->regs, DWC3_DCTL));
|
|
|
|
dbg_print_reg("DEVTEN", dwc3_readl(dwc->regs, DWC3_DEVTEN));
|
|
|
|
dbg_print_reg("DSTS", dwc3_readl(dwc->regs, DWC3_DSTS));
|
|
|
|
dbg_print_reg("DALPENA", dwc3_readl(dwc->regs, DWC3_DALEPENA));
|
|
|
|
dbg_print_reg("DGCMD", dwc3_readl(dwc->regs, DWC3_DGCMD));
|
|
|
|
|
|
|
|
dbg_print_reg("OCFG", dwc3_readl(dwc->regs, DWC3_OCFG));
|
|
|
|
dbg_print_reg("OCTL", dwc3_readl(dwc->regs, DWC3_OCTL));
|
|
|
|
dbg_print_reg("OEVT", dwc3_readl(dwc->regs, DWC3_OEVT));
|
|
|
|
dbg_print_reg("OSTS", dwc3_readl(dwc->regs, DWC3_OSTS));
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
static void dwc3_gadget_interrupt(struct dwc3 *dwc,
|
|
|
|
const struct dwc3_event_devt *event)
|
|
|
|
{
|
|
|
|
switch (event->type) {
|
|
|
|
case DWC3_DEVICE_EVENT_DISCONNECT:
|
|
|
|
dwc3_gadget_disconnect_interrupt(dwc);
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.disconnect++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEVICE_EVENT_RESET:
|
|
|
|
dwc3_gadget_reset_interrupt(dwc);
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.reset++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEVICE_EVENT_CONNECT_DONE:
|
|
|
|
dwc3_gadget_conndone_interrupt(dwc);
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.connect++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEVICE_EVENT_WAKEUP:
|
2014-11-25 15:29:58 -08:00
|
|
|
dwc3_gadget_wakeup_interrupt(dwc, false);
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.wakeup++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
2014-02-25 14:47:54 -06:00
|
|
|
case DWC3_DEVICE_EVENT_HIBER_REQ:
|
|
|
|
if (dev_WARN_ONCE(dwc->dev, !dwc->has_hibernation,
|
|
|
|
"unexpected hibernation event\n"))
|
|
|
|
break;
|
|
|
|
|
|
|
|
dwc3_gadget_hibernation_interrupt(dwc, event->event_info);
|
|
|
|
break;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
case DWC3_DEVICE_EVENT_LINK_STATUS_CHANGE:
|
|
|
|
dwc3_gadget_linksts_change_interrupt(dwc, event->event_info);
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.link_status_change++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
2014-03-10 15:24:52 -07:00
|
|
|
case DWC3_DEVICE_EVENT_SUSPEND:
|
|
|
|
if (dwc->revision < DWC3_REVISION_230A) {
|
|
|
|
dwc3_trace(trace_dwc3_gadget, "End of Periodic Frame");
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.eopf++;
|
2014-03-10 15:24:52 -07:00
|
|
|
} else {
|
|
|
|
dwc3_trace(trace_dwc3_gadget, "U3/L1-L2 Suspend Event");
|
|
|
|
dbg_event(0xFF, "GAD SUS", 0);
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.suspend++;
|
2015-04-11 00:56:27 -07:00
|
|
|
|
2014-08-28 16:47:51 -07:00
|
|
|
/*
|
|
|
|
* Ignore suspend event if usb cable is not connected
|
|
|
|
* and speed is not being detected.
|
|
|
|
*/
|
|
|
|
if (dwc->gadget.speed != USB_SPEED_UNKNOWN &&
|
|
|
|
dwc->vbus_active)
|
|
|
|
dwc3_gadget_suspend_interrupt(dwc,
|
|
|
|
event->event_info);
|
2014-03-10 15:24:52 -07:00
|
|
|
}
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEVICE_EVENT_SOF:
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "Start of Periodic Frame");
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.sof++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEVICE_EVENT_ERRATIC_ERROR:
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "Erratic Error");
|
2014-02-24 20:04:11 -08:00
|
|
|
if (!dwc->err_evt_seen) {
|
|
|
|
dbg_event(0xFF, "ERROR", 0);
|
|
|
|
dwc3_dump_reg_info(dwc);
|
|
|
|
}
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.erratic_error++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEVICE_EVENT_CMD_CMPL:
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "Command Complete");
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.cmdcmplt++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
case DWC3_DEVICE_EVENT_OVERFLOW:
|
2015-01-27 13:48:14 -06:00
|
|
|
dwc3_trace(trace_dwc3_gadget, "Overflow");
|
2013-02-14 16:33:30 +05:30
|
|
|
dbg_event(0xFF, "OVERFL", 0);
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.overflow++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
break;
|
|
|
|
default:
|
2015-01-27 13:49:28 -06:00
|
|
|
dev_WARN(dwc->dev, "UNKNOWN IRQ %d\n", event->type);
|
2014-02-28 11:04:38 -08:00
|
|
|
dwc->dbg_gadget_events.unknown_event++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
2014-02-24 20:04:11 -08:00
|
|
|
|
|
|
|
dwc->err_evt_seen = (event->type == DWC3_DEVICE_EVENT_ERRATIC_ERROR);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void dwc3_process_event_entry(struct dwc3 *dwc,
|
|
|
|
const union dwc3_event *event)
|
|
|
|
{
|
2014-04-30 17:45:10 -05:00
|
|
|
trace_dwc3_event(event->raw);
|
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
/* skip event processing in absence of vbus */
|
|
|
|
if (!dwc->vbus_active) {
|
|
|
|
dbg_print_reg("SKIP EVT", event->raw);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2015-10-21 12:50:15 -07:00
|
|
|
/* If run/stop is cleared don't process any more events */
|
|
|
|
if (!dwc->pullups_connected) {
|
|
|
|
dbg_print_reg("SKIP_EVT_PULLUP", event->raw);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/* Endpoint IRQ, handle it and return early */
|
|
|
|
if (event->type.is_devspec == 0) {
|
|
|
|
/* depevt */
|
|
|
|
return dwc3_endpoint_interrupt(dwc, &event->depevt);
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (event->type.type) {
|
|
|
|
case DWC3_EVENT_TYPE_DEV:
|
|
|
|
dwc3_gadget_interrupt(dwc, &event->devt);
|
|
|
|
break;
|
|
|
|
/* REVISIT what to do with Carkit and I2C events ? */
|
|
|
|
default:
|
|
|
|
dev_err(dwc->dev, "UNKNOWN IRQ type %d\n", event->raw);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
static irqreturn_t dwc3_process_event_buf(struct dwc3 *dwc, u32 buf)
|
2011-06-30 16:57:15 +03:00
|
|
|
{
|
2013-06-12 21:25:08 +03:00
|
|
|
struct dwc3_event_buffer *evt;
|
2011-06-30 16:57:15 +03:00
|
|
|
irqreturn_t ret = IRQ_NONE;
|
2013-06-12 21:25:08 +03:00
|
|
|
int left;
|
2013-06-12 21:11:14 +03:00
|
|
|
u32 reg;
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
evt = dwc->ev_buffs[buf];
|
|
|
|
left = evt->count;
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
if (!(evt->flags & DWC3_EVENT_PENDING))
|
|
|
|
return IRQ_NONE;
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
while (left > 0) {
|
|
|
|
union dwc3_event event;
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
event.raw = *(u32 *) (evt->buf + evt->lpos);
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
dwc3_process_event_entry(dwc, &event);
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2014-08-29 15:21:03 -07:00
|
|
|
if (dwc->err_evt_seen) {
|
|
|
|
/*
|
|
|
|
* if erratic error, skip remaining events
|
|
|
|
* while controller undergoes reset
|
|
|
|
*/
|
|
|
|
evt->lpos = (evt->lpos + left) %
|
|
|
|
DWC3_EVENT_BUFFERS_SIZE;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_GEVNTCOUNT(buf), left);
|
2016-01-29 21:14:24 +05:30
|
|
|
if (dwc3_notify_event(dwc,
|
|
|
|
DWC3_CONTROLLER_ERROR_EVENT, 0))
|
2014-08-29 15:21:03 -07:00
|
|
|
dwc->err_evt_seen = 0;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
/*
|
|
|
|
* FIXME we wrap around correctly to the next entry as
|
|
|
|
* almost all entries are 4 bytes in size. There is one
|
|
|
|
* entry which has 12 bytes which is a regular entry
|
|
|
|
* followed by 8 bytes data. ATM I don't know how
|
|
|
|
* things are organized if we get next to the a
|
|
|
|
* boundary so I worry about that once we try to handle
|
|
|
|
* that.
|
|
|
|
*/
|
|
|
|
evt->lpos = (evt->lpos + 4) % DWC3_EVENT_BUFFERS_SIZE;
|
|
|
|
left -= 4;
|
|
|
|
}
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2014-10-15 18:23:37 -07:00
|
|
|
dwc->bh_handled_evt_cnt[dwc->bh_dbg_index] += (evt->count / 4);
|
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
evt->count = 0;
|
|
|
|
evt->flags &= ~DWC3_EVENT_PENDING;
|
|
|
|
ret = IRQ_HANDLED;
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
/* Unmask interrupt */
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_GEVNTSIZ(buf));
|
|
|
|
reg &= ~DWC3_GEVNTSIZ_INTMASK;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_GEVNTSIZ(buf), reg);
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2016-11-14 12:32:43 -08:00
|
|
|
if (dwc->imod_interval)
|
|
|
|
dwc3_writel(dwc->regs, DWC3_GEVNTCOUNT(buf),
|
|
|
|
DWC3_GEVNTCOUNT_EHB);
|
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
return ret;
|
|
|
|
}
|
2013-06-12 21:11:14 +03:00
|
|
|
|
2017-03-20 16:10:39 -07:00
|
|
|
void dwc3_bh_work(struct work_struct *w)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = container_of(w, struct dwc3, bh_work);
|
|
|
|
|
|
|
|
pm_runtime_get_sync(dwc->dev);
|
|
|
|
dwc3_thread_interrupt(dwc->irq, dwc);
|
|
|
|
pm_runtime_put(dwc->dev);
|
|
|
|
}
|
|
|
|
|
2013-06-12 21:25:08 +03:00
|
|
|
static irqreturn_t dwc3_thread_interrupt(int irq, void *_dwc)
|
|
|
|
{
|
|
|
|
struct dwc3 *dwc = _dwc;
|
2015-10-12 13:25:44 -05:00
|
|
|
unsigned long flags;
|
2013-06-12 21:25:08 +03:00
|
|
|
irqreturn_t ret = IRQ_NONE;
|
|
|
|
int i;
|
2014-10-15 18:23:37 -07:00
|
|
|
unsigned temp_time;
|
|
|
|
ktime_t start_time;
|
|
|
|
|
|
|
|
start_time = ktime_get();
|
2013-06-12 21:25:08 +03:00
|
|
|
|
2015-10-12 13:25:44 -05:00
|
|
|
spin_lock_irqsave(&dwc->lock, flags);
|
2014-10-15 18:23:37 -07:00
|
|
|
dwc->bh_handled_evt_cnt[dwc->bh_dbg_index] = 0;
|
2013-06-12 21:25:08 +03:00
|
|
|
|
2015-08-27 14:49:21 -07:00
|
|
|
for (i = 0; i < dwc->num_normal_event_buffers; i++)
|
2013-06-12 21:25:08 +03:00
|
|
|
ret |= dwc3_process_event_buf(dwc, i);
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2015-10-12 13:25:44 -05:00
|
|
|
spin_unlock_irqrestore(&dwc->lock, flags);
|
2011-06-30 16:57:15 +03:00
|
|
|
|
2014-10-15 18:23:37 -07:00
|
|
|
temp_time = ktime_to_us(ktime_sub(ktime_get(), start_time));
|
|
|
|
dwc->bh_completion_time[dwc->bh_dbg_index] = temp_time;
|
|
|
|
dwc->bh_dbg_index = (dwc->bh_dbg_index + 1) % 10;
|
|
|
|
|
2011-06-30 16:57:15 +03:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2013-06-12 21:16:11 +03:00
|
|
|
static irqreturn_t dwc3_check_event_buf(struct dwc3 *dwc, u32 buf)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3_event_buffer *evt;
|
|
|
|
u32 count;
|
2013-06-12 21:11:14 +03:00
|
|
|
u32 reg;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2011-06-30 16:57:15 +03:00
|
|
|
evt = dwc->ev_buffs[buf];
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
count = dwc3_readl(dwc->regs, DWC3_GEVNTCOUNT(buf));
|
|
|
|
count &= DWC3_GEVNTCOUNT_MASK;
|
|
|
|
if (!count)
|
|
|
|
return IRQ_NONE;
|
|
|
|
|
2015-11-06 15:11:46 -08:00
|
|
|
if (count > evt->length) {
|
|
|
|
dbg_event(0xFF, "HUGE_EVCNT", count);
|
|
|
|
evt->lpos = (evt->lpos + count) % DWC3_EVENT_BUFFERS_SIZE;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_GEVNTCOUNT(buf), count);
|
|
|
|
return IRQ_HANDLED;
|
|
|
|
}
|
|
|
|
|
2011-06-30 16:57:15 +03:00
|
|
|
evt->count = count;
|
|
|
|
evt->flags |= DWC3_EVENT_PENDING;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2013-06-12 21:11:14 +03:00
|
|
|
/* Mask interrupt */
|
|
|
|
reg = dwc3_readl(dwc->regs, DWC3_GEVNTSIZ(buf));
|
|
|
|
reg |= DWC3_GEVNTSIZ_INTMASK;
|
|
|
|
dwc3_writel(dwc->regs, DWC3_GEVNTSIZ(buf), reg);
|
|
|
|
|
2016-11-15 13:08:59 +02:00
|
|
|
dwc3_writel(dwc->regs, DWC3_GEVNTCOUNT(buf), count);
|
|
|
|
|
2011-06-30 16:57:15 +03:00
|
|
|
return IRQ_WAKE_THREAD;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2016-04-14 15:57:10 -07:00
|
|
|
irqreturn_t dwc3_interrupt(int irq, void *_dwc)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
struct dwc3 *dwc = _dwc;
|
|
|
|
int i;
|
|
|
|
irqreturn_t ret = IRQ_NONE;
|
2014-10-15 18:23:37 -07:00
|
|
|
unsigned temp_cnt = 0;
|
|
|
|
ktime_t start_time;
|
|
|
|
|
|
|
|
start_time = ktime_get();
|
|
|
|
dwc->irq_cnt++;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
2014-08-29 15:21:03 -07:00
|
|
|
/* controller reset is still pending */
|
|
|
|
if (dwc->err_evt_seen)
|
|
|
|
return IRQ_HANDLED;
|
|
|
|
|
2015-08-27 14:49:21 -07:00
|
|
|
for (i = 0; i < dwc->num_normal_event_buffers; i++) {
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
irqreturn_t status;
|
|
|
|
|
2013-06-12 21:16:11 +03:00
|
|
|
status = dwc3_check_event_buf(dwc, i);
|
2011-06-30 16:57:15 +03:00
|
|
|
if (status == IRQ_WAKE_THREAD)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
ret = status;
|
2014-10-15 18:23:37 -07:00
|
|
|
|
|
|
|
temp_cnt += dwc->ev_buffs[i]->count;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2014-10-15 18:23:37 -07:00
|
|
|
dwc->irq_start_time[dwc->irq_dbg_index] = start_time;
|
|
|
|
dwc->irq_completion_time[dwc->irq_dbg_index] =
|
|
|
|
ktime_us_delta(ktime_get(), start_time);
|
|
|
|
dwc->irq_event_count[dwc->irq_dbg_index] = temp_cnt / 4;
|
|
|
|
dwc->irq_dbg_index = (dwc->irq_dbg_index + 1) % MAX_INTR_STATS;
|
|
|
|
|
2016-08-09 12:28:55 -07:00
|
|
|
if (ret == IRQ_WAKE_THREAD)
|
2017-03-20 16:10:39 -07:00
|
|
|
queue_work(dwc->dwc_wq, &dwc->bh_work);
|
2014-02-13 18:33:50 -08:00
|
|
|
|
2015-08-04 18:45:57 -07:00
|
|
|
return IRQ_HANDLED;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dwc3_gadget_init - Initializes gadget related registers
|
2012-02-15 18:56:56 -08:00
|
|
|
* @dwc: pointer to our controller context structure
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
*
|
|
|
|
* Returns 0 on success otherwise negative errno.
|
|
|
|
*/
|
2012-11-19 13:21:48 -05:00
|
|
|
int dwc3_gadget_init(struct dwc3 *dwc)
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
2014-05-13 15:45:00 +03:00
|
|
|
INIT_WORK(&dwc->wakeup_work, dwc3_gadget_wakeup_work);
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc->ctrl_req = dma_alloc_coherent(dwc->dev, sizeof(*dwc->ctrl_req),
|
|
|
|
&dwc->ctrl_req_addr, GFP_KERNEL);
|
|
|
|
if (!dwc->ctrl_req) {
|
|
|
|
dev_err(dwc->dev, "failed to allocate ctrl request\n");
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto err0;
|
|
|
|
}
|
|
|
|
|
2015-07-27 12:25:31 +05:30
|
|
|
dwc->ep0_trb = dma_alloc_coherent(dwc->dev, sizeof(*dwc->ep0_trb) * 2,
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
&dwc->ep0_trb_addr, GFP_KERNEL);
|
|
|
|
if (!dwc->ep0_trb) {
|
|
|
|
dev_err(dwc->dev, "failed to allocate ep0 trb\n");
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto err1;
|
|
|
|
}
|
|
|
|
|
2012-05-04 12:58:14 +03:00
|
|
|
dwc->setup_buf = kzalloc(DWC3_EP0_BOUNCE_SIZE, GFP_KERNEL);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
if (!dwc->setup_buf) {
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto err2;
|
|
|
|
}
|
|
|
|
|
2011-08-27 22:07:53 +03:00
|
|
|
dwc->ep0_bounce = dma_alloc_coherent(dwc->dev,
|
2012-05-04 12:58:14 +03:00
|
|
|
DWC3_EP0_BOUNCE_SIZE, &dwc->ep0_bounce_addr,
|
|
|
|
GFP_KERNEL);
|
2011-08-27 22:07:53 +03:00
|
|
|
if (!dwc->ep0_bounce) {
|
|
|
|
dev_err(dwc->dev, "failed to allocate ep0 bounce buffer\n");
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto err3;
|
|
|
|
}
|
|
|
|
|
2015-12-02 10:06:45 -06:00
|
|
|
dwc->zlp_buf = kzalloc(DWC3_ZLP_BUF_SIZE, GFP_KERNEL);
|
|
|
|
if (!dwc->zlp_buf) {
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto err4;
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc->gadget.ops = &dwc3_gadget_ops;
|
|
|
|
dwc->gadget.speed = USB_SPEED_UNKNOWN;
|
2011-11-28 12:46:59 +02:00
|
|
|
dwc->gadget.sg_supported = true;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc->gadget.name = "dwc3-gadget";
|
|
|
|
|
2015-11-16 10:47:24 -06:00
|
|
|
/*
|
|
|
|
* FIXME We might be setting max_speed to <SUPER, however versions
|
|
|
|
* <2.20a of dwc3 have an issue with metastability (documented
|
|
|
|
* elsewhere in this driver) which tells us we can't set max speed to
|
|
|
|
* anything lower than SUPER.
|
|
|
|
*
|
|
|
|
* Because gadget.max_speed is only used by composite.c and function
|
|
|
|
* drivers (i.e. it won't go into dwc3's registers) we are allowing this
|
|
|
|
* to happen so we avoid sending SuperSpeed Capability descriptor
|
|
|
|
* together with our BOS descriptor as that could confuse host into
|
|
|
|
* thinking we can handle super speed.
|
|
|
|
*
|
|
|
|
* Note that, in fact, we won't even support GetBOS requests when speed
|
|
|
|
* is less than super speed because we don't have means, yet, to tell
|
|
|
|
* composite.c that we are USB 2.0 + LPM ECN.
|
|
|
|
*/
|
|
|
|
if (dwc->revision < DWC3_REVISION_220A)
|
|
|
|
dwc3_trace(trace_dwc3_gadget,
|
|
|
|
"Changing max_speed on rev %08x\n",
|
|
|
|
dwc->revision);
|
|
|
|
|
|
|
|
dwc->gadget.max_speed = dwc->maximum_speed;
|
|
|
|
|
2013-12-09 15:55:38 -08:00
|
|
|
/*
|
|
|
|
* Per databook, DWC3 needs buffer size to be aligned to MaxPacketSize
|
|
|
|
* on ep out.
|
|
|
|
*/
|
|
|
|
dwc->gadget.quirk_ep_out_aligned_size = true;
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
/*
|
|
|
|
* REVISIT: Here we should clear all pending IRQs to be
|
|
|
|
* sure we're starting from a well known location.
|
|
|
|
*/
|
|
|
|
|
|
|
|
ret = dwc3_gadget_init_endpoints(dwc);
|
|
|
|
if (ret)
|
2015-12-02 10:06:45 -06:00
|
|
|
goto err5;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
ret = usb_add_gadget_udc(dwc->dev, &dwc->gadget);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dwc->dev, "failed to register udc\n");
|
2015-12-02 10:06:45 -06:00
|
|
|
goto err5;
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
}
|
|
|
|
|
2016-02-02 12:57:37 -08:00
|
|
|
if (!dwc->is_drd) {
|
|
|
|
pm_runtime_no_callbacks(&dwc->gadget.dev);
|
|
|
|
pm_runtime_set_active(&dwc->gadget.dev);
|
|
|
|
pm_runtime_enable(&dwc->gadget.dev);
|
|
|
|
pm_runtime_get(&dwc->gadget.dev);
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
return 0;
|
|
|
|
|
2015-12-02 10:06:45 -06:00
|
|
|
err5:
|
|
|
|
kfree(dwc->zlp_buf);
|
|
|
|
|
2011-08-27 22:07:53 +03:00
|
|
|
err4:
|
2013-09-11 17:42:47 -07:00
|
|
|
dwc3_gadget_free_endpoints(dwc);
|
2012-05-04 12:58:14 +03:00
|
|
|
dma_free_coherent(dwc->dev, DWC3_EP0_BOUNCE_SIZE,
|
|
|
|
dwc->ep0_bounce, dwc->ep0_bounce_addr);
|
2011-08-27 22:07:53 +03:00
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
err3:
|
2011-12-19 11:32:34 +02:00
|
|
|
kfree(dwc->setup_buf);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
|
|
|
err2:
|
usb: dwc3: Fix size used in dma_free_coherent()
commit 51fbc7c06c8900370c6da5fc4a4685add8fa4fb0 upstream.
In commit 2abd9d5fa60f9 ("usb: dwc3: ep0: Add chained TRB support"), the
size of the memory allocated with 'dma_alloc_coherent()' has been modified
but the corresponding calls to 'dma_free_coherent()' have not been updated
accordingly.
This has been spotted with coccinelle, using the following script:
////////////////////
@r@
expression x0, x1, y0, y1, z0, z1, t0, t1, ret;
@@
* ret = dma_alloc_coherent(x0, y0, z0, t0);
...
* dma_free_coherent(x1, y1, ret, t1);
@script:python@
y0 << r.y0;
y1 << r.y1;
@@
if y1.find(y0) == -1:
print "WARNING: sizes look different: '%s' vs '%s'" % (y0, y1)
////////////////////
Fixes: 2abd9d5fa60f9 ("usb: dwc3: ep0: Add chained TRB support")
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2016-10-07 22:12:39 +02:00
|
|
|
dma_free_coherent(dwc->dev, sizeof(*dwc->ep0_trb) * 2,
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc->ep0_trb, dwc->ep0_trb_addr);
|
|
|
|
|
|
|
|
err1:
|
|
|
|
dma_free_coherent(dwc->dev, sizeof(*dwc->ctrl_req),
|
|
|
|
dwc->ctrl_req, dwc->ctrl_req_addr);
|
|
|
|
|
|
|
|
err0:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2012-04-30 14:56:33 +03:00
|
|
|
/* -------------------------------------------------------------------------- */
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
void dwc3_gadget_exit(struct dwc3 *dwc)
|
|
|
|
{
|
2016-02-02 12:57:37 -08:00
|
|
|
if (dwc->is_drd) {
|
|
|
|
pm_runtime_put(&dwc->gadget.dev);
|
|
|
|
pm_runtime_disable(&dwc->gadget.dev);
|
|
|
|
}
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
usb_del_gadget_udc(&dwc->gadget);
|
|
|
|
|
|
|
|
dwc3_gadget_free_endpoints(dwc);
|
|
|
|
|
2012-05-04 12:58:14 +03:00
|
|
|
dma_free_coherent(dwc->dev, DWC3_EP0_BOUNCE_SIZE,
|
|
|
|
dwc->ep0_bounce, dwc->ep0_bounce_addr);
|
2011-08-27 22:07:53 +03:00
|
|
|
|
2011-12-19 11:32:34 +02:00
|
|
|
kfree(dwc->setup_buf);
|
2015-12-02 10:06:45 -06:00
|
|
|
kfree(dwc->zlp_buf);
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
|
usb: dwc3: Fix size used in dma_free_coherent()
commit 51fbc7c06c8900370c6da5fc4a4685add8fa4fb0 upstream.
In commit 2abd9d5fa60f9 ("usb: dwc3: ep0: Add chained TRB support"), the
size of the memory allocated with 'dma_alloc_coherent()' has been modified
but the corresponding calls to 'dma_free_coherent()' have not been updated
accordingly.
This has been spotted with coccinelle, using the following script:
////////////////////
@r@
expression x0, x1, y0, y1, z0, z1, t0, t1, ret;
@@
* ret = dma_alloc_coherent(x0, y0, z0, t0);
...
* dma_free_coherent(x1, y1, ret, t1);
@script:python@
y0 << r.y0;
y1 << r.y1;
@@
if y1.find(y0) == -1:
print "WARNING: sizes look different: '%s' vs '%s'" % (y0, y1)
////////////////////
Fixes: 2abd9d5fa60f9 ("usb: dwc3: ep0: Add chained TRB support")
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2016-10-07 22:12:39 +02:00
|
|
|
dma_free_coherent(dwc->dev, sizeof(*dwc->ep0_trb) * 2,
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 18:10:58 +03:00
|
|
|
dwc->ep0_trb, dwc->ep0_trb_addr);
|
|
|
|
|
|
|
|
dma_free_coherent(dwc->dev, sizeof(*dwc->ctrl_req),
|
|
|
|
dwc->ctrl_req, dwc->ctrl_req_addr);
|
|
|
|
}
|
2012-04-30 14:56:33 +03:00
|
|
|
|
2014-10-07 10:19:23 -05:00
|
|
|
int dwc3_gadget_suspend(struct dwc3 *dwc)
|
2012-04-30 14:56:33 +03:00
|
|
|
{
|
2013-12-19 13:43:19 -06:00
|
|
|
if (dwc->pullups_connected) {
|
2012-04-30 14:56:33 +03:00
|
|
|
dwc3_gadget_disable_irq(dwc);
|
2013-12-19 13:43:19 -06:00
|
|
|
dwc3_gadget_run_stop(dwc, true, true);
|
|
|
|
}
|
2012-04-30 14:56:33 +03:00
|
|
|
|
|
|
|
__dwc3_gadget_ep_disable(dwc->eps[0]);
|
|
|
|
__dwc3_gadget_ep_disable(dwc->eps[1]);
|
|
|
|
|
|
|
|
dwc->dcfg = dwc3_readl(dwc->regs, DWC3_DCFG);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int dwc3_gadget_resume(struct dwc3 *dwc)
|
|
|
|
{
|
|
|
|
struct dwc3_ep *dep;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
/* Start with SuperSpeed Default */
|
|
|
|
dwc3_gadget_ep0_desc.wMaxPacketSize = cpu_to_le16(512);
|
|
|
|
|
|
|
|
dep = dwc->eps[0];
|
2013-12-19 12:38:49 -06:00
|
|
|
ret = __dwc3_gadget_ep_enable(dep, &dwc3_gadget_ep0_desc, NULL, false,
|
|
|
|
false);
|
2012-04-30 14:56:33 +03:00
|
|
|
if (ret)
|
|
|
|
goto err0;
|
|
|
|
|
|
|
|
dep = dwc->eps[1];
|
2013-12-19 12:38:49 -06:00
|
|
|
ret = __dwc3_gadget_ep_enable(dep, &dwc3_gadget_ep0_desc, NULL, false,
|
|
|
|
false);
|
2012-04-30 14:56:33 +03:00
|
|
|
if (ret)
|
|
|
|
goto err1;
|
|
|
|
|
|
|
|
/* begin to receive SETUP packets */
|
|
|
|
dwc->ep0state = EP0_SETUP_PHASE;
|
|
|
|
dwc3_ep0_out_start(dwc);
|
|
|
|
|
|
|
|
dwc3_writel(dwc->regs, DWC3_DCFG, dwc->dcfg);
|
|
|
|
|
2014-10-07 10:19:23 -05:00
|
|
|
if (dwc->pullups_connected) {
|
|
|
|
dwc3_gadget_enable_irq(dwc);
|
|
|
|
dwc3_gadget_run_stop(dwc, true, false);
|
|
|
|
}
|
|
|
|
|
2012-04-30 14:56:33 +03:00
|
|
|
return 0;
|
|
|
|
|
|
|
|
err1:
|
|
|
|
__dwc3_gadget_ep_disable(dwc->eps[0]);
|
|
|
|
|
|
|
|
err0:
|
|
|
|
return ret;
|
|
|
|
}
|