From: Dinh Nguyen <dinguyen@opensource.altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv4 0/3] drivers/ddr/altera: Add the DDR controller driver for SoCFPGA
Date: Wed, 22 Jul 2015 23:03:59 -0500 [thread overview]
Message-ID: <55B067AF.4070601@opensource.altera.com> (raw)
In-Reply-To: <201507221501.12368.marex@denx.de>
On 7/22/15 8:01 AM, Marek Vasut wrote:
> On Wednesday, July 22, 2015 at 02:57:49 PM, Dinh Nguyen wrote:
>> On 7/22/15 4:00 AM, Marek Vasut wrote:
>>> On Wednesday, July 22, 2015 at 10:27:10 AM, Dinh Nguyen wrote:
>>>> On 7/20/15 2:40 PM, Marek Vasut wrote:
>>>>> On Monday, July 20, 2015 at 09:31:39 PM, Dinh Nguyen wrote:
>>>>> [...]
>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> yeah, I have some insane amount of cleanup patches and fixes
>>>>>>>>> already. I will post them once I'm done. What I am sorely missing
>>>>>>>>> is the UniPHY register interface documentation, it looks like that
>>>>>>>>> is not public, so I don't exactly know if what sequencer.c does is
>>>>>>>>> really correct. Sometimes I have serious doubts about that too .
>>>>>>>>> Can you give me the documentation please ?
>>>>>>>>
>>>>>>>> Have you seen this link[1]?
>>>>>>>
>>>>>>> Yes, but that is by far not all of the registers used in the
>>>>>>> sequencer.c, is it ?
>>>>>>
>>>>>> Looks like it's in the entire emi.pdf file[1]. Please look at volume
>>>>>> 3, or page 531 of 895. The section for the UniPHY.
>>>>>
>>>>> I extracted all the possible addresses used in the sequencer while
>>>>> cleaning it up, they're below.
>>
>> I cannot find these in any documentation.
>
> Cool %^)
>
>>>>> I checked the EMI RM, sure, but there seems to be many more registers
>>>>> all around the place than what are described in the EMI RM. Any ideas
>>>>> please ? Maybe this is not even the UniPHY anymore ?
>>>>
>>>> What I've been told was that the UniPHY was not really properly
>>>> documented, and that when anyone needed to modify the registers, they
>>>> would have to go back to the RTL to figure out exactly what's going on.
>>>
>>> I guess you cannot provide me with the RTL, right ?
>>
>> I don't think so, but will ask.
>
I was told that some of the RTL is actually deployed if you create a
Verilog DDR3 UniPHY example design for AV/CV system through IP
generation -- that should give you some more specific information. You
may have to create a soft-phy, soft-controller version for it to deploy
the unencrypted RTL.
I'll start this to see if I can find something helpful.
Dinh
prev parent reply other threads:[~2015-07-23 4:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 3:52 [U-Boot] [PATCHv4 0/3] drivers/ddr/altera: Add the DDR controller driver for SoCFPGA dinguyen at opensource.altera.com
2015-06-03 3:52 ` [U-Boot] [PATCHv4 1/3] driver/ddr/altera: Add DDR driver for Altera's SDRAM controller dinguyen at opensource.altera.com
2015-06-09 11:55 ` Pavel Machek
2015-06-09 12:58 ` Wolfgang Denk
2015-06-09 15:51 ` Dinh Nguyen
2015-06-22 9:38 ` Chin Liang See
2015-06-22 10:56 ` Pavel Machek
2015-06-03 3:52 ` [U-Boot] [PATCHv4 2/3] driver/ddr/altera: Add the sdram calibration portion dinguyen at opensource.altera.com
2015-06-09 12:21 ` Pavel Machek
2015-06-03 3:52 ` [U-Boot] [PATCHv4 3/3] arm: socfpga: enable the Altera SDRAM controller driver dinguyen at opensource.altera.com
2015-06-09 12:25 ` Pavel Machek
2015-06-26 16:43 ` [U-Boot] [PATCHv4 0/3] drivers/ddr/altera: Add the DDR controller driver for SoCFPGA Marek Vasut
2015-06-26 20:01 ` Marek Vasut
2015-07-12 19:50 ` Marek Vasut
2015-07-17 19:58 ` Dinh Nguyen
2015-07-17 20:22 ` Marek Vasut
2015-07-18 23:51 ` Marek Vasut
2015-07-20 13:40 ` Dinh Nguyen
2015-07-20 18:36 ` Marek Vasut
2015-07-20 19:31 ` Dinh Nguyen
2015-07-20 19:40 ` Marek Vasut
2015-07-21 22:46 ` Dinh Nguyen
2015-07-22 3:24 ` Marek Vasut
2015-07-23 18:29 ` Dinh Nguyen
2015-07-24 3:57 ` Marek Vasut
2015-07-22 8:27 ` Dinh Nguyen
2015-07-22 9:00 ` Marek Vasut
2015-07-22 12:57 ` Dinh Nguyen
2015-07-22 13:01 ` Marek Vasut
2015-07-23 4:03 ` Dinh Nguyen [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=55B067AF.4070601@opensource.altera.com \
--to=dinguyen@opensource.altera.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox