X86 platform drivers
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Alex Hung <alex.hung@canonical.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	platform-driver-x86@vger.kernel.org,
	Gabriele Mazzotta <gabriele.mzt@gmail.com>
Subject: Re: New dell-wireless driver
Date: Fri, 21 Nov 2014 18:09:06 -0800	[thread overview]
Message-ID: <20141122020906.GB24951@vmdeb7> (raw)
In-Reply-To: <201411222345.08384@pali>

On Sat, Nov 22, 2014 at 11:45:08PM +0100, Pali Rohár wrote:
> Hello,
> 
> I saw dell-wireless driver on platform-driver-x86 mailinglist [1] 
> which using DELLABCE acpi device and I do not like some parts in 
> this driver.

Hi Pali,

Thanks for reviewing and speaking up :)

> 
> First is that this driver export rfkill event as keypress which 
> is also reported to userspace by keyboard controller. So then 
> userspace receive two rfkill keypresses.

Alex, can you comment? Does the keyboard controller also see this event?

> 
> Second is that DELLABCE acpi device can also control "soft" 
> rfkill status and this driver does not enable it because it use 
> input class instead rfkill.
> 
> Anyway I have unfinished my version of DELLABCE acpi driver which 
> will use rfkill interface and plus allow to use hw switch events 
> in dell-laptop.ko driver.

Is this something that could be applied incrementally fo Alex's driver, or is it
something we'd be best starting over with?

We have some precedent for input drivers (there is one nearly identical to the
dell driver for hp, also by Alex). Using rfkill does seem like the better
approach without digging into it.

> 
> Currently dell-laptop.ko driver is using i8042 hook function for 
> detecting hw switch key press event. It is needed to detect if 
> rfkill state was changed or not.
> 
> My prepared patches for dell-laptop.ko allows to use acpi event 
> from DELLABCE driver, so i8042 hook function can be dropped. 
> Really it is not good idea to pass every PS/2 data from both 
> keyboard, touchpad and trackpoint to dell-laptop driver and if 
> there is alternative (DELLABCE) it is better to use it.
> 
> But now I would like to hear what do you think about it.
> 
> Because only one kernel driver can attach to DELLABCE acpi 
> device, I cannot use new dell-wireless driver. And I think only 
> one driver can hit mainline kernel.

I would like to see your patch, it sounds like it might be a better option.

-- 
Darren Hart
Intel Open Source Technology Center

  reply	other threads:[~2014-11-22 23:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 22:45 New dell-wireless driver Pali Rohár
2014-11-22  2:09 ` Darren Hart [this message]
2014-11-23  0:52   ` Pali Rohár
2014-11-22  3:44     ` Darren Hart
2014-11-23 15:11       ` Pali Rohár
2014-11-27  4:41     ` Alex Hung
2014-12-02 11:06       ` Gabriele Mazzotta
2014-12-02 12:01         ` Pali Rohár
2014-12-02 15:08         ` Gabriele Mazzotta
2014-12-03  8:50           ` Darren Hart
2014-12-04  6:52             ` Alex Hung
2014-12-04  9:57               ` Pali Rohár
2014-11-27  4:27   ` Alex Hung
2014-11-27 11:43     ` Pali Rohár
2014-11-28  5:33       ` Alex Hung

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=20141122020906.GB24951@vmdeb7 \
    --to=dvhart@infradead.org \
    --cc=alex.hung@canonical.com \
    --cc=gabriele.mzt@gmail.com \
    --cc=mjg59@srcf.ucam.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