public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MMC: DWMMC: Fix FIFO_DEPTH calculation
Date: Fri, 24 May 2013 15:46:29 +0900	[thread overview]
Message-ID: <519F0CC5.6090504@samsung.com> (raw)
In-Reply-To: <CAPs=JDeOmt17bYzxc3e1VGkbXmrifDAsapL2b=JFBa2=d1jjzg@mail.gmail.com>

Hi Jagan,

On 05/24/2013 03:15 PM, Rajeshwari Birje wrote:
> Hi Jagan,
> 
> Please find my comments below.
> On Fri, May 24, 2013 at 10:31 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>> On Fri, May 24, 2013 at 7:12 AM, Jaehoon Chung <jh80.chung@samsung.com> wrote:
>>> On 05/24/2013 03:27 AM, Jagan Teki wrote:
>>>> On Thu, May 23, 2013 at 6:45 PM, Rajeshwari Shinde
>>>> <rajeshwari.s@samsung.com> wrote:
>>>>> Current DWMMC driver used to give FIFO underrun/overrun error every 3rd time
>>>>> for mmc rescan command.
>>>>> In current code FIFO_DEPTH is getting calculated after reading the FIFOTH
>>>>> register and extracting the RX_WMARK bits from it i.e (RX_WMARK = FIFO_DEPTH/2 -1).
>>>>> Instead of storing the correct value, we were recalculating the FIFO_DEPT each
>>>>> time which is not correct.
>>>>>
>>>>> Signed-off-by: Hatim Ali <hatim.rv@samsung.com>
>>>>> Signed-off-by: Rajeshwari Shinde <rajeshwari.s@samsung.com>
>>>>> ---
>>>>>  drivers/mmc/dw_mmc.c |    6 ++++--
>>>>>  1 files changed, 4 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/drivers/mmc/dw_mmc.c b/drivers/mmc/dw_mmc.c
>>>>> index 4070d4e..be590a4 100644
>>>>> --- a/drivers/mmc/dw_mmc.c
>>>>> +++ b/drivers/mmc/dw_mmc.c
>>>>> @@ -332,11 +332,13 @@ static int dwmci_init(struct mmc *mmc)
>>>>>         dwmci_writel(host, DWMCI_BMOD, 1);
>>>>>
>>>>>         fifo_size = dwmci_readl(host, DWMCI_FIFOTH);
>>>>> -       if (host->fifoth_val)
>>>>> +       if (host->fifoth_val) {
>>>>
>>>> What is the inital value for host->fifoth_val, for the first time call.?
>>> It should be set into board-specific file(dw-mmc_exynos.c) or others.
>>
>> I am unable to find dw-mmc_exynos.c on the master, and also I haven't
>> see fifoth_val used other than dw_mmc.c
>> Could you please help me out.
> dw-mmc_exynos.c is merged in mmc tree. Yes  FIFO_DEPTH is set only in dw_mmc.c
host->fifoth_val should be set to hard-coding by developer.
In general case, it's right that fifoth_Val is calculated with register value.
But sometime, it needs to set to other value, not register value. 
Then we can use the host->fifoth_val in board-specific file.
Maybe it didn't use the host->fifoth_val anywhere. In future, we can use this.

Best Regards,
Jaehoon Chung
>>
>> Thanks,
>> Jagan.
>>
>>>
>>> Best Regards,
>>> Jaehoon Chung
>>>>
>>>>>                 fifoth_val = host->fifoth_val;
>>>>> -       else
>>>>> +       } else {
>>>>>                 fifoth_val = MSIZE(0x2) | RX_WMARK(fifo_size/2 -1) |
>>>>>                         TX_WMARK(fifo_size/2);
>>>>> +               host->fifoth_val = fifoth_val;
>>>>> +       }
>>>>>         dwmci_writel(host, DWMCI_FIFOTH, fifoth_val);
>>>>>
>>>>>         dwmci_writel(host, DWMCI_CLKENA, 0);
>>>>> --
>>>>> 1.7.4.4
>>>>>
>>>>
>>>> Thanks,
>>>> Jagan.
>>>>
>>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
> 

  reply	other threads:[~2013-05-24  6:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 13:15 [U-Boot] [PATCH] MMC: DWMMC: Fix FIFO_DEPTH calculation Rajeshwari Shinde
2013-05-23 17:01 ` Alim Akhtar
2013-05-23 18:27 ` Jagan Teki
2013-05-24  1:42   ` Jaehoon Chung
2013-05-24  5:01     ` Jagan Teki
2013-05-24  6:15       ` Rajeshwari Birje
2013-05-24  6:46         ` Jaehoon Chung [this message]
2013-05-24  8:14           ` Jagan Teki
2013-05-24  3:42 ` Jaehoon Chung

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=519F0CC5.6090504@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