All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: 'Jaehoon Chung' <jh80.chung@samsung.com>,
	linux-mmc@vger.kernel.org, cjb@laptop.org, will.newton@gmail.com
Subject: Re: [PATCH] mmc: dw_mmc: clear INSTS register when initialize
Date: Wed, 24 Apr 2013 12:05:51 +0900	[thread overview]
Message-ID: <51774C0F.9040104@samsung.com> (raw)
In-Reply-To: <000601ce408b$e60a4e70$b21eeb50$%jun@samsung.com>

On 04/24/2013 10:34 AM, Seungwon Jeon wrote:
> On Tuesday, April 23, 2013, Jaehoon Chung wrote:
>> On 04/23/2013 06:57 PM, Seungwon Jeon wrote:
>>> Hi,
>>>
>>> On Thursday, April 18, 2013, Joonyoung Shim wrote:
>>>> If pending interrupt for IDMAC exists when probe, it will call interrupt
>>>> handler unnecessarily.
>>>>
>>>> Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
>>>> ---
>>>>  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 323c502..b0057a2 100644
>>>> --- a/drivers/mmc/host/dw_mmc.c
>>>> +++ b/drivers/mmc/host/dw_mmc.c
>>>> @@ -2192,6 +2192,7 @@ int dw_mci_probe(struct dw_mci *host)
>>>>
>>>>  	/* Clear the interrupts for the host controller */
>>>>  	mci_writel(host, RINTSTS, 0xFFFFFFFF);
>>>> +	mci_writel(host, IDSTS, 0xFFFFFFFF);
>>> 0x337 is correct for bits. Could you check the bit filed?

I feel it's better to use already existing defines than 0x337.

>> I think that don't care which reset value used.
>> "It is recommended that you write 0xffff_ffff to the Raw Interrupt register @0x044 and IDSTS @0x8C
>> in order to clear any pending interrupts before setting the int_enable bit."
>> This boot mode case is also used the 0xffff_ffff.

Jaehoon, can i get this sentence from which document?

> In case IDSTS all 32bit are not for interrupt status unlike RINTSTS.
> IDSTS[31:17] is reserved and IDSTS[16:0] also contains 'reserved' and 'read-only' field.
> Correct use would be needed.
>
> Thanks,
> Seungwon Jeon
>>>>  	mci_writel(host, INTMASK, 0); /* disable all mmc interrupt first */
>>>>
>>>>  	/* Put in max timeout */
>>>> @@ -2243,6 +2244,7 @@ int dw_mci_probe(struct dw_mci *host)
>>>>  	 * receive ready and error such as transmit, receive timeout, crc error
>>>>  	 */
>>>>  	mci_writel(host, RINTSTS, 0xFFFFFFFF);
>>>> +	mci_writel(host, IDSTS, 0xFFFFFFFF);
>>> No need, it's already done above.

OK.

>>>
>>>>  	mci_writel(host, INTMASK, SDMMC_INT_CMD_DONE | SDMMC_INT_DATA_OVER |
>>>>  		   SDMMC_INT_TXDR | SDMMC_INT_RXDR |
>>>>  		   DW_MCI_ERROR_FLAGS | SDMMC_INT_CD);
>>>> @@ -2393,6 +2395,7 @@ int dw_mci_resume(struct dw_mci *host)
>>>>  	mci_writel(host, FIFOTH, host->fifoth_val);
>>>>
>>>>  	mci_writel(host, RINTSTS, 0xFFFFFFFF);
>>>> +	mci_writel(host, IDSTS, 0xFFFFFFFF);
>>> Same, incorrect bits.
>>>
>>> Thanks,
>>> Seungwon Jeon
>>>
>>>>  	mci_writel(host, INTMASK, SDMMC_INT_CMD_DONE | SDMMC_INT_DATA_OVER |
>>>>  		   SDMMC_INT_TXDR | SDMMC_INT_RXDR |
>>>>  		   DW_MCI_ERROR_FLAGS | SDMMC_INT_CD);
>>>> --
>>>> 1.7.9.5
>>>>
>>>> --
>>>> 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
>>>

Thanks.

  reply	other threads:[~2013-04-24  3:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18  5:21 [PATCH] mmc: dw_mmc: clear INSTS register when initialize Joonyoung Shim
2013-04-18  6:59 ` Jaehoon Chung
2013-04-23  9:57 ` Seungwon Jeon
2013-04-23 10:23   ` Jaehoon Chung
2013-04-24  1:34     ` Seungwon Jeon
2013-04-24  3:05       ` Joonyoung Shim [this message]
2013-04-25  0:45         ` Jaehoon Chung
2013-04-25  7:49           ` Joonyoung Shim
2013-04-26  4:24             ` Seungwon Jeon
2013-04-26  5:18               ` Jaehoon Chung
2013-04-26  5:35                 ` Seungwon Jeon

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=51774C0F.9040104@samsung.com \
    --to=jy0922.shim@samsung.com \
    --cc=cjb@laptop.org \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tgih.jun@samsung.com \
    --cc=will.newton@gmail.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 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.