Re: [PATCH 0/12] PM / sleep: Driver flags for system suspend/resume

2017-10-17 Thread Alan Stern
driver PM > flags"? PM flags won't directly be able to cover things like disabling clocks. But they could be useful for indicating explicitly whether the code to take care of those things needs to reside at the driver layer or at the bus layer. Alan Stern -- To unsubscribe from this lis

Re: [PATCH 01/12] PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags

2017-10-16 Thread Alan Stern
iver flags at > the core level. I'm curious: Why does the PCI bus type (and others) do this? Why doesn't it do what the driver says to do? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 2/3] docs-rst/usb: usb/devices is now at /sys/kernel/debug/

2017-04-16 Thread Alan Stern
> Note that many Linux distributions hard-wire the mount options for usbfs > in their init scripts, such as ``/etc/rc.d/rc.sysinit``, rather than > making it easy to set this per-system policy in ``/etc/fstab``. This is all totally out of date. usbfs is no longer a filesyste

Re: [PATCH 22/22] usb: document that URB transfer_buffer should be aligned

2017-03-31 Thread Alan Stern
On Thu, 30 Mar 2017, Oliver Neukum wrote: > Am Donnerstag, den 30.03.2017, 11:55 -0400 schrieb Alan Stern: > > > > I'm pretty sure that usb-storage does not do this, at least, not when > > operating in its normal Bulk-Only-Transport mode.  It never tries to > > rea

Re: [PATCH 22/22] usb: document that URB transfer_buffer should be aligned

2017-03-30 Thread Alan Stern
On Thu, 30 Mar 2017, Mauro Carvalho Chehab wrote: > Em Thu, 30 Mar 2017 10:26:32 -0400 (EDT) > Alan Stern <st...@rowland.harvard.edu> escreveu: > > > On Thu, 30 Mar 2017, Oliver Neukum wrote: > > > > > > Btw, I'm a lot more concerned about USB storage

Re: [PATCH 22/22] usb: document that URB transfer_buffer should be aligned

2017-03-30 Thread Alan Stern
Mauro wrote "the buffer can be continuous", but that is certainly not what he meant. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

2016-09-03 Thread Alan Stern
is possible to register trigger for many > ports. The patch could be changed to remove that assumption. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

2016-09-03 Thread Alan Stern
g and > presenting multiple USB ports. I'm still in favour of a single > attribute with space separated list. This scheme is commonly used > in existing interfaces. No such interface is needed if you do things the way I outlined above. Each trigger would require the user to specify either one port, one hub, or nothing at all. Multiple ports would not be used. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

2016-09-02 Thread Alan Stern
ger echo hub1-4 >/sys/class/led/foo/trigger echo usb >/sys/class/led/foo/trigger Yes, it would be possible to have a port-specific trigger for one LED and an overall USB activity trigger for another LED. I don't know how useful this would be -- you could probably imagine some

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

2016-08-31 Thread Alan Stern
eply starts with "Anyway, the serious limitation I see"). The code for a bunch of triggers must already be written. What would the user do if he wanted to flash a single LED in response to both CPU activity and MTD activity? If not echo "cpu mtd" >/sys/class/leds/foo/trigger then what? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

2016-08-30 Thread Alan Stern
t; way to achieve the same result? We could think about modifying USB > core to call some symbol from the trigger driver (see usage of > ledtrig_mtd_activity symbol) but is it any better than using > notification block? I don't think this is such a bad use of the USB notifier. All you ne

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-25 Thread Alan Stern
On Thu, 25 Aug 2016, Alan Stern wrote: > > Does the lsusb command do the mapping in the user space or maybe > > it takes the names from kernel? > > lsusb does the mapping in userspace, based on an ID database. On my > system (Fedora), the database is /etc/udev/hwdb.bi

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-25 Thread Alan Stern
> should it appear? > > > > Product name/symbol. Actually it should be USB subsystem responsibility > to provide the means for querying the product name by port id, if it > is possible at all. cat /sys/bus/usb/devices/PORT/product cat /sys/bus/usb/devices/PORT/