[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <91017889-2ae7-d467-eed3-6d3b2bb130b9@gmx.net>
Date: Thu, 31 Oct 2019 14:08:36 +0100
From: Stefan Wahren <wahrenst@....net>
To: Chen-Yu Tsai <wens@...nel.org>, Markus Mayer <mmayer@...adcom.com>,
Florian Fainelli <f.fainelli@...il.com>,
Zhang Rui <rui.zhang@...el.com>,
Eduardo Valentin <edubezval@...il.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Amit Kucheria <amit.kucheria@...durent.com>
Cc: Chen-Yu Tsai <wens@...e.org>,
bcm-kernel-feedback-list@...adcom.com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH] thermal: brcmstb: enable hwmon
Hi Chen-Yu,
Am 30.10.19 um 17:38 schrieb Chen-Yu Tsai:
> From: Chen-Yu Tsai <wens@...e.org>
>
> By defaul of-based thermal driver do not have hwmon entries registered.
>
> Do this explicitly so users can use standard hwmon interfaces and tools
> to read the temperature.
>
> This is based on similar changes for bcm2835_thermal in commit
> d56c19d07e0b ("thermal: bcm2835: enable hwmon explicitly").
>
> Signed-off-by: Chen-Yu Tsai <wens@...e.org>
> ---
>
> This patch was only compile tested. A similar patch [1] was submitted to
> the downstream kernel, which I did build and actually run on a Raspberry
> Pi 4.
just a note: from my understanding [2] the brcmstb_thermal isn't the
right driver for BCM2711. Please consider the current downstream
solution for BCM2711 support as a quick hack to avoid writing a new
thermal driver. But must confess that i didn't test Florian's recent
changes yet.
Regards
Stefan
[2] -
https://github.com/raspberrypi/linux/issues/3101#issuecomment-527554223
>
> This one for mainline is much simpler, as it does not need to deal with
> the error path or device removal, due to the use of devres.
>
> [1] https://github.com/raspberrypi/linux/pull/3307
>
> ---
> drivers/thermal/broadcom/brcmstb_thermal.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
Powered by blists - more mailing lists