From: Sebastian Reichel <sre@kernel.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFT/RFC] power_supply: bq2415x_charger: Initialize workqueue before scheduling it
Date: Mon, 27 Jul 2015 16:22:29 +0200 [thread overview]
Message-ID: <20150727142229.GD12993@earth> (raw)
In-Reply-To: <201507252349.06519@pali>
[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]
Hi,
On Sat, Jul 25, 2015 at 11:49:06PM +0200, Pali Rohár wrote:
> On Tuesday 14 July 2015 02:34:13 Krzysztof Kozlowski wrote:
> > The driver during probe registers a power supply notifier
> > (with bq2415x_notifier_call() callback) and calls it manually right
> > after. The notifier callback function schedules driver's workqueue
> > (bq->work).
> >
> > However the workqueue was initialized after these two events (after
> > registering power supply notifier and calling manually the callback).
> >
> > When power supply core notified the driver (executing its
> > bq2415x_notifier_call() callback) the scheduled workqueue could be
> > still uninitialized.
> >
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> > Reported-by: Pali Rohár <pali.rohar@gmail.com>
> >
> > ---
> >
> > I don't have the hardware, please test. Additionally I could not find
> > the commit which introduced the issue so I did not cc-stable.
> > ---
> > drivers/power/bq2415x_charger.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/power/bq2415x_charger.c
> > b/drivers/power/bq2415x_charger.c index e98dcb661cc9..527ed0f18796
> > 100644
> > --- a/drivers/power/bq2415x_charger.c
> > +++ b/drivers/power/bq2415x_charger.c
> > @@ -1601,6 +1601,7 @@ static int bq2415x_probe(struct i2c_client
> > *client, bq->reported_mode = BQ2415X_MODE_OFF;
> > bq->autotimer = 0;
> > bq->automode = 0;
> > + INIT_DELAYED_WORK(&bq->work, bq2415x_timer_work);
> >
> > if (np || ACPI_HANDLE(bq->dev)) {
> > ret = device_property_read_u32(bq->dev,
> > @@ -1677,7 +1678,6 @@ static int bq2415x_probe(struct i2c_client
> > *client, dev_info(bq->dev, "automode not supported\n");
> > }
> >
> > - INIT_DELAYED_WORK(&bq->work, bq2415x_timer_work);
> > bq2415x_set_autotimer(bq, 1);
> >
> > dev_info(bq->dev, "driver registered\n");
>
> Looks like this is really problem. I sent alternative patch to mailing
> list which should fix this problem too plus allows to load
> bq2415x_charger.ko in n900 qemu.
I have not yet reviewed your patch (just skipped over it), but the
qemu changes are a bit intrusive for -rc. I suggest to apply this
patch for 4.2-rc. The extended patch can then be added in 4.3.
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-27 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 0:34 [RFT/RFC] power_supply: bq2415x_charger: Initialize workqueue before scheduling it Krzysztof Kozlowski
2015-07-14 7:18 ` Pali Rohár
2015-07-25 21:49 ` Pali Rohár
2015-07-27 14:22 ` Sebastian Reichel [this message]
2015-07-27 14:48 ` Pali Rohár
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=20150727142229.GD12993@earth \
--to=sre@kernel.org \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali.rohar@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).