From: Chanwoo Choi <cw00.choi@samsung.com>
To: Hans de Goede <hdegoede@redhat.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v4] extcon: int3496: process id-pin first so that we start with the right status
Date: Mon, 19 Feb 2018 18:55:22 +0900 [thread overview]
Message-ID: <5A8A9F0A.70608@samsung.com> (raw)
In-Reply-To: <20180213192550.31579-1-hdegoede@redhat.com>
Hi,
On 2018년 02월 14일 04:25, Hans de Goede wrote:
> Some other drivers may be waiting for our extcon to show-up, exiting their
> probe methods with -EPROBE_DEFER until we show up.
>
> These drivers will typically get the cable state directly after getting
> the extcon, this commit changes the int3496 code to wait for the initial
> processing of the id-pin to complete before exiting probe() with 0, which
> will cause devices waiting on the defered probe to get reprobed.
>
> This fixes a race where the initial work might still be running while other
> drivers were already calling extcon_get_state().
>
> Fixes: 2f556bdb9f2e ("extcon: int3496: Add Intel INT3496 ACPI ... driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> Changes in v2:
> -Add Fixes tag
>
> Changes in v3:
> -Fix oops on probe by scheduling the work too early
>
> Changes in v4:
> -Ugh sorry about this, but we cannot call extcon_set_state() before
> extcon_dev_register() at all because before registration the cable array
> is not yet allocated. Instead wait for the initial processing of the
> id-pin to complete before exiting probe().
> ---
> drivers/extcon/extcon-intel-int3496.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/extcon/extcon-intel-int3496.c b/drivers/extcon/extcon-intel-int3496.c
> index c8691b5a9cb0..191e99f06a9a 100644
> --- a/drivers/extcon/extcon-intel-int3496.c
> +++ b/drivers/extcon/extcon-intel-int3496.c
> @@ -153,8 +153,9 @@ static int int3496_probe(struct platform_device *pdev)
> return ret;
> }
>
> - /* queue initial processing of id-pin */
> + /* process id-pin so that we start with the right status */
> queue_delayed_work(system_wq, &data->work, 0);
> + flush_delayed_work(&data->work);
>
> platform_set_drvdata(pdev, data);
>
>
Applied it instead of v3.
--
Best Regards,
Chanwoo Choi
Samsung Electronics
prev parent reply other threads:[~2018-02-19 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180213192600epcas4p1cc557008467633131627c99f390d3157@epcas4p1.samsung.com>
2018-02-13 19:25 ` [PATCH v4] extcon: int3496: process id-pin first so that we start with the right status Hans de Goede
2018-02-19 9:55 ` Chanwoo Choi [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=5A8A9F0A.70608@samsung.com \
--to=cw00.choi@samsung.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=stable@vger.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