public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Paul Mundt <paul.mundt@nokia.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 2.6.17-rc3-omap] omap_uwire byteswap bugfix
Date: Thu, 4 May 2006 10:07:24 -0700	[thread overview]
Message-ID: <200605041007.24948.david-b@pacbell.net> (raw)
In-Reply-To: <200605040818.44126.david-b@pacbell.net>

[-- Attachment #1: Type: text/plain, Size: 783 bytes --]

On Thursday 04 May 2006 8:18 am, David Brownell wrote:
> On Thursday 04 May 2006 7:53 am, Paul Mundt wrote:
> 
> > This breaks the build, SPI_LSB_FIRST isn't defined anywhere..
> > ...
> > Looks like this is missing..
> > 
> > 	http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/spi-devices-can-require-lsb-first-encodings.patch
> > 
> > which isn't in Linus's tree either yet however.
> 
> Whoops, yes.  My bad, sorry; it was in _my_ tree and I overlooked how it got there.
> I thought maybe Juha had merged it.
> 
> Simplest fix would be to merge that patch from Greg's tree.

I take that back.  Simplest fix is to remove that code fragment, since
an equivalent one -- in the spi_bitbang infrastructure -- is found in
that nyet-merged patch.

- Dave


[-- Attachment #2: omap-uwire-tweak.patch --]
[-- Type: text/x-diff, Size: 821 bytes --]

Build fix ... the LSB_FIRST option isn't yet merged, and in any
case this driver doesn't need it since the LSB_FIRST patch handles
it in the spi_bitbang infrastructure used by omap_uwire.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>

Index: osk/drivers/spi/omap_uwire.c
===================================================================
--- osk.orig/drivers/spi/omap_uwire.c	2006-05-03 08:03:40.000000000 -0700
+++ osk/drivers/spi/omap_uwire.c	2006-05-04 10:05:14.000000000 -0700
@@ -317,12 +317,6 @@ static int uwire_setup(struct spi_device
 		goto done;
 	}
 
-	if (spi->mode & SPI_LSB_FIRST) {
-		pr_debug("%s: lsb first?\n", spi->dev.bus_id);
-		status = -EINVAL;
-		goto done;
-	}
-
 	/* mode 0..3, clock inverted separately;
 	 * standard nCS signaling;
 	 * don't treat DI=high as "not ready"

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2006-05-04 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03  5:15 [PATCH 2.6.17-rc3-omap] omap_uwire byteswap bugfix David Brownell
2006-05-04 14:53 ` Paul Mundt
2006-05-04 15:18   ` David Brownell
2006-05-04 17:07     ` David Brownell [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=200605041007.24948.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=paul.mundt@nokia.com \
    /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