From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thierry Reding <thierry.reding@gmail.com>,
linux-pwm@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 0/4] pwm: lpss: clean up series
Date: Mon, 24 Oct 2016 17:43:21 +0300 [thread overview]
Message-ID: <20161024144325.130353-1-andriy.shevchenko@linux.intel.com> (raw)
There are clean ups and switch to new atomic API (would be considered as an
improvement).
The series tested on various Intel platforms, such as Edison and Minnowboard
MAX.
And the part I like most is -2 lines statistics!
Andy Shevchenko (3):
pwm: lpss: Avoid potential overflow of base_unit
pwm: lpss: Allow duty cycle to be 0
pwm: lpss: Switch to new atomic API
Mika Westerberg (1):
pwm: lpss: Do not export board infos for different PWM types
drivers/pwm/pwm-lpss-pci.c | 20 +++----
drivers/pwm/pwm-lpss-platform.c | 10 ++--
drivers/pwm/pwm-lpss.c | 120 +++++++++++++++++++++-------------------
drivers/pwm/pwm-lpss.h | 14 ++---
4 files changed, 81 insertions(+), 83 deletions(-)
--
2.9.3
next reply other threads:[~2016-10-24 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 14:43 Andy Shevchenko [this message]
2016-10-24 14:43 ` [PATCH v1 1/4] pwm: lpss: Avoid potential overflow of base_unit Andy Shevchenko
2016-10-25 9:33 ` Mika Westerberg
2016-10-24 14:43 ` [PATCH v1 2/4] pwm: lpss: Allow duty cycle to be 0 Andy Shevchenko
2016-10-25 9:38 ` Mika Westerberg
2016-10-24 14:43 ` [PATCH v1 3/4] pwm: lpss: Do not export board infos for different PWM types Andy Shevchenko
2016-10-24 14:43 ` [PATCH v1 4/4] pwm: lpss: Switch to new atomic API Andy Shevchenko
2016-10-25 9:39 ` Mika Westerberg
2016-11-14 10:32 ` [PATCH v1 0/4] pwm: lpss: clean up series Andy Shevchenko
2016-12-14 16:41 ` 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=20161024144325.130353-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-pwm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).