From: Flavio Suligoi <f.suligoi@asem.it>
To: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Mark Brown <broonie@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Flavio Suligoi <f.suligoi@asem.it>
Subject: [PATCH 1/1] spi: pxa2xx: add driver enabling message
Date: Mon, 8 Apr 2019 17:22:44 +0200 [thread overview]
Message-ID: <1554736964-6058-1-git-send-email-f.suligoi@asem.it> (raw)
Add an info message for the PXA2xx device driver start-up,
with the indication of the transfer mode used (DMA or GPIO).
This info is useful to individuate the timing when
the module starts.
Signed-off-by: Flavio Suligoi <f.suligoi@asem.it>
---
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 f7068cc..d449501 100644
--- a/drivers/spi/spi-pxa2xx.c
+++ b/drivers/spi/spi-pxa2xx.c
@@ -1826,6 +1826,9 @@ static int pxa2xx_spi_probe(struct platform_device *pdev)
goto out_error_clock_enabled;
}
+ dev_info(dev, "PXA2xx SPI master controller (%s mode)\n",
+ platform_info->enable_dma ? "DMA" : "PIO");
+
return status;
out_error_clock_enabled:
--
2.7.4
next reply other threads:[~2019-04-08 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 15:22 Flavio Suligoi [this message]
2019-04-09 13:48 ` [PATCH 1/1] spi: pxa2xx: add driver enabling message Jarkko Nikula
2019-04-09 14:11 ` Flavio Suligoi
2019-04-10 7:55 ` Jarkko Nikula
2019-04-10 8:13 ` Flavio Suligoi
2019-04-10 8:29 ` Jarkko Nikula
2019-04-10 8:47 ` Flavio Suligoi
2019-04-10 9:47 ` [PATCH v2 " Flavio Suligoi
2019-04-10 10:11 ` Jarkko Nikula
2019-04-10 10:16 ` Flavio Suligoi
2019-04-10 10:32 ` [PATCH " Mark Brown
2019-04-10 11:47 ` Flavio Suligoi
2019-04-10 11:54 ` Mark Brown
2019-04-10 12:01 ` Flavio Suligoi
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=1554736964-6058-1-git-send-email-f.suligoi@asem.it \
--to=f.suligoi@asem.it \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).