From: Conor Dooley <conor.dooley@microchip.com>
To: William Qiu <william.qiu@starfivetech.com>
Cc: <devicetree@vger.kernel.org>, <linux-pwm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, 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>,
Hal Feng <hal.feng@starfivetech.com>
Subject: Re: [PATCH v1 0/2] StarFive's Pulse Width Modulation driver support
Date: Wed, 1 Mar 2023 08:10:09 +0000 [thread overview]
Message-ID: <Y/8IYSYOsDrGIXzT@wendy> (raw)
In-Reply-To: <20230228091345.70515-1-william.qiu@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Hey William,
On Tue, Feb 28, 2023 at 05:13:43PM +0800, William Qiu wrote:
> 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
Is there a corresponding dts addition for this driver?
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-01 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:13 William Qiu
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 ` Conor Dooley [this message]
2023-03-01 8:17 ` [PATCH v1 0/2] StarFive's Pulse Width Modulation " 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=Y/8IYSYOsDrGIXzT@wendy \
--to=conor.dooley@microchip.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 \
--cc=william.qiu@starfivetech.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
Powered by JetHome