From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Mihai Sain <mihai.sain@microchip.com>,
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: Wed, 9 Oct 2024 08:04:38 +0100 [thread overview]
Message-ID: <cda8786a-493b-4838-8da9-5aa64c7603ae@linaro.org> (raw)
In-Reply-To: <ZwUJiAj_ZVztLvS5@finisterre.sirena.org.uk>
On 10/8/24 11:29 AM, Mark Brown wrote:
> On Tue, Oct 08, 2024 at 10:34:39AM +0100, Tudor Ambarus wrote:
>> 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).
>
>>> + 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?
>
> The objective of bringing the various AT91 drivers into consistency does
> seem useful so if this isn't OK for this driver we should probably
right, consistency is good.
> update the other drivers as well. Ensuring that people can get at the
Can be a goal. My point was that printing too much info in the boot log
may hide other more important information. Printing IP versions, irqs,
dma channels acquired (or worse, that a driver probed successful) shall
be part of debug prints if someone cares.
> IP version does feel useful, I guess it could also be a sysfs thing?
I'd also consider debugfs for IP version, it has less restrictions.
Mihai, do as you find best, it's just a suggestion.
next prev parent reply other threads:[~2024-10-09 7:04 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
2024-10-08 10:29 ` Mark Brown
2024-10-09 7:04 ` Tudor Ambarus [this message]
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=cda8786a-493b-4838-8da9-5aa64c7603ae@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).