linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
	linux-serial@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: Re: [PATCH/RFC] serial_core: Fix pm imbalance on unbind
Date: Thu, 20 Mar 2014 14:14:32 -0700	[thread overview]
Message-ID: <20140320211432.GA2813@kroah.com> (raw)
In-Reply-To: <CAMuHMdVmrEoRkqUB=3mBRNrPEJiR701YUmr8C7HX1O6UxT_NUg@mail.gmail.com>

On Thu, Mar 20, 2014 at 11:23:00AM +0100, Geert Uytterhoeven wrote:
> Hi Greg,
> 
> On Mon, Mar 10, 2014 at 8:54 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > From: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
> >
> > When a serial port is closed, uart_close() takes care of shutting down the
> > hardware, and powering it down.
> >
> > When a serial port is unbound while in use, uart_close() bypasses all of
> > this, as this is supposed to be done through uart_hangup() (invoked via
> > tty_vhangup() in uart_remove_one_port()).
> >
> > However, uart_hangup() does not set the hardware's power state, leaving it
> > powered up.  This may also lead to unbounded nesting counts in clock and
> > power management, depending on their internal implementation.
> >
> > Make sure to power down the port in uart_hangup(), except when the port is
> > used as a serial console. For serial consoles, this must be postponed until
> > after their deregistration in uart_remove_one_port() (symmetry with
> > registration in uart_configure_port(), invoked from uart_add_one_port()).
> >
> > After this, the module clock used by the sh-sci driver is disabled on
> > unbind while the serial port is in use.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
> 
> I noticed you have applied all serial patches I've sent, except for this one.
> Is there any specific reason you skipped this one?

It was marked "RFC" so I didn't think it was to be applied...

If it's ready, please resend.

thanks,

greg k-h

      reply	other threads:[~2014-03-20 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 19:54 [PATCH/RFC] serial_core: Fix pm imbalance on unbind Geert Uytterhoeven
2014-03-20 10:23 ` Geert Uytterhoeven
2014-03-20 21:14   ` Greg Kroah-Hartman [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=20140320211432.GA2813@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=geert+renesas@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    /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).