OSR's ntdev List: Issue with IOCTL_HID_SEND_IDLE_NOTIFICATION

Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:

Creating the right design for your requirements
Reviewing your existing driver code
Analyzing driver reliability/performance issues
Custom training mixed with consulting and focused directly on your specific areas of interest/concern.

Check us out. OSR, the Windows driver experts.

Monthly Seminars at OSR Headquarters

East Coast USA
Windows Internals and SW Drivers, Dulles (Sterling) VA, 13 November 2017

Kernel Debugging & Crash Analysis for Windows, Nashua (Amherst) NH, 4 December 2017

Writing WDF Drivers I: Core Concepts, Nashua (Amherst) NH, 8 January 2018

WDF Drivers II: Advanced Implementation Techniques, Nashua (Amherst) NH, 15 January 2018

		OSR Online Lists > ntdev
Issue with IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST

Welcome, Guest
You must login to post to this list

Message 1 of 3

15 Jun 17 01:08

praveen nair

xxxxxx@yahoo.com

Join Date: 29 Aug 2006

Posts To This List: 9

Issue with IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST

Hi, Our company is into developing USB keyboards with custom functionality. We have HID Mini drivers with usage tables for custom usages. In one of the keyboards, we are getting IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST message and after this application is not detecting our HID device or sending any HID commands. The same driver is working fine with another model. Application is from another vendor, in which we don't have much control or access to source code. Our driver is based on the hidusbfx2 sample in WDK. I am not sure anything different need to be done in this IOCTL handler or in any of the power management routines. Any pointers to address this issue will be of great help. thanks Praveen

Message 2 of 3

15 Jun 17 01:15

Doron Holan

xxxxxx@microsoft.com

Join Date: 08 Sep 2005

Posts To This List: 10090

Issue with IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST

<msdn> The IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST control code is the IOCTL of t= he idle notification request IRP that HIDClass sends to HID mini drivers, s= uch as HIDUSB, to inform the bus driver that the device is now idle. </> HIDclass will power down the device and expects that you arm the device for= wake such that it can wake itself up when used. If you don't want to idle = out, don't report wakecapable. I think you must also not set a reg key in d= evice parameters, but I am not sure. I have to wonder though why you need a custom miniport. The in box miniport= fully supports custom usages and custom usage pages. The HID spec fully al= lows for it.=20 d -----Original Message----- From: xxxxx@lists.osr.com [mailto:bounce-632990-26293@lists.o= sr.com] On Behalf Of xxxxx@yahoo.com Sent: Wednesday, June 14, 2017 10:08 PM To: Windows System Software Devs Interest List <xxxxx@lists.osr.com> Subject: [ntdev] Issue with IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST Hi, Our company is into developing USB keyboards with custom functionality. We = have HID Mini drivers with usage tables for custom usages. In one of the ke= yboards, we are getting IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST message an= d after this application is not detecting our HID device or sending any HID= commands. The same driver is working fine with another model. Application = is from another vendor, in which we don't have much control or access to so= urce code. Our driver is based on the hidusbfx2 sample in WDK. I am not sure anything different need to be done in this IOCTL handler or i= n any of the power management routines. Any pointers to address this issue = will be of great help. thanks Praveen=20 --- NTDEV is sponsored by OSR Visit the list online at: <https://na01.safelinks.protection.outlook.com/?u= rl=3Dhttp%3A%2F%2Fwww.osronline.com%2Fshowlists.cfm%3Flist%3Dntdev&data=3D0= 2%7C01%7CDoron.Holan%40microsoft.com%7Cdc9ee1a924de43f0475208d4b3ac8a43%7C7= 2f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636331001016513626&sdata=3D0cycIc= s2W8HPI3qBkPXkOoPZWCnMkFIv5L2CCc17ed4%3D&reserved=3D0> MONTHLY seminars on crash dump analysis, WDF, Windows internals and softwar= e drivers! Details at <https://na01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F= %2Fwww.osr.com%2Fseminars&data=3D02%7C01%7CDoron.Holan%40microsoft.com%7Cdc= 9ee1a924de43f0475208d4b3ac8a43%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7= C636331001016513626&sdata=3DWfPeFLxbuv6qIJR8nqX3HsfAeFK1iY1OrTaUZKuGWsQ%3D&= reserved=3D0> To unsubscribe, visit the List Server section of OSR Online at <https://na0= 1.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fwww.osronline.com%2F= page.cfm%3Fname%3DListServer&data=3D02%7C01%7CDoron.Holan%40microsoft.com%7= Cdc9ee1a924de43f0475208d4b3ac8a43%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C= 0%7C636331001016513626&sdata=3DUNm1c5fApCct7LakpQ5PrbwsJDQcglxWszOyvcM72qs%= 3D&reserved=3D0>

Message 3 of 3

15 Jun 17 08:09

praveen nair

xxxxxx@yahoo.com

Join Date: 29 Aug 2006

Posts To This List: 9

Issue with IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST

HI Doron, Thank you for the reply. I have set EnhancedPowerManagementEnabled=0 and IOCTL_HID_SEND_IDLE_NOTIFICATION_REQUEST has stopped coming to my driver. But there is not much deference in the app behavior. It is not recognizing the usage reported by my mini driver in one of the device models. Only difference i can see in the HW is, Remote Wakeup is set in the Configuration descriptor of the working device, where as this is not set in the other. Not sure whether this can affect the app behavior though. I think the reason for using HID Mini driver is to minimize the changes in the HW/firmware, and use same HW with different usages exposed through the mini driver. thanks Praveen

Posting Rules
You may not post new threads You may not post replies You may not post attachments	You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 02:32.

Contact Us - Osr Online Homepage - Top