From: Oleksij Rempel <ore@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de, Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Oleksij Rempel <linux@rempel-privat.de>
Subject: Re: [PATCH v1] spi: loopback-test: provide loop request option.
Date: Thu, 13 Jul 2017 06:55:12 +0200 [thread overview]
Message-ID: <e92fb0c9-cd6e-7cc8-fb7d-141cb8f2c0e7@pengutronix.de> (raw)
In-Reply-To: <20170712134020.17927-1-o.rempel@pengutronix.de>
On 12.07.2017 15:40, Oleksij Rempel wrote:
> From: Oleksij Rempel <linux@rempel-privat.de>
>
> Provide a module parameter to request internal
> loop by the SPI master controller.
> This should make loop testing easier without extra HW modification.
>
> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
> ---
> drivers/spi/spi-loopback-test.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/spi/spi-loopback-test.c b/drivers/spi/spi-loopback-test.c
> index f4875f177df0..34e1544d7d0e 100644
> --- a/drivers/spi/spi-loopback-test.c
> +++ b/drivers/spi/spi-loopback-test.c
> @@ -51,6 +51,14 @@ MODULE_PARM_DESC(loopback,
> "is checked to match tx_buf after the spi_message " \
> "is executed");
>
> +/* the device is jumpered for loopback - enabling some rx_buf tests */
> +int loop_req;
> +module_param(loop_req, int, 0);
> +MODULE_PARM_DESC(loop_req,
> + "if set enable controller will be asked to enable " \
i need to correct this ^^^.
And wait if there any other comments :)
> + "test loop mode. If supported, MISO and MOSI will be " \
> + "jumpered by SPI controller");
> +
> /* run only a specific test */
> int run_only_test = -1;
> module_param(run_only_test, int, 0);
> @@ -313,6 +321,16 @@ static int spi_loopback_test_probe(struct spi_device *spi)
> {
> int ret;
>
> + if (loop_req) {
> + spi->mode = SPI_LOOP | spi->mode;
> + ret = spi_setup(spi);
> + if (ret) {
> + dev_err(&spi->dev, "SPI setup wasn't successful %d\n", ret);
> + dev_err(&spi->dev, "SPI_LOOP is not supported by SPI master.");
> + return -ENODEV;
> + }
> + }
> +
> dev_info(&spi->dev, "Executing spi-loopback-tests\n");
>
> ret = spi_test_run_tests(spi, spi_tests);
>
next prev parent reply other threads:[~2017-07-13 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 13:40 Oleksij Rempel
2017-07-13 4:55 ` Oleksij Rempel [this message]
2017-07-13 7:42 ` Uwe Kleine-König
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=e92fb0c9-cd6e-7cc8-fb7d-141cb8f2c0e7@pengutronix.de \
--to=ore@pengutronix.de \
--cc=broonie@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=o.rempel@pengutronix.de \
/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®