From: Nicolin Chen <nicoleotsuka@gmail.com>
To: treding@nvidia.com
Cc: linux-tegra@vger.kernel.org, catalin.marinas@arm.com,
will.deacon@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: defconfig: Add HWMON INA3221 support
Date: Mon, 3 Jun 2019 14:17:46 -0700 [thread overview]
Message-ID: <20190603211745.GA21855@Asurada-Nvidia.nvidia.com> (raw)
In-Reply-To: <20190424181010.28950-1-nicoleotsuka@gmail.com>
On Wed, Apr 24, 2019 at 11:10:10AM -0700, Nicolin Chen wrote:
> Tegra186 board under arm64 is using this device, according to
> its dts file. So this patch enables its driver with a "=m" as
> the other HWMON drivers.
>
> Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com>
Sorry to ping this patch. But I am wondering if I sent it wrong
-- had been missing some other reviewers or maillists. May some
one kindly remind me?
Thank you
Nicolin
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 04cc2a2adc39..00043e706399 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -424,6 +424,7 @@ CONFIG_SENSORS_LM90=m
> CONFIG_SENSORS_PWM_FAN=m
> CONFIG_SENSORS_RASPBERRYPI_HWMON=m
> CONFIG_SENSORS_INA2XX=m
> +CONFIG_SENSORS_INA3221=m
> CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
> CONFIG_CPU_THERMAL=y
> CONFIG_THERMAL_EMULATION=y
> --
> 2.17.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-03 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 18:10 [PATCH] arm64: defconfig: Add HWMON INA3221 support Nicolin Chen
2019-06-03 21:17 ` Nicolin Chen [this message]
2019-06-14 16:01 ` Thierry Reding
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=20190603211745.GA21855@Asurada-Nvidia.nvidia.com \
--to=nicoleotsuka@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).