All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Grzegorz.Sygieda@tieto.com
Cc: linux@arm.linux.org.uk, greg@kroah.com,
	linus.walleij@stericsson.com,
	par-gunnar.p.hjalmdahl@stericsson.com,
	Lukasz.Rymanowski@tieto.com, linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] pl011: added clock management feature
Date: Wed, 10 Nov 2010 09:00:58 -0800	[thread overview]
Message-ID: <20101110170058.GB11947@suse.de> (raw)
In-Reply-To: <0CBD3CD1188FB94093DB405A20CBCFBE06C5C4D8D2@EXMB01.eu.tieto.com>

On Wed, Nov 10, 2010 at 10:15:53AM +0200, Grzegorz.Sygieda@tieto.com wrote:
> >On Tue, Nov 09, 2010 at 02:40:12PM -0800, Greg KH wrote:
> >> On Tue, Nov 09, 2010 at 04:30:37PM +0100, Linus Walleij wrote:
> >> > From: Grzegorz Sygieda <grzegorz.sygieda@tieto.com>
> >> > 
> >> > This patch allows to control the pl011 clock using set_termios 
> >> > callback. Any positive baudrate passed enables clock, otherwise 
> >> > disables. This saves a lot of power on submicron designs since we 
> >> > can clock off and disable unused UARTs.
> >> 
> >> That's nice, but it seems like an overload of what people 
> >> traditionally think of when it comes to baud rates.  Why not just 
> >> power down ports that are not open instead?
> >
> >We already do.  My question to Linus (in a previous message) is why this isn't sufficient.
> 
> The main goal was to disable/enable clock while port open. This is
> usefull for scenario, where some higher level driver wants to control
> the power consumption (using set_termios). In the same time a
> user-space app (eg. hciattach) is still bounded to the specific
> /dev/tty* device associated with particular uart. From user POV device
> is always open, and app does not have to respawn, and we can save
> power.

That is nice, but again, you are overloading a common interface (one
defined by POSIX I think) to do something else at the same time.  That
might cause problems with some users that expect you to be able to use a
baud rate of 0 :)

I like the idea, but not the overloading, sorry.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pl011: added clock management feature
Date: Wed, 10 Nov 2010 09:00:58 -0800	[thread overview]
Message-ID: <20101110170058.GB11947@suse.de> (raw)
In-Reply-To: <0CBD3CD1188FB94093DB405A20CBCFBE06C5C4D8D2@EXMB01.eu.tieto.com>

On Wed, Nov 10, 2010 at 10:15:53AM +0200, Grzegorz.Sygieda at tieto.com wrote:
> >On Tue, Nov 09, 2010 at 02:40:12PM -0800, Greg KH wrote:
> >> On Tue, Nov 09, 2010 at 04:30:37PM +0100, Linus Walleij wrote:
> >> > From: Grzegorz Sygieda <grzegorz.sygieda@tieto.com>
> >> > 
> >> > This patch allows to control the pl011 clock using set_termios 
> >> > callback. Any positive baudrate passed enables clock, otherwise 
> >> > disables. This saves a lot of power on submicron designs since we 
> >> > can clock off and disable unused UARTs.
> >> 
> >> That's nice, but it seems like an overload of what people 
> >> traditionally think of when it comes to baud rates.  Why not just 
> >> power down ports that are not open instead?
> >
> >We already do.  My question to Linus (in a previous message) is why this isn't sufficient.
> 
> The main goal was to disable/enable clock while port open. This is
> usefull for scenario, where some higher level driver wants to control
> the power consumption (using set_termios). In the same time a
> user-space app (eg. hciattach) is still bounded to the specific
> /dev/tty* device associated with particular uart. From user POV device
> is always open, and app does not have to respawn, and we can save
> power.

That is nice, but again, you are overloading a common interface (one
defined by POSIX I think) to do something else at the same time.  That
might cause problems with some users that expect you to be able to use a
baud rate of 0 :)

I like the idea, but not the overloading, sorry.

thanks,

greg k-h

  reply	other threads:[~2010-11-10 17:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 15:30 [PATCH] pl011: added clock management feature Linus Walleij
2010-11-09 15:30 ` Linus Walleij
2010-11-09 15:44 ` Russell King - ARM Linux
2010-11-09 15:44   ` Russell King - ARM Linux
2010-11-09 22:40 ` Greg KH
2010-11-09 22:40   ` Greg KH
2010-11-10  0:01   ` Russell King - ARM Linux
2010-11-10  0:01     ` Russell King - ARM Linux
2010-11-10  7:54     ` Grzegorz.Sygieda
2010-11-10  7:54       ` Grzegorz.Sygieda at tieto.com
2010-11-10  8:15     ` Grzegorz.Sygieda
2010-11-10  8:15       ` Grzegorz.Sygieda at tieto.com
2010-11-10 17:00       ` Greg KH [this message]
2010-11-10 17:00         ` Greg KH
2010-11-10 17:11       ` Russell King - ARM Linux
2010-11-10 17:11         ` Russell King - ARM Linux
2010-11-17  8:24         ` Grzegorz.Sygieda
2010-11-17  8:24           ` Grzegorz.Sygieda at tieto.com
2010-12-03 11:47   ` Vitaly Wool
2010-12-03 11:47     ` Vitaly Wool
2010-12-03 15:15     ` Russell King - ARM Linux
2010-12-03 15:15       ` Russell King - ARM Linux
2010-12-06  9:53       ` Vitaly Wool
2010-12-06  9:53         ` Vitaly Wool
2010-12-06 10:14         ` Russell King - ARM Linux
2010-12-06 10:14           ` Russell King - ARM Linux
2010-12-06 12:23           ` Par-Gunnar HJALMDAHL
2010-12-06 12:23             ` Par-Gunnar HJALMDAHL

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=20101110170058.GB11947@suse.de \
    --to=gregkh@suse.de \
    --cc=Grzegorz.Sygieda@tieto.com \
    --cc=Lukasz.Rymanowski@tieto.com \
    --cc=greg@kroah.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=par-gunnar.p.hjalmdahl@stericsson.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.