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 v3] sunxi: Make DRAM_ODT_EN Kconfig setting a bool
Date: Tue, 19 May 2015 18:50:56 +0200	[thread overview]
Message-ID: <555B69F0.5030909@redhat.com> (raw)
In-Reply-To: <20150519175409.6c1b6e34@k10>

Hi,

On 05/19/2015 04:54 PM, Siarhei Siamashka wrote:
> On Tue, 19 May 2015 14:56:39 +0200
> Hans de Goede <hdegoede@redhat.com> wrote:
>
>> Make DRAM_ODT_EN Kconfig setting a bool, add a separate DRAM_ODT_CORRECTION
>> setting for A23 SoCs and use DRAM_ODT_EN Kconfig everywhere instead of
>> only in dram_sun4i.c and hardcoding odt_en elsewhere.
>>
>> Note this commit makes no functional changes for existing boards,
>> its purpose is to allow changing the odt_en value on future A33 boards.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>
> The sun4i part is fine.
>
> Regarding the A23 part, the only nitpick from me is the newly added
> CONFIG_DRAM_ODT_CORRECTION option. The description does not seem
> to be very informative in Kconfig:
>
>> +if MACH_SUN8I_A23
>> +config DRAM_ODT_CORRECTION
>> +	int "sunxi dram odt correction value"
>> +	default 0
>> +	---help---
>> +	Set the dram odt correction value (range -255 - 255).
>> +endif
>
> Since the right correction value is extracted from the FEX file (or
> where are we expected to get it from?), a short instruction about
> converting the 'dram_odt_en' parameter from FEX into the
> DRAM_ODT_CORRECTION option for U-Boot would be quite useful here.

Thanks for the review, adding a blurb to the Kconfig help on how
to get the correction value from a fex file is a good idea, I've
added such a blurb to the version in my personal tree.

Regards,

Hans

      reply	other threads:[~2015-05-19 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 12:56 [U-Boot] [PATCH v3] sunxi: Make DRAM_ODT_EN Kconfig setting a bool Hans de Goede
2015-05-19 14:13 ` Ian Campbell
2015-05-19 15:28   ` Siarhei Siamashka
2015-05-19 16:39   ` Hans de Goede
2015-05-19 18:41     ` Ian Campbell
2015-05-19 14:54 ` Siarhei Siamashka
2015-05-19 16:50   ` Hans de Goede [this message]

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=555B69F0.5030909@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