From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-kernel@vger.kernel.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [BISECTED] (?) since 3.16: USB video cam of an HP Pavilion dv7 laptop not working
Date: Mon, 08 Sep 2014 17:17:05 +0200 [thread overview]
Message-ID: <540DC871.7040901@web.de> (raw)
Since 3.16 the builtin USB video cam of an HP Pavilion dv7 laptop shows only a
black screen with the application guvcview although the video LED is turned on.
There is no hint in dmesg. Also the output of guvcview shows no conspicuousness.
With kernel version 3.15.9 the camera works.
I tried to bisect between good v3.15 and bad v3.16, which identified
commit 9262c19d14c433a6a1ba25c3ff897cb89e412309
Author: Dan Williams <dan.j.williams@intel.com>
Date: Tue May 20 18:08:12 2014 -0700
usb: disable port power control if not supported in wHubCharacteristics
A hub indicates whether it supports per-port power control via the
wHubCharacteristics field in its descriptor. If it is not supported
a hub will still emulate ClearPortPower(PORT_POWER) requests by
stopping the link state machine. However, since this does not save
power do not bother suspending.
This also consolidates support checks into a
hub_is_port_power_switchable() helper.
Acked-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
In the bad bisection steps the video device even was not found. Therefore, I'm
not sure if I identified the right culprit.
Thanks for any help,
Jörg-Volker.
next reply other threads:[~2014-09-08 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 15:17 Jörg-Volker Peetz [this message]
2014-09-09 11:36 ` [BISECTED] (?) since 3.16: USB video cam of an HP Pavilion dv7 laptop not working Jörg-Volker Peetz
2014-10-01 20:51 ` Dominik Kopp
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=540DC871.7040901@web.de \
--to=jvpeetz@web.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@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).