All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: "Ulf Hansson" <ulf.hansson@linaro.org>,
	"Heiko Stübner" <heiko@sntech.de>
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: dw_mmc: fix pio mode when internal dmac is enabled
Date: Mon, 17 Aug 2015 19:21:21 +0900	[thread overview]
Message-ID: <55D1B5A1.3050209@samsung.com> (raw)
In-Reply-To: <CAPDyKFoCt=-PBWc+HPaF7Qe3DjgaiBo+-1GWYFvtZhgEsTPkMw@mail.gmail.com>

Hi, Ulf.

On 08/17/2015 07:16 PM, Ulf Hansson wrote:
> On 3 August 2015 at 17:04, Heiko Stübner <heiko@sntech.de> wrote:
>> The dw_mci_init_dma() may decide to not use dma, but pio instead, caused
>> by things like wrong dma settings in the system.
>>
>> Till now the code dw_mci_init_slot() always assumed that dma is available
>> when CONFIG_MMC_DW_IDMAC was defined, ignoring the host->use_dma var
>> set during dma init.
>>
>> So when now the dma init failed for whatever reason, the transfer sizes
>> would still be set for dma transfers, especially including the maximum
>> block-count calculated from host->ring_size and resulting in a
>>
>> [    4.991109] ------------[ cut here ]------------
>> [    4.991111] kernel BUG at drivers/mmc/core/core.c:256!
>> [    4.991113] Internal error: Oops - BUG: 0 [#1] SMP ARM
>>
>> because host->ring_size is 0 in this case and the slot init code uses
>> the wrong code to calculate the values.
>>
>> Fix this by selecting the correct calculations using the host->use_dma
>> variable instead of the CONFIG_MMC_DW_IDMAC config option.
>>
>> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
>> ---
>>  drivers/mmc/host/dw_mmc.c | 27 ++++++++++++++-------------
>>  1 file changed, 14 insertions(+), 13 deletions(-)
>>
>> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
>> index 40e9d8e..9ec3521 100644
>> --- a/drivers/mmc/host/dw_mmc.c
>> +++ b/drivers/mmc/host/dw_mmc.c
>> @@ -2391,19 +2391,20 @@ static int dw_mci_init_slot(struct dw_mci *host, unsigned int id)
>>                 mmc->max_seg_size = host->pdata->blk_settings->max_seg_size;
>>         } else {
>>                 /* Useful defaults if platform data is unset. */
>> -#ifdef CONFIG_MMC_DW_IDMAC
>> -               mmc->max_segs = host->ring_size;
>> -               mmc->max_blk_size = 65536;
>> -               mmc->max_seg_size = 0x1000;
>> -               mmc->max_req_size = mmc->max_seg_size * host->ring_size;
>> -               mmc->max_blk_count = mmc->max_req_size / 512;
>> -#else
>> -               mmc->max_segs = 64;
>> -               mmc->max_blk_size = 65536; /* BLKSIZ is 16 bits */
>> -               mmc->max_blk_count = 512;
>> -               mmc->max_req_size = mmc->max_blk_size * mmc->max_blk_count;
>> -               mmc->max_seg_size = mmc->max_req_size;
>> -#endif /* CONFIG_MMC_DW_IDMAC */
>> +               if (host->use_dma) {
>> +                       mmc->max_segs = host->ring_size;
> 
> I expect this may cause a compiler error since host->ring_size is only
> available in the struct dw_mci *host when CONFIG_MMC_DW_IDMAC is set.
> 
> I have already pulled in this patch from Jaehoon's pull request.
> Perhaps I should only amend the patch and change the host->ring_size
> to be always available no matter if CONFIG_MMC_DW_IDMAC is set or not?

Sorry for this. if you can, i think good that CONFIG_MMC_DW_IDMAC is removed at struct dw_mci.
Could you amend it?
If you want to get patch, i will send patch at now.

Best Regards,
Jaehoon Chung
> 
>> +                       mmc->max_blk_size = 65536;
>> +                       mmc->max_seg_size = 0x1000;
>> +                       mmc->max_req_size = mmc->max_seg_size * host->ring_size;
>> +                       mmc->max_blk_count = mmc->max_req_size / 512;
>> +               } else {
>> +                       mmc->max_segs = 64;
>> +                       mmc->max_blk_size = 65536; /* BLKSIZ is 16 bits */
>> +                       mmc->max_blk_count = 512;
>> +                       mmc->max_req_size = mmc->max_blk_size *
>> +                                           mmc->max_blk_count;
>> +                       mmc->max_seg_size = mmc->max_req_size;
>> +               }
>>         }
>>
>>         if (dw_mci_get_cd(mmc))
>> --
>> 2.1.4
>>
>>
> 
> Kind regards
> Uffe
> 


  reply	other threads:[~2015-08-17 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 15:04 [PATCH] mmc: dw_mmc: fix pio mode when internal dmac is enabled Heiko Stübner
2015-08-06  1:48 ` Jaehoon Chung
2015-08-17 10:16 ` Ulf Hansson
2015-08-17 10:21   ` Jaehoon Chung [this message]
2015-08-17 10:34     ` Ulf Hansson
2015-08-17 10:37       ` Heiko Stuebner

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=55D1B5A1.3050209@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tgih.jun@samsung.com \
    --cc=ulf.hansson@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.