Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Vijaya Krishna Nivarthi <quic_vnivarth@quicinc.com>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
	jirislaby@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	quic_msavaliy@quicinc.com, quic_vtanuku@quicinc.com
Subject: Re: [PATCH 0/2] Disable MMIO tracing from QUP wrapper and serial driver
Date: Mon, 2 May 2022 14:06:58 +0200	[thread overview]
Message-ID: <Ym/JYr3ltaKWqHQn@kroah.com> (raw)
In-Reply-To: <1651488314-19382-1-git-send-email-quic_vnivarth@quicinc.com>

On Mon, May 02, 2022 at 04:15:12PM +0530, Vijaya Krishna Nivarthi wrote:
> Register read/write tracing is causing excessive
> logging and filling the rtb buffer and effecting
> performance.
> 
> Disabled MMIO tracing from QUP wrapper and serial
> driver to disable register read/write tracing.
> 
> Vijaya Krishna Nivarthi (2):
>   soc: qcom: geni: Disable MMIO tracing
>   tty: serial: qcom_geni_serial: Disable MMIO tracing
> 
>  drivers/soc/qcom/qcom-geni-se.c       | 8 +++++++-
>  drivers/tty/serial/qcom_geni_serial.c | 8 +++++++-
>  2 files changed, 14 insertions(+), 2 deletions(-)
> 
> -- 
> 

Doesn't this series depend on the MMIO tracing series?  Why not just
make it part of that one?

confused,

greg k-h

  parent reply	other threads:[~2022-05-02 12:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 10:45 [PATCH 0/2] Disable MMIO tracing from QUP wrapper and serial driver Vijaya Krishna Nivarthi
2022-05-02 10:45 ` [PATCH 1/2] soc: qcom: geni: Disable MMIO tracing Vijaya Krishna Nivarthi
2022-05-02 12:07   ` Greg KH
2022-05-02 10:45 ` [PATCH 2/2] tty: serial: qcom_geni_serial: " Vijaya Krishna Nivarthi
2022-05-02 12:07   ` Greg KH
2022-05-02 12:06 ` Greg KH [this message]
2022-05-05  3:19   ` [PATCH 0/2] Disable MMIO tracing from QUP wrapper and serial driver Sai Prakash Ranjan

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=Ym/JYr3ltaKWqHQn@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=quic_msavaliy@quicinc.com \
    --cc=quic_vnivarth@quicinc.com \
    --cc=quic_vtanuku@quicinc.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox