From: Xiubo Li <Li.Xiubo@freescale.com>
To: thierry.reding@gmail.com, linux-pwm@vger.kernel.org
Cc: robh+dt@kernel.org, pawel.moll@arm.com, rdunlap@infradead.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
Xiubo Li <Li.Xiubo@freescale.com>
Subject: [PATCHv3 0/3] ftm-pwm: Convert to direct regmap API usage
Date: Mon, 18 Aug 2014 11:32:32 +0800 [thread overview]
Message-ID: <1408332755-35102-1-git-send-email-Li.Xiubo@freescale.com> (raw)
This is depended on the following patches, which has been applied by
Mark into his Regmap-Tree:
https://lkml.org/lkml/2014/7/15/6
https://lkml.org/lkml/2014/7/15/5
https://lkml.org/lkml/2014/7/15/7
Changes in V3:
- Use the regmap framework's endianness method instead of its own.
Changes in V2:
- Adds detail descriptions of these patches.
Xiubo Li (3):
pwm: ftm-pwm: Clean up the code.
pwm: ftm-pwm: Convert to direct regmap API usage.
pwm: documentation: Add 'big-endian' property for FTM PWM.
.../devicetree/bindings/pwm/pwm-fsl-ftm.txt | 22 +++++-
drivers/pwm/pwm-fsl-ftm.c | 90 +++++++++++-----------
2 files changed, 68 insertions(+), 44 deletions(-)
--
1.8.5
next reply other threads:[~2014-08-18 3:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 3:32 Xiubo Li [this message]
2014-08-18 3:32 ` [PATCHv3 1/3] pwm: ftm-pwm: Clean up the code Xiubo Li
2014-08-18 3:32 ` [PATCHv3 2/3] pwm: ftm-pwm: Convert to direct regmap API usage Xiubo Li
2014-08-18 8:36 ` Thierry Reding
2014-08-18 8:45 ` Li.Xiubo-KZfg59tc24xl57MIdRCFDg
2014-08-18 3:32 ` [PATCHv3 3/3] pwm: documentation: Add 'big-endian' property for FTM PWM Xiubo Li
2014-08-18 9:59 ` Mark Rutland
2014-08-18 12:11 ` Li.Xiubo
2014-08-18 8:31 ` [PATCHv3 0/3] ftm-pwm: Convert to direct regmap API usage Thierry Reding
2014-08-18 8:43 ` Li.Xiubo
2014-08-18 8:49 ` Thierry Reding
2014-08-18 8:55 ` Li.Xiubo
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=1408332755-35102-1-git-send-email-Li.Xiubo@freescale.com \
--to=li.xiubo@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--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).