All of lore.kernel.org
 help / color / mirror / Atom feed
From: menghui lin <menghui.lin@mediatek.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	"HenryC Chen (陳建豪)" <HenryC.Chen@mediatek.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	linux-mediatek@lists.infradead.org,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"Chen Zhong" <chen.zhong@mediatek.com>,
	linux-arm-kernel@lists.infradead.org,
	"John Crispin" <blogic@openwrt.org>
Subject: Re: [PATCH V4 2/2] regulator: mt6323: Add support for MT6323 regulator
Date: Thu, 4 Feb 2016 10:42:43 +0800	[thread overview]
Message-ID: <1454553763.24913.8.camel@mtksdaap41> (raw)
In-Reply-To: <20160203122952.GF4455@sirena.org.uk>

On Wed, 2016-02-03 at 12:29 +0000, Mark Brown wrote:
> On Wed, Feb 03, 2016 at 01:39:02PM +0800, menghui lin wrote:
> > On Tue, 2016-02-02 at 19:38 +0000, Mark Brown wrote:
> 
> > > How does the driver know if it needs to change the mode (ie, how can it
> > > tell if the current mode is inadequate) and surely if we can only change
> > > in one direction this isn't terribly useful?
> 
> > I think the datasheet of buck/ldo could provide information about power
> > capability of each mode. The driver should adjust regulator mode per its
> > device's power requirement.
> 
> That's of no help for a consumer driver which doesn't know what
> regulator is supplying it.
> 
> > case 1:
> 
> > We have a USB typeC micro-controller, which has two modes - standby and
> > normal. It requires 1.8V and 3.3V to operate (both powers are always
> > on). The device stays in standby mode when there is no cable in. When
> > cable in, we got an interrupt and change device into normal mode.
> 
> > The standby mode power consumption is quite small, so we would like the
> > change mode of regulator into STANDBY to save more power. And we change
> > into NORMAL when we receive cable-in interrupt.
> 
> This seems like something that we ought to be doing via runtime PM
> anyway which should be going through the suspend mode bindings, though
> that would need some plumbing in.
> 
> > case 2:
> 
> > About buck regulator for CPU, it usually provides PWM mode, PWM/PFM Auto
> > mode, PFM mode. I think it could map to FAST, NORMAL, IDLE mode
> > respectively. Most of time we would use just normal mode. However, we
> > would change regulator into PWM mode time to time to test buck output
> > performance on the tested board.
> 
> That's a test use that doesn't seem a good fit for upstream at all.

Hi Mark,

Thanks for your response.
It seems more work is required for dynamic mode switch.
For MT6323 regulator patch, we would remove mode-switch related code for
now to provide basic regulator support first.

WARNING: multiple messages have this Message-ID (diff)
From: menghui.lin@mediatek.com (menghui lin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 2/2] regulator: mt6323: Add support for MT6323 regulator
Date: Thu, 4 Feb 2016 10:42:43 +0800	[thread overview]
Message-ID: <1454553763.24913.8.camel@mtksdaap41> (raw)
In-Reply-To: <20160203122952.GF4455@sirena.org.uk>

On Wed, 2016-02-03 at 12:29 +0000, Mark Brown wrote:
> On Wed, Feb 03, 2016 at 01:39:02PM +0800, menghui lin wrote:
> > On Tue, 2016-02-02 at 19:38 +0000, Mark Brown wrote:
> 
> > > How does the driver know if it needs to change the mode (ie, how can it
> > > tell if the current mode is inadequate) and surely if we can only change
> > > in one direction this isn't terribly useful?
> 
> > I think the datasheet of buck/ldo could provide information about power
> > capability of each mode. The driver should adjust regulator mode per its
> > device's power requirement.
> 
> That's of no help for a consumer driver which doesn't know what
> regulator is supplying it.
> 
> > case 1:
> 
> > We have a USB typeC micro-controller, which has two modes - standby and
> > normal. It requires 1.8V and 3.3V to operate (both powers are always
> > on). The device stays in standby mode when there is no cable in. When
> > cable in, we got an interrupt and change device into normal mode.
> 
> > The standby mode power consumption is quite small, so we would like the
> > change mode of regulator into STANDBY to save more power. And we change
> > into NORMAL when we receive cable-in interrupt.
> 
> This seems like something that we ought to be doing via runtime PM
> anyway which should be going through the suspend mode bindings, though
> that would need some plumbing in.
> 
> > case 2:
> 
> > About buck regulator for CPU, it usually provides PWM mode, PWM/PFM Auto
> > mode, PFM mode. I think it could map to FAST, NORMAL, IDLE mode
> > respectively. Most of time we would use just normal mode. However, we
> > would change regulator into PWM mode time to time to test buck output
> > performance on the tested board.
> 
> That's a test use that doesn't seem a good fit for upstream at all.

Hi Mark,

Thanks for your response.
It seems more work is required for dynamic mode switch.
For MT6323 regulator patch, we would remove mode-switch related code for
now to provide basic regulator support first.

  reply	other threads:[~2016-02-04  2:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 12:00 [PATCH V4 1/2] regulator: Add document for MT6323 regulator John Crispin
2016-01-27 12:00 ` John Crispin
2016-01-27 12:00 ` John Crispin
2016-01-27 12:00 ` [PATCH V4 2/2] regulator: mt6323: Add support " John Crispin
2016-01-27 12:00   ` John Crispin
2016-01-27 14:41   ` Mark Brown
2016-01-27 14:41     ` Mark Brown
2016-01-28  7:16     ` Henry Chen
2016-01-28  7:16       ` Henry Chen
2016-01-28  7:16       ` Henry Chen
2016-01-28 11:38       ` Mark Brown
2016-01-28 11:38         ` Mark Brown
     [not found]     ` <20160127144105.GQ6042-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-01-28 18:13       ` John Crispin
2016-01-28 18:13         ` John Crispin
2016-01-28 18:13         ` John Crispin
2016-01-28 23:13         ` Mark Brown
2016-01-28 23:13           ` Mark Brown
2016-01-29  9:52           ` menghui lin
2016-01-29  9:52             ` menghui lin
2016-01-29 11:27             ` Mark Brown
2016-01-29 11:27               ` Mark Brown
2016-01-29 12:11               ` menghui lin
2016-01-29 12:11                 ` menghui lin
2016-02-02 19:38                 ` Mark Brown
2016-02-02 19:38                   ` Mark Brown
2016-02-03  5:39                   ` menghui lin
2016-02-03  5:39                     ` menghui lin
2016-02-03 12:29                     ` Mark Brown
2016-02-03 12:29                       ` Mark Brown
2016-02-04  2:42                       ` menghui lin [this message]
2016-02-04  2:42                         ` menghui lin
2016-02-02 19:39                 ` Mark Brown
2016-02-02 19:39                   ` Mark Brown
2016-02-08 12:14   ` kbuild test robot
2016-02-08 12:14     ` kbuild test robot
2016-02-08 12:14     ` kbuild test robot
2016-02-01 15:40 ` [PATCH V4 1/2] regulator: Add document " Rob Herring
2016-02-01 15:40   ` Rob Herring

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=1454553763.24913.8.camel@mtksdaap41 \
    --to=menghui.lin@mediatek.com \
    --cc=HenryC.Chen@mediatek.com \
    --cc=blogic@openwrt.org \
    --cc=broonie@kernel.org \
    --cc=chen.zhong@mediatek.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.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.