From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Mihai Sain <mihai.sain@microchip.com>,
broonie@kernel.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: atmel-quadspi: Print the controller version and used irq
Date: Tue, 8 Oct 2024 10:34:39 +0100 [thread overview]
Message-ID: <1c525e43-d71c-4c4a-a8ac-96627cd6ea7e@linaro.org> (raw)
In-Reply-To: <20241008083226.51163-1-mihai.sain@microchip.com>
Hi, Mihai,
On 10/8/24 9:32 AM, Mihai Sain wrote:
> Add support to print the controller version and used irq
> similar to other at91 drivers (spi, twi, usart).
>
> Signed-off-by: Mihai Sain <mihai.sain@microchip.com>
> ---
> drivers/spi/atmel-quadspi.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/spi/atmel-quadspi.c b/drivers/spi/atmel-quadspi.c
> index 95cdfc28361e..757f07132585 100644
> --- a/drivers/spi/atmel-quadspi.c
> +++ b/drivers/spi/atmel-quadspi.c
> @@ -687,6 +687,8 @@ static int atmel_qspi_probe(struct platform_device *pdev)
> pm_runtime_mark_last_busy(&pdev->dev);
> pm_runtime_put_autosuspend(&pdev->dev);
>
> + dev_info(&pdev->dev, "AT91 QSPI Controller version %#x (irq %d)\n",
> + atmel_qspi_read(aq, QSPI_VERSION), irq);
This pollutes the console. Better to add a dev_dbg if you care.
And irq number doesn't bring too much value as you can see it in dt,
isn't it?
Cheers,
ta
next prev parent reply other threads:[~2024-10-08 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 8:32 [PATCH] spi: atmel-quadspi: Print the controller version and used irq Mihai Sain
2024-10-08 9:34 ` Tudor Ambarus [this message]
2024-10-08 10:29 ` Mark Brown
2024-10-09 7:04 ` Tudor Ambarus
2025-01-10 10:25 ` Alexander Dahl
2025-01-13 7:52 ` Mihai.Sain
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=1c525e43-d71c-4c4a-a8ac-96627cd6ea7e@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mihai.sain@microchip.com \
--cc=nicolas.ferre@microchip.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;
as well as URLs for NNTP newsgroup(s).