From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raul Rangel Subject: Re: [PATCH v1 0/4] Add tracing for SDHCI register access Date: Fri, 12 Apr 2019 08:50:12 -0600 Message-ID: <20190412145012.GA101407@google.com> References: <20190411220822.81845-1-rrangel@chromium.org> <7b77ebcb-b42b-2d14-f5f1-b37e07b88469@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <7b77ebcb-b42b-2d14-f5f1-b37e07b88469@intel.com> Sender: linux-kernel-owner@vger.kernel.org To: Adrian Hunter Cc: linux-trace-devel@vger.kernel.org, linux-mmc@vger.kernel.org, djkurtz@chromium.org, zwisler@chromium.org, Ludovic Barre , Steven Rostedt , Jisheng Zhang , Masahiro Yamada , Faiz Abbas , linux-kernel@vger.kernel.org, Oleksij Rempel , Liming Sun , Wolfram Sang , Ingo Molnar , Prabu Thangamuthu , Chunyan Zhang , Ulf Hansson List-Id: linux-mmc@vger.kernel.org On Fri, Apr 12, 2019 at 09:26:44AM +0300, Adrian Hunter wrote: > On 12/04/19 1:08 AM, Raul E Rangel wrote: > > I was debugging a SDHC hardware bug and got tired of having to > > translate the register values by hand. This patch set makes it so all > > SDHC register read and write operations can be traced and easily read by > > a human. > > While this might be useful for people unfamiliar with SDHCI, I am not sure > it should be in the upstream kernel. Can you help me understand your hesitation? Would you prefer removing the pretty printing? Or would you prefer not having any trace events at all? The xhci driver has a bunch of pretty print trace events that make it invaluable when debugging. https://github.com/torvalds/linux/blob/d7563ca5bfca53398e100eb74345c5d3ef06bf9d/drivers/usb/host/xhci.h#L2160 > Also, it doesn't seem ideal for every > driver to add its own plumbing for such a feature. What do you mean by every driver having to add it's own plumbing? Any driver that uses sdhci_readX or sdhci_writeX get the functionality for free. Thanks, Raul