From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934448AbeE2NLh (ORCPT ); Tue, 29 May 2018 09:11:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:45736 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933756AbeE2NLa (ORCPT ); Tue, 29 May 2018 09:11:30 -0400 Date: Tue, 29 May 2018 15:11:09 +0200 From: Greg KH To: Oleksandr Shamray Cc: arnd@arndb.de, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, openbmc@lists.ozlabs.org, joel@jms.id.au, jiri@resnulli.us, tklauser@distanz.ch, linux-serial@vger.kernel.org, vadimp@mellanox.com, system-sw-low-level@mellanox.com, robh+dt@kernel.org, openocd-devel-owner@lists.sourceforge.net, linux-api@vger.kernel.org, davem@davemloft.net, mchehab@kernel.org Subject: Re: [patch v23 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver Message-ID: <20180529131109.GD30119@kroah.com> References: <1527594545-19870-1-git-send-email-oleksandrs@mellanox.com> <1527594545-19870-3-git-send-email-oleksandrs@mellanox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1527594545-19870-3-git-send-email-oleksandrs@mellanox.com> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 29, 2018 at 02:49:03PM +0300, Oleksandr Shamray wrote: > +static int aspeed_jtag_idle(struct jtag *jtag, > + struct jtag_run_test_idle *runtest) > +{ > + struct aspeed_jtag *aspeed_jtag = jtag_priv(jtag); > + > + dev_dbg(aspeed_jtag->dev, "runtest, status:%d, mode:%s, state:%s, reset:%d, tck:%d\n", > + aspeed_jtag->status, > + aspeed_jtag->mode & JTAG_XFER_HW_MODE ? "HW" : "SW", > + end_status_str[runtest->endstate], runtest->reset, > + runtest->tck); You have dev_dbg() lines all over the place. They can all be removed now, right? ftrace works well, and if you really want to do this properly, use tracepoints in the jtag core code so that you can get the information for all devices as needed. But don't put them all over the driver, now that it's all working, there's no need, right? > +static void aspeed_jtag_xfer_push_data_last(struct aspeed_jtag *aspeed_jtag, > + enum jtag_xfer_type type, > + u32 shift_bits, > + enum jtag_endstate endstate) > +{ > + if (endstate == JTAG_STATE_IDLE) { > + if (type == JTAG_SIR_XFER) { > + dev_dbg(aspeed_jtag->dev, "IR Keep Pause\n"); Like this, doesn't provide much info, does it? thanks, greg k-h