From: Wu Hao <hao.wu@intel.com>
To: mdf@kernel.org, linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-api@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux@roeck-us.net, jdelvare@suse.com,
gregkh@linuxfoundation.org, Wu Hao <hao.wu@intel.com>
Subject: [PATCH v6 0/3] add thermal/power management features for FPGA DFL drivers
Date: Tue, 10 Sep 2019 13:50:37 +0800 [thread overview]
Message-ID: <1568094640-4920-1-git-send-email-hao.wu@intel.com> (raw)
Hi Mortiz and all,
This patchset adds thermal and power management features for FPGA DFL
drivers. Both patches are using hwmon as userspace interfaces.
As previous dfl patches have been merged, so I resubmit this one after
rebase and clean up, as dependency is resolved now.
(This patchset is generated against char-misc-next).
Please help with review to see if any comments, thank you very much!
Main changes from v5:
- rebase and clean up (remove empty uinit function) per changes in recent
merged dfl patches.
- update date in sysfs doc.
Main changes from v4:
- rebase due to Documentation format change (dfl.txt -> rst).
- clamp threshold inputs for sysfs interfaces. (patch#3)
- update sysfs doc to add more description for ltr sysfs interfaces.
(patch#3)
Main changes from v3:
- use HWMON_CHANNEL_INFO.
Main changes from v2:
- switch to standard hwmon APIs for thermal hwmon:
temp1_alarm --> temp1_max
temp1_alarm_status --> temp1_max_alarm
temp1_crit_status --> temp1_crit_alarm
temp1_alarm_policy --> temp1_max_policy
- switch to standard hwmon APIs for power hwmon:
power1_cap --> power1_max
power1_cap_status --> power1_max_alarm
power1_crit_status --> power1_crit_alarm
Wu Hao (2):
fpga: dfl: fme: add thermal management support
fpga: dfl: fme: add power management support
Xu Yilun (1):
Documentation: fpga: dfl: add descriptions for thermal/power
management interfaces
Documentation/ABI/testing/sysfs-platform-dfl-fme | 134 ++++++++
Documentation/fpga/dfl.rst | 10 +
drivers/fpga/Kconfig | 2 +-
drivers/fpga/dfl-fme-main.c | 385 +++++++++++++++++++++++
4 files changed, 530 insertions(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2019-09-10 6:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 5:50 Wu Hao [this message]
2019-09-10 5:50 ` [PATCH v6 1/3] Documentation: fpga: dfl: add descriptions for thermal/power management interfaces Wu Hao
2019-09-10 19:29 ` Guenter Roeck
2019-09-10 5:50 ` [PATCH v6 2/3] fpga: dfl: fme: add thermal management support Wu Hao
2019-10-14 6:12 ` Wu, Hao
2019-09-10 5:50 ` [PATCH v6 3/3] fpga: dfl: fme: add power " Wu Hao
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=1568094640-4920-1-git-send-email-hao.wu@intel.com \
--to=hao.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mdf@kernel.org \
/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).