From: Thierry Reding <thierry.reding@gmail.com>
To: "Vokáč Michal" <Michal.Vokac@ysoft.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Lukasz Majewski" <l.majewski@majess.pl>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
"Lothar Waßmann" <LW@karo-electronics.de>
Subject: Re: [RCF PATCH v2 2/2] pwm: imx: Configure output to GPIO in disabled state
Date: Fri, 12 Oct 2018 18:00:37 +0200 [thread overview]
Message-ID: <20181012160037.GH31561@ulmo> (raw)
In-Reply-To: <1539163920-9442-3-git-send-email-michal.vokac@ysoft.com>
[-- Attachment #1: Type: text/plain, Size: 4634 bytes --]
On Wed, Oct 10, 2018 at 09:33:26AM +0000, Vokáč Michal wrote:
> Normally the PWM output is held LOW when PWM is disabled. This can cause
> problems when inverted PWM signal polarity is needed. With this behavior
> the connected circuit is fed by 100% duty cycle instead of being shut-off.
>
> Allow users to define a "gpio" and a "pwm" pinctrl states. The pwm pinctrl
> state is then selected when PWM is enabled and the gpio pinctrl state is
> selected when PWM is disabled. Also add a new pwm-gpios GPIO that is used
> to drive the output in the gpio state.
>
> If all the pinctrl states and the pwm-gpios are not correctly specified
> in DT the logic will work as before.
>
> As an example, with this patch a PWM controlled backlight with inversed
> signal polarity can be used in full brightness range. Without this patch
> the backlight can not be turned off as brightness = 0 disables the PWM
> and that in turn set PWM output LOW, that is full brightness.
>
> Output of the PWM with "default" pinctrl and with "pwm"+"gpio" pinctrl:
>
> +--------------+------------+---------------+---------------------------+
> | After reset | Bootloader | Linux pinctrl | User (sysfs, backlight..) |
> | 100k pull-up | (not used) | | enable | disable |
> +--------------+------------+---------------+---------------------------+
> ___________________________ default _ _ _
> |_________________| |_| |_| |_|_____________
>
> pwm + gpio
> ___________________________________________ _ _ _ _____________
> |_| |_| |_| |_|
>
> Signed-off-by: Michal Vokáč <michal.vokac@ysoft.com>
> ---
> Changes in v2:
> - Utilize the "pwm" and "gpio" pinctrl states.
> - Use the pwm-gpios signal to drive the output in "gpio" pinctrl state.
> - Select the right pinctrl state in probe.
>
> drivers/pwm/pwm-imx.c | 86 +++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 86 insertions(+)
>
> diff --git a/drivers/pwm/pwm-imx.c b/drivers/pwm/pwm-imx.c
> index 6cd3b72..3502123 100644
> --- a/drivers/pwm/pwm-imx.c
> +++ b/drivers/pwm/pwm-imx.c
> @@ -10,11 +10,13 @@
> #include <linux/clk.h>
> #include <linux/delay.h>
> #include <linux/err.h>
> +#include <linux/gpio/consumer.h>
> #include <linux/io.h>
> #include <linux/kernel.h>
> #include <linux/module.h>
> #include <linux/of.h>
> #include <linux/of_device.h>
> +#include <linux/pinctrl/consumer.h>
> #include <linux/platform_device.h>
> #include <linux/pwm.h>
> #include <linux/slab.h>
> @@ -92,10 +94,45 @@ struct imx_chip {
> void __iomem *mmio_base;
>
> struct pwm_chip chip;
> +
> + struct pinctrl *pinctrl;
> + struct pinctrl_state *pinctrl_pins_gpio;
> + struct pinctrl_state *pinctrl_pins_pwm;
> + struct gpio_desc *pwm_gpiod;
> };
>
> +
> #define to_imx_chip(chip) container_of(chip, struct imx_chip, chip)
>
> +static int imx_pwm_init_pinctrl_info(struct imx_chip *imx_chip,
> + struct platform_device *pdev)
> +{
> + imx_chip->pinctrl = devm_pinctrl_get(&pdev->dev);
> + if (!imx_chip->pinctrl || IS_ERR(imx_chip->pinctrl)) {
This is not correct. First, I don't think devm_pinctrl_get() will ever
return NULL, so the !imx_chip->pinctrl is useless. And if it did return
NULL and imx_chip->pinctrl could therefore be NULL, then...
> + dev_info(&pdev->dev, "can not get pinctrl\n");
> + return PTR_ERR(imx_chip->pinctrl);
... this is rubbish because it returns PTR_ERR(NULL) which is 0 and that
represents success.
While at it, dev_info() -> dev_err() might be more appropriate here. Or
if you want to make pinctrl support optional make this dev_dbg() like
the message further below.
> + }
> +
> + imx_chip->pinctrl_pins_pwm = pinctrl_lookup_state(imx_chip->pinctrl,
> + "pwm");
> + imx_chip->pinctrl_pins_gpio = pinctrl_lookup_state(imx_chip->pinctrl,
> + "gpio");
> + imx_chip->pwm_gpiod = devm_gpiod_get_optional(&pdev->dev, "pwm",
> + GPIOD_IN);
> +
> + if (PTR_ERR(imx_chip->pwm_gpiod) == -EPROBE_DEFER) {
> + return -EPROBE_DEFER;
> + } else if (IS_ERR(imx_chip->pwm_gpiod) ||
> + IS_ERR(imx_chip->pinctrl_pins_pwm) ||
> + IS_ERR(imx_chip->pinctrl_pins_gpio)) {
> + dev_dbg(&pdev->dev, "PWM pinctrl information incomplete\n");
Another option would be to make this (and the above) dev_warn() since we
do want people to update the DTB if at all possible. Without the DTB the
PWM could be susceptible to the issue that we're trying to fix.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-12 16:00 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 9:33 [RCF PATCH v2 0/2] pwm: imx: Configure output to GPIO in disabled state Vokáč Michal
2018-10-10 9:33 ` [RCF PATCH v2 1/2] dt-bindings: pwm: imx: Allow switching PWM output between PWM and GPIO Vokáč Michal
2018-10-10 13:39 ` Thierry Reding
2018-10-29 15:52 ` Vokáč Michal
2018-10-10 9:33 ` [RCF PATCH v2 2/2] pwm: imx: Configure output to GPIO in disabled state Vokáč Michal
2018-10-12 8:57 ` [RCF PATCH,v2,2/2] " Uwe Kleine-König
2018-10-12 15:04 ` Vokáč Michal
2018-10-12 15:54 ` Thierry Reding
2018-10-12 16:08 ` Uwe Kleine-König
2018-10-14 20:24 ` Uwe Kleine-König
2018-10-15 8:45 ` Thierry Reding
2018-10-29 15:55 ` Vokáč Michal
2018-10-29 15:54 ` Vokáč Michal
2018-11-07 9:33 ` Uwe Kleine-König
2018-11-07 13:32 ` Vokáč Michal
2018-11-07 15:01 ` Uwe Kleine-König
2018-11-08 15:21 ` Vokáč Michal
2018-11-08 19:18 ` Uwe Kleine-König
2018-11-09 14:24 ` Vokáč Michal
2018-11-09 16:55 ` Uwe Kleine-König
2018-11-14 9:09 ` Uwe Kleine-König
2018-11-14 11:34 ` Thierry Reding
2018-11-14 21:51 ` Uwe Kleine-König
2018-11-15 15:25 ` Thierry Reding
2018-11-15 20:37 ` Uwe Kleine-König
2018-11-16 7:34 ` Lothar Waßmann
2018-11-16 8:25 ` Uwe Kleine-König
2018-11-22 15:42 ` Vokáč Michal
2018-11-22 16:23 ` Uwe Kleine-König
2018-11-22 16:46 ` Vokáč Michal
2018-11-22 19:03 ` Uwe Kleine-König
2018-11-23 15:15 ` Vokáč Michal
2018-11-25 20:56 ` Uwe Kleine-König
2018-11-26 9:11 ` Lothar Waßmann
2018-11-26 9:18 ` Uwe Kleine-König
2018-11-26 10:03 ` Lothar Waßmann
2018-11-26 11:51 ` Thierry Reding
2018-11-26 12:23 ` Lothar Waßmann
2018-11-26 13:34 ` Thierry Reding
2018-11-26 15:50 ` Vokáč Michal
2018-11-16 9:51 ` Thierry Reding
2018-11-16 10:39 ` Uwe Kleine-König
2018-11-16 11:56 ` Lothar Waßmann
2018-11-18 11:30 ` Uwe Kleine-König
2018-11-16 12:24 ` Thierry Reding
2018-11-18 20:08 ` Uwe Kleine-König
2018-11-19 8:48 ` Uwe Kleine-König
2018-11-22 15:03 ` Thierry Reding
2018-11-22 16:17 ` Uwe Kleine-König
2018-11-20 13:14 ` Vokáč Michal
2018-11-20 16:54 ` Uwe Kleine-König
2018-11-22 14:23 ` Vokáč Michal
2018-11-19 7:44 ` Linus Walleij
2018-11-19 8:32 ` Uwe Kleine-König
2018-11-20 8:35 ` Linus Walleij
2018-11-20 9:16 ` Viresh Kumar
2018-11-20 9:53 ` Uwe Kleine-König
2018-11-14 11:14 ` Thierry Reding
2018-10-12 16:00 ` Thierry Reding [this message]
2018-10-29 15:53 ` [RCF PATCH v2 2/2] " Vokáč Michal
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=20181012160037.GH31561@ulmo \
--to=thierry.reding@gmail.com \
--cc=LW@karo-electronics.de \
--cc=Michal.Vokac@ysoft.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=l.majewski@majess.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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).