On Tue, 8 Dec 2015, Josh Triplett wrote:
> On Tue, Dec 08, 2015 at 11:04:00AM -0500, Alan Stern wrote:
> > On Mon, 7 Dec 2015, Josh Triplett wrote:
> >
> > > > You're looking at the wrong files. The files to monitor are the ones
> > > > in /sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.1/2-3.
On Tue, Dec 08, 2015 at 11:04:00AM -0500, Alan Stern wrote:
> On Mon, 7 Dec 2015, Josh Triplett wrote:
>
> > > You're looking at the wrong files. The files to monitor are the ones
> > > in /sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.1/2-3.1.2/power
> > > (assuming that this device really is
On Mon, 7 Dec 2015, Josh Triplett wrote:
> > You're looking at the wrong files. The files to monitor are the ones
> > in /sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.1/2-3.1.2/power
> > (assuming that this device really is the mouse and not something else).
> > Handy shortcut link: /sys/bu
On Mon, Dec 07, 2015 at 05:02:34PM -0500, Alan Stern wrote:
> On Mon, 7 Dec 2015, Josh Triplett wrote:
>
> > The following files appear under the power directory when plugged in via
> > the dock:
> >
> > ~$ head
> > /sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.1/2-3.1.2/2-3.1.2:1.1/power/*
On Mon, Dec 07, 2015 at 03:45:23PM -0600, Felipe Balbi wrote:
>
> Hi,
>
> Josh Triplett writes:
> > On Mon, Dec 07, 2015 at 03:03:40PM -0600, Felipe Balbi wrote:
> >> Josh Triplett writes:
> >> >> > Looking at the sysfs path for the input device as shown in dmesg,
> >> >> > /sys/devices/pci
On Mon, 7 Dec 2015, Felipe Balbi wrote:
> if those are not enabled, then the device doesn't have pm_runtime
> callbacks, see:
>
> int dpm_sysfs_add(struct device *dev)
> {
> int rc;
>
> rc = sysfs_create_group(&dev->kobj, &pm_attr_group);
> if (rc)
> return rc;
>
On Mon, 7 Dec 2015, Josh Triplett wrote:
> The following files appear under the power directory when plugged in via
> the dock:
>
> ~$ head
> /sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.1/2-3.1.2/2-3.1.2:1.1/power/*
> ==>
> /sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.1/2-3.1.2/2-3.1
Hi,
Josh Triplett writes:
> On Mon, Dec 07, 2015 at 03:03:40PM -0600, Felipe Balbi wrote:
>> Josh Triplett writes:
>> >> > Looking at the sysfs path for the input device as shown in dmesg,
>> >> > /sys/devices/pci\:00/\:00\:14.0/usb2/2-3/2-3.1/2-3.1.2/2-3.1.2\:1.1/supports_autosuspend
>
On Mon, Dec 07, 2015 at 03:03:40PM -0600, Felipe Balbi wrote:
> Josh Triplett writes:
> >> > Looking at the sysfs path for the input device as shown in dmesg,
> >> > /sys/devices/pci\:00/\:00\:14.0/usb2/2-3/2-3.1/2-3.1.2/2-3.1.2\:1.1/supports_autosuspend
> >> > did say "1". However, the d
Hi,
Josh Triplett writes:
>> > Looking at the sysfs path for the input device as shown in dmesg,
>> > /sys/devices/pci\:00/\:00\:14.0/usb2/2-3/2-3.1/2-3.1.2/2-3.1.2\:1.1/supports_autosuspend
>> > did say "1". However, the device didn't actually appear to have
>> > autosuspend *enabled*.
On Mon, Dec 07, 2015 at 02:29:39PM -0600, Felipe Balbi wrote:
>
> Hi,
>
> Josh Triplett writes:
> > I have a USB Lenovo ThinkPad Keyboard with TrackPoint (vendor:product
> > 17ef:6009), and a ThinkPad Yoga 12 (Broadwell version) with OneLink Pro
> > dock. If I plug the keyboard/mouse directly in
Hi,
Josh Triplett writes:
> I have a USB Lenovo ThinkPad Keyboard with TrackPoint (vendor:product
> 17ef:6009), and a ThinkPad Yoga 12 (Broadwell version) with OneLink Pro
> dock. If I plug the keyboard/mouse directly into the laptop,
> it works fine. If I plug it into the dock, the keyboard wor
12 matches
Mail list logo
