From: Wenhua Lin <Wenhua.Lin@unisoc.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>, <linux-pwm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
wenhua lin <wenhua.lin1994@gmail.com>,
Wenhua Lin <Wenhua.Lin@unisoc.com>,
Xiongpeng Wu <xiongpeng.wu@unisoc.com>,
zhaochen su <zhaochen.su29@gmail.com>,
Zhaochen Su <Zhaochen.Su@unisoc.com>,
Xiaolong Wang <Xiaolong.Wang@unisoc.com>
Subject: [PATCH V2 0/6] pwm: sprd: Modification of UNISOC Platform PWM Driver
Date: Thu, 25 Jan 2024 10:55:27 +0800 [thread overview]
Message-ID: <20240125025533.10315-1-Wenhua.Lin@unisoc.com> (raw)
Due to new usage scenarios, some upgrades are made to unisoc's pwm driver.
Patch 1 supports the change of channel offset on UMS9620.
Patch 2 supports more brightness levels (duty cycle) for backlight control.
Patch 3 optimizes the calculation method of duty.
Patch 4 converts dt-binding file from txt to yaml
Patch 5-6 update pwm-sprd.yaml according to patch 1 and patch 2.
Change in V2:
-Change dev_err to dev_info in PATCH 2/6.
-Add maintainer to gitconfig.
Wenhua Lin (6):
pwm: sprd: Add support for UMS9620
pwm: sprd: Improve the pwm backlight control function
pwm: sprd: Optimize the calculation method of duty
dt-bindings: pwm: sprd: Convert to YAML
pwm: sprd: Add sprd,ums9620-pwm compatible
dt-bindings: pwm: sprd: Add sprd,mod attribute
.../devicetree/bindings/pwm/pwm-sprd.txt | 40 -------
.../devicetree/bindings/pwm/pwm-sprd.yaml | 106 ++++++++++++++++++
drivers/pwm/pwm-sprd.c | 71 ++++++++++--
3 files changed, 165 insertions(+), 52 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/pwm/pwm-sprd.txt
create mode 100644 Documentation/devicetree/bindings/pwm/pwm-sprd.yaml
--
2.17.1
next reply other threads:[~2024-01-25 3:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 2:55 Wenhua Lin [this message]
2024-01-25 2:55 ` [PATCH V2 1/6] pwm: sprd: Add support for UMS9620 Wenhua Lin
2024-01-26 7:24 ` Uwe Kleine-König
2024-01-25 2:55 ` [PATCH V2 2/6] pwm: sprd: Improve the pwm backlight control function Wenhua Lin
2024-01-25 7:20 ` Chunyan Zhang
2024-01-25 21:13 ` Uwe Kleine-König
2024-01-25 2:55 ` [PATCH V2 3/6] pwm: sprd: Optimize the calculation method of duty Wenhua Lin
2024-01-26 7:30 ` Uwe Kleine-König
2024-01-25 2:55 ` [PATCH V2 4/6] dt-bindings: pwm: sprd: Convert to YAML Wenhua Lin
2024-01-25 17:31 ` Conor Dooley
2024-01-30 22:17 ` Rob Herring
2024-01-25 2:55 ` [PATCH V2 5/6] pwm: sprd: Add sprd,ums9620-pwm compatible Wenhua Lin
2024-01-25 21:08 ` Uwe Kleine-König
2024-01-25 2:55 ` [PATCH V2 6/6] dt-bindings: pwm: sprd: Add sprd,mod attribute Wenhua Lin
2024-01-25 17:24 ` Conor Dooley
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=20240125025533.10315-1-Wenhua.Lin@unisoc.com \
--to=wenhua.lin@unisoc.com \
--cc=Xiaolong.Wang@unisoc.com \
--cc=Zhaochen.Su@unisoc.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wenhua.lin1994@gmail.com \
--cc=xiongpeng.wu@unisoc.com \
--cc=zhang.lyra@gmail.com \
--cc=zhaochen.su29@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).