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


Groups > linux.kernel > #1351350

Re: Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree

From Mark Brown <broonie@kernel.org>
Newsgroups linux.kernel
Subject Re: Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree
Date 2016-03-07 08:50 +0100
Message-ID <r9Y5r-8lu-15@gated-at.bofh.it> (permalink)
References <r9jvk-68k-19@gated-at.bofh.it> <r9wLU-73U-1@gated-at.bofh.it> <r9BVg-2m0-5@gated-at.bofh.it> <r9Fct-4og-11@gated-at.bofh.it> <r9Xj4-7Of-3@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 Mon, Mar 07, 2016 at 12:06:46PM +0530, Laxman Dewangan wrote:

> Following will not help
>             depends on THERMAL_OF if THERMAL_OF
> because THERMAL_OF is always "y" even if THERMAL is "m".

> Build error can by resolved by adding below in the Kconfig
>     depends on THERMAL

> but the issue is if THERMAL is "m" and  REGULATOR_MAX8973 is "y" as per the

So that should be depends on THERMAL if THERMAL_OF

> failure rand config then REGULATOR_MAX8973 automatically become "m". This
> may break some existing platform.

That's an inevitable consequence of adding this support, you can't get
around it.

> Also this driver does not need hard dependency in the thermal as max8973
> does not support thermal but max77621 supports it which is again optional.

> Some of driver use
>     drivers/power/charger-manager.c:#ifdef CONFIG_THERMAL
>     drivers/power/power_supply_core.c:#ifdef CONFIG_THERMAL

> So can we give the similar try here and test for build?

This is still a hack; if this is causing real problems the thermal
subsystem should be doing something to avoid the issue (for example
providing an always built in stub) though I suspect in reality it's not
a practical issue.

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


Thread

Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree Mark Brown <broonie@kernel.org> - 2016-03-05 13:30 +0100
  Re: Applied "regulator: max8973: add support for junction thermal  warning" to the regulator tree Mark Brown <broonie@kernel.org> - 2016-03-06 03:40 +0100
    Re: Applied "regulator: max8973: add support for junction thermal  warning" to the regulator tree Laxman Dewangan <ldewangan@nvidia.com> - 2016-03-06 09:10 +0100
      Re: Applied "regulator: max8973: add support for junction thermal  warning" to the regulator tree Mark Brown <broonie@kernel.org> - 2016-03-06 12:40 +0100
        Re: Applied "regulator: max8973: add support for junction thermal  warning" to the regulator tree Laxman Dewangan <ldewangan@nvidia.com> - 2016-03-07 08:00 +0100
          Re: Applied "regulator: max8973: add support for junction thermal  warning" to the regulator tree Mark Brown <broonie@kernel.org> - 2016-03-07 08:50 +0100
            Re: Applied "regulator: max8973: add support for junction thermal  warning" to the regulator tree Laxman Dewangan <ldewangan@nvidia.com> - 2016-03-07 12:10 +0100
              Re: Applied "regulator: max8973: add support for junction thermal  warning" to the regulator tree Mark Brown <broonie@kernel.org> - 2016-03-08 10:20 +0100

csiph-web