From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 1/2] mtd: cqspi: Simplify indirect write code
Date: Wed, 04 May 2016 21:16:39 +0200 [thread overview]
Message-ID: <572A4A97.9080008@denx.de> (raw)
In-Reply-To: <20160504190452.GB9986@amd>
On 05/04/2016 09:04 PM, Pavel Machek wrote:
> Hi!
>
>> The indirect write code is buggy pile of nastiness which fails horribly
>> when the system runs fast enough to saturate the controller. The failure
>> results in some pages (256B) not being written to the flash. This can be
>> observed on systems which run with Dcache enabled and L2 cache enabled,
>> like the Altera SoCFPGA.
>>
>> This patch replaces the whole unmaintainable indirect write implementation
>> with the one from upcoming Linux CQSPI driver, which went through multiple
>> rounds of thorough review and testing. While this makes the patch look
>> terrifying and violates all best-practices of software development, all
>> the patch does is it plucks out duplicate ad-hoc code distributed across
>> the driver and replaces it with more compact code doing exactly the same
>> thing.
>
> Ok, sorry, I still don't understand the changelog.
>
> First, it describes the bug with L2 cache enabled, but then it says
> that "all the patch does .. doing exactly the same thing".
>
> So I assume it does not do the same thing, but replaces duplicated
> code in u-boot with working code from Linux?
Ah right, the linux code also does FIFO level checking, so it doesn't
overflow during the writes.
> Thanks for doing this,
> Pavel
>
>
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2016-05-04 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 17:25 [U-Boot] [PATCH V2 1/2] mtd: cqspi: Simplify indirect write code Marek Vasut
2016-05-03 17:25 ` [U-Boot] [PATCH V2 2/2] mtd: cqspi: Simplify indirect read code Marek Vasut
2016-05-04 9:00 ` Stefan Roese
2016-05-04 9:00 ` [U-Boot] [PATCH V2 1/2] mtd: cqspi: Simplify indirect write code Stefan Roese
2016-05-04 19:04 ` Pavel Machek
2016-05-04 19:16 ` Marek Vasut [this message]
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=572A4A97.9080008@denx.de \
--to=marex@denx.de \
--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