Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1308450

Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for max77620/max20024

From Mark Brown <broonie@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for max77620/max20024
Date 2016-01-13 15:30 +0100
Message-ID <qQuAW-X1-11@gated-at.bofh.it> (permalink)
References (5 earlier) <qQsz9-7YE-29@gated-at.bofh.it> <qQsSu-89F-5@gated-at.bofh.it> <qQt2a-8ek-11@gated-at.bofh.it> <qQtlw-9v-15@gated-at.bofh.it> <qQtES-hT-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Wed, Jan 13, 2016 at 06:41:11PM +0530, Laxman Dewangan wrote:
> On Wednesday 13 January 2016 06:39 PM, Mark Brown wrote:

> >What is "it" and why can't we check what the current configuration is
> >while setting FPS to NONE?

> I will have platform specific data in callback of enable/disable only.
> Which call back do I need to set this? enable/disable or post register?

I'm sorry but I can't parse what you're saying here.

> >>I need to set the FPS src properly for each rails before callback happen
> >>from regulator init so that enable/disable/is_enable can handle it properly.

> >Why not just reorder the callback so it happens before the constraints
> >are applied?

> which callback I need to reorder for getting the context for configruation?

The existing call to parse the DT.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH V2 6/6] regulator: max77620: add regulator driver for max77620/max20024 Laxman Dewangan <ldewangan@nvidia.com> - 2016-01-12 10:30 +0100
  Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-01-13 02:30 +0100
    Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Mark Brown <broonie@kernel.org> - 2016-01-13 13:00 +0100
      Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Laxman Dewangan <ldewangan@nvidia.com> - 2016-01-13 13:20 +0100
        Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Mark Brown <broonie@kernel.org> - 2016-01-13 13:40 +0100
          Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Laxman Dewangan <ldewangan@nvidia.com> - 2016-01-13 13:50 +0100
            Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Mark Brown <broonie@kernel.org> - 2016-01-13 14:10 +0100
              Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Laxman Dewangan <ldewangan@nvidia.com> - 2016-01-13 14:30 +0100
                Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Mark Brown <broonie@kernel.org> - 2016-01-13 15:30 +0100
                Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Laxman Dewangan <ldewangan@nvidia.com> - 2016-01-13 16:00 +0100
                Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Mark Brown <broonie@kernel.org> - 2016-01-13 17:00 +0100
    Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for  max77620/max20024 Laxman Dewangan <ldewangan@nvidia.com> - 2016-01-13 13:00 +0100

csiph-web