From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] driver/ddr: Fix DDR4 driver for ARM
Date: Thu, 19 Jun 2014 11:05:54 -0700 [thread overview]
Message-ID: <53A32682.7070503@freescale.com> (raw)
In-Reply-To: <CAJgR-BgQuqas549fLbO8_bzsRa+h5S4_4SLvcin4F_hqMC13xg@mail.gmail.com>
Noted. Maybe we can pull in part of barrier.h into io.h. It is easier but I am
not sure if it is the cleanest way to go.
York
On 06/19/2014 11:01 AM, Jon Loeliger wrote:
> That might be a fine starting point. But I might point out
> that U-Boot has some notions down this line already too.
> For example, do a 'git grep wmb' in the U-Boot repo.
> Also ponder arch/arm/include/asm/io.h too.
>
> HTH,
> jdl
>
> On Thu, Jun 19, 2014 at 12:47 PM, York Sun <yorksun@freescale.com> wrote:
>> On 06/18/2014 07:57 AM, Jon Loeliger wrote:
>>> On Tue, Jun 17, 2014 at 5:07 PM, York Sun <yorksun@freescale.com> wrote:
>>>> Previously the driver was only tested on Power SoCs. Minor fix is needed
>>>> for ARM SoCs.
>>>>
>>>> Signed-off-by: York Sun <yorksun@freescale.com>
>>>
>>>
>>> Hi York!
>>>
>>>
>>>> --- a/drivers/ddr/fsl/fsl_ddr_gen4.c
>>>> +++ b/drivers/ddr/fsl/fsl_ddr_gen4.c
>>>
>>>> @@ -183,12 +184,20 @@ step2:
>>>> * we choose the max, that is 500 us for all of case.
>>>> */
>>>> udelay(500);
>>>> +#ifdef CONFIG_PPC
>>>> asm volatile("sync;isync");
>>>> +#else
>>>> + asm volatile("dsb sy;isb");
>>>> +#endif
>>>>
>>>> /* Let the controller go */
>>>> temp_sdram_cfg = ddr_in32(&ddr->sdram_cfg) & ~SDRAM_CFG_BI;
>>>> ddr_out32(&ddr->sdram_cfg, temp_sdram_cfg | SDRAM_CFG_MEM_EN);
>>>> +#ifdef CONFIG_PPC
>>>> asm volatile("sync;isync");
>>>> +#else
>>>> + asm volatile("dsb sy;isb");
>>>> +#endif
>>>>
>>>> total_gb_size_per_controller = 0;
>>>> for (i = 0; i < CONFIG_CHIP_SELECTS_PER_CTRL; i++) {
>>>
>>> This is a great example where we should try to introduce better abstractions
>>> in much the same way that Linux has. Specifically, we (U-Boot) collective
>>> might work toward some common lower-level abstractions such as a
>>> memory_barrier() (and variants), and let those generic names get mapped
>>> into architecture-specific implementations via a linked binding. Then this
>>> code would not need to change, nor would #ifdefs be needed.
>>>
>>
>> Jon,
>>
>> Are you suggesting to pick arch/<arch>/include/asm/barrier.h from Linux, or part
>> of it?
>>
>> York
>>
prev parent reply other threads:[~2014-06-19 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 22:07 [U-Boot] [PATCH] driver/ddr: Fix DDR4 driver for ARM York Sun
2014-06-18 14:57 ` Jon Loeliger
2014-06-18 15:46 ` York Sun
2014-06-19 17:47 ` York Sun
[not found] ` <CAJgR-BgQuqas549fLbO8_bzsRa+h5S4_4SLvcin4F_hqMC13xg@mail.gmail.com>
2014-06-19 18:05 ` York Sun [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=53A32682.7070503@freescale.com \
--to=yorksun@freescale.com \
--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.