From: Esben Haabendal <esben.haabendal@gmail.com>
To: Chuanhua Han <chuanhua.han@nxp.com>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
"broonie\@kernel.org" <broonie@kernel.org>,
"linux-spi\@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] spi: spi-mem: Add the spi_set_xfer_bpw function
Date: Wed, 10 Oct 2018 08:38:42 +0200 [thread overview]
Message-ID: <87d0sii9vx.fsf@gmail.com> (raw)
In-Reply-To: <AM6PR04MB435784E00F0C68A310CD281B97E00@AM6PR04MB4357.eurprd04.prod.outlook.com> (Chuanhua Han's message of "Wed, 10 Oct 2018 02:42:54 +0000")
Chuanhua Han <chuanhua.han@nxp.com> writes:
>> I am using XSPI mode on LS1021A, talking to a lot of different SPI devices.
>> And they all work, and I believe everything is quite "normal".
>>
> Since I don't have the board of LS1021, I can't test it. I use other boards
> with DSPI (such as LS1043, LS2088, etc.),
> and I test sp-flash connected on DSPI. If XSPI mode is used at this time, data
> cannot be transmitted normally.
Please describe what happens in much more detailed terms that "cannot be
transmitted normally". It is simply impossible to assist you when you
report problems in such general terms.
/Esben
next prev parent reply other threads:[~2018-10-10 6:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 7:06 [PATCH 1/2] spi: spi-mem: Add the spi_set_xfer_bpw function Chuanhua Han
2018-09-21 7:06 ` [PATCH 2/2] spi: spi-fsl-dspi: Fix support for XSPI transport mode Chuanhua Han
2018-09-28 6:37 ` Chuanhua Han
2018-09-28 6:55 ` Boris Brezillon
2018-09-29 14:56 ` Esben Haabendal
2018-09-29 15:43 ` Boris Brezillon
2018-09-30 2:49 ` Chuanhua Han
2018-09-21 7:06 ` [PATCH] spi: spi-mem: Adjust op len based on message/transfer size limitations Chuanhua Han
2018-09-21 7:15 ` Chuanhua Han
2018-09-28 6:37 ` [PATCH 1/2] spi: spi-mem: Add the spi_set_xfer_bpw function Chuanhua Han
2018-09-28 6:44 ` Boris Brezillon
2018-09-28 6:59 ` Chuanhua Han
2018-09-28 7:18 ` Boris Brezillon
2018-09-28 7:29 ` Chuanhua Han
2018-09-28 13:26 ` Mark Brown
2018-10-09 9:52 ` Chuanhua Han
2018-10-09 10:05 ` Boris Brezillon
2018-10-09 10:24 ` Chuanhua Han
2018-10-09 11:20 ` Esben Haabendal
2018-10-10 2:42 ` Chuanhua Han
2018-10-10 6:38 ` Esben Haabendal [this message]
2018-10-09 10:33 ` Mark Brown
2018-10-09 13:50 ` Esben Haabendal
2018-10-09 10:53 ` Esben Haabendal
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=87d0sii9vx.fsf@gmail.com \
--to=esben.haabendal@gmail.com \
--cc=boris.brezillon@bootlin.com \
--cc=broonie@kernel.org \
--cc=chuanhua.han@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.