Re: [U-Boot] [RFC] [PATCH 0/4] Add support for Freescale's 85xx and P1/P2xxx eSPI controller

2010-10-27 Thread Can Aydin
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 so

[U-Boot] [PATCH v3 2/2] Freescale 85xx/P1/P2 eSPI controller driver

2010-10-26 Thread Can Aydin
Add support for Freescale eSPI driver in P1/P2 board configuration Signed-off-by: Can Aydin --- Changes for v2: - Coding style cleanup - Removed modifications to common code Changes for v3: - fixed whitespace between function calls and parameters - replaced

[U-Boot] [PATCH v3 1/2] Freescale 85xx/P1/P2 eSPI controller driver

2010-10-26 Thread Can Aydin
Driver for the Freescale eSPI controller found in 85xx, P1/P2 and P4xx SoCs. Signed-off-by: Can Aydin --- Changes for v2: - Coding style cleanup - Removed modifications to common code Changes for v3: - fixed whitespace between function calls and parameters

Re: [U-Boot] [PATCH v2] Freescale 85xx/P1/P2 eSPI controller driver

2010-10-24 Thread Can Aydin
Dear Wolfgang Denk, On 24/10/2010 11:21 PM, Wolfgang Denk wrote: > Dear Can Aydin, > > In message<1287920728-6458-1-git-send-email-can.ay...@locatacorp.com> you > wrote: >> Driver for the Freescale eSPI controller found in 85xx, P1/P2 and P4xx SoCs. > ... >> +

[U-Boot] [PATCH v2] Freescale 85xx/P1/P2 eSPI controller driver

2010-10-24 Thread Can Aydin
Driver for the Freescale eSPI controller found in 85xx, P1/P2 and P4xx SoCs. Signed-off-by: Can Aydin --- Changes for v2: - Coding style cleanup - Removed modifications to common code drivers/spi/Makefile|1 + drivers/spi/fsl_espi.c | 256

Re: [U-Boot] [RFC] [PATCH 0/4] Add support for Freescale's 85xx and P1/P2xxx eSPI controller

2010-09-28 Thread Can Aydin
Dear Wolfgang, On 28/09/2010 10:46 PM, Wolfgang Denk wrote: > > >> People could also choose to bitbang the SPI on their custom hardware but >> again I feel that might defeat the purpose and spirit of u-boot. (Then >> again, I'm new so don't quote me on that). > Oops? Where exactly do you see co

Re: [U-Boot] [RFC] [PATCH 0/4] Add support for Freescale's 85xx and P1/P2xxx eSPI controller

2010-09-28 Thread Can Aydin
On 28/09/2010 11:22 PM, Reinhard Meyer wrote: Dear Wolfgang Denk, Can Aydin, True, a GPIO pin could be re-purposed to serve as chip select, but that would involve a soldering iron and a steady hand as the P1/P2xxRDB That was not the question. Reinhard asked if the SPI Chip Select Pins could

Re: [U-Boot] [RFC] [PATCH 0/4] Add support for Freescale's 85xx and P1/P2xxx eSPI controller

2010-09-28 Thread Can Aydin
>> Can the Chip Select Pins be used as GPIO? It might be simpler to do >> that than >> adding a speciality to common code. > True, a GPIO pin could be re-purposed to serve as chip select, but that > would involve a soldering iron and a steady hand as the P1/P2xxRDB > boards are reference design b

Re: [U-Boot] [RFC] [PATCH 0/4] Add support for Freescale's 85xx and P1/P2xxx eSPI controller

2010-09-28 Thread Can Aydin
Dear Reinhard, On 28/09/2010 9:02 PM, Reinhard Meyer wrote: > Dear Can Aydin, >> The reason this is an RFC is that unfortunately the hardware on these >> chips does not permit indefinite SPI transactions on a given chip >> select. A chip select is asserted only when a &#x

[U-Boot] [RFC] [PATCH 4/4] FSL eSPI support on P1/P2 RDB platforms

2010-09-28 Thread Can Aydin
Add FSL eSPI support on P1/P2 RDB platforms Signed-off-by: Can Aydin --- include/configs/P1_P2_RDB.h | 18 ++ 1 files changed, 18 insertions(+), 0 deletions(-) diff --git a/include/configs/P1_P2_RDB.h b/include/configs/P1_P2_RDB.h index 7e901e1..d830b4a 100644 --- a

[U-Boot] [RFC] [PATCH 2/4] Freescale 85xx/P1/P2 eSPI controller driver

2010-09-28 Thread Can Aydin
Driver for the Freescale eSPI controller found in 85xx, P1/P2 and P4xx SoCs. Signed-off-by: Can Aydin --- drivers/spi/Makefile |1 + drivers/spi/fsl_espi.c | 251 include/fsl_espi.h | 50 ++ 3 files changed, 302

[U-Boot] [RFC] [PATCH 3/4] FSL eSPI support for the Spansion Flash driver

2010-09-28 Thread Can Aydin
-by: Can Aydin --- drivers/mtd/spi/spansion.c | 60 --- 1 files changed, 55 insertions(+), 5 deletions(-) mode change 100644 => 100755 drivers/mtd/spi/spansion.c diff --git a/drivers/mtd/spi/spansion.c b/drivers/mtd/spi/spansion.c old mode 100644

[U-Boot] [RFC] [PATCH 1/4] Support for 'single frame' spi flash commands

2010-09-28 Thread Can Aydin
s the case with the Freescale eSPI controller. Signed-off-by: Can Aydin --- drivers/mtd/spi/spi_flash.c | 38 +++-- drivers/mtd/spi/spi_flash_internal.h |9 2 files changed, 44 insertions(+), 3 deletions(-) mode change 100644 => 10075

[U-Boot] [RFC] [PATCH 0/4] Add support for Freescale's 85xx and P1/P2xxx eSPI controller

2010-09-28 Thread Can Aydin
Hi All, This patch series adds support for the eSPI controller found on the newer range of Freescale SoCs including the 85xx, P1/P2xx (and I believe the P4xx) series. The reason this is an RFC is that unfortunately the hardware on these chips does not permit indefinite SPI transactions on a

Re: [U-Boot] [PATCH] eSPI and Intel E1000 support for P1/P2 RDB

2010-09-15 Thread Can Aydin
On 9/08/2010 5:57 AM, Wolfgang Denk wrote: > Dear Kumar Gala, > > In message<57cdb146-383a-4629-b7e4-c2729200a...@kernel.crashing.org> you > wrote: >> On Jun 23, 2010, at 8:56 AM, Poonam Aggrwal wrote: >> >>> This patch enables the eSPI configuration to use >>> the Spansion Flash on P1 and P2 R

[U-Boot] P20xx/P10xx/MPC85xx eSPI direct boot

2010-06-06 Thread Can Aydin
Has anyone come across (or written) a tool/script/makefile target to pack u-boot into a SPI boot image (i.e. with boot header and config symbols) to boot directly from SPI on the P2020RDB (or P1020 etc.) and/or MPC8536DS? Would it be within the scope of u-boot to have such an option? Can

[U-Boot] Toggling pins using the BDI3000

2010-05-02 Thread Can Aydin
ratio and boot ROM location from the signals, and more importantly, override any erroneus signals that the hardware on the platform (P2020RDB and later, the prototype) might be providing (or failing to provide) it. (without using an oscilloscope and a soldering iron that is). Regards, Can