All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Cc: Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	jim.cromie@gmail.com, Joe Perches <joe@perches.com>,
	Jason Baron <jbaron@akamai.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH v4 0/3] Venus dynamic debug
Date: Sun, 14 Jun 2020 01:39:16 +0300	[thread overview]
Message-ID: <20200613223919.7038-1-stanimir.varbanov@linaro.org> (raw)

Hello,

Time for v4 with following changes:
 * 1/3 taken comments into account - Greg KH
 * 2/3 kept the patch version from v2.

Cc: jim.cromie@gmail.com
Cc: Joe Perches <joe@perches.com>
Cc: Jason Baron <jbaron@akamai.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

I decided to keep 2/3 as it was in v2 of the current patchset
where the grouping of KERN_DEBUG messages has been accomplished
by dynamic debug 'format' filter. Depending on how WIP patches
from Jim [1] will progress I'm ready to change that. Until then
I'd like to have a  way to group the debug messages.
In case 2/3 is not accepted I'm willing to drop it from next
pull request.

v3 can be found at [2].

regards.
Stan

[1] https://lore.kernel.org/lkml/20200613155738.2249399-1-jim.cromie@gmail.com/T/#t
[2] https://lore.kernel.org/lkml/20200609104604.1594-1-stanimir.varbanov@linaro.org/

Stanimir Varbanov (3):
  venus: Add debugfs interface to set firmware log level
  venus: Make debug infrastructure more flexible
  venus: Add a debugfs file for SSR trigger

 drivers/media/platform/qcom/venus/Makefile    |  2 +-
 drivers/media/platform/qcom/venus/core.c      |  3 +
 drivers/media/platform/qcom/venus/core.h      |  8 +++
 drivers/media/platform/qcom/venus/dbgfs.c     | 51 +++++++++++++++
 drivers/media/platform/qcom/venus/dbgfs.h     | 12 ++++
 drivers/media/platform/qcom/venus/helpers.c   |  2 +-
 drivers/media/platform/qcom/venus/hfi_msgs.c  | 30 ++++-----
 drivers/media/platform/qcom/venus/hfi_venus.c | 27 ++++++--
 .../media/platform/qcom/venus/pm_helpers.c    |  3 +-
 drivers/media/platform/qcom/venus/vdec.c      | 63 +++++++++++++++++--
 drivers/media/platform/qcom/venus/venc.c      |  4 ++
 11 files changed, 172 insertions(+), 33 deletions(-)
 create mode 100644 drivers/media/platform/qcom/venus/dbgfs.c
 create mode 100644 drivers/media/platform/qcom/venus/dbgfs.h

-- 
2.17.1


             reply	other threads:[~2020-06-13 22:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13 22:39 Stanimir Varbanov [this message]
2020-06-13 22:39 ` [PATCH v4 1/3] venus: Add debugfs interface to set firmware log level Stanimir Varbanov
2020-06-14  6:35   ` Greg KH
2020-06-15 10:34     ` Stanimir Varbanov
2020-06-13 22:39 ` [PATCH v4 2/3] venus: Make debug infrastructure more flexible Stanimir Varbanov
2020-06-14  6:37   ` Greg KH
2020-06-15  9:55     ` Stanimir Varbanov
2020-06-15 12:03       ` Greg KH
2020-06-16 11:23         ` Stanimir Varbanov
2020-06-13 22:39 ` [PATCH v4 3/3] venus: Add a debugfs file for SSR trigger Stanimir Varbanov

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=20200613223919.7038-1-stanimir.varbanov@linaro.org \
    --to=stanimir.varbanov@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@akamai.com \
    --cc=jim.cromie@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.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.