From: Eduardo Valentin <edubezval@gmail.com>
To: Jon Mason <jon.mason@broadcom.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
rafal@milecki.pl, Florian Fainelli <f.fainelli@gmail.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH] thermal: broadcom: ns-thermal: depends/default only for NS/NSP
Date: Wed, 31 May 2017 20:09:08 -0700 [thread overview]
Message-ID: <20170601030906.GA4502@localhost.localdomain> (raw)
In-Reply-To: <1496260544-4200-1-git-send-email-jon.mason@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
On Wed, May 31, 2017 at 03:55:44PM -0400, Jon Mason wrote:
> ARCH_BCM_IPROC includes support for many SoCs, not all of which have the
> same thermal hardware interface as the Northstar/Northstar Plus SoCs.
> This is not a major issue, as this driver will only be probed if the
> relevant device tree entry is present. However, it will result in a
> slightly larger than necessary kernel. By limiting the driver to only
> work on the NS/NSP SoCs, we can avoid the issue.
>
> Suggested-by: Scott Branden <scott.branden@broadcom.com>
> Signed-off-by: Jon Mason <jon.mason@broadcom.com>
Should this commit message include a Fixes: tag?
Maybe
Fixes: a94cb7e ("thermal: broadcom: add Northstar thermal driver")
> ---
> drivers/thermal/broadcom/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/thermal/broadcom/Kconfig b/drivers/thermal/broadcom/Kconfig
> index 42c098e86f84..c729dad2348c 100644
> --- a/drivers/thermal/broadcom/Kconfig
> +++ b/drivers/thermal/broadcom/Kconfig
> @@ -8,8 +8,8 @@ config BCM2835_THERMAL
>
> config BCM_NS_THERMAL
> tristate "Northstar thermal driver"
> - depends on ARCH_BCM_IPROC || COMPILE_TEST
> - default y if ARCH_BCM_IPROC
> + depends on ARCH_BCM_NSP || ARCH_BCM_5301X || COMPILE_TEST
> + default y if ARCH_BCM_NSP || ARCH_BCM_5301X
> help
> Support for the Northstar and Northstar Plus family of SoCs (e.g.
> BCM4708, BCM4709, BCM5301x, BCM95852X, etc). It contains DMU (Device
> --
> 2.7.4
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-01 3:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 19:55 [PATCH] thermal: broadcom: ns-thermal: depends/default only for NS/NSP Jon Mason
2017-05-31 20:03 ` Florian Fainelli
2017-06-01 3:09 ` Eduardo Valentin [this message]
2017-06-01 15:51 ` Jon Mason
2017-06-01 5:29 ` Rafał Miłecki
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=20170601030906.GA4502@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=jon.mason@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafal@milecki.pl \
--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 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.