From: Billy Tsai <billy_tsai@aspeedtech.com>
To: <jdelvare@suse.com>, <linux@roeck-us.net>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <joel@jms.id.au>,
<andrew@codeconstruct.com.au>, <ukleinek@kernel.org>,
<billy_tsai@aspeedtech.com>, <linux-hwmon@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<linux-pwm@vger.kernel.org>, <BMC-SW@aspeedtech.com>
Subject: [PATCH v1 0/2] Enable WDT reload feature
Date: Thu, 24 Oct 2024 15:15:46 +0800 [thread overview]
Message-ID: <20241024071548.3370363-1-billy_tsai@aspeedtech.com> (raw)
Aspeed PWM controller has the WDT reload feature, which changes the duty
cycle to a preprogrammed value after a WDT/EXTRST#.
Billy Tsai (2):
hwmon: (aspeed-g6-pwm-tacho): Extend the #pwm-cells to 4
hwmon: (aspeed-g6-pwm-tacho): Support the WDT reload
.../bindings/hwmon/aspeed,g6-pwm-tach.yaml | 25 +++++++++-
drivers/hwmon/aspeed-g6-pwm-tach.c | 49 +++++++++++++++++++
drivers/pwm/core.c | 6 +--
include/linux/pwm.h | 10 ++++
4 files changed, 86 insertions(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2024-10-24 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 7:15 Billy Tsai [this message]
2024-10-24 7:15 ` [PATCH v1 1/2] hwmon: (aspeed-g6-pwm-tacho): Extend the #pwm-cells to 4 Billy Tsai
2024-10-24 13:45 ` Rob Herring (Arm)
2024-10-24 14:10 ` Rob Herring
2024-10-24 7:15 ` [PATCH v1 2/2] hwmon: (aspeed-g6-pwm-tacho): Support the WDT reload Billy Tsai
2024-10-24 15:40 ` [PATCH v1 0/2] Enable WDT reload feature Uwe Kleine-König
2024-10-24 16:07 ` Guenter Roeck
2024-10-25 2:00 ` Billy Tsai
2024-10-25 8:10 ` Uwe Kleine-König
2024-10-25 9:49 ` Billy Tsai
[not found] ` <OSQPR06MB72521C20B39B1469B5C6DCBC8B4F2@OSQPR06MB7252.apcprd06.prod.outlook.com>
2024-10-25 10:19 ` Uwe Kleine-König
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=20241024071548.3370363-1-billy_tsai@aspeedtech.com \
--to=billy_tsai@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=ukleinek@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).