linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Roger Quadros <rogerq@ti.com>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Haojian Zhuang <haojian.zhuang@linaro.org>,
	Benoit Cousson <bcousson@baylibre.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: single: call pcs_soc->rearm() whenever IRQ mask is changed
Date: Thu, 14 Nov 2013 10:24:48 -0800	[thread overview]
Message-ID: <20131114182447.GJ10317@atomide.com> (raw)
In-Reply-To: <20131112195611.GT15154@atomide.com>

* Tony Lindgren <tony@atomide.com> [131112 11:57]:
> * Linus Walleij <linus.walleij@linaro.org> [131112 10:45]:
> > On Fri, Oct 11, 2013 at 7:23 PM, Tony Lindgren <tony@atomide.com> wrote:
> > > * Linus Walleij <linus.walleij@linaro.org> [131011 09:27]:
> > >> On Fri, Oct 11, 2013 at 6:13 PM, Roger Quadros <rogerq@ti.com> wrote:
> > >>
> > >> > On OMAPs the IO ring must be rearmed each time the pad wakeup
> > >> > configuration is changed. So call pcs_soc->rearm() from
> > >> > pcs_irq_set().
> > >> >
> > >> > Signed-off-by: Roger Quadros <rogerq@ti.com>
> > >>
> > >> If Tony needs to apply this with the other patches: Acked-by.
> > >
> > > Just replied with a slightly modified version of Roger's patch
> > > suggesting you pull in the signed tag I posted for you yesterday
> > > and then you can pick up Roger's fix into the pinctrl tree :)
> > 
> > Hm now that I go over these old mails in my inbox I start to
> > worry that I missed something here, I have no memory of pulling
> > a tag for OMAP... is this all in the state
> > it needs to be for OMAP?
> 
> The other pinctrl-single related patches are now merged to mainline:
> 
> 1b9c0fb365cbb1154f4e7997061db972cbf58300 pinctrl: single: Fix build when not built on ARM
> dc7743aa3c49fabbc6dc9edbcf7df74d776ac32e pinctrl: single: Add support for auxdata
> 3e6cee1786a13cb2308609b5f8c020e1754e37cf pinctrl: single: Add support for wake-up interrupts
> 02e483f66deb6bd8df6af450726574614eb53be3 pinctrl: single: Prepare for supporting SoC specific features
> 
> The fix from Roger is still missing. You can go ahead and queue
> it, or if you prefer me to do it I can add it to my fixes.

Actually Linus, I'll queue this with your ack as the interrupts-extended
property is now merged in and I can also enable some minimal wake-up
events for omap3.

Regards,

Tony

  reply	other threads:[~2013-11-14 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 16:13 [PATCH] pinctrl: single: call pcs_soc->rearm() whenever IRQ mask is changed Roger Quadros
2013-10-11 16:19 ` Linus Walleij
2013-10-11 17:23   ` Tony Lindgren
2013-11-12 18:44     ` Linus Walleij
2013-11-12 19:56       ` Tony Lindgren
2013-11-14 18:24         ` Tony Lindgren [this message]
2013-11-19  8:41           ` Linus Walleij
2013-10-11 17:21 ` Tony Lindgren
2013-10-14  8:15   ` Roger Quadros

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=20131114182447.GJ10317@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=grygorii.strashko@ti.com \
    --cc=haojian.zhuang@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    --cc=rogerq@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).