From: Longbin Li <looong.bin@gmail.com>
To: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Chen Wang" <unicorn_wang@outlook.com>,
"Inochi Amaoto" <inochiama@gmail.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Longbin Li" <looong.bin@gmail.com>
Cc: linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: [PATCH v5 0/3] riscv: pwm: sophgo: add pwm support for SG2044
Date: Wed, 28 May 2025 18:11:35 +0800 [thread overview]
Message-ID: <20250528101139.28702-1-looong.bin@gmail.com> (raw)
This patch adds PWM controller support for four independent
PWM channel outputs.
---
Changes in v5:
- Rename function and variables for clarity.
- Modify code style.
Changes in v4:
You can simply review or test the patches at the link [4].
- add tags for mail.
Changes in v3:
You can simply review or test the patches at the link [3].
- Rename macro definitions to unify naming.
- Modify code style.
Changes in v2:
You can simply review or test the patches at the link [2].
- Modify variable naming and code logic.
- update "MODULE_AUTHOR".
Changes in v1:
You can simply review or test the patches at the link [1].
Link: https://lore.kernel.org/linux-riscv/20250407072056.8629-1-looong.bin@gmail.com/ [1]
Link: https://lore.kernel.org/linux-riscv/20250418022948.22853-1-looong.bin@gmail.com/ [2]
Link: https://lore.kernel.org/linux-riscv/20250424012335.6246-1-looong.bin@gmail.com/ [3]
Link: https://lore.kernel.org/linux-riscv/20250428013501.6354-1-looong.bin@gmail.com/ [4]
---
Longbin Li (3):
pwm: sophgo: reorganize the code structure
pwm: sophgo: add driver for SG2044
dt-bindings: pwm: sophgo: add pwm controller for SG2044
.../bindings/pwm/sophgo,sg2042-pwm.yaml | 4 +-
drivers/pwm/pwm-sophgo-sg2042.c | 141 +++++++++++++++---
2 files changed, 127 insertions(+), 18 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-28 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 10:11 Longbin Li [this message]
2025-05-28 10:11 ` [PATCH v5 1/3] dt-bindings: pwm: sophgo: add pwm controller for SG2044 Longbin Li
2025-05-28 10:11 ` [PATCH v5 2/3] pwm: sophgo: reorganize the code structure Longbin Li
2025-05-28 10:11 ` [PATCH v5 3/3] pwm: sophgo: add driver for SG2044 Longbin Li
2025-05-30 7:50 ` Uwe Kleine-König
2025-05-30 9:48 ` Longbin Li
2025-05-30 14:51 ` Uwe Kleine-König
2025-05-29 3:27 ` [PATCH v5 0/3] riscv: pwm: sophgo: add pwm support " Chen Wang
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=20250528101139.28702-1-looong.bin@gmail.com \
--to=looong.bin@gmail.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=ukleinek@kernel.org \
--cc=unicorn_wang@outlook.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).