Linux Input/HID development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Juan Parrado" <jparrado.1817@gmail.com>, linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com
Subject: Re: [PATCH v2] [PATCH v2] xpad.c: Add support to Hori Real Arcade Pro 4
Date: Mon, 09 Nov 2026 10:43:34 +0000	[thread overview]
Message-ID: <sashiko-outbox-204846@kernel.org> (raw)
In-Reply-To: <20261109103715.11017-1-jparrado1817@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Medium] Input: xpad - missing MAP_TRIGGERS_TO_BUTTONS for Hori Real
  Arcade Pro 4
- [Low] Input: xpad - Author/Signed-off-by email mismatch and changelog
  issues
--

commit ae6f93fb0a7ea08dae09b3962836f14f01d5f458
Author: Juan Parrado <jparrado.1817@gmail.com>

> xpad.c: Add support to Hori Real Arcade Pro 4
>
> Add specific support to Hori Real Arcade Pro 4.
>
> v2 fixed format
>
> Signed-off-by: Juan Parrado <jparrado1817@gmail.com>

[Severity: Low]
The Author address (jparrado.1817@gmail.com) does not match the
Signed-off-by address (jparrado1817@gmail.com), and the "v2 fixed format"
revision note should be placed below the "---" separator rather than in the
commit log.

Also, the commit subject should use the "Input: xpad - ..." prefix, and the
changelog should explain why an explicit xpad_device[] entry is needed when
vendor 0x0f0d is already matched by XPAD_XBOX360_VENDOR(0x0f0d) in
xpad_table[].

> diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
> index 810e52782ae89..2567ea3bd2604 100644
> --- a/drivers/input/joystick/xpad.c
> +++ b/drivers/input/joystick/xpad.c
> @@ -255,6 +255,7 @@ static const struct xpad_device {
>  	{ 0x0f0d, 0x0063, "Hori Real Arcade Pro Hayabusa (USA) Xbox One", MAP_TRIGGERS_TO_BUTTONS, XTYPE_XBOXONE },
>  	{ 0x0f0d, 0x0067, "HORIPAD ONE", 0, XTYPE_XBOXONE },
>  	{ 0x0f0d, 0x0078, "Hori Real Arcade Pro V Kai Xbox One", MAP_TRIGGERS_TO_BUTTONS, XTYPE_XBOXONE },
> +	{ 0x0f0d, 0x008c, "Real Arcade Pro 4", 0, XTYPE_XBOX360 },
>  	{ 0x0f0d, 0x00c5, "Hori Fighting Commander ONE", MAP_TRIGGERS_TO_BUTTONS, XTYPE_XBOXONE },
>  	{ 0x0f0d, 0x00dc, "HORIPAD FPS for Nintendo Switch", MAP_TRIGGERS_TO_BUTTONS, XTYPE_XBOX360 },
>  	{ 0x0f0d, 0x0151, "Hori Racing Wheel Overdrive for Xbox Series X", 0, XTYPE_XBOXONE },

[Severity: Medium]
Should this entry set MAP_TRIGGERS_TO_BUTTONS instead of 0?

The Hori Real Arcade Pro 4 is an arcade fightstick with digital pushbuttons
for L2/R2 rather than analog triggers, and the other Hori Real Arcade Pro
entries in xpad_device[] set MAP_TRIGGERS_TO_BUTTONS so LT/RT are reported
as BTN_TL2/BTN_TR2 instead of ABS_Z/ABS_RZ.  Previously, 0x0f0d:0x008c bound
via XPAD_XBOX360_VENDOR(0x0f0d) with XTYPE_UNKNOWN, where xpad_probe()
auto-detected XTYPE_XBOX360 and still honored the triggers_to_buttons module
parameter; adding an explicit XTYPE_XBOX360 entry with mapping 0 bypasses
that XTYPE_UNKNOWN fallback in xpad_probe() and prevents overriding the
trigger mapping via module parameters.

Also, all surrounding 0x0f0d entries in xpad_device[] include the "Hori "
vendor prefix in the device name string ("Hori Real Arcade Pro 4").

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261109103715.11017-1-jparrado1817@gmail.com?part=1

  reply	other threads:[~2026-11-09 10:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 22:02 [PATCH] xpad.c: Add support to Hori Real Arcade Pro 4 Juan Parrado García
2026-11-09 10:37 ` [PATCH v2] [PATCH v2] " Juan Parrado
2026-11-09 10:43   ` sashiko-bot [this message]
2026-11-09 19:41     ` [PATCH v3] [PATCH v3] xpad.c - " Juan Parrado
2026-11-09 19:58     ` Juan Parrado
2026-11-11 19:49       ` Dmitry Torokhov

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=sashiko-outbox-204846@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jparrado.1817@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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