From: sashiko-bot@kernel.org
To: "Mikhail Gavrilov" <mikhail.v.gavrilov@gmail.com>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH v9 1/8] HID: topping: transport for the M62's vendor controls
Date: Sun, 18 Oct 2026 13:13:03 +0000 [thread overview]
Message-ID: <sashiko-outbox-176149@kernel.org> (raw)
In-Reply-To: <20261018124838.129349-2-mikhail.v.gavrilov@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] HID: topping: missing pm_ptr() on topping_driver PM callbacks
--
commit cefe32a6b81c6b7ed6128d273a5c5c6a50f7896a
Author: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
HID: topping: transport for the M62's vendor controls
This commit adds a HID transport driver for the Topping M62 USB audio
interface's vendor control protocol, connecting to snd-usb-audio via the
component framework.
> diff --git a/drivers/hid/hid-topping.c b/drivers/hid/hid-topping.c
> new file mode 100644
> index 0000000000000..a8854b2d15306
> --- /dev/null
> +++ b/drivers/hid/hid-topping.c
> @@ -0,0 +1,498 @@
[ ... ]
> +static struct hid_driver topping_driver = {
> + .name = "topping",
> + .id_table = topping_devices,
> + .probe = topping_probe,
> + .remove = topping_remove,
> + .raw_event = topping_raw_event,
> + .suspend = topping_suspend,
> + .resume = topping_resume,
> + .reset_resume = topping_resume,
> +};
> +module_hid_driver(topping_driver);
[Severity: Low]
In drivers/hid/hid-core.c, hid_driver_suspend(), hid_driver_resume(), and
hid_driver_reset_resume() are only built when CONFIG_PM is enabled:
drivers/hid/hid-core.c:
#ifdef CONFIG_PM
int hid_driver_suspend(struct hid_device *hdev, pm_message_t state)
{
if (hdev->driver && hdev->driver->suspend)
return hdev->driver->suspend(hdev, state);
return 0;
}
Should .suspend, .resume, and .reset_resume in topping_driver be wrapped
with pm_ptr() so that topping_suspend() and topping_resume() can be
eliminated by the compiler when CONFIG_PM is disabled?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261018124838.129349-1-mikhail.v.gavrilov@gmail.com?part=1
next prev parent reply other threads:[~2026-10-18 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 12:48 [PATCH v9 0/8] the Topping M62's and E2x2 OTG's vendor controls, on the component framework Mikhail Gavrilov
2026-10-18 12:48 ` [PATCH v9 1/8] HID: topping: transport for the M62's vendor controls Mikhail Gavrilov
2026-10-18 13:13 ` sashiko-bot [this message]
2026-10-18 12:48 ` [PATCH v9 2/8] ALSA: usb-audio: add the Topping " Mikhail Gavrilov
2026-10-18 12:48 ` [PATCH v9 3/8] HID: topping: add the E2x2 OTG Mikhail Gavrilov
2026-10-18 12:48 ` [PATCH v9 4/8] ALSA: usb-audio: add the Topping E2x2 OTG's vendor controls Mikhail Gavrilov
2026-10-18 12:48 ` [PATCH v9 5/8] HID: topping: report the M62's battery level Mikhail Gavrilov
2026-10-18 13:10 ` sashiko-bot
2026-10-18 12:48 ` [PATCH v9 6/8] ALSA: usb-audio: add the Topping M62's port power settings Mikhail Gavrilov
2026-10-18 12:48 ` [PATCH v9 7/8] ALSA: usb-audio: add the Topping M62's mutes Mikhail Gavrilov
2026-10-18 12:48 ` [PATCH v9 8/8] ALSA: usb-audio: add the Topping E2x2 OTG's input mutes Mikhail Gavrilov
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-176149@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--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