linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <linux-arm-kernel@lists.infradead.org>
Cc: <broonie@kernel.org>, <alexandre.belloni@bootlin.com>,
	<Ludovic.Desroches@microchip.com>, <linux-spi@vger.kernel.org>
Subject: Re: [PATCH] spi: atmel-quadspi: Add verbose debug facilities to monitor register accesses
Date: Wed, 25 Mar 2020 07:44:43 +0000	[thread overview]
Message-ID: <8737481.hkyJJAYeat@192.168.0.120> (raw)
In-Reply-To: <20200320121117.GA3961@sirena.org.uk>

On Friday, March 20, 2020 2:11:17 PM EET Mark Brown wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
> On Fri, Mar 20, 2020 at 06:51:01AM +0000, Tudor.Ambarus@microchip.com wrote:
> > From: Tudor Ambarus <tudor.ambarus@microchip.com>
> > 
> > This feature should not be enabled in release but can be useful for
> > developers who need to monitor register accesses at some specific places.
> 
> Looks a lot like the trace regmap would give you....

oh, I wasn't aware of that, I'll take a look. Thanks for the suggestion.
ta



  reply	other threads:[~2020-03-25  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20  6:51 [PATCH] spi: atmel-quadspi: Add verbose debug facilities to monitor register accesses Tudor.Ambarus-UWL1GkI3JZL3oGB3hsPCZA
     [not found] ` <20200320065058.891221-1-tudor.ambarus-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2020-03-20 12:11   ` Mark Brown
2020-03-25  7:44     ` Tudor.Ambarus [this message]
2020-03-20 13:05   ` Applied "spi: atmel-quadspi: Add verbose debug facilities to monitor register accesses" to the spi tree Mark Brown

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=8737481.hkyJJAYeat@192.168.0.120 \
    --to=tudor.ambarus@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-spi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).