From: Yash Shah <yash.shah@sifive.com>
To: palmer@sifive.com, linux-pwm@vger.kernel.org,
linux-riscv@lists.infradead.org
Cc: thierry.reding@gmail.com, robh+dt@kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sachin.ghadi@sifive.com,
paul.walmsley@sifive.com, Yash Shah <yash.shah@sifive.com>
Subject: [RFC v2 0/2] PWM support for HiFive Unleashed
Date: Fri, 14 Dec 2018 11:50:40 +0530 [thread overview]
Message-ID: <1544768442-12530-1-git-send-email-yash.shah@sifive.com> (raw)
This patch series adds PWM drivers and DT documentation for
HiFive Unleashed board. The patches are mostly based on Wesley's patch.
V2 of this patchset incorporates below items pointed out in v1.
V2 changed from V1:
1. Remove inclusion of dt-bindings/pwm/pwm.h
2. Remove artificial alignments
3. Replace ioread32/iowrite32 with readl/writel
4. Remove camelcase
5. Change dev_info to dev_dbg for unnecessary log
6. Correct typo in driver name
7. Remove use of of_match_ptr macro
8. Update the DT compatible strings and Add reference to a common
versioning document
Yash Shah (2):
pwm: sifive: Add DT documentation for SiFive PWM Controller
pwm: sifive: Add a driver for SiFive SoC PWM
.../devicetree/bindings/pwm/pwm-sifive.txt | 44 ++++
drivers/pwm/Kconfig | 10 +
drivers/pwm/Makefile | 1 +
drivers/pwm/pwm-sifive.c | 229 +++++++++++++++++++++
4 files changed, 284 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pwm/pwm-sifive.txt
create mode 100644 drivers/pwm/pwm-sifive.c
--
1.9.1
next reply other threads:[~2018-12-14 6:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 6:20 Yash Shah [this message]
2018-12-14 6:20 ` [RFC v2 1/2] pwm: sifive: Add DT documentation for SiFive PWM Controller Yash Shah
2018-12-17 21:16 ` Uwe Kleine-König
2019-01-04 5:09 ` Yash Shah
2018-12-18 17:20 ` Rob Herring
2019-01-04 5:03 ` Yash Shah
2018-12-14 6:20 ` [RFC v2 2/2] pwm: sifive: Add a driver for SiFive SoC PWM Yash Shah
2018-12-17 22:11 ` Uwe Kleine-König
2019-01-04 5:14 ` Yash Shah
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=1544768442-12530-1-git-send-email-yash.shah@sifive.com \
--to=yash.shah@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.com \
--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).