From: Matthias Brugger <matthias.bgg@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>,
matthias.bgg@kernel.org, rui.zhang@intel.com,
edubezval@gmail.com, daniel.lezcano@linaro.org,
f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, eric@anholt.net
Cc: geert+renesas@glider.be, pmladek@suse.com,
linux-pm@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH] thermal: bcm2835: enable hwmon explicitly
Date: Tue, 23 Oct 2018 23:20:18 +0200 [thread overview]
Message-ID: <12ca4f71-8ba9-91dd-f5a0-0c72c91401ef@gmail.com> (raw)
In-Reply-To: <459136891.184150.1540296101955@email.1und1.de>
Hi Stefan,
On 23/10/2018 14:01, Stefan Wahren wrote:
> Hi Matthias,
>
>> matthias.bgg@kernel.org hat am 21. Oktober 2018 um 23:58 geschrieben:
>>
>>
>> From: Matthias Brugger <mbrugger@suse.com>
>>
>> By defaul of-based thermal driver do not enable hwmon.
>> This patch does this explicitly, so that the temperature can be read
>> through the common hwmon sysfs.
>>
>> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
>
> Acked-by: Stefan Wahren <stefan.wahren@i2se.com>
>
> I'm just curious which board and config did you use for your tests?
>
I use the RPi3 B+. I suppose when asking about the config, you want to know if I
also enable the RASPBERRYPI_HWMON, yes I enable that as well. Actually this
patch is for openSUSE Leap. You can find the whole config (if you are
interested) here:
https://kernel.suse.com/cgit/kernel-source/tree/config/arm64/default?h=SLE15
Regards,
Matthias
next prev parent reply other threads:[~2018-10-23 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 21:58 matthias.bgg
2018-10-23 12:01 ` Stefan Wahren
2018-10-23 21:20 ` Matthias Brugger [this message]
2018-11-07 19:04 ` Stefan Wahren
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=12ca4f71-8ba9-91dd-f5a0-0c72c91401ef@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=matthias.bgg@kernel.org \
--cc=mbrugger@suse.com \
--cc=pmladek@suse.com \
--cc=rjui@broadcom.com \
--cc=rui.zhang@intel.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.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
all inboxes | Powered by JetHome®