s3c-hsotg driver updates/fixes
Subsystems (2)
An update for the USB PHY clock and fixes for the s3c-hsotg driver.
This fixes some of the issues that are being seen on various versions of the core.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 1274846966-23247-1-git-send-email-ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org
PATCH 1/11 USB: s3c_hsotg: Add support for external USB clock
From: Maurus Cuelenaere <[email protected]>
The PLL that drives the USB clock supports 3 input clocks: 12, 24 and 48Mhz. This patch adds support to the USB driver for setting the correct register bit according to the given clock.
This depends on the following patch:
[PATCH] ARM: S3C64XX: Add USB external clock definition
--- drivers/usb/gadget/s3c-hsotg.c | 19 +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-)
drivers/usb/gadget/s3c-hsotg.c +19 -0
@@ -23,6 +23,7 @@#include <linux/delay.h> #include <linux/io.h> #include <linux/slab.h> +#include <linux/clk.h> #include <linux/usb/ch9.h> #include <linux/usb/gadget.h>
@@ -2699,6 +2700,7 @@ static void __devinit s3c_hsotg_initep(struct s3c_hsotg *hsotg,*/ static void s3c_hsotg_otgreset (struct s3c_hsotg *hsotg) { +struct clk *xusbxti;u32 osc;writel (0 ,S3C_PHYPWR );
@@ -2706,6 +2708,23 @@ static void s3c_hsotg_otgreset(struct s3c_hsotg *hsotg) osc = hsotg->plat->is_osc ?S3C_PHYCLK_EXT_OSC :0 ; + xusbxti =clk_get (hsotg->dev,"xusbxti" ); +if (xusbxti && !IS_ERR (xusbxti)) { +switch (clk_get_rate (xusbxti)) { +case 12000000 : + osc |=S3C_PHYCLK_CLKSEL_12M ; +break ; +case 24000000 : + osc |=S3C_PHYCLK_CLKSEL_24M ; +break ; +default : +case 48000000 : +/* default reference clock */ +break ; + } +clk_put (xusbxti); + } +writel (osc |0x10 ,S3C_PHYCLK );/* issue a full set of resets to the otg and core */
Signature · 6 lines
1.6.3.3 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH 2/11 USB: s3c_hsotg: define USB_GADGET_DUALSPEED in Kconfig
In reply to a message not in the archiveFrom: Maurus Cuelenaere <[email protected]>
The s3c_hsotg driver sets usb_gadget->is_dualspeed to 1, yet it doesn't define USB_GADGET_DUALSPEED in Kconfig. This triggers a NULL pointer dereference in the composite driver (which is fixed in another patch).
--- drivers/usb/gadget/Kconfig | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
drivers/usb/gadget/Kconfig +1 -0
@@ -295,6 +295,7 @@ config USB_GADGET_S3C_HSOTG boolean "S3C HS/OtG USB Device controller" depends on S3C_DEV_USB_HSOTG select USB_GADGET_S3C_HSOTG_PIO + select USB_GADGET_DUALSPEED help The Samsung S3C64XX USB2.0 high-speed gadget controller integrated into the S3C64XX series SoC.
Signature · 6 lines
1.6.3.3 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH 4/11 USB: s3c-hsotg: SoftDisconnect minimum 3ms
In reply to a message not in the archiveThe shortest period SoftDisconnect can be asserted for is 3 milliseconds according to the V210 datasheet, so ensure that we add an msleep() to the registration code to enforce this.
--- drivers/usb/gadget/s3c-hsotg.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-)
drivers/usb/gadget/s3c-hsotg.c +3 -0
@@ -2602,6 +2602,9 @@ int usb_gadget_register_driver(struct usb_gadget_driver *driver)writel (S3C_DCTL_CGOUTNak | S3C_DCTL_CGNPInNAK, hsotg->regs +S3C_DCTL ); +/* must be at-least 3ms to allow bus to see disconnect */ +msleep (3 ); +/* remove the soft-disconnect and let's go */ __bic32 (hsotg->regs +S3C_DCTL , S3C_DCTL_SftDiscon);
Signature · 6 lines
1.6.3.3 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH 5/11 USB: s3c-hsotg: Ensure FIFOs are fully flushed after layout
In reply to a message not in the archiveAccording to the design guide, if the FIFO layout is changed, then the FIFOs must be flushed to ensure all FIFO pointers are correct.
--- drivers/usb/gadget/s3c-hsotg.c | 27 +++++++++++++++++++++++++++ 1 files changed, 27 insertions(+), 0 deletions(-)
drivers/usb/gadget/s3c-hsotg.c +27 -0
@@ -301,6 +301,7 @@ static void s3c_hsotg_init_fifo(struct s3c_hsotg *hsotg)unsigned int ep;unsigned int addr;unsigned int size; +int timeout;u32 val;/* the ryu 2.6.24 release ahs
@@ -338,6 +339,32 @@ static void s3c_hsotg_init_fifo(struct s3c_hsotg *hsotg)writel (val, hsotg->regs +S3C_DPTXFSIZn (ep)); } + +/* according to p428 of the design guide, we need to ensure that +* all fifos are flushed before continuing. +*/ + +writel (S3C_GRSTCTL_TxFNum (0x10 ) | S3C_GRSTCTL_TxFFlsh | + S3C_GRSTCTL_RxFFlsh, hsotg->regs +S3C_GRSTCTL ); + +/* wait until the fifos are both flushed */ + timeout =100 ; +while (1 ) { + val =readl (hsotg->regs +S3C_GRSTCTL ); + +if ((val & (S3C_GRSTCTL_TxFFlsh | S3C_GRSTCTL_RxFFlsh)) ==0 ) +break ; + +if (--timeout ==0 ) { +dev_err (hsotg->dev, +"%s: timeout flushing fifos (GRSTCTL=%08x)\n" , + __func__, val); + } + +udelay (1 ); + } + +dev_dbg (hsotg->dev,"FIFOs reset, timeout at %d\n" , timeout); }/**
Signature · 6 lines
1.6.3.3 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH 7/11 USB: s3c-hsotg: Increase TX fifo limit
In reply to a message not in the archiveUp the FIFO size for the TX to 1024 entries, as this now seems to work with all the cores. This fixes a problem when using large packets on a core with MPS set to 512 can hang due to insufficient space for the writes.
The hang arises due to getting the non-periodic FIFO empty IRQ but not being able to satisfy any requests since there is never enough space to write 512 bytes into the buffer. This means we end up with a stream of interrupt requests.
It is easier to up the TX FIFO to fill the space we left for it than to try and fix the positions in the code where we should have limited the max-packet size to < TXFIFOSIZE, since the TXFIFOSIZE depends on how the TX FIFOs have been setup.
--- drivers/usb/gadget/s3c-hsotg.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
drivers/usb/gadget/s3c-hsotg.c +2 -2
@@ -311,11 +311,11 @@ static void s3c_hsotg_init_fifo(struct s3c_hsotg *hsotg)hsotg->regs + S3C_GNPTXFSIZ); */ -/* set FIFO sizes to 2048/0x1C0 */ +/* set FIFO sizes to 2048/1024 */ writel (2048 , hsotg->regs +S3C_GRXFSIZ );writel (S3C_GNPTXFSIZ_NPTxFStAddr (2048 ) | -S3C_GNPTXFSIZ_NPTxFDep (0x1C0 ), +S3C_GNPTXFSIZ_NPTxFDep (1024 ), hsotg->regs +S3C_GNPTXFSIZ );/* Arange all the rest of the TX FIFOs, as some versions of this
Signature · 6 lines
1.6.3.3 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH 3/11 USB: s3c-hsotg: Ensure TX FIFO addresses setup when initialising FIFOs
In reply to Ben DooksSome versions of the S3C HS OtG block startup with overlapping TX FIFO information, so change the fifo_init code to ensure that known values are set into the FIFO registers at initialisation/reset time.
This also ensures that the FIFO RAM pointers are in a known state before use.
--- drivers/usb/gadget/s3c-hsotg.c | 27 +++++++++++++++++++++++++++ 1 files changed, 27 insertions(+), 0 deletions(-)
drivers/usb/gadget/s3c-hsotg.c +27 -0
@@ -298,6 +298,11 @@ static void s3c_hsotg_ctrl_epint(struct s3c_hsotg *hsotg,*/ static void s3c_hsotg_init_fifo (struct s3c_hsotg *hsotg) { +unsigned int ep; +unsigned int addr; +unsigned int size; +u32 val; +/* the ryu 2.6.24 release ahs writel(0x1C0, hsotg->regs + S3C_GRXFSIZ); writel(S3C_GNPTXFSIZ_NPTxFStAddr(0x200) |
@@ -311,6 +316,28 @@ static void s3c_hsotg_init_fifo(struct s3c_hsotg *hsotg)writel (S3C_GNPTXFSIZ_NPTxFStAddr (2048 ) |S3C_GNPTXFSIZ_NPTxFDep (0x1C0 ), hsotg->regs +S3C_GNPTXFSIZ ); + +/* Arange all the rest of the TX FIFOs, as some versions of this +* block have overlapping default addresses. This also ensures +* that if the settings have been changed, then they are set to +* known values. +*/ + +/* start at the end of the GNPTXFSIZ, rounded up */ + addr =2048 +1024 ; + size =768 ; + +/* currently we allocate TX FIFOs for all possible endpoints, +* and assume that they are all the same size. +*/ + +for (ep =0 ; ep <=15 ; ep++) { + val = addr; + val |= size << S3C_DPTXFSIZn_DPTxFSize_SHIFT; + addr += size; + +writel (val, hsotg->regs +S3C_DPTXFSIZn (ep)); + } }/**
Signature · 1 line
1.6.3.3
PATCH 6/11 USB: s3c-hsotg: Enable soft disconnect during initialization
In reply to Ben DooksFrom: Thomas Abraham <[email protected]>
Enable soft disconnect bit the OTG core during initialization. Without this, the host sees that a gadget is connected and tries to enumerate. The soft disconnect should be enabled until the USB gadget driver is registered with this otg driver.
--- drivers/usb/gadget/s3c-hsotg.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-)
drivers/usb/gadget/s3c-hsotg.c +3 -0
@@ -2806,6 +2806,9 @@ static void s3c_hsotg_init(struct s3c_hsotg *hsotg)writel (0 , hsotg->regs +S3C_DAINTMSK ); +/* Be in disconnected state until gadget is registered */ +__orr32 (hsotg->regs +S3C_DCTL , S3C_DCTL_SftDiscon); +if (0 ) {/* post global nak until we're ready */ writel(S3C_DCTL_SGNPInNAK | S3C_DCTL_SGOUTNak,
Signature · 1 line
1.6.3.3