From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] DW SPI: fixes and improvements
Date: Wed, 21 Mar 2018 19:07:05 +0000 [thread overview]
Message-ID: <1521659224.9805.52.camel@synopsys.com> (raw)
In-Reply-To: <CAD6G_RQBGYMdDc+KnR3U3nuSKiHgcZ0xeybqEHnYkDU+AofPVQ@mail.gmail.com>
Hi Jagan,
On Thu, 2018-03-22 at 00:04 +0530, Jagan Teki wrote:
> On Tue, Mar 13, 2018 at 8:44 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> > On Mon, Mar 5, 2018 at 6:47 PM, Eugeniy Paltsev
> > <Eugeniy.Paltsev@synopsys.com> wrote:
> > > Various fixes and improvements of designware spi driver.
> > >
> > > Eugeniy Paltsev (5):
> > > DW SPI: fix tx data loss on FIFO flush
> > > DW SPI: fix transmit only mode
> > > DW SPI: refactor poll_transfer functions
> > > DW SPI: add option to use external gpio for chip select
> > > DW SPI: use 32 bit access instead of 16 and 32 bit mix
> >
> > Can someone test this series?
We did test it on or platform (Synopsys HSDK) where it works just fine.
-Alexey
prev parent reply other threads:[~2018-03-21 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 13:17 [U-Boot] [PATCH 0/5] DW SPI: fixes and improvements Eugeniy Paltsev
2018-03-05 13:17 ` [U-Boot] [PATCH 1/5] DW SPI: fix tx data loss on FIFO flush Eugeniy Paltsev
2018-03-21 19:14 ` Jagan Teki
2018-03-05 13:17 ` [U-Boot] [PATCH 2/5] DW SPI: fix transmit only mode Eugeniy Paltsev
2018-03-05 13:17 ` [U-Boot] [PATCH 3/5] DW SPI: refactor poll_transfer functions Eugeniy Paltsev
2018-03-05 13:17 ` [U-Boot] [PATCH 4/5] DW SPI: add option to use external gpio for chip select Eugeniy Paltsev
2018-03-05 13:17 ` [U-Boot] [PATCH 5/5] DW SPI: use 32 bit access instead of 16 and 32 bit mix Eugeniy Paltsev
2018-03-13 15:14 ` [U-Boot] [PATCH 0/5] DW SPI: fixes and improvements Jagan Teki
2018-03-21 18:34 ` Jagan Teki
2018-03-21 19:07 ` Alexey Brodkin [this message]
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=1521659224.9805.52.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox