devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiubo Li <Li.Xiubo@freescale.com>
To: thierry.reding@gmail.com, mark.rutland@arm.com,
	linux-pwm@vger.kernel.org
Cc: robh+dt@kernel.org, pawel.moll@arm.com,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	rdunlap@infradead.org, galak@codeaurora.org,
	ijc+devicetree@hellion.org.uk, Xiubo Li <Li.Xiubo@freescale.com>
Subject: [PATCHv4 0/3] ftm-pwm: Convert to direct regmap API usage
Date: Tue, 19 Aug 2014 12:38:00 +0800	[thread overview]
Message-ID: <1408423083-19827-1-git-send-email-Li.Xiubo@freescale.com> (raw)


This is depended on the following patches, which have already been merged
into linux-next 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 V4:
- Modified the 'static struct regmap_config fsl_pwm_regmap_config = {}'
  to 'static const struct regmap_config fsl_pwm_regmap_config = {}'
- Followed the Mark Rutland's advice.

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        | 23 +++++-
 drivers/pwm/pwm-fsl-ftm.c                          | 90 +++++++++++-----------
 2 files changed, 69 insertions(+), 44 deletions(-)

-- 
1.8.5


             reply	other threads:[~2014-08-19  4:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19  4:38 Xiubo Li [this message]
2014-08-19  4:38 ` [PATCHv4 1/3] pwm: ftm-pwm: Clean up the code Xiubo Li
2014-08-19  4:38 ` [PATCHv4 2/3] pwm: ftm-pwm: Convert to direct regmap API usage Xiubo Li
2014-08-19  4:38 ` [PATCHv4 3/3] pwm: documentation: Add 'big-endian' property for FTM PWM Xiubo Li

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=1408423083-19827-1-git-send-email-Li.Xiubo@freescale.com \
    --to=li.xiubo@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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).