From: Chanwoo Choi <cw00.choi@samsung.com>
To: Roger Quadros <rogerq@ti.com>
Cc: linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] extcon: Fix extcon_cable_get_state() from getting old state after notification
Date: Fri, 31 Jul 2015 15:38:08 +0900 [thread overview]
Message-ID: <55BB17D0.8000701@samsung.com> (raw)
In-Reply-To: <1436194018-18696-3-git-send-email-rogerq@ti.com>
Hi Roger,
On 07/06/2015 11:46 PM, Roger Quadros wrote:
> Currently the extcon code notifiers the interested listeners
> before it updates the extcon state with the new state.
> This will cause the listeners that use extcon_cable_get_state()
> to get the stale state and loose the new state.
>
> Fix this by first changing the extcon state variable and then
> notifying listeners.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> ---
> drivers/extcon/extcon.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
Applied it.
Thanks,
Chanwoo Choi
>
> diff --git a/drivers/extcon/extcon.c b/drivers/extcon/extcon.c
> index 868c6e2..26d1e1e 100644
> --- a/drivers/extcon/extcon.c
> +++ b/drivers/extcon/extcon.c
> @@ -275,19 +275,25 @@ int extcon_update_state(struct extcon_dev *edev, u32 mask, u32 state)
> spin_lock_irqsave(&edev->lock, flags);
>
> if (edev->state != ((edev->state & ~mask) | (state & mask))) {
> + u32 old_state;
> +
> if (check_mutually_exclusive(edev, (edev->state & ~mask) |
> (state & mask))) {
> spin_unlock_irqrestore(&edev->lock, flags);
> return -EPERM;
> }
>
> + old_state = edev->state;
> + edev->state &= ~mask;
> + edev->state |= state & mask;
> +
> for (index = 0; index < edev->max_supported; index++) {
> - if (is_extcon_changed(edev->state, state, index, &attached))
> - raw_notifier_call_chain(&edev->nh[index], attached, edev);
> + if (is_extcon_changed(old_state, edev->state, index,
> + &attached))
> + raw_notifier_call_chain(&edev->nh[index],
> + attached, edev);
> }
>
> - edev->state &= ~mask;
> - edev->state |= state & mask;
>
> /* This could be in interrupt handler */
> prop_buf = (char *)get_zeroed_page(GFP_ATOMIC);
>
prev parent reply other threads:[~2015-07-31 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:46 [PATCH 0/2] extcon: fixes for v4.2-rc1 Roger Quadros
2015-07-06 14:46 ` [PATCH 1/2] extcon: fix hang and extcon_get/set_cable_state() Roger Quadros
[not found] ` <1436194018-18696-2-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2015-07-07 12:40 ` Ivan T. Ivanov
2015-07-07 12:58 ` Roger Quadros
2015-07-07 13:06 ` [PATCH v2 " Roger Quadros
[not found] ` <1436274375-10308-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2015-07-07 14:04 ` Ivan T. Ivanov
2015-07-31 3:43 ` Chanwoo Choi
2015-07-10 15:54 ` Chanwoo Choi
[not found] ` <CAGTfZH3qM6_R8F8bE7oEUYhS0hW0hv7fKzYJ6K6z+dZmExCExA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-27 10:39 ` Roger Quadros
2015-07-27 23:26 ` Chanwoo Choi
2015-07-06 14:46 ` [PATCH 2/2] extcon: Fix extcon_cable_get_state() from getting old state after notification Roger Quadros
2015-07-31 6:38 ` 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=55BB17D0.8000701@samsung.com \
--to=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rogerq@ti.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).