Bug 1090555
Summary: | Disable HID Battery reporting for Broadcom HID/HCI device | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bastien Nocera <bnocera> | ||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 20 | CC: | bnocera, btissoir, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab | ||||||
Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2014-12-10 15:03:23 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Bastien Nocera
2014-04-23 15:06:25 UTC
What does "...fail after a while" mean? Does it report valid values after a fresh boot and then they aren't updated after that? Created attachment 889001 [details] 0001-HID-input-disable-battery-for-0A5C-4502.patch Adding a proposed patch to fix the issue: taking the hammer, and disabling the battery property :) I just scheduled a test build here, any feedback appreciated so I can also send this upstream: http://koji.fedoraproject.org/koji/taskinfo?taskID=6770010 (In reply to Josh Boyer from comment #1) > What does "...fail after a while" mean? That it times out. It usually takes longer than those 5 seconds. > Does it report valid values after a > fresh boot and then they aren't updated after that? Never does, even using the provided keyboard. The power supply class still shows up with the new kernel: $ ls -l /sys/class/power_supply/ total 0 0 lrwxrwxrwx. 1 root root 0 Apr 24 11:04 hid--battery -> ../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.0/0003:0A5C:4502.0004/power_supply/hid--battery $ uname -r 3.14.1-200.bz1090555.fc20.x86_64 #define USB_VENDOR_ID_BROADCOM 0x046e That should probably read 0x0a5c? Created attachment 889340 [details] 0001-HID-input-disable-battery-for-0A5C-4502.patch V2 Sorry for the typo in the patch. New patch and new build here: http://koji.fedoraproject.org/koji/taskinfo?taskID=6775015 Bizarrely, it's not working and the battery still shows up: $ uname -r 3.14.1-200.bz1090555.1.fc20.x86_64 $ ls -l /sys/class/power_supply/ total 0 lrwxrwxrwx. 1 root root 0 Apr 24 21:04 hid--battery -> ../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/0003:0A5C:4503.0005/power_supply/hid--battery *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. It's obviously not been resolved. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those. This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |