[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9DA1C2E5-C9EB-48AD-846D-92CC0C434BFE@realtek.com>
Date: Wed, 15 Mar 2023 14:02:31 +0000
From: Phinex Hung <phinex@...ltek.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
"jdelvare@...e.com" <jdelvare@...e.com>
CC: "linux@...ck-us.net" <linux@...ck-us.net>,
"linux-hwmon@...r.kernel.org" <linux-hwmon@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] hwmon: drivetemp: support to be a platform driver for thermal_of
On 15/03/2023 21:11, "Krzysztof Kozlowski" <krzk@...nel.org <mailto:krzk@...nel.org>> wrote:
Hi Krzysztof,
Thanks for your comment.
>Please use scripts/get_maintainers.pl to get a list of necessary people
>and lists to CC. It might happen, that command when run on an older
>kernel, gives you outdated entries. Therefore please be sure you base
>your patches on recent Linux kernel.
I am working on git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
For master branch.
Is there any updated git repo that I should rebase my patch?
>Bindings are always separate.
Would separate in the next patch.
>No such vendor prefix. Are you sure you are describing real hardware?
>Also device specific part looks too generic. What device is it exactly?
It's a generic patch, just want to support thermal zone using a simple device tree.
Any SoC with SCSI interface and attached hard drives can benefit this change.
Normally a THERMAL_OF require a platform device to add a thermal zone.
Original drivetemp.c works quite well as a hwmon device, but no thermal zone support.
My patch just extend its capability to support a simple thermal zone created with this hwmon.
This is bind to any specific vendor, just to provide an easy way to handle cooling when hard drives' temperature gets high.
Best Regards,
Phinex
Powered by blists - more mailing lists