From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pwm: Fill pwm->args before calling pwm_request_from_chip()
Date: Tue, 17 May 2016 13:11:47 +0200 [thread overview]
Message-ID: <20160517131147.7f505f2b@bbrezillon> (raw)
In-Reply-To: <20160517110438.GB26166@ulmo.ba.sec>
On Tue, 17 May 2016 13:04:38 +0200
Thierry Reding <thierry.reding@gmail.com> wrote:
> On Tue, May 17, 2016 at 12:35:33PM +0200, Boris Brezillon wrote:
> [...]
> > diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
> > index 427142d..3d2eeaa 100644
> > --- a/drivers/pwm/core.c
> > +++ b/drivers/pwm/core.c
> > @@ -143,10 +143,6 @@ of_pwm_xlate_with_flags(struct pwm_chip *pc, const struct of_phandle_args *args)
> > if (args->args[0] >= pc->npwm)
> > return ERR_PTR(-EINVAL);
> >
> > - pwm = pwm_request_from_chip(pc, args->args[0], NULL);
> > - if (IS_ERR(pwm))
> > - return pwm;
> > -
> > pwm->args.period = args->args[1];
> >
> > if (args->args[2] & PWM_POLARITY_INVERTED)
> > @@ -154,6 +150,10 @@ of_pwm_xlate_with_flags(struct pwm_chip *pc, const struct of_phandle_args *args)
> > else
> > pwm->args.polarity = PWM_POLARITY_NORMAL;
> >
> > + pwm = pwm_request_from_chip(pc, args->args[0], NULL);
> > + if (IS_ERR(pwm))
> > + return pwm;
> > +
>
> Can't do that, because now you're dereferencing an uninitialized
> pointer.
Yes, forget this patch, it's not needed anyway since all PWM users are
now directly calling pwm_apply_args() after requesting the PWM. The bad
news is I broke bisectibilty :-(.
Still does not explain the bug reported by Mika.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-17 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 10:35 [PATCH] pwm: Fill pwm->args before calling pwm_request_from_chip() Boris Brezillon
2016-05-17 10:35 ` Boris Brezillon
2016-05-17 11:04 ` Thierry Reding
2016-05-17 11:11 ` Boris Brezillon [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=20160517131147.7f505f2b@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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