public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Darren Hart <dvhart@infradead.org>
Cc: Alex Hung <alex.hung@canonical.com>,
	Corentin Chary <corentin.chary@gmail.com>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	acpi4asus-user@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v2] asus-rbtn: new driver for asus radio button for Windows 8
Date: Tue, 7 Jul 2015 16:25:18 +0200	[thread overview]
Message-ID: <20150707142518.GI12087@pali> (raw)
In-Reply-To: <20150706224328.GB111639@vmdeb7>

On Monday 06 July 2015 15:43:28 Darren Hart wrote:
> On Mon, Jul 06, 2015 at 09:35:40AM +0800, Alex Hung wrote:
> > ATK4001 is an ACPI device for wireless hotkey, similar to how Dell and
> > HP are doing it.  It is just ASUS who decides LED should be controlled
> > by software unlike HP whose LED is driven by hardware pins on mini
> > card.
> 
> Alex, please refrain from top posting on Linux kernel mailing lists, it breaks
> the established practice the readers are setup for.
> 
> Regarding the ATK4001 device, it did sound like it did more than control the
> radios and the associcated LED. If that is all it does, then asus-rbtn is fine.
> If it does something beyond that, we need understand what that is, as a more
> platform-centric name would be more appropriate.
> 
> Thanks,

Yes, I understand too that ATK4001 device has more functions as one for
LED control. And in this case it is not good to use name from one
specific functionality.

And about name:

I chose name rbtn for dell driver because ACPI device in DSDT table is
named RBTN and acpi id is DELRBTN.

I think that acpi-rbtn.c (radio button) is not ideal name for driver
which at SW level controls LED device associated with wireless devices.

I would rather follow acpi device name, but in this case ATK4001 is even
worse name which does not say anything...

Maybe better name could be asus-wireless? Still I do not have any good
name, so choose something...

-- 
Pali Rohár
pali.rohar@gmail.com

  reply	other threads:[~2015-07-07 14:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  2:57 [PATCH][v2] asus-rbtn: new driver for asus radio button for Windows 8 Alex Hung
2015-06-25  4:04 ` Darren Hart
2015-06-25  6:58 ` Paul Bolle
2015-06-25 20:00   ` Darren Hart
2015-06-26 14:56 ` Pali Rohár
2015-06-26 15:24   ` Alex Hung
2015-06-29 12:29     ` Pali Rohár
2015-06-30  8:38       ` Alex Hung
2015-06-30  8:58         ` Pali Rohár
2015-06-30 16:09           ` Alex Hung
2015-06-30 17:04             ` Pali Rohár
2015-07-01 11:48             ` Pali Rohár
2015-07-02  7:10               ` Alex Hung
2015-07-03  7:25                 ` Pali Rohár
2015-07-06  1:35                   ` Alex Hung
2015-07-06 22:43                     ` Darren Hart
2015-07-07 14:25                       ` Pali Rohár [this message]
2015-07-09 20:52                         ` Darren Hart
2015-07-10  1:52                           ` Alex Hung
2015-07-12 13:02                             ` Corentin Chary
2015-06-30 16:17       ` Darren Hart

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=20150707142518.GI12087@pali \
    --to=pali.rohar@gmail.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=alex.hung@canonical.com \
    --cc=corentin.chary@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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