From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mmc/dwmmc: remove recursive FIFO threshold setup
Date: Wed, 27 Nov 2013 17:20:49 +0900 [thread overview]
Message-ID: <5295AB61.9020903@samsung.com> (raw)
In-Reply-To: <1385538313.2648.24.camel@abrodkin-8560l>
Hi, Alexey.
On 11/27/2013 04:45 PM, Alexey Brodkin wrote:
> Hi Pantelis,
>
> On Wed, 2013-11-27 at 09:21 +0200, Pantelis Antoniou wrote:
>> Hi Alexey,
>>
>> On Nov 27, 2013, at 9:11 AM, Alexey Brodkin wrote:
>>
>
>> ATM if no host->fifoth_val value is provided the code will calculate one and write it.
>> Otherwise it will write the one configured.
>
> Indeed. But what I faced - if you try to run U-Boot more than 1 time
> after powering up your board then this calculated value will be
> calculated improperly. And in my comment to the patch itself I described
> it.
I understood your point. It's possible. If we set to calculated value,
then it's set to value lower than previous value. right?
if host->fifoth_val is always used somewhere, this value should be fixed.
But host->fifoth val was not used anywhere, so need to calculate the value.
This is problem.
Best Regards,
Jaehoon Chung
>
> So there're 2 options:
> 1. Re-implement calculation in such a way so it gets the same value on
> 2nd, 3rd and other U-Boot runs. Moreover it's not clear to me how this
> calculation is intended to work?
>
> We take some initial value and then modify it - note it's not simply
> overrided with some value, but initial/default value is read from the
> register, then goes some math, and then we put new value back.
>
> How do we know which value/configuration was by default so we do
> particular modifications later? What is a logic behind this?
>
> So why we need this functionality (unclear reconfiguration) if default
> register value works flawlessly in majority of cases and for some corner
> cases users may specify their custom value that will simply override
> default value.
>
>>> Still I have a couple of questions to you:
>>> 1. Why there's no example/instance of "host->fifoth_val" setup/usage in
>>> U-Boot source tree? If there was at least one I would leave
>>> "host->fifoth_val".
>>>
>>
>> I would guess it's because everyone uses the default setting of 0 which
>> results in a somewhat sane value.
>
> Regards,
> Alexey
>
prev parent reply other threads:[~2013-11-27 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 15:08 [U-Boot] [PATCH] mmc/dwmmc: remove recursive FIFO threshold setup Alexey Brodkin
2013-11-27 5:33 ` Jaehoon Chung
[not found] ` <1385536307.2648.9.camel@abrodkin-8560l>
2013-11-27 7:21 ` Pantelis Antoniou
[not found] ` <1385538313.2648.24.camel@abrodkin-8560l>
2013-11-27 8:04 ` Pantelis Antoniou
2013-11-27 12:30 ` Alexey Brodkin
2013-11-27 8:20 ` Jaehoon Chung [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=5295AB61.9020903@samsung.com \
--to=jh80.chung@samsung.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