From: Aditya Prayoga <aditya@kobol.io>
To: linux-gpio@vger.kernel.org
Cc: Richard Genoud <richard.genoud@gmail.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Gauthier Provost <gauthier@kobol.io>,
Alban Browaeys <alban.browaeys@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
Dennis Gilmore <dennis@ausil.us>,
Ralph Sennhauser <ralph.sennhauser@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Aditya Prayoga <aditya@kobol.io>
Subject: [PATCH RESEND 0/2] gpio: mvebu: Add support for multiple PWM lines
Date: Mon, 6 Aug 2018 10:29:14 +0800 [thread overview]
Message-ID: <1533522556-55055-1-git-send-email-aditya@kobol.io> (raw)
Hi everyone,
Helios4, an Armada 388 based NAS SBC, provides 2 (4-pins) fan connectors.
The PWM pins on both connector are connected to GPIO on bank 1. Current gpio-
mvebu does not allow more than one PWM on the same bank.
Resend the patch to add more reviewer.
Aditya
---
Aditya Prayoga (2):
gpio: mvebu: Add support for multiple PWM lines per GPIO chip
gpio: mvebu: Allow to use non-default PWM counter
drivers/gpio/gpio-mvebu.c | 111 ++++++++++++++++++++++++++++++++++++++--------
1 file changed, 92 insertions(+), 19 deletions(-)
--
2.7.4
next reply other threads:[~2018-08-06 2:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 2:29 Aditya Prayoga [this message]
2018-08-06 2:29 ` [PATCH RESEND 1/2] gpio: mvebu: Add support for multiple PWM lines per GPIO chip Aditya Prayoga
2018-08-06 3:38 ` Andrew Lunn
2018-08-08 10:27 ` Aditya Prayoga
2018-08-29 7:54 ` Linus Walleij
2018-08-29 8:02 ` Thomas Petazzoni
2018-08-29 12:09 ` Linus Walleij
2018-08-29 12:52 ` Andrew Lunn
2018-08-29 8:13 ` Gregory CLEMENT
2018-08-06 2:29 ` [PATCH RESEND 2/2] gpio: mvebu: Allow to use non-default PWM counter Aditya Prayoga
2018-08-06 13:52 ` Andrew Lunn
2018-08-08 11:40 ` Aditya Prayoga
2018-08-09 15:03 ` Richard Genoud
2018-08-09 15:43 ` Andrew Lunn
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=1533522556-55055-1-git-send-email-aditya@kobol.io \
--to=aditya@kobol.io \
--cc=alban.browaeys@gmail.com \
--cc=andrew@lunn.ch \
--cc=dennis@ausil.us \
--cc=gauthier@kobol.io \
--cc=gregory.clement@bootlin.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=ralph.sennhauser@gmail.com \
--cc=richard.genoud@gmail.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).