From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 01/10] arm: vf610: fix anadig register struct
Date: Thu, 17 Oct 2013 13:20:09 +0200 [thread overview]
Message-ID: <20131017132009.17f3f3e9@lilith> (raw)
In-Reply-To: <a5951a033e56dac0b367045f950973bc401ca624.1380539729.git.marcel@ziswiler.com>
Hi Marcel,
On Mon, 30 Sep 2013 13:26:06 +0200, Marcel Ziswiler
<marcel@ziswiler.com> wrote:
> The anadig_reg structure started at the wrong offset (fixed by adding
> resvA[4]), was missing some reserved field required for alignment
> purpose (resvB[3] between pll4_denom and pll6_ctrl) and further
> contained too short a reserved field causing further miss-alignment
> (resv10[7]).
>
> Discovered and tested by temporarily putting the following debug
> instrumentation into board_init():
> struct anadig_reg *anadig = (struct anadig_reg *)ANADIG_BASE_ADDR;
> printf("&anadig->pll3_ctrl=0x%p\n", &anadig->pll3_ctrl);
> printf("&anadig->pll5_ctrl=0x%p\n", &anadig->pll5_ctrl);
>
> Signed-off-by: Marcel Ziswiler <marcel@ziswiler.com>
> ---
> arch/arm/include/asm/arch-vf610/crm_regs.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/include/asm/arch-vf610/crm_regs.h b/arch/arm/include/asm/arch-vf610/crm_regs.h
> index 85f1fda..57a0242 100644
> --- a/arch/arm/include/asm/arch-vf610/crm_regs.h
> +++ b/arch/arm/include/asm/arch-vf610/crm_regs.h
> @@ -55,6 +55,7 @@ struct ccm_reg {
>
> /* Analog components control digital interface (ANADIG) */
> struct anadig_reg {
> + u32 resvA[4];
Can you name reserved fields based on their byte or register
index offset?
> u32 pll3_ctrl;
> u32 resv0[3];
> u32 pll7_ctrl;
> @@ -72,12 +73,13 @@ struct anadig_reg {
> u32 pll4_num;
> u32 resv7[3];
> u32 pll4_denom;
> + u32 resvB[3];
> u32 pll6_ctrl;
> u32 resv8[3];
> u32 pll6_num;
> u32 resv9[3];
> u32 pll6_denom;
> - u32 resv10[3];
> + u32 resv10[7];
> u32 pll5_ctrl;
> u32 resv11[3];
> u32 pll3_pfd;
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-10-17 11:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 11:26 [U-Boot] [PATCH v2 00/10] arm: vf610/vf610twr: vybrid tower fixes and enhancements Marcel Ziswiler
2013-09-30 11:26 ` [U-Boot] [PATCH v2 01/10] arm: vf610: fix anadig register struct Marcel Ziswiler
2013-10-17 11:20 ` Albert ARIBAUD [this message]
2013-10-17 11:21 ` Albert ARIBAUD
2013-09-30 11:26 ` [U-Boot] [PATCH v2 02/10] arm: vf610: clean-up " Marcel Ziswiler
2013-09-30 11:26 ` [U-Boot] [PATCH v2 03/10] arm: vf610: add uart0 clock definition Marcel Ziswiler
2013-09-30 11:26 ` [U-Boot] [PATCH v2 04/10] arm: vf610: add anadig pll5 definitions Marcel Ziswiler
2013-10-17 12:38 ` Albert ARIBAUD
2013-09-30 11:26 ` [U-Boot] [PATCH v2 05/10] arm: vf610: add enet1 base address definition Marcel Ziswiler
2013-09-30 11:26 ` [U-Boot] [PATCH v2 06/10] arm: vf610: add rmii clkout iomux definition Marcel Ziswiler
2013-09-30 11:26 ` [U-Boot] [PATCH v2 07/10] arm: vf610: add uart0 tx/rx iomux definitions Marcel Ziswiler
2013-09-30 11:26 ` [U-Boot] [PATCH v2 08/10] arm: vf610: add rmii1 " Marcel Ziswiler
2013-09-30 11:26 ` [U-Boot] [PATCH v2 09/10] arm: vf610: fix double iomux configuration for vf610twr board Marcel Ziswiler
2013-09-30 11:26 ` [U-Boot] [PATCH v2 10/10] arm: vf610: remove obsolete uart port configuration Marcel Ziswiler
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=20131017132009.17f3f3e9@lilith \
--to=albert.u.boot@aribaud.net \
--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