public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Dinh Nguyen <dinh.linux@gmail.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	dinguyen@altera.com, linux-mmc@vger.kernel.org,
	Doug Anderson <dianders@chromium.org>,
	James Hogan <james.hogan@imgtec.com>,
	Seungwon Jeon <tgih.jun@samsung.com>, Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH] mmc: dw_mmc: Handle the Hardware Locked Write Error(HLE)
Date: Fri, 02 Aug 2013 14:48:37 +0900	[thread overview]
Message-ID: <51FB4835.4030809@samsung.com> (raw)
In-Reply-To: <51FB3F53.50301@gmail.com>

On 08/02/2013 02:10 PM, Dinh Nguyen wrote:
> Hi Jaehoon,
> 
> On 08/01/2013 11:14 PM, Jaehoon Chung wrote:
>> You can refer to Seungwon's patch.
>>
>> https://patchwork.kernel.org/patch/1814991/
> 
> Thanks alot for the referral. It appears that this exactly what I'm
> seeing on the SOCFPGA platform. The command buffer is already filled
> with a command when software sets the start_bit.
Right, HLE is triggered when the command buffer is filled fully.
Previously command is waiting for completing, ongoing next command..and next..
Then i found the HLE interrupt is triggered.

> 
> Wonder what happened to Senugwon's patch? I would think that the driver
> should at least clear the HLE interrupt when it is triggered?
I known that Seungwon's patch is just noticed the HLE interrupt.
We need to discuss how clear the HLE interrupt.
In my case, reset the fifo and resend the command that didn't complete.
if you have any other idea, let me share.

Best Regards,
Jaehoon Chung
> 
> Thanks,
> Dinh
>>
>> Best Regards,
>> Jaehoon Chung
>>
>> On 08/02/2013 12:50 PM, dinguyen@altera.com wrote:
>>> From: Dinh Nguyen <dinguyen@altera.com>
>>>
>>> The Handle the Hardware Locked Write Error(HLE) was getting triggered
>>> intermittently on the SOCFPGA platform. But since the driver did not
>>> have a mechanism to handle this interrupt, it was stuck in the ISR.
>>>
>>> Clear the HLE interrupt when it gets triggered.
>>>
>>> Signed-off-by: Dinh Nguyen <dinguyen@altera.com>
>>> Cc: Doug Anderson <dianders@chromium.org>
>>> Cc: Jaehoon Chung <jh80.chung@samsung.com>
>>> Cc: James Hogan <james.hogan@imgtec.com>
>>> Cc: Seungwon Jeon <tgih.jun@samsung.com>
>>> Cc: Chris Ball <cjb@laptop.org>
>>> ---
>>>  drivers/mmc/host/dw_mmc.c |    3 +++
>>>  1 file changed, 3 insertions(+)
>>>
>>> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
>>> index ee5f167..ef30bec 100644
>>> --- a/drivers/mmc/host/dw_mmc.c
>>> +++ b/drivers/mmc/host/dw_mmc.c
>>> @@ -1664,6 +1664,9 @@ static irqreturn_t dw_mci_interrupt(int irq, void *dev_id)
>>>  			queue_work(host->card_workqueue, &host->card_work);
>>>  		}
>>>  
>>> +		if (pending & SDMMC_INT_HLE)
>>> +			mci_writel(host, RINTSTS, SDMMC_INT_HLE);
>>> +
>>>  		/* Handle SDIO Interrupts */
>>>  		for (i = 0; i < host->num_slots; i++) {
>>>  			struct dw_mci_slot *slot = host->slot[i];
>>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2013-08-02  5:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  3:50 [PATCH] mmc: dw_mmc: Handle the Hardware Locked Write Error(HLE) dinguyen
2013-08-02  4:14 ` Jaehoon Chung
2013-08-02  5:10   ` Dinh Nguyen
2013-08-02  5:48     ` 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=51FB4835.4030809@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=cjb@laptop.org \
    --cc=dianders@chromium.org \
    --cc=dinguyen@altera.com \
    --cc=dinh.linux@gmail.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tgih.jun@samsung.com \
    /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