All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Balaji Rao <balajirrao-4Bgg8jF3iZdg9hUCZPvPmw@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Andy Green <andy-4Bgg8jF3iZdWk0Htik3J/w@public.gmane.org>,
	David Brownell
	<dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] spi_bitbang: Add support for non-blocking synchronous transfers
Date: Sat, 28 Feb 2009 11:15:24 +0100	[thread overview]
Message-ID: <20090228111524.1594a58e@lska2> (raw)
In-Reply-To: <20090228095846.GA32044-bnrf61MYqdMYW0ZX77RX+A@public.gmane.org>

On Sat, 28 Feb 2009 15:28:48 +0530
Balaji Rao <balajirrao-4Bgg8jF3iZdg9hUCZPvPmw@public.gmane.org> wrote:

> The master is not spi_s3c24xx but spi_s3x24xx_gpio, whose txrx are
> very simple code.
> 
> Additionally all of this has been tested and found to work. The code,
> along with the modified new spi based lis302dl driver is all in
> andy-tracking [1].

Oh, I didn't notice that. Nice then.

I see from the git logs that this and some other related patches have
been added now. Another question I have then is about the name: to me 
spi_non_blocking_transfer() sounds like it would do the opposite of
what I guess it does - it would go ahead without blocking on the call.

I guess what the name means is that it will not sleep during the call,
but for pushing it upstream, could it be better to name it something
else? Perhaps spi_sync and then rename the existing API name (which I
think is more than a bit strange), or maybe spi_sync_nowait or
something?

// Simon

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H

WARNING: multiple messages have this Message-ID (diff)
From: Simon Kagstrom <simon.kagstrom@gmail.com>
To: Balaji Rao <balajirrao@openmoko.org>
Cc: linux-kernel@vger.kernel.org,
	David Brownell <dbrownell@users.sourceforge.net>,
	Andy Green <andy@openmoko.com>,
	spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH 2/2] spi_bitbang: Add support for non-blocking synchronous transfers
Date: Sat, 28 Feb 2009 11:15:24 +0100	[thread overview]
Message-ID: <20090228111524.1594a58e@lska2> (raw)
In-Reply-To: <20090228095846.GA32044@fedora.yogi>

On Sat, 28 Feb 2009 15:28:48 +0530
Balaji Rao <balajirrao@openmoko.org> wrote:

> The master is not spi_s3c24xx but spi_s3x24xx_gpio, whose txrx are
> very simple code.
> 
> Additionally all of this has been tested and found to work. The code,
> along with the modified new spi based lis302dl driver is all in
> andy-tracking [1].

Oh, I didn't notice that. Nice then.

I see from the git logs that this and some other related patches have
been added now. Another question I have then is about the name: to me 
spi_non_blocking_transfer() sounds like it would do the opposite of
what I guess it does - it would go ahead without blocking on the call.

I guess what the name means is that it will not sleep during the call,
but for pushing it upstream, could it be better to name it something
else? Perhaps spi_sync and then rename the existing API name (which I
think is more than a bit strange), or maybe spi_sync_nowait or
something?

// Simon

  parent reply	other threads:[~2009-02-28 10:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28  8:10 [PATCH 0/2] spi: Add support for non-blocking synchronous transfers Balaji Rao
2009-02-28  8:10 ` [PATCH 1/2] " Balaji Rao
2009-02-28  8:11 ` [PATCH 2/2] spi_bitbang: " Balaji Rao
     [not found]   ` <20090228081117.31964.51155.stgit-bnrf61MYqdMYW0ZX77RX+A@public.gmane.org>
2009-02-28  9:09     ` Simon Kagstrom
2009-02-28  9:09       ` Simon Kagstrom
2009-02-28  9:58       ` Balaji Rao
2009-02-28  9:58         ` Balaji Rao
     [not found]         ` <20090228095846.GA32044-bnrf61MYqdMYW0ZX77RX+A@public.gmane.org>
2009-02-28 10:15           ` Simon Kagstrom [this message]
2009-02-28 10:15             ` Simon Kagstrom
2009-02-28 10:59             ` Balaji Rao
2009-02-28 10:59               ` Balaji Rao
     [not found] ` <20090228081036.31964.80618.stgit-bnrf61MYqdMYW0ZX77RX+A@public.gmane.org>
2009-02-28 20:33   ` [PATCH 0/2] spi: " David Brownell
2009-02-28 20:33     ` David Brownell
     [not found]     ` <200902281233.50612.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-02-28 22:12       ` Balaji Rao
2009-02-28 22:12         ` Balaji Rao
     [not found]         ` <20090228221247.GA3107-bnrf61MYqdMYW0ZX77RX+A@public.gmane.org>
2009-02-28 23:19           ` David Brownell
2009-02-28 23:19             ` David Brownell
2009-03-01  5:11             ` Balaji Rao
2009-03-01  9:49               ` David Brownell
2009-03-01 10:23                 ` Balaji Rao
2009-03-01  7:48     ` Andy Green
     [not found]       ` <49AA3DD6.4040807-4Bgg8jF3iZdWk0Htik3J/w@public.gmane.org>
2009-03-01  9:43         ` David Brownell
2009-03-01  9:43           ` David Brownell

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=20090228111524.1594a58e@lska2 \
    --to=simon.kagstrom-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=andy-4Bgg8jF3iZdWk0Htik3J/w@public.gmane.org \
    --cc=balajirrao-4Bgg8jF3iZdg9hUCZPvPmw@public.gmane.org \
    --cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.