linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Cc: Jingoo Han <jg1.han@samsung.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] backlight: pwm: reject legacy pwm request for device defined in dt
Date: Mon, 05 Oct 2015 12:46:30 +0000	[thread overview]
Message-ID: <20151005124630.GC17172@x1> (raw)
In-Reply-To: <20150921232225.GF11284@x1>

On Tue, 22 Sep 2015, Lee Jones wrote:

> On Sun, 14 Jun 2015, Vladimir Zapolskiy wrote:
> 
> > 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>
> > ---
> >  drivers/video/backlight/pwm_bl.c | 13 +++++++------
> >  1 file changed, 7 insertions(+), 6 deletions(-)
> 
> Applied, thanks.

Slight change of plan, as the patch does not apply.

Please rebase it on top of the backlight tree and resubmit with my
Ack.

> > diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
> > index 57cb9ec..9991cdb 100644
> > --- a/drivers/video/backlight/pwm_bl.c
> > +++ b/drivers/video/backlight/pwm_bl.c
> > @@ -271,15 +271,16 @@ static int pwm_backlight_probe(struct platform_device *pdev)
> >  	}
> >  
> >  	pb->pwm = devm_pwm_get(&pdev->dev, NULL);
> > -	if (IS_ERR(pb->pwm)) {
> > +	if (IS_ERR(pb->pwm) && !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)) {
> > +		dev_err(&pdev->dev, "unable to request PWM\n");
> > +		ret = PTR_ERR(pb->pwm);
> > +		goto err_alloc;
> >  	}
> >  
> >  	dev_dbg(&pdev->dev, "got pwm for backlight\n");
> 

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2015-10-05 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 14:29 [PATCH] backlight: pwm: reject legacy pwm request for device defined in dt Vladimir Zapolskiy
2015-09-21 15:16 ` Vladimir Zapolskiy
2015-09-21 23:22 ` Lee Jones
2015-10-05 12:46   ` Lee Jones [this message]

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=20151005124630.GC17172@x1 \
    --to=lee.jones@linaro.org \
    --cc=jg1.han@samsung.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --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).