From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Hans de Goede" <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-pwm@vger.kernel.org
Cc: Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH v3 0/6] pinctrl: intel: Enable PWM optional feature
Date: Fri, 11 Nov 2022 20:43:22 +0200 [thread overview]
Message-ID: <20221111184328.58108-1-andriy.shevchenko@linux.intel.com> (raw)
This is a continuation of the previously applied PWM LPSS cleanup series.
Now, we would like to enable PWM optional feature that may be embedded
into Intel pin control IPs (starting from Sky Lake platforms).
I would like to route this via Intel pin control tree with issuing
an immutable branch for both PINCTRL and PWM subsystems, but I'm
open for other suggestions.
Hans, I dared to leave your Rb tags, however the patches are slightly
differ, because of the Uwe's suggestion on how to handle the missing
headers. I hope you are okay with that. If not, please comment what
must be amended then.
Changelog v3:
- added tags (Uwe, Linus, Thierry)
- fixed some spelling issues in the commit messages
- changed a paragraph in the commit message of the patch 3 (Uwe)
- replaced -ENODEV check with IS_REACHABLE() in the patch 6 (Uwe)
Changelog v2:
- added tag (Mika)
- added base-commit to the series, to make sure LKP can test it
Cc: Hans de Goede <hdegoede@redhat.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
Andy Shevchenko (6):
pwm: Add a stub for devm_pwmchip_add()
pwm: lpss: Rename MAX_PWMS --> LPSS_MAX_PWMS
pwm: lpss: Include headers we are the direct user of
pwm: lpss: Allow other drivers to enable PWM LPSS
pwm: lpss: Add pwm_lpss_probe() stub
pinctrl: intel: Enumerate PWM device when community has a capability
drivers/pinctrl/intel/pinctrl-intel.c | 32 +++++++++++++++
drivers/pwm/pwm-lpss.c | 2 +-
drivers/pwm/pwm-lpss.h | 34 ++++-----------
.../linux/platform_data/x86}/pwm-lpss.h | 41 ++++++++-----------
include/linux/pwm.h | 5 +++
5 files changed, 64 insertions(+), 50 deletions(-)
copy {drivers/pwm => include/linux/platform_data/x86}/pwm-lpss.h (51%)
base-commit: 9abf2313adc1ca1b6180c508c25f22f9395cc780
--
2.35.1
next reply other threads:[~2022-11-11 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 18:43 Andy Shevchenko [this message]
2022-11-11 18:43 ` [PATCH v3 1/6] pwm: Add a stub for devm_pwmchip_add() Andy Shevchenko
2022-11-11 18:43 ` [PATCH v3 2/6] pwm: lpss: Rename MAX_PWMS --> LPSS_MAX_PWMS Andy Shevchenko
2022-11-11 18:43 ` [PATCH v3 3/6] pwm: lpss: Include headers we are the direct user of Andy Shevchenko
2022-11-11 18:43 ` [PATCH v3 4/6] pwm: lpss: Allow other drivers to enable PWM LPSS Andy Shevchenko
2022-11-11 18:43 ` [PATCH v3 5/6] pwm: lpss: Add pwm_lpss_probe() stub Andy Shevchenko
2022-11-11 18:43 ` [PATCH v3 6/6] pinctrl: intel: Enumerate PWM device when community has a capability 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=20221111184328.58108-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).