All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] SoCFPGA PL330 DMA driver and ECC scrubbing
Date: Fri, 29 Jun 2018 17:17:26 +0200	[thread overview]
Message-ID: <277351bc-f902-826b-f9f3-f00f380b1e81@denx.de> (raw)
In-Reply-To: <adb2bf50-55e0-f9a7-5c49-39ccbfb54e49@gmail.com>

On 06/29/2018 05:06 PM, Jason Rush wrote:
> On 6/29/2018 9:52 AM, Marek Vasut wrote:
>> On 06/29/2018 04:44 PM, Jason Rush wrote:
>>> On 6/29/2018 9:34 AM, Marek Vasut wrote:
>>>> On 06/29/2018 04:31 PM, Jason Rush wrote:
>>>>> Dinh,
>>>> Hi,
>>>>
>>>>> A while ago, you posted the following patchset for SoCFPGA to add the PL330
>>>>> DMA driver, and updated the SoCFPGA SDRAM init to write zeros to SDRAM to
>>>>> initialize the ECC bits if ECC was enabled:
>>>>>
>>>>> https://lists.denx.de/pipermail/u-boot/2016-October/269643.html
>>>>>
>>>>> I know it's been a long time, so I'll summarize some of the conversation...
>>>>>
>>>>> At the time, you had a problem with the patchset causing the SPL to fail to
>>>>> find the MMC.  You had tracked it down to an issue with the following commit
>>>>> "a78cd8613204 ARM: Rework and correct barrier definitions".  You and Marek
>>>>> discussed it a bit, but I don't think there was a real conclusion.  You
>>>>> submitted a second version of the patchset asking for advice on debugging
>>>>> the issue:
>>>>>
>>>>> https://lists.denx.de/pipermail/u-boot/2016-December/275822.html
>>>>>
>>>>> No real conversation came from the second patchset, and that was the end of
>>>>> the patch.
>>>>>
>>>>> I was hoping we could revisit adding your patchset again. I am working on a
>>>>> custom SoCFPGA board with a Cyclone V and ECC SDRAM. I rebased your patchset
>>>>> against v2018.05 and it is working on my custom board (although I don't have
>>>>> an MMC). I also tested it on a SoCKit booting from an MMC (I forced it to
>>>>> scrub the SDRAM on the SoCKit, because it doesn't have ECC RAM), and the
>>>>> SoCKit finds the MMC and boots.
>>>>>
>>>>> I don't have any suggestions on why it is working now on my board and not
>>>>> back when you first submitted the patchset.  Maybe something else was fixed
>>>>> in the MMC? I was hoping you and Marek could test this patch again on some
>>>>> different SoCFPGA boards to see if you get the same results.
>>>> Look at this patch
>>>> http://git.denx.de/?p=u-boot/u-boot-socfpga.git;a=commit;h=9bb8a249b292d26f152c20e3641600b3d7b3924b
>>>>
>>>> You likely want similar approach, it's faster then the DMA and much simpler.
>>>>
>>> Thanks Marek.  I'll give it a try.  Would you be interested in a similar patch for the Gen 5?
>> I don't have any Gen5 board which uses ECC, do you ?
>> If so, yes, prepare a patch, it should be very similar.
>>
>> Make sure to measure how long it takes to scrub the memory and how much
>> memory you have, I'd be interested in the numbers.
>>
> Looking at the master branch, it doesn't look like that code is ever being called?
> The sdram_init_ecc_bits() function is called from the ddr_calibration_sequence function(),
> but I can't find where ddr_calibration_sequence is called().

git grep for it, it's called from somewhere in the arch/arm/mach-socfpga/

> Either way, I can test it. I have a custom Cyclone V board with ECC, and the Intel Arria V SoC
> Dev Kit I can test it on too which I think has ECC.

Please do.

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2018-06-29 15:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29 14:31 [U-Boot] SoCFPGA PL330 DMA driver and ECC scrubbing Jason Rush
2018-06-29 14:34 ` Marek Vasut
2018-06-29 14:44   ` Jason Rush
2018-06-29 14:52     ` Marek Vasut
2018-06-29 15:06       ` Jason Rush
2018-06-29 15:17         ` Marek Vasut [this message]
2018-07-03 13:58           ` Jason Rush
2018-07-03 14:08             ` Marek Vasut
2018-07-03 23:45               ` Jason Rush
2018-07-04  7:23                 ` Marek Vasut
2018-07-05 23:11                   ` Jason Rush
2018-07-05 23:10                     ` Marek Vasut
2018-07-05 23:28                       ` Jason Rush
2018-07-06 22:56                       ` Jason Rush
2018-07-09  8:08                         ` Marek Vasut
2018-07-10 12:10                           ` Jason Rush
2018-07-10 16:11                             ` Marek Vasut
2018-07-11  3:11                               ` Jason Rush
2018-07-11  8:55                                 ` Marek Vasut
2018-07-11 13:49                                   ` Jason Rush
2018-07-11 13:48                                     ` Marek Vasut
2018-07-11 13:56                                       ` Jason Rush
2018-07-11 14:05                                         ` Marek Vasut
2018-07-11 17:30                                         ` Trent Piepho
2018-07-11 18:54                                           ` Marek Vasut
2018-07-13 12:50                                             ` Jason Rush
2018-07-13 14:54                                               ` Marek Vasut

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=277351bc-f902-826b-f9f3-f00f380b1e81@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.