Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mv_ddr: ddr3: only use active chip-selects when tuning ODT #18

Conversation

cpackham
Copy link
Contributor

On boards with particularly short traces the read sampling can end up 0
which can end up configuring an excessively long ODT read delay due to
the integer underflow of 'min_read_sample - 1'. When the read sampling
in ddr3_tip_write_additional_odt_setting gets a value lower than cas_l
make cas_l the minimum.

Signed-off-by: Chris Packham chris.packham@alliedtelesis.co.nz

Copy link
Contributor Author

@cpackham cpackham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually it appears that the problem is in the loop. Instead of going from 0 to MAX_CS_NUM it should be looking at only the active chip seltects

Inactive chip-selects will give invalid values for read_sample so don't
consider them when trying to determine the overall min/max read sample.

Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
@cpackham cpackham changed the title mv_ddr: ddr3: configure tODT read timings based on cas_l mv_ddr: ddr3: only use active chip-selects when tuning ODT Feb 28, 2019
stroese pushed a commit to stroese/u-boot that referenced this pull request Mar 19, 2019
Inactive chip-selects will give invalid values for read_sample so don't
consider them when trying to determine the overall min/max read sample.

Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>

[MarvellEmbeddedProcessors/mv-ddr-marvell#18]
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Signed-off-by: Stefan Roese <sr@denx.de>
@pali
Copy link
Contributor

pali commented Mar 2, 2021

This pull request was already merged by commit a87f4f7e81cef3afba0a002ab5d031dbffc9fa22 into master branch.

@kostapr kostapr closed this Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants