From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] Fix bug in T4240QDS code. Don't access nonexistent registers
Date: Tue, 22 Jul 2014 14:16:27 -0700 [thread overview]
Message-ID: <53CED4AB.6070607@freescale.com> (raw)
In-Reply-To: <1402929678-7496-1-git-send-email-vvv444@gmail.com>
This patch points out a bug in T4240QDS code. But the fix is not correct.
Shaohui, please take a closer look and submit a patch to fix it. I believe the
code should check each Bank of each SerDes (totally 8 clocks).
Thanks Vasili for pointing out.
York
On 06/16/2014 07:41 AM, Vasili Galka wrote:
> The code in misc_init_r() verifies actual SERDES clocks versus
> expected. It supposes that the number of clocks is MAX_SERDES.
> However, the number of pllcr0 registers is only SRDS_MAX_BANK. This
> clearly results in access to wrong memory. I don't have the datasheet
> to design a correct solution, but at least let's change it to access
> only the existing registers.
>
> Signed-off-by: Vasili Galka <vvv444@gmail.com>
> Cc: York Sun <yorksun@freescale.com>
> ---
> board/freescale/t4qds/t4240qds.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/board/freescale/t4qds/t4240qds.c b/board/freescale/t4qds/t4240qds.c
> index fe1bc7f..6646042 100644
> --- a/board/freescale/t4qds/t4240qds.c
> +++ b/board/freescale/t4qds/t4240qds.c
> @@ -662,7 +662,7 @@ int misc_init_r(void)
> }
> }
>
> - for (i = 0; i < MAX_SERDES; i++) {
> + for (i = 0; i < SRDS_MAX_BANK; i++) {
> u32 pllcr0 = srds_regs->bank[i].pllcr0;
> u32 expected = pllcr0 & SRDS_PLLCR0_RFCK_SEL_MASK;
> if (expected != actual[i]) {
>
next prev parent reply other threads:[~2014-07-22 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 14:41 [U-Boot] [RFC PATCH] Fix bug in T4240QDS code. Don't access nonexistent registers Vasili Galka
2014-06-17 15:55 ` York Sun
2014-07-22 21:16 ` York Sun [this message]
2014-07-22 21:31 ` York Sun
2014-07-23 1:59 ` Shaohui Xie
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=53CED4AB.6070607@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox