From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>, Joel Stanley <joel@jms.id.au>
Cc: Andrew Jeffery <andrew@codeconstruct.com.au>,
linux-hwmon@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-pwm@vger.kernel.org,
kernel@pengutronix.de
Subject: [PATCH 0/2] hwmon: (aspeed-g6-pwm-tacho): Prepare for further pwm core changes
Date: Mon, 18 Mar 2024 17:09:48 +0100 [thread overview]
Message-ID: <cover.1710777536.git.u.kleine-koenig@pengutronix.de> (raw)
Hello,
there is a pending rework for the pwm framework[1] that requires a
preparatory change for all pwm drivers. When creating them I wasn't
aware of the aspeed-g6-pwm-tacho driver, just found this now while doing
build tests with my series.
To not delay application of my series, I'd like to take the two patches
from this series via my pwm tree.
To state the (maybe) obvious: This series depends on the following commits:
7e1449cd15d1 "hwmon: (aspeed-g6-pwm-tacho): Support for ASPEED g6 PWM/Fan tach"
024913dbf99f pwm: Provide pwmchip_alloc() function and a devm variant of it
4e59267c7a20 pwm: Provide an inline function to get the parent device of a given chip
The earliest commit containing all those is:
15223fdbdf4f "Merge tag 'hwmon-for-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging"
Best regards
Uwe
[1] https://lore.kernel.org/linux-pwm/cover.1710670958.git.u.kleine-koenig@pengutronix.de
Uwe Kleine-König (2):
hwmon: (aspeed-g6-pwm-tacho): Make use of pwmchip_parent() accessor
hwmon: (aspeed-g6-pwm-tacho): Make use of devm_pwmchip_alloc()
function
drivers/hwmon/aspeed-g6-pwm-tach.c | 21 ++++++++++++---------
1 file changed, 12 insertions(+), 9 deletions(-)
base-commit: f6cef5f8c37f58a3bc95b3754c3ae98e086631ca
--
2.43.0
next reply other threads:[~2024-03-18 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 16:09 Uwe Kleine-König [this message]
2024-03-18 16:09 ` [PATCH 1/2] hwmon: (aspeed-g6-pwm-tacho): Make use of pwmchip_parent() accessor Uwe Kleine-König
2024-03-18 16:44 ` Guenter Roeck
2024-03-18 16:09 ` [PATCH 2/2] hwmon: (aspeed-g6-pwm-tacho): Make use of devm_pwmchip_alloc() function Uwe Kleine-König
2024-03-18 16:45 ` Guenter Roeck
2024-04-13 8:33 ` [PATCH 0/2] hwmon: (aspeed-g6-pwm-tacho): Prepare for further pwm core changes 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=cover.1710777536.git.u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=andrew@codeconstruct.com.au \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).