From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v0 3/5] arm: mvebu: Fix SAR1_CPU_CORE_MASK
Date: Wed, 28 Oct 2015 17:34:36 +0100 [thread overview]
Message-ID: <5630F91C.6040103@denx.de> (raw)
In-Reply-To: <1446047056-16801-4-git-send-email-dirk.eibach@gdsys.cc>
Hi Dirk,
On 28.10.2015 16:44, dirk.eibach at gdsys.cc wrote:
> From: Dirk Eibach <dirk.eibach@gdsys.cc>
>
> SAR1_CPU_CORE_MASK was wrong, probably copy/paste
> from another architecture.
>
> Signed-off-by: Dirk Eibach <dirk.eibach@gdsys.cc>
> ---
>
> drivers/ddr/marvell/a38x/ddr3_hws_hw_training_def.h | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/ddr/marvell/a38x/ddr3_hws_hw_training_def.h b/drivers/ddr/marvell/a38x/ddr3_hws_hw_training_def.h
> index 7500a72..06d0ab1 100644
> --- a/drivers/ddr/marvell/a38x/ddr3_hws_hw_training_def.h
> +++ b/drivers/ddr/marvell/a38x/ddr3_hws_hw_training_def.h
> @@ -23,8 +23,8 @@
>
> #define CPU_CONFIGURATION_REG(id) (0x21800 + (id * 0x100))
> #define CPU_MRVL_ID_OFFSET 0x10
> -#define SAR1_CPU_CORE_MASK 0x00000018
> -#define SAR1_CPU_CORE_OFFSET 3
> +#define SAR1_CPU_CORE_MASK 0x38000000
> +#define SAR1_CPU_CORE_OFFSET 27
>
> #define NEW_FABRIC_TWSI_ADDR 0x4e
> #ifdef DB_784MP_GP
> @@ -461,7 +461,4 @@
> #define CLK_CPU_2200 13
> #define CLK_CPU_2400 14
>
> -#define SAR1_CPU_CORE_MASK 0x00000018
> -#define SAR1_CPU_CORE_OFFSET 3
> -
> #endif /* _DDR3_HWS_HW_TRAINING_DEF_H */
Thanks for spotting. Seems to be correct from the datasheet. How did
you find this problem? What exactly did happen on your board?
Reviewed-by: Stefan Roese <sr@denx.de>
Thanks,
Stefan
next prev parent reply other threads:[~2015-10-28 16:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 15:44 [U-Boot] [PATCH v0 0/5] Some improvements for mvebu/a38x dirk.eibach at gdsys.cc
2015-10-28 15:44 ` [U-Boot] [PATCH v0 1/5] pci: mvebu: Fix Armada 38x support dirk.eibach at gdsys.cc
2015-10-28 16:24 ` Stefan Roese
2015-11-17 12:55 ` Anton Schubert
2015-11-18 12:48 ` Dirk Eibach
2015-11-18 13:23 ` Anton Schubert
2015-11-18 14:51 ` Dirk Eibach
2015-10-28 15:44 ` [U-Boot] [PATCH v0 2/5] arm: mvebu: Add gpio support dirk.eibach at gdsys.cc
2015-10-28 16:41 ` Stefan Roese
2015-10-28 15:44 ` [U-Boot] [PATCH v0 3/5] arm: mvebu: Fix SAR1_CPU_CORE_MASK dirk.eibach at gdsys.cc
2015-10-28 16:34 ` Stefan Roese [this message]
2015-10-29 9:41 ` Dirk Eibach
2015-10-29 9:45 ` Luka Perkov
2015-10-28 15:44 ` [U-Boot] [PATCH v0 4/5] arm: mvebu: Fix ddr3_init() cpu config dirk.eibach at gdsys.cc
2015-10-28 16:35 ` Stefan Roese
2015-10-29 9:51 ` Dirk Eibach
2015-10-29 10:03 ` Stefan Roese
2016-03-24 8:37 ` Stefan Roese
2015-10-28 15:44 ` [U-Boot] [PATCH v0 5/5] spi: Add support for Armada 38x second controller dirk.eibach at gdsys.cc
2015-10-28 16:29 ` Jagan Teki
2015-10-28 16:39 ` Stefan Roese
2015-10-29 9:54 ` Dirk Eibach
2015-10-29 10:02 ` Stefan Roese
2015-10-29 10:31 ` Dirk Eibach
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=5630F91C.6040103@denx.de \
--to=sr@denx.de \
--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.