From: ezequiel@vanguardiasur.com.ar (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 05/12] mtd: pxa3xx_nand: rework flash detection and timing setup
Date: Sat, 16 May 2015 18:23:23 -0300 [thread overview]
Message-ID: <5557B54B.9010307@vanguardiasur.com.ar> (raw)
In-Reply-To: <20150512143943.GC32171@kwain>
On 05/12/2015 11:39 AM, Antoine Tenart wrote:
> Ezequiel,
>
> On Mon, May 11, 2015 at 07:10:56PM -0300, Ezequiel Garcia wrote:
>>
>> On 05/11/2015 11:58 AM, Antoine Tenart wrote:
>> [..]
>>> -
>>> - /* calculate flash information */
>>> - host->read_id_bytes = (f->page_size == 2048) ? 4 : 2;
>>> -
>>
>> [..]
>>> @@ -1732,6 +1669,7 @@ static int alloc_nand_resource(struct platform_device *pdev)
>>> host->mtd = mtd;
>>> host->cs = cs;
>>> host->info_data = info;
>>> + host->read_id_bytes = 4;
>>
>> Are you sure this is correct? The value is set according to the page
>> size before this patch.
>
> Before reading the ID, the pxa3xx driver uses a default configuration,
> builtin_flash_types[0], which defines a page size of 2048 leading to set
> host->read_id_bytes to 4.
>
> I'm using this default value here.
>
> There might be an issue, as host->read_id_bytes isn't updated after
> reading the ID (and getting the actual page size). I don't know if this
> can be a problem. I can modify pxa3xx_nand_config_flash() to update
> host->read_id_bytes if needed. What do you think?
>
Well, once the device is detected, READ_ID shouldn't be used, so I'm not
sure what's the point of that.
--
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2015-05-16 21:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 14:58 [PATCH v5 00/12] ARM: berlin: add nand support Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 01/12] mtd: pxa3xx_nand: add a non mandatory ECC clock Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 02/12] Documentation: bindings: document the clocks for pxa3xx-nand Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 03/12] mtd: pxa3xx_nand: add a default chunk size Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 04/12] mtd: pxa3xx_nand: add helpers to setup the timings Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 05/12] mtd: pxa3xx_nand: rework flash detection and timing setup Antoine Tenart
2015-05-11 22:10 ` Ezequiel Garcia
2015-05-12 14:39 ` Antoine Tenart
2015-05-16 21:23 ` Ezequiel Garcia [this message]
2015-05-20 13:55 ` Antoine Tenart
2015-05-20 13:56 ` Ezequiel Garcia
2015-05-20 14:04 ` Antoine Tenart
2015-05-16 22:02 ` Ezequiel Garcia
2015-05-20 14:03 ` Antoine Tenart
2015-05-20 14:05 ` Ezequiel Garcia
2015-05-11 14:58 ` [PATCH v5 06/12] mtd: pxa3xx_nand: clean up the pxa3xx timings Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 07/12] mtd: nand: add Samsung K9GBG08U0A-M to nand_ids table Antoine Tenart
2015-05-16 18:57 ` Ezequiel Garcia
2015-05-20 14:06 ` Antoine Tenart
2015-05-20 14:09 ` Ezequiel Garcia
2015-05-20 14:24 ` Antoine Tenart
2015-05-20 14:43 ` Antoine Tenart
2015-05-24 18:42 ` Ezequiel Garcia
2015-07-20 18:08 ` Brian Norris
2015-07-20 18:22 ` Ezequiel Garcia
2015-05-11 14:58 ` [PATCH v5 08/12] mtd: pxa3xx_nand: add support for the Marvell Berlin nand controller Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 09/12] Documentation: bindings: add the Berlin nand controller compatible Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 10/12] mtd: nand: let Marvell Berlin SoCs select the pxa3xx driver Antoine Tenart
2015-05-11 14:59 ` [PATCH v5 11/12] ARM: berlin: add BG2Q node for the nand Antoine Tenart
2015-05-11 14:59 ` [PATCH v5 12/12] ARM: berlin: enable flash on the BG2Q DMP Antoine Tenart
2015-05-16 21:37 ` [PATCH v5 00/12] ARM: berlin: add nand support Ezequiel Garcia
2015-05-20 14:08 ` Antoine Tenart
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=5557B54B.9010307@vanguardiasur.com.ar \
--to=ezequiel@vanguardiasur.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).