Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

On 17 July 2015 at 11:36, Ezequiel Garcia wrote: > Hi Antoine, > > On 07/17/2015 10:41 AM, Antoine Tenart wrote: >> >> Hi guys, >> >> On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: >>> >>> >>> This series was part of a bigger one[1], which was split into smaller >>> ones as asked

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

On 17 July 2015 at 11:36, Ezequiel Garcia wrote: > Hi Antoine, > > On 07/17/2015 10:41 AM, Antoine Tenart wrote: >> >> Hi guys, >> >> On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: >>> >>> >>> This series was part of a bigger one[1], which was split

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Ezequiel Garcia writes: >> >> The issue I see is that : >> - there is a bug in the clk driver for pxa3xx I introduced (CKEN_AB) >> - and shutting down the GCU clock prevents the NAND from working (I can't >> explain that one yet) Ah actually it's even trickier, but it has nothing to do with

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Ezequiel Garcia ezequ...@vanguardiasur.com.ar writes: The issue I see is that : - there is a bug in the clk driver for pxa3xx I introduced (CKEN_AB) - and shutting down the GCU clock prevents the NAND from working (I can't explain that one yet) Ah actually it's even trickier, but it has

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

On 3 August 2015 at 01:44, Robert Jarzmik wrote: > Ezequiel Garcia writes: > >> Just tested linux-next (hence *without* the patchset) and I see >> the same "Wait time out". In other words, pxa3xx-nand is broken >> on PXA :/ >> >> Interestingly, the culprit doesn't seem to be in pxa3xx-nand

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

On 3 August 2015 at 01:44, Robert Jarzmik robert.jarz...@free.fr wrote: Ezequiel Garcia ezequ...@vanguardiasur.com.ar writes: Just tested linux-next (hence *without* the patchset) and I see the same Wait time out. In other words, pxa3xx-nand is broken on PXA :/ Interestingly, the culprit

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Ezequiel Garcia writes: > Just tested linux-next (hence *without* the patchset) and I see > the same "Wait time out". In other words, pxa3xx-nand is broken > on PXA :/ > > Interestingly, the culprit doesn't seem to be in pxa3xx-nand itself. > Reverting the recent commits on pxa3xx-nand doesn't

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

On 20 July 2015 at 16:49, Robert Jarzmik wrote: > Ezequiel Garcia writes: > >> Here you go: >> >> http://git.infradead.org/users/ezequielg/linux/shortlog/refs/heads/pxa3xx-nand-timing-rework-v2 > > Okay, I've tested this on cm-x300. The result is not bright : > nand: device found,

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Ezequiel Garcia ezequ...@vanguardiasur.com.ar writes: Just tested linux-next (hence *without* the patchset) and I see the same Wait time out. In other words, pxa3xx-nand is broken on PXA :/ Interestingly, the culprit doesn't seem to be in pxa3xx-nand itself. Reverting the recent commits on

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

On 20 July 2015 at 16:49, Robert Jarzmik robert.jarz...@free.fr wrote: Ezequiel Garcia ezequ...@vanguardiasur.com.ar writes: Here you go: http://git.infradead.org/users/ezequielg/linux/shortlog/refs/heads/pxa3xx-nand-timing-rework-v2 Okay, I've tested this on cm-x300. The result is not

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Ezequiel Garcia writes: > Here you go: > > http://git.infradead.org/users/ezequielg/linux/shortlog/refs/heads/pxa3xx-nand-timing-rework-v2 Okay, I've tested this on cm-x300. The result is not bright : nand: device found, Manufacturer ID: 0xec, Chip ID: 0xdc nand: Samsung NAND

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Ezequiel Garcia ezequ...@vanguardiasur.com.ar writes: Here you go: http://git.infradead.org/users/ezequielg/linux/shortlog/refs/heads/pxa3xx-nand-timing-rework-v2 Okay, I've tested this on cm-x300. The result is not bright : nand: device found, Manufacturer ID: 0xec, Chip ID: 0xdc

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

On 17 July 2015 at 14:55, Robert Jarzmik wrote: > Ezequiel Garcia writes: > >> Hi Antoine, >> >> On 07/17/2015 10:41 AM, Antoine Tenart wrote: >>> Hi guys, >>> >>> On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: This series was part of a bigger one[1], which was split

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

On 17 July 2015 at 14:55, Robert Jarzmik robert.jarz...@free.fr wrote: Ezequiel Garcia ezequ...@vanguardiasur.com.ar writes: Hi Antoine, On 07/17/2015 10:41 AM, Antoine Tenart wrote: Hi guys, On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: This series was part of a bigger

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Ezequiel Garcia writes: > Hi Antoine, > > On 07/17/2015 10:41 AM, Antoine Tenart wrote: >> Hi guys, >> >> On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: >>> >>> This series was part of a bigger one[1], which was split into smaller >>> ones as asked by Ezequiel[2]. When we take

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Hi Antoine, On 07/17/2015 10:41 AM, Antoine Tenart wrote: Hi guys, On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: This series was part of a bigger one[1], which was split into smaller ones as asked by Ezequiel[2]. When we take this into account, this is v7. In addition,

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Hi guys, On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: > > This series was part of a bigger one[1], which was split into smaller > ones as asked by Ezequiel[2]. When we take this into account, this is > v7. In addition, there was absolutely no comment for more than 1 month >

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Hi Antoine, On 07/17/2015 10:41 AM, Antoine Tenart wrote: Hi guys, On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: This series was part of a bigger one[1], which was split into smaller ones as asked by Ezequiel[2]. When we take this into account, this is v7. In addition,

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Hi guys, On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: This series was part of a bigger one[1], which was split into smaller ones as asked by Ezequiel[2]. When we take this into account, this is v7. In addition, there was absolutely no comment for more than 1 month (since

Re: [PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Ezequiel Garcia ezequ...@vanguardiasur.com.ar writes: Hi Antoine, On 07/17/2015 10:41 AM, Antoine Tenart wrote: Hi guys, On Tue, Jul 07, 2015 at 05:08:23PM +0200, Antoine Tenart wrote: This series was part of a bigger one[1], which was split into smaller ones as asked by Ezequiel[2].

[PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Hi, This series was part of a bigger one[1], which was split into smaller ones as asked by Ezequiel[2]. When we take this into account, this is v7. In addition, there was absolutely no comment for more than 1 month (since June 2nd). Given this, I really expect the series to be merge soon as other

[PATCH v2 0/4] mtd: pxa3xx_nand: rework the timing setup

Hi, This series was part of a bigger one[1], which was split into smaller ones as asked by Ezequiel[2]. When we take this into account, this is v7. In addition, there was absolutely no comment for more than 1 month (since June 2nd). Given this, I really expect the series to be merge soon as other