From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Hans de Goede" <hdegoede@redhat.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>
Subject: [PATCH v3 0/8] pwm: lpss: Clean up and convert to a pure library
Date: Tue, 27 Sep 2022 17:47:15 +0300 [thread overview]
Message-ID: <20220927144723.9655-1-andriy.shevchenko@linux.intel.com> (raw)
First of all, a set of cleanups and code deduplications (for better
maintenance) to the PWM LPSS driver.
Second, we may (re-)use the core part as a library in the future in
the devices that combine the same PWM IP in their address space. So
convert the core file to be a pure library which doesn't require any
special resource handling or alike.
Changelog v3:
- postponed last patch until we have a new user
- added tags (Uwe, Hans)
- expanded commit message on why forward declarations are preferred over
full header inclusions
Changelog v2:
- replace patch 1 by Uwe's version (Uwe)
- update NS patch to have a default namespace defined (Uwe)
- describe all changes done in patch 4 (Uwe)
Andy Shevchenko (7):
pwm: lpss: Move exported symbols to PWM_LPSS namespace
pwm: lpss: Move resource mapping to the glue drivers
pwm: lpss: Include headers we are direct user of
pwm: lpss: Use device_get_match_data to get device data
pwm: lpss: Use DEFINE_RUNTIME_DEV_PM_OPS() and pm_ptr() macros
pwm: lpss: Make use of bits.h macros for all masks
pwm: lpss: Add a comment to the bypass field
Uwe Kleine-König (1):
pwm: lpss: Deduplicate board info data structures
drivers/pwm/pwm-lpss-pci.c | 48 ++++++++-------------------------
drivers/pwm/pwm-lpss-platform.c | 40 +++++++--------------------
drivers/pwm/pwm-lpss.c | 46 ++++++++++++++++++++++++++-----
drivers/pwm/pwm-lpss.h | 18 +++++++++++--
4 files changed, 77 insertions(+), 75 deletions(-)
--
2.35.1
next reply other threads:[~2022-09-27 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 14:47 Andy Shevchenko [this message]
2022-09-27 14:47 ` [PATCH v3 1/8] pwm: lpss: Deduplicate board info data structures Andy Shevchenko
2022-09-27 14:47 ` [PATCH v3 2/8] pwm: lpss: Move exported symbols to PWM_LPSS namespace Andy Shevchenko
2022-09-27 14:47 ` [PATCH v3 3/8] pwm: lpss: Move resource mapping to the glue drivers Andy Shevchenko
2022-09-27 14:47 ` [PATCH v3 4/8] pwm: lpss: Include headers we are direct user of Andy Shevchenko
2022-09-27 15:10 ` Uwe Kleine-König
2022-09-27 15:26 ` Andy Shevchenko
2022-09-27 15:55 ` Uwe Kleine-König
2022-09-27 16:18 ` Andy Shevchenko
2022-09-27 16:24 ` Andy Shevchenko
2022-09-27 14:47 ` [PATCH v3 5/8] pwm: lpss: Use device_get_match_data to get device data Andy Shevchenko
2022-09-27 14:47 ` [PATCH v3 6/8] pwm: lpss: Use DEFINE_RUNTIME_DEV_PM_OPS() and pm_ptr() macros Andy Shevchenko
2022-09-27 14:47 ` [PATCH v3 7/8] pwm: lpss: Make use of bits.h macros for all masks Andy Shevchenko
2022-09-27 14:47 ` [PATCH v3 8/8] pwm: lpss: Add a comment to the bypass field Andy Shevchenko
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=20220927144723.9655-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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