From: Tom Rini <trini@konsulko.com>
To: Masahisa Kojima <masahisa.kojima@linaro.org>
Cc: u-boot@lists.denx.de, Jassi Brar <jaswinder.singh@linaro.org>,
Satoru Okamoto <okamoto.satoru@socionext.com>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH 2/4] spi: synquacer: wait until slave is deselected
Date: Fri, 10 Jun 2022 17:40:21 -0400 [thread overview]
Message-ID: <20220610214021.GB2484912@bill-the-cat> (raw)
In-Reply-To: <20220517084139.6986-3-masahisa.kojima@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
On Tue, May 17, 2022 at 05:41:37PM +0900, Masahisa Kojima wrote:
> synquacer_cs_set() function does not wait the chip select
> is deasserted when the driver sets the DMSTOP to deselect
> the slave.
> This commit checks the Slave Select Released(SRS) bit to wait
> until the slave is deselected.
>
> Signed-off-by: Masahisa Kojima <masahisa.kojima@linaro.org>
> Signed-off-by: Satoru Okamoto <okamoto.satoru@socionext.com>
> Acked-by: Jassi Brar <jaswinder.singh@linaro.org>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-06-10 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 8:41 [PATCH 0/4] spi-synquacer fixes and improvement Masahisa Kojima
2022-05-17 8:41 ` [PATCH 1/4] spi: synquacer: busy variable must be initialized before use Masahisa Kojima
2022-05-18 3:42 ` Jassi Brar
2022-06-10 21:40 ` Tom Rini
2022-05-17 8:41 ` [PATCH 2/4] spi: synquacer: wait until slave is deselected Masahisa Kojima
2022-05-18 3:42 ` Jassi Brar
2022-06-10 21:40 ` Tom Rini [this message]
2022-05-17 8:41 ` [PATCH 3/4] spi: synquacer: DMSTART bit must not be set while transferring Masahisa Kojima
2022-05-18 3:43 ` Jassi Brar
2022-06-10 21:40 ` Tom Rini
2022-05-17 8:41 ` [PATCH 4/4] spi: synquacer: simplify tx completion checking Masahisa Kojima
2022-05-18 3:43 ` Jassi Brar
2022-06-10 21:40 ` Tom Rini
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=20220610214021.GB2484912@bill-the-cat \
--to=trini@konsulko.com \
--cc=jagan@amarulasolutions.com \
--cc=jaswinder.singh@linaro.org \
--cc=masahisa.kojima@linaro.org \
--cc=okamoto.satoru@socionext.com \
--cc=u-boot@lists.denx.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 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.