public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Daniel Drake <drake@endlessm.com>
Cc: Chris Chiu <chiu@endlessm.com>, Jiri Kosina <jikos@kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org,
	Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: [PATCH] HID: add Asus macrokey support for Asus "Republic of Gamers" laptop
Date: Wed, 1 Feb 2017 09:18:52 +0100	[thread overview]
Message-ID: <20170201081852.GA31658@mail.corp.redhat.com> (raw)
In-Reply-To: <CAD8Lp46eSzFTEF2VbOHESBHRPOQ0UWO34-DNQYkkwWNKT9kf9g@mail.gmail.com>

On Jan 31 2017 or thereabouts, Daniel Drake wrote:
> Hi Benjamin,
> 
> On Tue, Dec 13, 2016 at 2:16 AM, Benjamin Tissoires
> <benjamin.tissoires@redhat.com> wrote:
> > On Dec 12 2016 or thereabouts, Chris Chiu wrote:
> >> ROG means ASUS "Republic of Gamers" laptops. The input device info
> >> also represents itself as "ASASTeK COMPUTER INC. ROG MacroKey". It
> >> uses special HID_USAGE code for function keys. This commit remap the
> >> special code to standard keycode for function keys handling. It's
> >> verified on GL553VD/VE, GL753VD/VE.
> >>
> >> Signed-off-by: Chris Chiu <chiu@endlessm.com>
> >> Reported-by: Yukai Li <yukaili@gmail.com>
> >> ---
> >
> > Hi Chris,
> >
> > there is no real point of having a separate driver from hid-asus. The
> > HID tree prefer to group drivers by vendors, so these keyboards should
> > be supported through hid-asus.
> 
> Thanks for the feedback. We will submit a new version soon.
> 
> Just to confirm, hid-asus currently depends on I2C_HID. The new
> devices being quirked now are USB devices. With this patch should we
> now update it to depend on I2C_HID && USB_HID?
> 

Actually you can remove the I2C_HID dependency entirely (and not add one
for USB_HID). In the Kconfig, the modules are already guarded by a
"if HID", and there is nothing transport specific in hid-asus as far as
I can tell.

Note: we should also probably clean up the Kconfig once again and remove
all the "depends on HID" for those that are guarded by the if statement.

Cheers,
Benjamin

  reply	other threads:[~2017-02-01  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 12:42 [PATCH] HID: add Asus macrokey support for Asus "Republic of Gamers" laptop Chris Chiu
2016-12-13  8:16 ` Benjamin Tissoires
2017-01-31 19:42   ` Daniel Drake
2017-02-01  8:18     ` Benjamin Tissoires [this message]
2016-12-14 10:20 ` Jiri Kosina
2016-12-14 16:50   ` Chris Chiu

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=20170201081852.GA31658@mail.corp.redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=chiu@endlessm.com \
    --cc=drake@endlessm.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@endlessm.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