All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Simon Wood <simon@mungewell.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ivan Baldo <ibaldo@adinet.com.uy>, evilcow <evilcow93@yahoo.com>
Subject: Re: [PATCH] HID: hid-lg4ff: Support new version of G27
Date: Fri, 14 Mar 2014 15:44:42 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.00.1403141544350.3690@pobox.suse.cz> (raw)
In-Reply-To: <1394736123-2102-1-git-send-email-simon@mungewell.org>

On Thu, 13 Mar 2014, Simon Wood wrote:

> It has been reported that there is a new hardware version of the G27
> in the 'wild'. This patch add's this new revision so that it can be
> sent the command to switch to native mode.
> 
> Reported-by: "Ivan Baldo" <ibaldo@adinet.com.uy>
> Tested-by: "evilcow" <evilcow93@yahoo.com>
> Signed-off-by: Simon Wood <simon@mungewell.org>
> ---
>  drivers/hid/hid-lg4ff.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/hid/hid-lg4ff.c b/drivers/hid/hid-lg4ff.c
> index befe0e3..24883b4 100644
> --- a/drivers/hid/hid-lg4ff.c
> +++ b/drivers/hid/hid-lg4ff.c
> @@ -43,6 +43,7 @@
>  #define G25_REV_MIN 0x22
>  #define G27_REV_MAJ 0x12
>  #define G27_REV_MIN 0x38
> +#define G27_2_REV_MIN 0x39
>  
>  #define to_hid_device(pdev) container_of(pdev, struct hid_device, dev)
>  
> @@ -130,6 +131,7 @@ static const struct lg4ff_usb_revision lg4ff_revs[] = {
>  	{DFP_REV_MAJ,  DFP_REV_MIN,  &native_dfp},	/* Driving Force Pro */
>  	{G25_REV_MAJ,  G25_REV_MIN,  &native_g25},	/* G25 */
>  	{G27_REV_MAJ,  G27_REV_MIN,  &native_g27},	/* G27 */
> +	{G27_REV_MAJ,  G27_2_REV_MIN,  &native_g27},	/* G27 v2 */
>  };

Applied, thanks.

-- 
Jiri Kosina
SUSE Labs

      reply	other threads:[~2014-03-14 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 18:42 [PATCH] HID: hid-lg4ff: Support new version of G27 Simon Wood
2014-03-14 14:44 ` Jiri Kosina [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=alpine.LNX.2.00.1403141544350.3690@pobox.suse.cz \
    --to=jkosina@suse.cz \
    --cc=evilcow93@yahoo.com \
    --cc=ibaldo@adinet.com.uy \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon@mungewell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.