When calling xhci_dbg_regs() we actually _do_ want to know XHCI's
version. This might help figure out why certain problems only happen
in some cases.

Signed-off-by: Felipe Balbi <felipe.ba...@linux.intel.com>
 drivers/usb/host/xhci-dbg.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/usb/host/xhci-dbg.c b/drivers/usb/host/xhci-dbg.c
index a3b67f33d4d8..363d125300ea 100644
--- a/drivers/usb/host/xhci-dbg.c
+++ b/drivers/usb/host/xhci-dbg.c
@@ -37,10 +37,8 @@ void xhci_dbg_regs(struct xhci_hcd *xhci)
                        &xhci->cap_regs->hc_capbase, temp);
        xhci_dbg(xhci, "//   CAPLENGTH: 0x%x\n",
                        (unsigned int) HC_LENGTH(temp));
-#if 0
        xhci_dbg(xhci, "//   HCIVERSION: 0x%x\n",
                        (unsigned int) HC_VERSION(temp));
        xhci_dbg(xhci, "// xHCI operational registers at %p:\n", xhci->op_regs);

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