mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: "'David Brownell'" <david-b@pacbell.net>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
	spi-devel-general@lists.sourceforge.net,
	kyungmin.park@samsung.com,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: RE: [PATCH] [drivers] [SPI] SPI_GPIO: add support for controllers without MISO or MOSI pin
Date: Wed, 01 Jul 2009 08:57:50 +0200	[thread overview]
Message-ID: <000101c9fa19$44051540$cc0f3fc0$%szyprowski@samsung.com> (raw)
In-Reply-To: <200906301839.13764.david-b@pacbell.net>

Hello,

On Wednesday, July 01, 2009 3:39 AM, David Brownell wrote:

> > --- a/drivers/spi/spi_bitbang.c
> > +++ b/drivers/spi/spi_bitbang.c
> > @@ -392,6 +392,22 @@ int spi_bitbang_transfer(struct spi_device *spi, struct spi_message *m)
> >         unsigned long           flags;
> >         int                     status = 0;
> >
> > +       if (spi->master->flags & SPI_MASTER_NO_RX) {
> > +               struct spi_transfer *xfer;
> > +               list_for_each_entry(xfer, &m->transfers, transfer_list) {
> > +                       if (xfer->rx_buf)
> > +                               return -EINVAL;
> > +               }
> > +       }
> 
> Actually these two loops should merge, and likely move with
> spi_async() into the spi.c core code ... I'll split this
> support into a separate patch.

Ok. 

I created two separate loops because I thought that it will be faster, especially when the check must be done for each transfer
message request.

Best regards
--
Marek Szyprowski
Samsung Poland R&D Center




      reply	other threads:[~2009-07-01  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  5:35 Marek Szyprowski
2009-07-01  1:39 ` David Brownell
2009-07-01  6:57   ` Marek Szyprowski [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='000101c9fa19$44051540$cc0f3fc0$%szyprowski@samsung.com' \
    --to=m.szyprowski@samsung.com \
    --cc=david-b@pacbell.net \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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®