From: Jon Hunter <jon-hunter@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Andreas Fenkart <andreas.fenkart@streamunlimited.com>,
khilman@deeprootsystems.com, grant.likely@secretlab.ca,
linus.walleij@linaro.org, linux-omap@vger.kernel.org,
daniel@zonque.org
Subject: Re: gpio/omap v2: map irq_enable/disable to mask/unmask.
Date: Thu, 11 Apr 2013 12:52:14 -0500 [thread overview]
Message-ID: <5166F84E.9050502@ti.com> (raw)
In-Reply-To: <5166DCAD.1030409@ti.com>
On 04/11/2013 10:54 AM, Santosh Shilimkar wrote:
> On Thursday 11 April 2013 06:48 PM, Andreas Fenkart wrote:
>> Hi Santosh,
>>
>> I submitted the following patch a while back.
>> https://patchwork.kernel.org/patch/1886421/
>>
>> As already said, the patch is straight forward, but without it,
>> we probably will not see decent SDIO performance on am335x chips.
>>
>> [why it is needed]
>>
> Why part is clear for me.
>
>> There are still open questions to gpio patch itself, see here
>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg87217.html
>>
>> So could we pls reopen that thread? It might be on the other side
>> of your mailbox
>>
> Your idea is reasonable and probably patch make lot of sense for
> edge triggered interrupt.
>
> Can you please repost the patch with the more comprehensive change-log
> as discussed in the thread.
Originally, I had a question on enable/disable versus mask/unmask, but
looking at the way we have implemented mask/unmask for omap, I don't
think that my question is really applicable. Yes so please re-post.
Jon
prev parent reply other threads:[~2013-04-11 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 13:18 gpio/omap v2: map irq_enable/disable to mask/unmask Andreas Fenkart
2013-04-11 15:40 ` Tony Lindgren
2013-04-11 15:54 ` Santosh Shilimkar
2013-04-11 17:52 ` Jon Hunter [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=5166F84E.9050502@ti.com \
--to=jon-hunter@ti.com \
--cc=andreas.fenkart@streamunlimited.com \
--cc=daniel@zonque.org \
--cc=grant.likely@secretlab.ca \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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.