X86 platform drivers
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: "Pali Rohár" <pali.rohar@gmail.com>, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/3] platform/dell-wmi: Fix driver interface version query
Date: Tue, 1 Aug 2017 12:54:05 -0700	[thread overview]
Message-ID: <20170801195405.GB3110@fury> (raw)
In-Reply-To: <CALCETrUHw-bDMo6mrNM8+tdNDn71-ycb-aDtFTv82B0s8FiKHA@mail.gmail.com>

On Tue, Aug 01, 2017 at 11:08:26AM -0700, Andy Lutomirski wrote:
> On Tue, Aug 1, 2017 at 8:43 AM, Pali Rohár <pali.rohar@gmail.com> wrote:
> > On Tuesday 01 August 2017 08:37:26 Andy Lutomirski wrote:
> >> When I converted dell-wmi to the new bus infrastructure, I left the
> >> call to dell_wmi_check_descriptor_buffer() in dell_wmi_init().  This
> >> could cause two problems:
> >>
> >>  - An error message when loading the driver on a system without
> >>    dell-wmi.  We'd try to read the event descriptor even if the WMI
> >>    GUID wasn't there.
> >>
> >>  - A possible race if dell-wmi was loaded manually before wmi was
> >>    fully initialized.
> >>
> >> Fix it by moving the call to the probe function where it belongs.
> >>
> >> Fixes: bff589be59c5 ("platform/x86: dell-wmi: Convert to the WMI bus infrastructure")
> >> Signed-off-by: Andy Lutomirski <luto@kernel.org>

> > Hi! You should move also dell_wmi_events_set_enabled() into
> > dell_wmi_probe() as there is no need to enable receiving events prior to
> > creating input device.
> 
> I thought of that and intentionally didn't do it: I wanted to leave
> enable and the disable paired properly, and there's nothing that
> tracks the enabled state per device.  Also, it's at least
> theoretically possible to have more than one instance of dell-wmi in a
> system (my laptop already has *two* wmi busses), and moving this code
> to ->probe would break this.
> 
> (The current wmi.c code can't handle the same GUID on two busses, but
> it could easily be added if anyone ever finds a laptop that does
> that.)
> 

Better still, thanks Andy.

-- 
Darren Hart
VMware Open Source Technology Center

  reply	other threads:[~2017-08-01 19:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 15:37 [PATCH 0/3] Three WMI improvements Andy Lutomirski
2017-08-01 15:37 ` [PATCH 1/3] platform/dell-wmi: Fix driver interface version query Andy Lutomirski
2017-08-01 15:43   ` Pali Rohár
2017-08-01 18:08     ` Andy Lutomirski
2017-08-01 19:54       ` Darren Hart [this message]
2017-08-01 20:45       ` Pali Rohár
2017-08-01 20:59         ` Darren Hart
2017-08-01 21:16           ` Pali Rohár
2017-08-02  2:25             ` Andy Lutomirski
2017-08-02  2:54               ` Darren Hart
2017-08-01 19:52     ` Darren Hart
2017-08-01 20:06   ` Darren Hart
2017-08-01 20:36     ` Pali Rohár
2017-08-01 15:37 ` [PATCH 2/3] platform/dell-wmi: Update dell_wmi_check_descriptor_buffer() to new model Andy Lutomirski
2017-08-01 15:44   ` Pali Rohár
2017-08-19  0:14     ` Darren Hart
2017-08-01 15:37 ` [PATCH 3/3] platform/wmi: Expose the raw WDG data in sysfs Andy Lutomirski
2017-08-01 15:46   ` Pali Rohár
2017-08-01 18:29     ` Andy Lutomirski
2017-08-01 20:03   ` Darren Hart
2017-08-01 20:19     ` Andy Lutomirski
2017-08-01 20:40       ` Pali Rohár
2017-08-01 21:17         ` Darren Hart
2017-08-01 21:20           ` Rafael J. Wysocki
2017-08-01 21:36             ` Pali Rohár
2017-08-01 21:32               ` Rafael J. Wysocki
2017-08-01 22:06                 ` Darren Hart
2017-08-01 21:31           ` Pali Rohár
2017-08-01 22:39             ` Darren Hart
2017-08-01 23:51               ` Andy Lutomirski
2017-08-02  2:22                 ` Darren Hart
2017-08-02  7:49                   ` Pali Rohár
2017-08-04 15:03                     ` Andy Lutomirski
2017-08-06 21:36                       ` Pali Rohár
2017-08-06 22:09                         ` Andy Lutomirski

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=20170801195405.GB3110@fury \
    --to=dvhart@infradead.org \
    --cc=luto@kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=platform-driver-x86@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