From: Chris Ball <cjb@laptop.org>
To: Balaji T K <balajitk@ti.com>
Cc: Francesco Lavra <francescolavra.fl@gmail.com>,
linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: omap_hsmmc: clear status flags before starting a new command
Date: Sun, 25 Aug 2013 15:41:49 -0400 [thread overview]
Message-ID: <87haedpngi.fsf@octavius.laptop.org> (raw)
In-Reply-To: <521A5D7C.4050208@ti.com> (Balaji T. K.'s message of "Mon, 26 Aug 2013 01:09:40 +0530")
Hi,
On Sun, Aug 25 2013, Balaji T K wrote:
> On Saturday 29 June 2013 11:55 AM, Francesco Lavra wrote:
>> Commit 1f6b9fa40e76fffaaa0b3bd6a0bfdcf1cdc06efa consolidated writes to
>> the STAT register in one location, moving them from omap_hsmmc_do_irq()
>> to omap_hsmmc_irq(). This move has the unwanted side effect that the
>> controller status flags are potentially cleared after a new command has
>> been started as a consequence of reading the previous status flags.
>> This means that if the new command changes the status flags before the
>> IRQ routine returns, those flags may be cleared without handling the
>> event which asserted them, and thus missing the event.
>> Move the writing of the STAT register back in omap_hsmmc_do_irq(),
>> before handling the status flags which generated the interrupt.
>>
>> Signed-off-by: Francesco Lavra <francescolavra.fl@gmail.com>
>
> Reviewed and Tested-by: Balaji T K <balajitk@ti.com>
Thanks, pushed to mmc-next for 3.12.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
prev parent reply other threads:[~2013-08-25 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 6:25 [PATCH] mmc: omap_hsmmc: clear status flags before starting a new command Francesco Lavra
2013-08-25 2:02 ` Chris Ball
2013-08-25 19:39 ` Balaji T K
2013-08-25 19:41 ` Chris Ball [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=87haedpngi.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=balajitk@ti.com \
--cc=francescolavra.fl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox