From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Mark Brown <broonie@kernel.org>, Tim Harvey <tharvey@gateworks.com>
Cc: Jan Glauber <jan.glauber@caviumnetworks.com>,
linux-spi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wolfgang Grandegger <wg@grandegger.com>,
linux-can <linux-can@vger.kernel.org>
Subject: Re: MCP251x SPI CAN controller on Cavium ThunderX
Date: Wed, 15 Nov 2017 11:54:20 +0100 [thread overview]
Message-ID: <bfa971bb-1217-ed86-d1d8-e353ecc506aa@pengutronix.de> (raw)
In-Reply-To: <20171114120207.xbee2cgsai4qka46@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1272 bytes --]
On 11/14/2017 01:02 PM, Mark Brown wrote:
> On Mon, Nov 13, 2017 at 01:17:42PM -0800, Tim Harvey wrote:
>
>> When a register is read from the mcp251x driver the
>> octeon_spi_do_transfer() gets a spi_message with a single spi_xfer of
>> len=3, a tx_buf, and an rx_buf which I believe is supposed to shift
>> out 3 bytes out MOSI and shift in 3 bytes from MISO where the last
>> byte shifted in would be the response.
>
> No, that will simultaneously transmit and recieve three bytes.
That's what the driver supposed to do.
> If you want to transmit two bytes and then recieve one byte you need
> two xfers, one with a len of 2 and a tx_buf, the other with a len of
> 1 and a rx_buf.
To read a register (mcp251x_read_reg()) the mcp251x does a 3 byte full
duplex transfer. The first byte send is the command (read register) the
second byte the register number the third byte is a dummy. The first 2
bytes received are ignored the 3rd byte is the register contents.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-11-15 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 21:17 Tim Harvey
2017-11-14 12:02 ` Mark Brown
2017-11-15 10:54 ` Marc Kleine-Budde [this message]
2017-11-15 12:07 ` Jan Glauber
2017-11-15 12:40 ` Marc Kleine-Budde
2017-11-15 13:31 ` Marc Kleine-Budde
2017-11-15 14:24 ` Jan Glauber
2017-11-15 15:39 ` Mark Brown
2017-11-15 16:02 ` David Daney
2017-11-15 18:23 ` Tim Harvey
2017-11-15 23:18 ` Tim Harvey
2017-11-16 12:12 ` Marc Kleine-Budde
2017-11-16 16:13 ` Tim Harvey
2017-11-16 12:41 ` 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=bfa971bb-1217-ed86-d1d8-e353ecc506aa@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=broonie@kernel.org \
--cc=jan.glauber@caviumnetworks.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tharvey@gateworks.com \
--cc=wg@grandegger.com \
/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®