From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Jingoo Han <jg1.han@samsung.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2] backlight: pwm: reject legacy pwm request for device defined in dt
Date: Mon, 12 Oct 2015 13:30:29 +0000 [thread overview]
Message-ID: <20151012153029.62f948d2@bbrezillon> (raw)
In-Reply-To: <561BB2BC.9090907@atmel.com>
Hi Vladimir,
On Mon, 12 Oct 2015 15:16:44 +0200
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> Le 12/10/2015 14:29, Vladimir Zapolskiy a écrit :
> > Platform PWM backlight data provided by board's device tree should be
> > complete enough to successfully request a pwm device using pwm_get()
> > API. This change fixes a bug, when an arbitrary (first found) PWM is
> > connected to a "pwm-backlight" compatible device, when explicit PWM
> > device reference is not given.
> >
> > Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt
> > already describes "pwms" as a required property, instead of blind
> > selection of a potentially wrong PWM reject legacy PWM device
> > registration request, leave legacy API only for non-dt cases.
> >
> > Based on initial implementation done by Dmitry Eremin-Solenikov.
> >
> > Reported-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> > Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
> > Acked-by: Thierry Reding <thierry.reding@gmail.com>
> > Acked-by: Lee Jones <lee.jones@linaro.org>
>
> It seems good to me:
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>
> (Adding some people to the Cc: list).
>
>
> > ---
> > The change is based on lee-backlight/for-backlight-next
> >
> > Changes from v1 to v2:
> > * rebased on top of Nicolas' commit
> > 68feaca0b13 ("backlight: pwm: Handle EPROBE_DEFER while requesting the PWM")
> >
> > Links to previous discussions of the change:
> > * https://patchwork.ozlabs.org/patch/483993/
> > * https://patchwork.ozlabs.org/patch/398849/
> >
> > drivers/video/backlight/pwm_bl.c | 19 +++++++++----------
> > 1 file changed, 9 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
> > index eff379b..ae3c6b6 100644
> > --- a/drivers/video/backlight/pwm_bl.c
> > +++ b/drivers/video/backlight/pwm_bl.c
> > @@ -271,19 +271,18 @@ static int pwm_backlight_probe(struct platform_device *pdev)
> > }
> >
> > pb->pwm = devm_pwm_get(&pdev->dev, NULL);
> > - if (IS_ERR(pb->pwm)) {
> > - ret = PTR_ERR(pb->pwm);
> > - if (ret = -EPROBE_DEFER)
> > - goto err_alloc;
> > -
> > + if (IS_ERR(pb->pwm) && PTR_ERR(pb->pwm) != -EPROBE_DEFER
> > + && !pdev->dev.of_node) {
> > dev_err(&pdev->dev, "unable to request PWM, trying legacy API\n");
> > pb->legacy = true;
> > pb->pwm = pwm_request(data->pwm_id, "pwm-backlight");
> > - if (IS_ERR(pb->pwm)) {
> > - dev_err(&pdev->dev, "unable to request legacy PWM\n");
> > - ret = PTR_ERR(pb->pwm);
> > - goto err_alloc;
> > - }
> > + }
> > +
> > + if (IS_ERR(pb->pwm)) {
> > + ret = PTR_ERR(pb->pwm);
> > + if (ret != -EPROBE_DEFER)
> > + dev_err(&pdev->dev, "unable to request PWM\n");
> > + goto err_alloc;
> > }
> >
> > dev_dbg(&pdev->dev, "got pwm for backlight\n");
> >
>
>
I still think it would be cleaner to do what Thierry proposed here [1].
IMO, embedding the complexity of different error cases depending on the
way PWM devices were defined (OF, pdata, ...) is rather risky and
make the code even more complicated.
Best Regards,
Boris
[1]https://lkml.org/lkml/2015/10/5/319
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-12 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 12:29 [PATCH v2] backlight: pwm: reject legacy pwm request for device defined in dt Vladimir Zapolskiy
2015-10-12 13:16 ` Nicolas Ferre
2015-10-12 13:30 ` Boris Brezillon [this message]
2015-10-12 13:54 ` Vladimir Zapolskiy
2015-10-12 14:06 ` Boris Brezillon
2015-10-12 14:19 ` Vladimir Zapolskiy
2015-10-12 15:19 ` Boris Brezillon
2015-10-12 15:32 ` Vladimir Zapolskiy
2015-10-12 17:11 ` Robert Jarzmik
2015-10-13 7:29 ` Lee Jones
2015-10-15 10:45 ` Vladimir Zapolskiy
2015-10-13 9:21 ` Robert Jarzmik
2015-10-15 11:03 ` Lee Jones
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=20151012153029.62f948d2@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=jg1.han@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=robert.jarzmik@free.fr \
--cc=thierry.reding@gmail.com \
--cc=vladimir_zapolskiy@mentor.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).