public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Can Aydin <can.aydin@locatacorp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] [PATCH 0/4] Add support for Freescale's 85xx and P1/P2xxx eSPI controller
Date: Wed, 27 Oct 2010 21:50:38 +1100	[thread overview]
Message-ID: <4CC803FE.6060601@locatacorp.com> (raw)
In-Reply-To: <9FCE46230501DF4D9461B9ACC152FD7104CCB725@zmy16exm20.fsl.freescale.net>


On 13/10/2010 9:25 PM, Xie Shaohui-B21989 wrote:
> Hi Can,
>
> Are there any differences between your patches and
> http://lists.denx.de/pipermail/u-boot/2009-March/049093.html ?
>
>
> Best Regards,
> Shaohui Xie
>

Hello Shaohui,

Firstly,  I apologize for responding so late, we've been having some 
issues with our mail server.

In terms of differences, the big trivial one is that any modifications 
to common code such as spi_flash have been removed from the latest 
iteration of the patch. It is now just an eSPI driver with support added 
for cmd_spi in  P1_P2_RDB.h.

You'll note that the more significant change is that the spi_xfer 
function works quite differently now; the older version called an 80us 
delay between the tx and rx buffer accesses and always assumed that the 
rx buffer had valid data, this caused problems when transferring large 
amounts data at higher clock rates as tx/rx over-/under-flows would 
cause data corruption.

Hence, additional macros have also been defined for the various register 
fields that need to be checked for tx/rx buffer states during the 
read/write cycle.

Smaller, more cosmetic changes have also been made to reduce magic 
numbers and such.

I've been trying to send in the v3 submission of the patch for a couple 
of days now but have not, as yet, succeeded in getting it through. Third 
time lucky I hope.

Regards,

Can

  reply	other threads:[~2010-10-27 10:50 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 22:14 [U-Boot] [RFC PATCH 0/3] Add device tree support for ARM to U-Boot John Rigby
2010-08-05 22:14 ` [U-Boot] [RFC 1/3] FDT: Add fixup support of multiple banks of memory John Rigby
2010-08-05 23:26   ` Kumar Gala
2010-08-05 23:36     ` John Rigby
2010-08-10 19:39       ` Grant Likely
2010-08-10 20:17         ` Dan Malek
2010-08-10 20:26           ` Grant Likely
2010-08-10 21:17             ` Dan Malek
2010-08-10 21:03         ` John Rigby
2010-08-10 21:09           ` Grant Likely
2010-08-10 22:22         ` Scott Wood
2010-09-28  9:56     ` [U-Boot] [RFC] [PATCH 0/4] Add support for Freescale's 85xx and P1/P2xxx eSPI controller Can Aydin
2010-09-28 11:02       ` Reinhard Meyer
2010-09-28 11:49         ` Can Aydin
2010-09-28 12:27           ` Can Aydin
2010-09-28 12:46           ` Wolfgang Denk
2010-09-28 13:22             ` Reinhard Meyer
2010-09-28 23:37               ` Can Aydin
2010-09-28 23:50             ` Can Aydin
2010-10-13 10:25       ` Xie Shaohui-B21989
2010-10-27 10:50         ` Can Aydin [this message]
2010-08-05 22:14 ` [U-Boot] [RFC 2/3] ARM: WIP: add flat device tree support John Rigby
2010-08-05 22:31   ` Wolfgang Denk
2010-08-05 23:07     ` John Rigby
2010-08-10 19:44   ` Grant Likely
2010-08-10 19:46     ` Grant Likely
2010-08-10 20:23     ` Albert ARIBAUD
2010-08-10 20:48       ` John Rigby
2010-08-10 21:01         ` Wolfgang Denk
2010-08-05 22:14 ` [U-Boot] [RFC 3/3] ARM: add config for beagle with fdt enabled John Rigby
2010-08-05 22:35   ` Wolfgang Denk
2010-08-05 23:04     ` John Rigby
2010-09-01 16:53 ` [U-Boot] [PATCH 0/5] Device tree support for ARM John Rigby
2010-09-01 16:53 ` [U-Boot] [PATCH 1/5] FDT: Add fixup support for multiple banks of memory John Rigby
2010-09-01 16:53 ` [U-Boot] [PATCH 2/5] FDT: only call boot_get_fdt from generic code John Rigby
2010-09-01 16:53 ` [U-Boot] [PATCH 3/5] boot: change some arch ifdefs to feature ifdefs John Rigby
2010-09-01 16:53 ` [U-Boot] [PATCH 4/5] ARM: add flat device tree support John Rigby
2010-10-06 15:26   ` Rob Herring
2010-09-01 16:53 ` [U-Boot] [PATCH 5/5] ARM: enable device tree for beagle John Rigby
2010-09-01 16:59   ` John Rigby

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=4CC803FE.6060601@locatacorp.com \
    --to=can.aydin@locatacorp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox