linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH v2 0/6] HID: Misc. fixes
Date: Wed, 26 May 2021 12:46:39 +0200	[thread overview]
Message-ID: <72853307-3e7a-a98e-8870-0c7d74506e65@redhat.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2105261238110.28378@cbobk.fhfr.pm>

Hi,

On 5/26/21 12:38 PM, Jiri Kosina wrote:
> On Wed, 5 May 2021, Hans de Goede wrote:
> 
>> Hi Jiri, Benjamin,
>>
>> Here is v2 of what started out as a small series to fix spurious wakeups
>> on T101HA 2-in-1s.
>>
>> This adds the discussed hid_is_usb_device() helper and uses that in:
>>
>> "HID: multitouch: Disable event reporting on suspend when our parent is
>> not a wakeup-source"
>>
>> To avoid needing to add a "depends on USB_HID" to hid-multitouch Kconfig
>> settings.
>>
>> I've checked all other hid_is_using_ll_driver(hdev, &usb_hid_driver) callers
>> and the only one which can truely benefit from the new helper is the
>> hid-asus driver, which also deals with some I2C devices on some Asus hw.
>>
>> All other drivers using hid_is_using_ll_driver(hdev, &usb_hid_driver)
>> are only for USB devices, so dropping the "depends on USB_HID" does not
>> make sense for them.
>>
>> The one other driver which may benefit from the new hid_is_usb_device()
>> helper would be the Wacom driver which seems to also support I2C devices,
>> but that contains a lot of USB specific code, so I don't think we can
>> easily drop the "depends on USB_HID" there.
>>
>> Even though this is a bit if a mixed-bag of patches, their are several
>> dependencies between them, so these should probably all go on a single
>> topic branch.
> 
> Now in for-5.13/upstream-fixes. Thanks,

Thank you, it seems that in the process of dropping the patches which
you had already merged from v1 of this series; and replacing them with v2,
you completely dropped:

[PATCH v2 5/6] HID: asus: Cleanup Asus T101HA keyboard-dock handling

(which was also in v1) at least I cannot find this in either one of:

https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/log/drivers/hid/hid-asus.c?h=for-next
https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/log/drivers/hid/hid-asus.c?h=for-5.13/upstream-fixes

Regards,

Hans


  reply	other threads:[~2021-05-26 10:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 21:39 [PATCH v2 0/6] HID: Misc. fixes Hans de Goede
2021-05-05 21:39 ` [PATCH v2 1/6] HID: core: Remove extraneous empty line before EXPORT_SYMBOL_GPL(hid_check_keys_pressed) Hans de Goede
2021-05-05 21:39 ` [PATCH v2 2/6] HID: core: Add a hid_is_usb_device() helper function Hans de Goede
2021-05-05 21:39 ` [PATCH v2 3/6] HID: multitouch: Disable event reporting on suspend on the Asus T101HA touchpad Hans de Goede
2021-05-05 21:39 ` [PATCH v2 4/6] HID: multitouch: Disable event reporting on suspend when our parent is not a wakeup-source Hans de Goede
2021-05-05 21:39 ` [PATCH v2 5/6] HID: asus: Cleanup Asus T101HA keyboard-dock handling Hans de Goede
2021-05-05 21:39 ` [PATCH v2 6/6] HID: asus: Switch to the new hid_is_usb_device() helper Hans de Goede
2021-05-26 10:38 ` [PATCH v2 0/6] HID: Misc. fixes Jiri Kosina
2021-05-26 10:46   ` Hans de Goede [this message]
2021-05-26 11:06     ` Jiri Kosina

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=72853307-3e7a-a98e-8870-0c7d74506e65@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).