[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191226105536.302C.4A936039@socionext.com>
Date: Thu, 26 Dec 2019 10:55:36 +0900
From: Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>
To: Mark Brown <broonie@...nel.org>
Cc: linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Keiji Hayashibara <hayashibara.keiji@...ionext.com>,
Masami Hiramatsu <masami.hiramatsu@...aro.org>,
Jassi Brar <jaswinder.singh@...aro.org>
Subject: Re: [PATCH 4/5] spi: uniphier: Add SPI_LOOP to the capabilities
Hi Mark,
Thanks for your comment.
On Wed, 25 Dec 2019 18:01:42 +0000 <broonie@...nel.org> wrote:
> On Tue, Dec 24, 2019 at 09:58:26AM +0900, Kunihiko Hayashi wrote:
> > Add SPI_LOOP to the capabilities to support loopback mode.
>
> > master->min_speed_hz = DIV_ROUND_UP(clk_rate, SSI_MAX_CLK_DIVIDER);
> > - master->mode_bits = SPI_CPOL | SPI_CPHA | SPI_CS_HIGH | SPI_LSB_FIRST;
> > + master->mode_bits = SPI_CPOL | SPI_CPHA | SPI_CS_HIGH | SPI_LSB_FIRST |
> > + SPI_LOOP;
>
> I'd expect to see a matching change that configures the hardware
> in loopback mode when the driver is in SPI_MODE? There's nothing
> in the existing driver.
I see. When doing loopback test using spi-loopback-test.c, I thought
'loop_req=1' option was needed, however, the controller doesn't need it.
We can ignore this patch.
Thank you,
---
Best Regards,
Kunihiko Hayashi
Powered by blists - more mailing lists