From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-omap <linux-omap@vger.kernel.org>,
Dave Gerlach <d-gerlach@ti.com>
Subject: Re: [PATCH] tty: serial: 8250: omap: Add pinctrl support for suspend
Date: Thu, 6 Nov 2014 12:35:44 -0800 [thread overview]
Message-ID: <20141106203544.GE31454@atomide.com> (raw)
In-Reply-To: <CAGo_u6qTqp1Wpo8E26gLpStu_EiRw32gstkCiXw+EWNDWSnHbw@mail.gmail.com>
* Nishanth Menon <nm@ti.com> [141106 11:59]:
> On Thu, Nov 6, 2014 at 1:42 PM, Sebastian Andrzej Siewior
> <bigeasy@linutronix.de> wrote:
> > On 11/06/2014 08:15 PM, Nishanth Menon wrote:
> >> sounds good to me *IF* omap8250_enable_wakeup (wakeirq handling) is
> >> the way we want to continue doing things for daisychain? -> Tony, can
> >> you comment?
> >> http://marc.info/?l=linux-omap&m=141222144402707&w=2
> >>
> >> I wonder if wakeirq explicit handling is valid anymore and something
> >> given the potential race and alternate approach proposed?
> >
> > The wakeirq logic is already in the driver. So if we go for the
> > alternate approach, the pinctrl patch is obsolete? Or does it mean we
> > get rid of the map8250_enable_wakeup() including the second irq we have
> > now (and keep the pinctl change)?
>
> based on Thomas's feedback we should probably not carry forward
> wakeirq as a seperate irq with it's own request_irq instead it psuedo
> triggers uart's interrupt irq -> I am not clear about the direction
The pinctrl change in this patch and the wake-up events are a separate
issue.
As some omaps need the RX pin remuxed temporarily to GPIO for wake-up
events, the $subject patch seems just fine to me.
For the wake-up interrupts, the issue Thomas was concerned was
re-entrant interrupts and handling the wake-up interrupts in various
different ways. From hardware point of view the wake-up events behave
like a separate IRQ controller, so the request_irq part is fine.
> Tony wants drivers to take in the approach in the thread above - all I
> wondered was if it had any conflict of pin_sleep -> if the generic
> handler retriggers the irq before the suspend_handler, then
> configuring sleep is gonna break daisychain support. not sure if there
> is any specific direction drivers should take.
The wake-irq is disabled during runtime and should be enabled so
that should not be an issue.
> Again, Tony is the right guy to comment about this.
Yeah I'll repost the patches for the generic wake-irq handling.
Fixing up the drivers to use that is trivial once we've agreed on
the generic wake-up event handling.
Regards,
Tony
next prev parent reply other threads:[~2014-11-06 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 19:07 [PATCH] tty: serial: 8250: omap: Add pinctrl support for suspend Sebastian Andrzej Siewior
2014-11-06 19:15 ` Nishanth Menon
2014-11-06 19:42 ` Sebastian Andrzej Siewior
2014-11-06 19:57 ` Nishanth Menon
2014-11-06 20:35 ` Tony Lindgren [this message]
2014-11-25 18:05 ` Sebastian Andrzej Siewior
2014-11-25 18:22 ` Tony Lindgren
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=20141106203544.GE31454@atomide.com \
--to=tony@atomide.com \
--cc=bigeasy@linutronix.de \
--cc=d-gerlach@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nm@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.