All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Gilad Broner <gbroner@codeaurora.org>
Cc: James.Bottomley@HansenPartnership.com,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, santoshsy@gmail.com,
	linux-scsi-owner@vger.kernel.org, subhashj@codeaurora.org,
	ygardi@codeaurora.org, draviv@codeaurora.org,
	Lee Susman <lsusman@codeaurora.org>,
	Sujit Reddy Thumma <sthumma@codeaurora.org>,
	Vinayak Holikatti <vinholikatti@gmail.com>,
	"James E.J. Bottomley" <JBottomley@parallels.com>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v7 3/3] scsi: ufs: add trace events and dump prints for debug
Date: Thu, 12 Mar 2015 12:13:14 -0400	[thread overview]
Message-ID: <20150312121314.19c40cfd@gandalf.local.home> (raw)
In-Reply-To: <1426175700-23152-4-git-send-email-gbroner@codeaurora.org>

On Thu, 12 Mar 2015 17:55:00 +0200
Gilad Broner <gbroner@codeaurora.org> wrote:

> Add trace events to driver to allow monitoring and profilig
> of activities such as PM suspend/resume, hibernate enter/exit,
> clock gating and clock scaling up/down.
> In addition, add UFS host controller register dumps to provide
> detailed information in case of errors to assist in analysis
> of issues.
> 
> Signed-off-by: Dolev Raviv <draviv@codeaurora.org>
> Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
> Signed-off-by: Lee Susman <lsusman@codeaurora.org>
> Signed-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>
> Signed-off-by: Yaniv Gardi <ygardi@codeaurora.org>
> ---
>  drivers/scsi/ufs/ufs-qcom.c |  53 +++++
>  drivers/scsi/ufs/ufshcd.c   | 511 +++++++++++++++++++++++++++++++++++++++++---
>  drivers/scsi/ufs/ufshcd.h   |  49 ++++-
>  drivers/scsi/ufs/ufshci.h   |   1 +


>  include/trace/events/ufs.h  | 213 ++++++++++++++++++

For the tracing part...

Acked-by: Steven Rostedt <rostedt@goodmis.org>

-- Steve

>  5 files changed, 790 insertions(+), 37 deletions(-)
>  create mode 100644 include/trace/events/ufs.h

  reply	other threads:[~2015-03-12 16:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 15:54 [PATCH v7 0/3] Add ioctl and debug utilities to UFS driver Gilad Broner
2015-03-12 15:54 ` [PATCH v7 1/3] scsi: ufs: add ioctl interface for query request Gilad Broner
2015-03-12 15:54   ` Gilad Broner
2015-03-18 13:17   ` Dov Levenglick
2015-03-12 15:54 ` [PATCH v7 2/3] scsi: ufs: add debugfs for ufs Gilad Broner
2015-03-18 13:19   ` Dov Levenglick
2015-03-18 13:19     ` Dov Levenglick
2015-03-27 13:05   ` James Bottomley
2015-03-12 15:55 ` [PATCH v7 3/3] scsi: ufs: add trace events and dump prints for debug Gilad Broner
2015-03-12 16:13   ` Steven Rostedt [this message]
2015-03-18 13:20   ` Dov Levenglick
2015-03-18 13:20     ` Dov Levenglick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150312121314.19c40cfd@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=JBottomley@parallels.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=draviv@codeaurora.org \
    --cc=gbroner@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi-owner@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsusman@codeaurora.org \
    --cc=mingo@redhat.com \
    --cc=santoshsy@gmail.com \
    --cc=sthumma@codeaurora.org \
    --cc=subhashj@codeaurora.org \
    --cc=vinholikatti@gmail.com \
    --cc=ygardi@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.