From: Nishanth Menon <nm@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Javier Martinez Canillas <javier@dowhile0.org>
Cc: Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Kevin Hilman <khilman@linaro.org>,
linux-omap <linux-omap@vger.kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: regressions in linux-next?
Date: Wed, 23 Apr 2014 08:29:51 -0500 [thread overview]
Message-ID: <5357C04F.3060902@ti.com> (raw)
In-Reply-To: <CACRpkdZ1Sv9oWhPWYEemGEnsCojs5amMMkru8DjpPxc=c9MRHA@mail.gmail.com>
On 04/23/2014 08:01 AM, Linus Walleij wrote:
> On Wed, Apr 23, 2014 at 9:24 AM, Javier Martinez Canillas
> <javier@dowhile0.org> wrote:
>
>> Linus, what do you think of the following patch?
>>
>> From ede333e85e0320d32e8c2d123560808ed7e43ece Mon Sep 17 00:00:00 2001
>> From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>> Date: Wed, 23 Apr 2014 09:13:54 +0200
>> Subject: [PATCH 1/1] gpio: don't call irq_set_irq_type() on IRQ domain map
>> function
> (...)
>
> So no setting a default type in the mapping function...
>
>> - irq_set_irq_type(irq, chip->irq_default_type);
>
> But there are drivers exploiting this to set up the hardware to some
> default state :-(
>
> What about this:
>
> if (chip->irq_default_type != IRQ_TYPE_NONE)
> irq_set_irq_type(irq, chip->irq_default_type);
>
> This way you can pass IRQ_TYPE_NONE and nothing happens in
> the mapping.
What if these drivers depend on IRQ_TYPE_NONE to do something for the
GPIO pins?
would you expect these drivers to pass IRQ_TYPE_DEFAULT? OR I wonder
if we could pass some flag like -1 for platforms that dont care?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-04-23 13:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:18 regressions in linux-next? Nishanth Menon
2014-04-22 13:29 ` Peter Ujfalusi
2014-04-22 15:52 ` Javier Martinez Canillas
2014-04-22 19:37 ` Ezequiel Garcia
2014-04-22 22:32 ` Javier Martinez Canillas
2014-04-22 22:00 ` Linus Walleij
2014-04-22 23:03 ` Javier Martinez Canillas
2014-04-22 23:47 ` Tony Lindgren
2014-04-24 15:16 ` Kevin Hilman
2014-04-24 15:25 ` Nishanth Menon
2014-04-24 15:37 ` Javier Martinez Canillas
2014-04-24 15:42 ` Tony Lindgren
2014-04-24 16:33 ` Javier Martinez Canillas
2014-04-24 16:47 ` Tony Lindgren
2014-04-24 15:40 ` Tony Lindgren
2014-04-24 15:46 ` Nishanth Menon
2014-04-24 16:17 ` Tony Lindgren
2014-04-24 17:08 ` Nishanth Menon
2014-04-24 19:59 ` Aaro Koskinen
2014-04-24 19:22 ` Aaro Koskinen
2014-04-28 22:04 ` Paul Walmsley
2014-04-22 15:13 ` Nishanth Menon
2014-04-22 21:57 ` Nishanth Menon
2014-04-22 22:45 ` Javier Martinez Canillas
2014-04-22 22:52 ` Nishanth Menon
2014-04-22 23:08 ` Javier Martinez Canillas
2014-04-23 1:30 ` Nishanth Menon
2014-04-23 7:24 ` Javier Martinez Canillas
2014-04-23 10:59 ` Peter Ujfalusi
2014-04-23 13:01 ` Linus Walleij
2014-04-23 13:29 ` Nishanth Menon [this message]
2014-04-23 14:38 ` Linus Walleij
2014-04-23 14:50 ` Javier Martinez Canillas
2014-04-23 14:52 ` Linus Walleij
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=5357C04F.3060902@ti.com \
--to=nm@ti.com \
--cc=javier@dowhile0.org \
--cc=khilman@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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.