Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933963AbcDFJZP (ORCPT ); Wed, 6 Apr 2016 05:25:15 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:48251 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933702AbcDFJZM (ORCPT ); Wed, 6 Apr 2016 05:25:12 -0400 Date: Wed, 6 Apr 2016 05:25:09 -0400 From: Greg KH To: changbin.du@intel.com Cc: balbi@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] usb: dwc3: add debugfs node to dump FIFO/Queue available space Message-ID: <20160406092509.GA29930@kroah.com> References: <1459931243-26405-1-git-send-email-changbin.du@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1459931243-26405-1-git-send-email-changbin.du@intel.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3269 Lines: 99 On Wed, Apr 06, 2016 at 04:27:23PM +0800, changbin.du@intel.com wrote: > From: "Du, Changbin" > > For DWC3 USB controller, the Global Debug Queue/FIFO Space Available > Register(GDBGFIFOSPACE) can be used to dump FIFO/Queue available space. > This can be used to check some special issues, like whether data is > successfully copied from memory to fifo when a trb is blocked. > > Signed-off-by: Du, Changbin > --- > drivers/usb/dwc3/core.h | 5 +++++ > drivers/usb/dwc3/debugfs.c | 45 +++++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 50 insertions(+) Why did you not include the linux-usb@vger mailing list? > > diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h > index 6254b2f..899cf76 100644 > --- a/drivers/usb/dwc3/core.h > +++ b/drivers/usb/dwc3/core.h > @@ -348,6 +348,11 @@ > #define DWC3_DSTS_LOWSPEED (2 << 0) > #define DWC3_DSTS_FULLSPEED1 (3 << 0) > > +/* Global Debug Queue/FIFO Space Available Register */ > +#define DWC3_GDBGFIFOSPACE_NUM(x) (((x) << 0) & 0x1F) > +#define DWC3_GDBGFIFOSPACE_TYPE(x) (((x) << 5) & 0xE0) > +#define DWC3_GDBGFIFOSPACE_GET_SPACE(x) (((x) >> 16) & 0xFFFF) > + > /* Device Generic Command Register */ > #define DWC3_DGCMD_SET_LMP 0x01 > #define DWC3_DGCMD_SET_PERIODIC_PAR 0x02 > diff --git a/drivers/usb/dwc3/debugfs.c b/drivers/usb/dwc3/debugfs.c > index 9ac37fe..f9a8d9e 100644 > --- a/drivers/usb/dwc3/debugfs.c > +++ b/drivers/usb/dwc3/debugfs.c > @@ -426,6 +426,45 @@ static const struct file_operations dwc3_mode_fops = { > .release = single_release, > }; > > +static int dwc3_fifo_show(struct seq_file *s, void *unused) > +{ > + struct dwc3 *dwc = s->private; > + unsigned long flags; > + unsigned int type, index; > + const char *name; > + u32 reg; > + > + static const char * const fifo_names[] = { > + "TxFIFO", "RxFIFO", "TxReqQ", "RxReqQ", "RxInfoQ", > + "DescFetchQ", "EventQ", "ProtocolStatusQ"}; > + spin_lock_irqsave(&dwc->lock, flags); > + for (type = 0; type < 8; type++) { > + name = fifo_names[type]; > + for (index = 0; index < 32; index++) { > + dwc3_writel(dwc->regs, DWC3_GDBGFIFOSPACE, > + DWC3_GDBGFIFOSPACE_NUM(index) | > + DWC3_GDBGFIFOSPACE_TYPE(type)); > + reg = dwc3_readl(dwc->regs, DWC3_GDBGFIFOSPACE); > + seq_printf(s, "%s%02d = %d\n", name, index, > + DWC3_GDBGFIFOSPACE_GET_SPACE(reg)); > + } > + } > + spin_unlock_irqrestore(&dwc->lock, flags); > + return 0; > +} > + > +static int dwc3_fifo_open(struct inode *inode, struct file *file) > +{ > + return single_open(file, dwc3_fifo_show, inode->i_private); > +} > + > +static const struct file_operations dwc3_fifo_fops = { > + .open = dwc3_fifo_open, > + .read = seq_read, > + .llseek = seq_lseek, > + .release = single_release, > +}; > + > static int dwc3_testmode_show(struct seq_file *s, void *unused) > { > struct dwc3 *dwc = s->private; > @@ -648,6 +687,12 @@ int dwc3_debugfs_init(struct dwc3 *dwc) > goto err1; > } > > + file = debugfs_create_file("fifo", S_IRUGO, root, dwc, &dwc3_fifo_fops); > + if (!file) { > + ret = -ENOMEM; Um, no, that's not the error here. You shouldn't care at all about debugfs api call results. Just keep moving on here please. thanks, greg k-h