All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Lilja <lilja.magnus@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] SPI: Fix 32 bit transfers in mxc_spi.c
Date: Mon, 11 Jan 2010 19:41:57 +0100	[thread overview]
Message-ID: <4B4B70F5.7090203@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1001042103220.4269@axis700.grange>

Hi

Guennadi Liakhovetski skrev:
>>>> Hm, I'm afraid, I broke more than just that. Now that I look at this loop,
>>>> looks like I broke not only 32-bit transfers, but also all transfers with
>>>> bitlen > 16, and this fix is then incomplete - it doesn't fix cases with
>>>> bitlen > 32. Magnus, looks like you also only use single-block (bitlen=32)
>>>> transfers? Do you have a chance to test > 32-bit transfers too?
>>> No, I don't have anything suitable on the SPI bus that would allow me
>>> to test > 32-bit transfer.
>>
>> So, what was the verdict? I can only test SPI with the ATLAS (32 bit xfers).
>>
>> Can the patch be accepted even though it doesn't fix all problems or 
>> does it have to a "fix-everything"-patch?
> 
> I would prefer a proper fix, or an explicit restriction on transfer 
> length.

In that case it will be the latter, explicit restriction on transfer length with a printf and returning an error code from spi_xfer.

Regards, Magnus

      reply	other threads:[~2010-01-11 18:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 18:58 [U-Boot] [PATCH] SPI: Fix 32 bit transfers in mxc_spi.c Magnus Lilja
2009-12-02 22:32 ` Wolfgang Denk
2009-12-03  0:25   ` Guennadi Liakhovetski
2009-12-03  7:13     ` Magnus Lilja
2010-01-04 19:38       ` Magnus Lilja
2010-01-04 20:04         ` Guennadi Liakhovetski
2010-01-11 18:41           ` Magnus Lilja [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=4B4B70F5.7090203@gmail.com \
    --to=lilja.magnus@gmail.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.