For some reason, the value of the HPTXFSIZ register was built in the
ptxfsiz variable, while there was also a hptxfsiz variable availble.
Better just use that and remove the (now unused) ptxfsiz variable.

Signed-off-by: Matthijs Kooijman <matth...@stdin.nl>
Acked-by: Paul Zimmerman <pa...@synopsys.com>
---
 drivers/staging/dwc2/core.c | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/drivers/staging/dwc2/core.c b/drivers/staging/dwc2/core.c
index 1f89886..5799f47 100644
--- a/drivers/staging/dwc2/core.c
+++ b/drivers/staging/dwc2/core.c
@@ -507,7 +507,7 @@ void dwc2_disable_host_interrupts(struct dwc2_hsotg *hsotg)
 static void dwc2_config_fifos(struct dwc2_hsotg *hsotg)
 {
        struct dwc2_core_params *params = hsotg->core_params;
-       u32 rxfsiz, nptxfsiz, ptxfsiz, hptxfsiz, dfifocfg;
+       u32 rxfsiz, nptxfsiz, hptxfsiz, dfifocfg;
 
        if (!params->enable_dynamic_fifo)
                return;
@@ -539,12 +539,12 @@ static void dwc2_config_fifos(struct dwc2_hsotg *hsotg)
        /* Periodic Tx FIFO */
        dev_dbg(hsotg->dev, "initial hptxfsiz=%08x\n",
                readl(hsotg->regs + HPTXFSIZ));
-       ptxfsiz = params->host_perio_tx_fifo_size <<
-                 FIFOSIZE_DEPTH_SHIFT & FIFOSIZE_DEPTH_MASK;
-       ptxfsiz |= (params->host_rx_fifo_size +
-                   params->host_nperio_tx_fifo_size) <<
-                  FIFOSIZE_STARTADDR_SHIFT & FIFOSIZE_STARTADDR_MASK;
-       writel(ptxfsiz, hsotg->regs + HPTXFSIZ);
+       hptxfsiz = params->host_perio_tx_fifo_size <<
+                  FIFOSIZE_DEPTH_SHIFT & FIFOSIZE_DEPTH_MASK;
+       hptxfsiz |= (params->host_rx_fifo_size +
+                    params->host_nperio_tx_fifo_size) <<
+                   FIFOSIZE_STARTADDR_SHIFT & FIFOSIZE_STARTADDR_MASK;
+       writel(hptxfsiz, hsotg->regs + HPTXFSIZ);
        dev_dbg(hsotg->dev, "new hptxfsiz=%08x\n",
                readl(hsotg->regs + HPTXFSIZ));
 
-- 
1.8.4.rc1

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to