From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot, fsl_espi.c driver
Date: Thu, 9 Oct 2014 11:06:31 -0700 [thread overview]
Message-ID: <5436CEA7.6040006@freescale.com> (raw)
In-Reply-To: <OF0A783710.B34A5D0D-ONC1257D6C.005F9804-C1257D6C.00616440@transmode.se>
Dear Joakim,
On 10/09/2014 10:43 AM, Joakim Tjernlund wrote:
> York Sun <yorksun@freescale.com> wrote on 2014/10/09 18:25:40:
>>
>> Dear Joakim,
>>
>> Thanks for raising a concern.
>>
>> It's not fair to blame the last person who submitted a patch. We are all
> working
>
> No of course not, I just noticed you guys had been in there and patched up
> some problem
> so I hoped you would be interested to fix the remaining problems. This
> driver should never
> have been committed in the first place.
>
>> to make it better as an opensource comminuty. You have done a good job
> to hack
>> it to work. Would it be nicer if you can submit this or improved patch
> to u-boot
>> community for further review and testing, after putting informing commit
>> message? The mailing list address is CC'ed.
>
> Main problem with this driver is that TX does not work for:
> len > max_tran_len (nor does RX)
> does not TX the last odd bytes(len % 4 != 0)
> Does not work with TX only(RX buf == NULL)
>
> Silently ignores SPI_LSB_FIRST
>
> On top of that it uses malloc all over and copies data back and forth for
> no good
> reason, image a big SPI transfer with many MB(like my FPGA load).
>
> I am not in a good position fix this properly as my FPGA is TX only so I
> cannot test
> RX at all(which is broken by my hack)
>
> Finally, just to illustrate the merits of this driver, after transmission
> is done
> there is:
> if (*buffer == 0x0b) {
> data_in += tran_len;
> data_len -= tran_len;
> *(int *)buffer += tran_len;
> }
> what is the magic 0x0b test all about?
>
Thanks for the report. Driver maintainer (CC'ed) will take a look.
York
next prev parent reply other threads:[~2014-10-09 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF97D116FF.E9D0D2BB-ONC1257D6C.00582932-C1257D6C.00593FFA@transmode.se>
2014-10-09 16:25 ` [U-Boot] u-boot, fsl_espi.c driver York Sun
2014-10-09 16:58 ` Jagan Teki
2014-10-09 17:43 ` Joakim Tjernlund
2014-10-09 18:06 ` York Sun [this message]
2014-10-09 21:13 ` Joakim Tjernlund
2014-10-22 22:12 ` Joakim Tjernlund
2014-10-22 22:14 ` York Sun
2014-10-28 11:17 ` Mingkai.Hu at freescale.com
2014-10-29 18:43 ` Joakim Tjernlund
[not found] ` <OFD4798B41.D3AF8E28-ONC1257D80.00659E56-C1257D80.0066D615@LocalDomain>
2014-11-18 9:12 ` Joakim Tjernlund
2014-11-18 21:31 ` Jagan Teki
2014-11-19 18:09 ` Joakim Tjernlund
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=5436CEA7.6040006@freescale.com \
--to=yorksun@freescale.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.