linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: linux-serial@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Kevin Hilman <khilman@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH] serial: omap: Add support for optional wake-up interrupt
Date: Fri, 18 Oct 2013 09:45:35 -0700	[thread overview]
Message-ID: <20131018164535.GQ15154@atomide.com> (raw)
In-Reply-To: <20131018163740.GP15154@atomide.com>

* Tony Lindgren <tony@atomide.com> [131018 09:38]:
> * Felipe Balbi <balbi@ti.com> [131018 09:19]:
> > > @@ -786,7 +813,10 @@ static void serial_omap_shutdown(struct uart_port *port)
> > >  
> > >  	pm_runtime_mark_last_busy(up->dev);
> > >  	pm_runtime_put_autosuspend(up->dev);
> > > -	free_irq(up->port.irq, up);
> > > +
> > > +	for (i = 0; i < ARRAY_SIZE(up->irqs); i++)
> > > +		if (up->irqs[i])
> > > +			devm_free_irq(up->port.dev, up->irqs[i], up);
> > 
> > do you need this at all if you're using devm_* ?
> 
> So it seems, startup and shutdown are managed by serial_core and
> that's what at least clps711x.c serial driver is doing.

And that means devm_* in this case does not really help us
here..

I guess we could keep the IRQ requested from probe, but
there's probably a reason why it's done in startup/shutdown.

So I'll just drop the devm_* changes for now.

Regards,

Tony

  reply	other threads:[~2013-10-18 16:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 23:28 [PATCH] serial: omap: Add support for optional wake-up interrupt Tony Lindgren
2013-10-18 16:19 ` Felipe Balbi
2013-10-18 16:37   ` Tony Lindgren
2013-10-18 16:45     ` Tony Lindgren [this message]
2013-10-18 22:56       ` Tony Lindgren
2013-10-21  9:07         ` Roger Quadros
2013-10-21 12:21         ` Felipe Balbi
2013-10-22 13:49           ` 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=20131018164535.GQ15154@atomide.com \
    --to=tony@atomide.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=khilman@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --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).