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

On Mon 2016-08-29 10:21:48, Rafał Miłecki wrote: > On 29 August 2016 at 10:05, Pavel Machek <pa...@ucw.cz> wrote: > >> >2) Having "ports" subdir with RW files, one per each existing physical > >> >port > >> >In this situation we don't

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

Hi! > This commit adds a new trigger responsible for turning on LED when USB > device gets connected to the specified USB port. This can can useful for > various home routers that have USB port(s) and a proper LED telling user > a device is connected. > > The trigger gets its documentation file

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

On Wed 2016-08-31 14:23:13, Alan Stern wrote: > On Tue, 30 Aug 2016, Rafał Miłecki wrote: > > > >> As you quite often need more complex LED management, there are > > >> triggers that were introduced in 2006 by c3bc9956ec52f ("[PATCH] LED: > > >> add LED trigger tupport"). Some triggers are

Re: [BUG 4.9] New led trigger usbport gets the kernel to panic

On Fri 2016-12-02 09:48:18, Ralph Sennhauser wrote: > On Thu, 1 Dec 2016 17:56:07 +0100 > Rafał Miłecki wrote: > > > On 12/01/2016 03:28 PM, Ralph Sennhauser wrote: > > > Below the oops with your debug patch applied. > > > > > > (...) > > > > > > root@wrt1900acs:/# cd

Re: v4.10-rc8 (-rc6) boot regression on Intel desktop, does not boot after cold boots, boots after reboot

> > > > > ...1d.7: PCI fixup... pass 2 > > > > > ...1d.7: PCI fixup... pass 3 > > > > > ...1d.7: PCI fixup... pass 3 done > > > > > > > > > > ...followed by hang. So yes, it looks USB related. > > > > > > > > > > (Sometimes it hangs with some kind backtrace involving secondary CPU > > > > >

Re: v4.10-rc8 (-rc6) boot regression on Intel desktop, does not boot after cold boots, boots after reboot

On Wed 2017-04-12 17:08:35, Frederic Weisbecker wrote: > On Mon, Apr 03, 2017 at 08:20:50PM +0200, Pavel Machek wrote: > > > > > > > ...1d.7: PCI fixup... pass 2 > > > > > > > ...1d.7: PCI fixup... pass 3 > > > > > > > ...1d.7:

v4.13-rc2: usb mouse stopped working?

Hi! On thinkpad x220, USB mouse stopped working in v4.13-rc2. v4.12 was ok, iirc. Now, USB mouse is so common hw that I may have something wrong in my config...? But I did not change anything there. In v4.9: [ 87.064408] input: Logitech USB Optical Mouse as

Re: v4.13-rc2: usb mouse stopped working?

Hi! > > On thinkpad x220, USB mouse stopped working in v4.13-rc2. v4.12 was > > ok, iirc. > > > > Now, USB mouse is so common hw that I may have something wrong in my > > config...? But I did not change anything there. > > Well, your particular USB mouse requires an always-poll quirk, so it's

Re: v4.13-rc2: usb mouse stopped working?

Hi! > > In v4.9: > > > > [ 87.064408] input: Logitech USB Optical Mouse as > > /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1.1/2-1.1.1.1:1.0/0003:046D:C05A.0005/input/input18 > > [ 87.065951] hid-generic 0003:046D:C05A.0005: input,hidraw0: USB HID > > v1.11 Mouse [Logitech

Re: [PATCH v2] USB: add SPDX identifiers to all remaining files in drivers/usb/

On Thu 2017-11-09 11:40:28, Greg Kroah-Hartman wrote: > On Thu, Nov 09, 2017 at 10:51:48AM +0100, Pavel Machek wrote: > > Hi! > > > > > It's good to have SPDX identifiers in all files to make it easier to > > > audit the kernel tree for correct licenses. &g

Re: [PATCH v2] USB: add SPDX identifiers to all remaining files in drivers/usb/

Hi! > It's good to have SPDX identifiers in all files to make it easier to > audit the kernel tree for correct licenses. > > Update the drivers/usb/ and include/linux/usb* files with the correct > SPDX license identifier based on the license text in the file itself. > The SPDX identifier is a

v4.15-rc5: resume took way too long, warning in syslog

Hi! v4.15-rc5.. resume took _way_ too long, and I have warn_on in dmesg as a bonus. It looks like USB problem...? I never seen this before. Pavel [42266.070103] PM: Syncing filesystems ... done. [42266.948883] Freezing

Re: v4.15-rc5: resume took way too long, warning in syslog

On Fri 2017-12-29 11:23:36, Alan Stern wrote: > On Fri, 29 Dec 2017, Pavel Machek wrote: > > > Hi! > > > > v4.15-rc5.. resume took _way_ too long, and I have warn_on in dmesg as > > a bonus. It looks like USB problem...? I never seen this before. >

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi! > Let's add support for the GPIO controlled USB PHY on the MDM6600 modem. > It is used on some Motorola Mapphone series of phones and tablets such > as Droid 4. ... > So it seems that MDM6600 is currently not yet idling even with it's > radio turned off, but that's something that is beyond

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi! > > Does ofonod work for you? I could not get that one to work... > > Because it's looking for a Gobi modem but the MDM6600 isn't one and > doesn't expose that layout (and doesn't really need to anyway). I > don't think ofono has a generic QMI driver, so you'd either need to for > ce it to

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

On Sat 2018-03-24 07:25:17, Tony Lindgren wrote: > * Dan Williams <d...@redhat.com> [180324 14:00]: > > On Fri, 2018-03-23 at 21:13 +0100, Pavel Machek wrote: > > > Does ofonod work for you? I could not get that one to work... > > > > Because it's looking fo

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi! > > > > Hmm. Interesting. Anyway, for me ttyUSB4 is interesting, as it seems > > > > to react to AT commands, and in particular reacts to ADT123; (; is > > > > important). > > > > > > Is that to dial a voice call? > > > > Yes. And it is ATD123; not ATD. > > Strange, no semicolon is needed

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi! > > Hmm. Interesting. Anyway, for me ttyUSB4 is interesting, as it seems > > to react to AT commands, and in particular reacts to ADT123; (; is > > important). > > Is that to dial a voice call? Yes. And it is ATD123; not ATD. > > AT+CMGF=1 > > AT+CMGS="123" > > foo^Z > > > > Works for SMS

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi! > idle lcd off phy-mapphone-mdm6600ohci-platform > 153mW 284mW 344mW > > So it seems that MDM6600 is currently not yet idling even with it's > radio turned off, but that's something that is beyond the control of > this USB PHY driver. This patch does get us to

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi! > > user@devuan:/sys/devices/platform/4400.ocp/4a064000.usbhshost$ > > sudo lsusb > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > user@devuan:/sys/devices/platform/4400.ocp/4a064000.usbhshost$ >

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi! > > > Do you have the related dts patches picked from next? > > > > > > fdd192037fce ("ARM: dts: omap4-droid4: Fix USB PHY port naming") > > > e5b9fd7bdeb5 ("ARM: dts: omap4-droid4: Configure MDM6600 USB PHY") > > > > > > But yeah all you need to do is have phy-mapphone-mdm6600 and > > >

Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

On Fri 2018-03-23 12:35:21, Sebastian Reichel wrote: > Hi, > > On Fri, Mar 23, 2018 at 11:54:55AM +0100, Pavel Machek wrote: > > Hi! > > > > > > > Do you have the related dts patches picked from next? > > > > > > > > > &

<    1   2