From: Xiubo Li <Li.Xiubo@freescale.com>
To: thierry.reding@gmail.com, linux-pwm@vger.kernel.org
Cc: broonie@kernel.org, swarren@nvidia.com,
linux-kernel@vger.kernel.org, Xiubo Li <Li.Xiubo@freescale.com>
Subject: [PATCH 3/3] pwm: ftm-pwm: Add big-endian support
Date: Fri, 21 Mar 2014 12:53:10 +0800 [thread overview]
Message-ID: <1395377590-23537-4-git-send-email-Li.Xiubo@freescale.com> (raw)
In-Reply-To: <1395377590-23537-1-git-send-email-Li.Xiubo@freescale.com>
Now for the following scenarios:
SoC | CPU | FTM-PWM | 'big-endian' property is needed?
-------------|--------|---------|---------------------------------
Vybird | LE | LE | No
LS1 | LE | BE | Yes
LS2 | LE | LE | No
Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
---
drivers/pwm/pwm-fsl-ftm.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/pwm/pwm-fsl-ftm.c b/drivers/pwm/pwm-fsl-ftm.c
index 5d999c1..9a82741 100644
--- a/drivers/pwm/pwm-fsl-ftm.c
+++ b/drivers/pwm/pwm-fsl-ftm.c
@@ -409,6 +409,7 @@ static struct regmap_config fsl_pwm_regmap_config = {
static int fsl_pwm_probe(struct platform_device *pdev)
{
+ struct device_node *np = pdev->dev.of_node;
struct fsl_pwm_chip *fpc;
struct resource *res;
void __iomem *base;
@@ -422,6 +423,11 @@ static int fsl_pwm_probe(struct platform_device *pdev)
fpc->chip.dev = &pdev->dev;
+ if (of_property_read_bool(np, "big-endian"))
+ fsl_pwm_regmap_config.val_format_endian = REGMAP_ENDIAN_BIG;
+ else
+ fsl_pwm_regmap_config.val_format_endian = REGMAP_ENDIAN_NATIVE;
+
res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
base = devm_ioremap_resource(&pdev->dev, res);
if (IS_ERR(base))
--
1.8.4
next prev parent reply other threads:[~2014-03-21 4:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 4:53 [PATCH 0/3] FTM PWM adds regmap and endianness support Xiubo Li
2014-03-21 4:53 ` [PATCH 1/3] pwm: ftm-pwm: Clean up the code Xiubo Li
2014-04-28 14:57 ` Thierry Reding
2014-04-28 15:16 ` Li.Xiubo
2014-03-21 4:53 ` [PATCH 2/3] pwm: ftm-pwm: Convert to direct regmap API usage Xiubo Li
2014-04-28 14:59 ` Thierry Reding
2014-04-28 15:14 ` Li.Xiubo
2014-03-21 4:53 ` Xiubo Li [this message]
2014-04-28 15:02 ` [PATCH 3/3] pwm: ftm-pwm: Add big-endian support Thierry Reding
2014-04-28 15:11 ` Li.Xiubo
2014-04-10 6:05 ` [PATCH 0/3] FTM PWM adds regmap and endianness support Li.Xiubo
2014-04-28 13:10 ` Thierry Reding
2014-04-28 14:26 ` Li.Xiubo
2014-04-28 14:56 ` Thierry Reding
2014-04-28 15:21 ` 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=1395377590-23537-4-git-send-email-Li.Xiubo@freescale.com \
--to=li.xiubo@freescale.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=swarren@nvidia.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).