From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Yasushi SHOJI <yashi@atmark-techno.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Simon Horman <horms@verge.net.au>,
linux-renesas-soc@vger.kernel.org
Subject: Re: mmc: tmio: why enable/disable SDIO irq on every transaction with IOMOD?
Date: Thu, 1 Dec 2016 11:46:22 +0100 [thread overview]
Message-ID: <20161201104622.GA1541@katana> (raw)
In-Reply-To: <CAPDyKFop3a6eHhOZq1E=BdFiHzmpu4uEx0F79nyBVCOu6z6usw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Hi,
thanks for the report and thanks to Ulf for forwarding. Adding
renesas-soc list, too.
> > So my question is that "What is the reason behind to disable IRQ with
> > SDIO_MODE? Is there any situation which masking with SDIO_INFO1_MASK
> > is not enough?
This code predates the time since I took over maintainership of the
driver, so I had to dig in git history.
The code was introduced with 845ecd20239c28 ("mmc: tmio_mmc: implement
SDIO IRQ support") which was in 2010. I don't have that old datasheets
to check if the SCLKDIVEN restriction was already present in the SDHI
cores which were available back then.
My assumption is that it was not, or it was overlooked. So, it might be
just for completeness that not only the individual IRQs have been
disabled but also the big master switch (IOMOD) was turned off.
My further assumption is that it is very likely good enough to disable
the individual IRQs. If we can't guarantee the conditions to set IOMOD,
it seems okay to me to just leave it.
Do you have a patch which works for you?
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-01 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 6:23 mmc: tmio: why enable/disable SDIO irq on every transaction with IOMOD? Yasushi SHOJI
2016-11-29 8:52 ` Ulf Hansson
2016-12-01 10:46 ` Wolfram Sang [this message]
2016-12-01 12:46 ` Yasushi SHOJI
2016-12-01 14:49 ` Wolfram Sang
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=20161201104622.GA1541@katana \
--to=wsa-dev@sang-engineering.com \
--cc=horms@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yashi@atmark-techno.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