public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] sun6i: Make dram clk and zq value Kconfig options
Date: Tue, 18 Nov 2014 12:32:02 +0100	[thread overview]
Message-ID: <546B2E32.2090008@redhat.com> (raw)
In-Reply-To: <1416250484.25454.28.camel@hellion.org.uk>

Hi,

On 11/17/2014 07:54 PM, Ian Campbell wrote:
> On Sun, 2014-11-16 at 17:16 +0100, Hans de Goede wrote:
> 
>> +config DRAM_ZQ
>> +	int "sun6i dram zq value" if EXPERT
>> +	default 123
> 
> == 0x7b, which differs from the previous default of 0x78 (not by much,
> but still)

Right, this is deliberate as I've gotten access to more boards, 123 seems
a better default (this is also what most A10 / A13 / A20 boards use).

> 
>> diff --git a/configs/Colombus_defconfig b/configs/Colombus_defconfig
>> index bef568d..5e245a3 100644
>> --- a/configs/Colombus_defconfig
>> +++ b/configs/Colombus_defconfig
>> @@ -4,3 +4,5 @@ CONFIG_FDTFILE="sun6i-a31-colombus.dtb"
>>  +S:CONFIG_ARCH_SUNXI=y
>>  +S:CONFIG_MACH_SUN6I=y
>>  +S:CONFIG_TARGET_COLOMBUS=y
>> ++S:CONFIG_DRAM_CLK=288
>> ++S:CONFIG_DRAM_ZQ=379
> 
> Do these actually take affect if CONFIG_EXPERT=n?

Ugh, I just checked, and no they don't.

> Perhaps CONFIG_TARGET_COLOMBUS should select DRAM_CLK == 288 and
> DRAM_CLK should be a hidden option?

I would prefer to keep these inside the defconfig's so that for
adding a new board only a defconfig needs to be added.

Currently the only CONFIG_TARGET_BOARD we actually use in u-boot is
the bananapi gmac tx clk delay tweak, and I would actually like
to keep things that way. Actually thinking more about this, I
think that that should be turned into a GMAC specific Kconfig option
and all the CONFIG_TARGET_BOARD stuff should be dropped, as it is
just a drag causing extra maintenance going forward.

So is there a way to not show a choice to the user unless EXPERT
mode is set, and still override it from Kconfig ?

If that is not (easily) possible, then I guess we will just need
to not make these "if EXPERT".

Regards,

Hans

  reply	other threads:[~2014-11-18 11:32 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
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 [this message]
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=546B2E32.2090008@redhat.com \
    --to=hdegoede@redhat.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