Linux Power Management development
 help / color / mirror / Atom feed
From: Lubomir Rintel <lkundrak@v3.sk>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
	Amit Kucheria <amit.kucheria@verdurent.com>,
	kongxinwei <kong.kongxinwei@hisilicon.com>,
	Wangtao <kevin.wangtao@hisilicon.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal: hisilicon: Don't enable by default
Date: Tue, 17 Mar 2020 20:27:48 +0100	[thread overview]
Message-ID: <20200317192748.GB24359@furthur.local> (raw)
In-Reply-To: <1940ceca-c791-5fa6-c680-461a27c09ccf@linaro.org>

On Tue, Mar 17, 2020 at 06:45:29PM +0100, Daniel Lezcano wrote:
> On 17/03/2020 18:41, Lubomir Rintel wrote:
> > Users are generally unlikely to have a HiSilicon thermal sensor.
> 
> Why ?

Because most computers don't run on HiSilicon chips.

> The thermal sensor is needed for the thermal mitigation.

If it's really needed, shouldn't ARCH_HISI depend on it?

In any case, I submitted this, because the driver enabled itself when I
turned on COMPILE_TEST, which was entirely unexpected. Unless I'm
mistaken, defaulting to off seems to be a standard practice for most
drivers, including thermal.

Would this be a better idea?

  default y if ARCH_HISI

Thanks
Lubo

> 
> > Like most other thermal drivers, don't build it by default/
> >
> > Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
> > ---
> >  drivers/thermal/Kconfig | 1 -
> >  1 file changed, 1 deletion(-)
> > 
> > diff --git a/drivers/thermal/Kconfig b/drivers/thermal/Kconfig
> > index 02c3aa322a4a6..2062f8ec272b6 100644
> > --- a/drivers/thermal/Kconfig
> > +++ b/drivers/thermal/Kconfig
> > @@ -233,7 +233,6 @@ config HISI_THERMAL
> >  	depends on ARCH_HISI || COMPILE_TEST
> >  	depends on HAS_IOMEM
> >  	depends on OF
> > -	default y
> >  	help
> >  	  Enable this to plug hisilicon's thermal sensor driver into the Linux
> >  	  thermal framework. cpufreq is used as the cooling device to throttle
> > 
> 
> 
> -- 
>  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
> 
> Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
> <http://twitter.com/#!/linaroorg> Twitter |
> <http://www.linaro.org/linaro-blog/> Blog
> 

  reply	other threads:[~2020-03-17 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 17:41 [PATCH] thermal: hisilicon: Don't enable by default Lubomir Rintel
2020-03-17 17:45 ` Daniel Lezcano
2020-03-17 19:27   ` Lubomir Rintel [this message]
2020-03-17 20:05     ` Daniel Lezcano

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=20200317192748.GB24359@furthur.local \
    --to=lkundrak@v3.sk \
    --cc=amit.kucheria@verdurent.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=kevin.wangtao@hisilicon.com \
    --cc=kong.kongxinwei@hisilicon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox