From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-arm-kernel@lists.infradead.org,
Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org
Subject: Re: [PATCH v2 2/2] spi: pxa2xx: Debug print DMA burst and threshold
Date: Mon, 4 Mar 2019 14:28:23 +0200 [thread overview]
Message-ID: <fa772fa9-dd01-a7b0-2846-3349de005166@linux.intel.com> (raw)
In-Reply-To: <20190226114921.48205-2-andriy.shevchenko@linux.intel.com>
On 2/26/19 1:49 PM, Andy Shevchenko wrote:
> It's useful during debug to see what DMA burst and threshold sizes are.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/spi/spi-pxa2xx.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
> index 7a86654045fc..7cc4e85290b0 100644
> --- a/drivers/spi/spi-pxa2xx.c
> +++ b/drivers/spi/spi-pxa2xx.c
> @@ -1338,6 +1338,9 @@ static int setup(struct spi_device *spi)
> dev_warn(&spi->dev,
> "in setup: DMA burst size reduced to match bits_per_word\n");
> }
> + dev_dbg(&spi->dev,
> + "in setup: DMA burst and threshold set to %u, %u\n",
> + chip->dma_burst_size, chip->dma_threshold);
Printing chip->dma_threshold is not very informal here just after the
pxa2xx_spi_set_dma_burst_and_threshold() call which sets it to
(8 - 1 ) << 10 | (8 - 1) << 6 = 7616.
--
Jarkko
next prev parent reply other threads:[~2019-03-04 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 11:49 [PATCH v2 1/2] spi: pxa2xx: Introduce DMA burst size support Andy Shevchenko
2019-02-26 11:49 ` [PATCH v2 2/2] spi: pxa2xx: Debug print DMA burst and threshold Andy Shevchenko
2019-03-04 12:28 ` Jarkko Nikula [this message]
2019-03-04 12:37 ` [PATCH v2 1/2] spi: pxa2xx: Introduce DMA burst size support Jarkko Nikula
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=fa772fa9-dd01-a7b0-2846-3349de005166@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
/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).