From: William Qiu <william.qiu@starfivetech.com>
To: <devicetree@vger.kernel.org>, <linux-pwm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Thierry Reding <thierry.reding@gmail.com>,
William Qiu <william.qiu@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>
Subject: [PATCH v1 0/2] StarFive's Pulse Width Modulation driver support
Date: Tue, 28 Feb 2023 17:13:43 +0800 [thread overview]
Message-ID: <20230228091345.70515-1-william.qiu@starfivetech.com> (raw)
Hi,
This patchset adds initial rudimentary support for the StarFive
Pulse Width Modulation controller driver. And this driver will
be used in StarFive's VisionFive 2 board.The first patch add
Documentations for the device and Patch 2 adds device probe for
the module.
The patch series is based on v6.2.
William Qiu (2):
dt-bindings: PWM: Add StarFive PWM module
pwm: starfive: Add PWM driver support
.../devicetree/bindings/pwm/pwm-starfive.yaml | 54 ++++
MAINTAINERS | 7 +
drivers/pwm/Kconfig | 10 +
drivers/pwm/Makefile | 1 +
drivers/pwm/pwm-starfive-ptc.c | 256 ++++++++++++++++++
5 files changed, 328 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pwm/pwm-starfive.yaml
create mode 100644 drivers/pwm/pwm-starfive-ptc.c
--
2.34.1
next reply other threads:[~2023-02-28 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:13 William Qiu [this message]
2023-02-28 9:13 ` [PATCH v1 1/2] dt-bindings: PWM: Add StarFive PWM module William Qiu
2023-02-28 14:07 ` Krzysztof Kozlowski
2023-03-01 2:35 ` William Qiu
2023-02-28 9:13 ` [PATCH v1 2/2] pwm: starfive: Add PWM driver support William Qiu
2023-02-28 14:34 ` Krzysztof Kozlowski
2023-03-01 6:18 ` William Qiu
2023-03-01 8:10 ` [PATCH v1 0/2] StarFive's Pulse Width Modulation " Conor Dooley
2023-03-01 8:17 ` William Qiu
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=20230228091345.70515-1-william.qiu@starfivetech.com \
--to=william.qiu@starfivetech.com \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@starfivetech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--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).