From: "HACHIMI Samir" <shachimi@adeneo-embedded.com>
To: <shawn.guo@linaro.org>, <thierry.reding@avionic-design.de>
Cc: <linux-arm-kernel@lists.infradead.org>, <s.hauer@pengutronix.de>,
<linux-kernel@vger.kernel.org>,
"HACHIMI Samir" <shachimi@adeneo-embedded.com>
Subject: [PATCH v2 0/2] imx6q: pwm: Activate stop_mode and configure pinmux
Date: Mon, 27 Aug 2012 17:34:30 +0200 [thread overview]
Message-ID: <3465D313FDFB824F9A9C8CD24FA4F6BCB4ACFC@frontmail.adetel.com> (raw)
From: Samir Hachimi <shachimi@adeneo-embedded.com>
This patch series enables support for pwm driver on imx6q SoC. The first
patch of the series configure the pinctrl for pwm in device-tree. Actually
they are several pin who can be set to pwmO for each pwm, so I assume that
all of them must be enabled when configuring pin.
The second patch activate stop_enable mode and unset the enable bit during
configuration of pwm, and set the enable bit in pwm CR register during enable.
Changes since v1:
Remove default pwm pinmux configuration in DT as Shawn and Matt suggested.
Now, pwm used pwm's clocks properties to configure pwm's clock.
Need Shawn's patch '[PATCH v2 0/4] Move imx6q/28/23 clock lookup over to device tree' to work.
Use Benoît's '[PATCH] pwm-imx: Fix config / enable / disable' (un)setting the cr enable bit to enable/disable pwm.
The second patch used driver_data instead of cpu_is_xxx macros, to check used architecture and enabled stop_enable mode.
Samir Hachimi (2):
Add clock look-up for pwm.
Enable Stop_enable mode during configuration of pwm.
arch/arm/boot/dts/imx6q.dtsi | 68 ++++++++++++++++++++++++++++++++++++++++++
drivers/pwm/pwm-imx.c | 59 ++++++++++++++++++++++++++----------
2 files changed, 111 insertions(+), 16 deletions(-)
next reply other threads:[~2012-08-27 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 15:34 HACHIMI Samir [this message]
2012-08-28 6:39 ` Sascha Hauer
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=3465D313FDFB824F9A9C8CD24FA4F6BCB4ACFC@frontmail.adetel.com \
--to=shachimi@adeneo-embedded.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=thierry.reding@avionic-design.de \
/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
all inboxes | Powered by JetHome®