mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Fries <David@fries.net>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] spi: spidev_test: Warn when the mode is not the requested mode
Date: Mon, 13 Jun 2022 09:35:35 -0500	[thread overview]
Message-ID: <YqdLNyIX8MCQ7Sfs@spacedout.fries.net> (raw)

Print a warning if the device mode doesn't match the requested mode.
The user doesn't enter the mode in hex so it isn't obvious when
setting the mode succeeds that the mode isn't the requested mode.  The
kernel logs a message, it will be more visible if the test also prints
a warning.  I was testing --quad, which is unsupported, but doesn't
cause the mode request to fail.

Signed-off-by: David Fries <David@Fries.net>
---
Sorry forgot to run checkpatch.pl though it was silent about the
comments, which I reworded.

 tools/spi/spidev_test.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/tools/spi/spidev_test.c b/tools/spi/spidev_test.c
index 83844f8b862a..941d713d6f23 100644
--- a/tools/spi/spidev_test.c
+++ b/tools/spi/spidev_test.c
@@ -417,6 +417,7 @@ int main(int argc, char *argv[])
 {
 	int ret = 0;
 	int fd;
+	uint32_t request;
 
 	parse_opts(argc, argv);
 
@@ -429,7 +430,10 @@ int main(int argc, char *argv[])
 
 	/*
 	 * spi mode
+	 * WR is write 'mode' to request the transfer mode
+	 * RD is read what mode the device actually is
 	 */
+	request = mode;
 	ret = ioctl(fd, SPI_IOC_WR_MODE32, &mode);
 	if (ret == -1)
 		pabort("can't set spi mode");
@@ -437,6 +441,14 @@ int main(int argc, char *argv[])
 	ret = ioctl(fd, SPI_IOC_RD_MODE32, &mode);
 	if (ret == -1)
 		pabort("can't get spi mode");
+	/*
+	 * Drivers can reject some mode options without returning an error.
+	 * Warn in this case to avoid the user thinking the requested mode is
+	 * supported since it didn't give an error.
+	 */
+	if (request != mode)
+		printf("WARNING device does not support requested mode 0x%x\n",
+			request);
 
 	/*
 	 * bits per word
-- 
2.30.2

             reply	other threads:[~2022-06-13 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 14:35 David Fries [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-13  5:39 David Fries
2022-06-13 12:08 ` Mark Brown
2022-06-13 17:24 ` 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=YqdLNyIX8MCQ7Sfs@spacedout.fries.net \
    --to=david@fries.net \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®