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, 04 Jan 2010 20:38:42 +0100 [thread overview]
Message-ID: <4B4243C2.4030900@gmail.com> (raw)
In-Reply-To: <59b21cf20912022313m3e684e2ge1314a0f0f4868b@mail.gmail.com>
Hi
Magnus Lilja skrev:
> 2009/12/3 Guennadi Liakhovetski <lg@denx.de>:
>> On Wed, 2 Dec 2009, Wolfgang Denk wrote:
>>
>>> Dear Guennadi,
>>>
>>> In message <1257965907-5622-1-git-send-email-lilja.magnus@gmail.com> Magnus Lilja wrote:
>>>> diff --git a/drivers/spi/mxc_spi.c b/drivers/spi/mxc_spi.c
>>>> index fad9840..8b5d4be 100644
>>>> --- a/drivers/spi/mxc_spi.c
>>>> +++ b/drivers/spi/mxc_spi.c
>>>> @@ -142,6 +142,8 @@ int spi_xfer(struct spi_slave *slave, unsigned int bitlen, const void *dout,
>>>> *(u8 *)din = data;
>>>> else if (bitlen < 17)
>>>> *(u16 *)din = data;
>>>> + else
>>>> + *in_l = data;
>>>> }
>>>> }
>>> Could you please comment ?
>> 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?
Regards, Magnus
next prev parent reply other threads:[~2010-01-04 19:38 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 [this message]
2010-01-04 20:04 ` Guennadi Liakhovetski
2010-01-11 18:41 ` Magnus Lilja
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=4B4243C2.4030900@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.