From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/4] ddr: marvell: use correct TREFI value
Date: Thu, 18 Jan 2018 17:16:08 +1300 [thread overview]
Message-ID: <20180118041610.20669-3-judge.packham@gmail.com> (raw)
In-Reply-To: <20180118041610.20669-1-judge.packham@gmail.com>
The ternary operation had the HIGH/LOW values the
wrong way round. Update it to use the correct value.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
---
Changes in v2:
- new
drivers/ddr/marvell/a38x/ddr3_training.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ddr/marvell/a38x/ddr3_training.c b/drivers/ddr/marvell/a38x/ddr3_training.c
index 043143adf08a..2eb6e05783d4 100644
--- a/drivers/ddr/marvell/a38x/ddr3_training.c
+++ b/drivers/ddr/marvell/a38x/ddr3_training.c
@@ -1375,7 +1375,7 @@ int ddr3_tip_freq_set(u32 dev_num, enum hws_access_type access_type,
/* adjust t_refi to new frequency */
t_refi = (tm->interface_params[if_id].interface_temp ==
- HWS_TEMP_HIGH) ? TREFI_LOW : TREFI_HIGH;
+ HWS_TEMP_HIGH) ? TREFI_HIGH : TREFI_LOW;
t_refi *= 1000; /*psec */
/* HCLK in[ps] */
--
2.15.1
next prev parent reply other threads:[~2018-01-18 4:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 4:16 [U-Boot] [PATCH v2 0/4] ddr: marvell: update DDR driver Chris Packham
2018-01-18 4:16 ` [U-Boot] [PATCH v2 1/4] ddr: marvell: only assert M_ODT[0] on write for a single CS Chris Packham
2018-01-18 4:16 ` Chris Packham [this message]
2018-01-18 4:16 ` [U-Boot] [PATCH v2 3/4] ddr: marvell: update additional ODT setting Chris Packham
2018-01-18 4:16 ` [U-Boot] [PATCH v2 4/4] ddr: marvell: update ddr controller init and freq Chris Packham
2018-01-20 8:59 ` [U-Boot] [PATCH v2 0/4] ddr: marvell: update DDR driver Stefan Roese
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=20180118041610.20669-3-judge.packham@gmail.com \
--to=judge.packham@gmail.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