From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] sun6i: dram: Do not try to initialize a second dram chan on A31s
Date: Mon, 17 Nov 2014 19:00:32 +0000 [thread overview]
Message-ID: <1416250832.25454.31.camel@hellion.org.uk> (raw)
In-Reply-To: <1416154613-8506-3-git-send-email-hdegoede@redhat.com>
On Sun, 2014-11-16 at 17:16 +0100, Hans de Goede wrote:
> The A31s only has one dram channel, so do not bother with trying to initalize
"initialize"
> a second channel.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> arch/arm/cpu/armv7/sunxi/Makefile | 2 +-
> arch/arm/cpu/armv7/sunxi/dram_sun6i.c | 11 +++++++++--
> 2 files changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/cpu/armv7/sunxi/Makefile b/arch/arm/cpu/armv7/sunxi/Makefile
> index 3b6ae47..1337b60 100644
> --- a/arch/arm/cpu/armv7/sunxi/Makefile
> +++ b/arch/arm/cpu/armv7/sunxi/Makefile
> @@ -10,6 +10,7 @@
> obj-y += timer.o
> obj-y += board.o
> obj-y += clock.o
> +obj-y += cpu_info.o
> obj-y += pinmux.o
> obj-$(CONFIG_MACH_SUN6I) += prcm.o
> obj-$(CONFIG_MACH_SUN8I) += prcm.o
> @@ -21,7 +22,6 @@ obj-$(CONFIG_MACH_SUN7I) += clock_sun4i.o
> obj-$(CONFIG_MACH_SUN8I) += clock_sun6i.o
>
> ifndef CONFIG_SPL_BUILD
> -obj-y += cpu_info.o
> ifdef CONFIG_ARMV7_PSCI
> obj-y += psci.o
> endif
> diff --git a/arch/arm/cpu/armv7/sunxi/dram_sun6i.c b/arch/arm/cpu/armv7/sunxi/dram_sun6i.c
> index 30439dc..2ac0b58 100644
> --- a/arch/arm/cpu/armv7/sunxi/dram_sun6i.c
> +++ b/arch/arm/cpu/armv7/sunxi/dram_sun6i.c
> @@ -372,10 +372,15 @@ unsigned long sunxi_dram_init(void)
> .rows = 16,
> };
>
> + /* A31s only has one channel */
> + if (sunxi_get_ss_bonding_id() == SUNXI_SS_BOND_ID_A31S)
> + para.chan = 1;
mctl_channel_init seems to contain some auto detection code, I suppose
that doesn't work in this case for some reason? Or is this just an
optimisation? In which case is the benefit just quicker to boot?
> +
> mctl_sys_init();
>
> mctl_dll_init(0, ¶);
> - mctl_dll_init(1, ¶);
> + if (para.chan == 2)
> + mctl_dll_init(1, ¶);
Both this an the next one are basically unrolled for-loops over
0-para.chan now. I suppose it doesn't really matter.
Ian.
next prev parent reply other threads:[~2014-11-17 19:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 16:16 [U-Boot] [PATCH 1/5] sun6i: Make dram clk and zq value Kconfig options Hans de Goede
2014-11-16 16:16 ` [U-Boot] [PATCH 2/5] sun6i: Add sunxi_get_ss_bonding_id() function Hans de Goede
2014-11-17 18:57 ` Ian Campbell
2014-11-16 16:16 ` [U-Boot] [PATCH 3/5] sun6i: dram: Do not try to initialize a second dram chan on A31s Hans de Goede
2014-11-17 19:00 ` Ian Campbell [this message]
2014-11-18 12:34 ` Hans de Goede
2014-11-18 14:08 ` Ian Campbell
2014-11-16 16:16 ` [U-Boot] [PATCH 4/5] sun6i: Drop some "unknown magic" from dram init Hans de Goede
2014-11-17 19:01 ` Ian Campbell
2014-11-18 12:47 ` Hans de Goede
2014-11-16 16:16 ` [U-Boot] [PATCH 5/5] sun6i: Add new CSQ_CS908 board Hans de Goede
2014-11-17 19:03 ` Ian Campbell
2014-11-18 12:47 ` Hans de Goede
2014-11-18 14:10 ` Ian Campbell
2014-11-19 13:41 ` Hans de Goede
2014-11-17 18:54 ` [U-Boot] [PATCH 1/5] sun6i: Make dram clk and zq value Kconfig options Ian Campbell
2014-11-18 11:32 ` Hans de Goede
2014-11-18 14:07 ` Ian Campbell
2014-11-19 13:39 ` Hans de Goede
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=1416250832.25454.31.camel@hellion.org.uk \
--to=ijc@hellion.org.uk \
--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