[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200522162901.GP5801@sirena.org.uk>
Date: Fri, 22 May 2020 17:29:01 +0100
From: Mark Brown <broonie@...nel.org>
To: dillon min <dillon.minfei@...il.com>
Cc: Rob Herring <robh+dt@...nel.org>, p.zabel@...gutronix.de,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Alexandre Torgue <alexandre.torgue@...com>,
thierry.reding@...il.com, Sam Ravnborg <sam@...nborg.org>,
Dave Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
"open list:DRM PANEL DRIVERS" <dri-devel@...ts.freedesktop.org>,
linux-clk <linux-clk@...r.kernel.org>
Subject: Re: [PATCH v4 3/8] spi: stm32: Add 'SPI_SIMPLEX_RX', 'SPI_3WIRE_RX'
support for stm32f4
On Fri, May 22, 2020 at 11:59:25PM +0800, dillon min wrote:
> but, after spi-core create a dummy tx_buf or rx_buf, then i can't get
> the correct spi_3wire direction.
> actually, this dummy tx_buf is useless for SPI_3WIRE. it's has meaning
> for SPI_SIMPLE_RX mode,
> simulate SPI_FULL_DUMPLEX
Oh, that's annoying. I think the fix here is in the core, it should
ignore MUST_TX and MUST_RX in 3WIRE mode since they clearly make no
sense there.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists