Your message dated Thu, 21 Jan 2016 01:06:35 +0900 with message-id <caeq9gek-99xabss8iuhdjjt2ori+f53daxpjd6+1pan35dr...@mail.gmail.com> and subject line Re: Bug#810894: src:linux: GPIO probe failure on Linkstation LS-WXL/WSXL has caused the Debian Bug report #810894, regarding src:linux: GPIO probe failure on Linkstation LS-WXL/WSXL to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 810894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:linux Version: 3.16.7-ckt20-1+deb8u1 Severity: normal Control: notfound -1 3.16.7-ckt4-3 Control: found -1 3.16.7-ckt7-1 Control: found -1 3.16.7-ckt20-1+deb8u1 Control: notfound -1 4.2.6-3~bpo8+2 Control: notfound -1 4.3.3-5~bpo8+1 Control: notfound -1 4.4~rc8-1~exp1 X-Debbugs-Cc: debian-...@lists.debian.org Dear Maintainer, I need to run the following command to enable USB port on Linkstation LS-WXL/WSXL (armel/kirkwood with DTS [0] ): echo 37 >/sys/class/gpio/export echo out > /sys/class/gpio/gpio37/direction echo 1 > /sys/class/gpio/gpio37/value The 3-line script runs well on Jessie rootfs + kernel listed below: - 3.16.7-ckt4-3 - 4.2.6-3~bpo8+2 - 4.4~rc8-1~exp1 But fails from 3.16.7-ckt7-1 to 3.16.7-ckt20-1+deb8u1 (latest jessie kernel). The error message is like this: # echo 37 >/sys/class/gpio/export -bash: echo: write error: Device or resource busy I believe it's a regression between 3.16.7-ckt4-3 and 3.16.7-ckt7-1. I see the kernel config keeps the same for above two version, so it's only related to source code change. I wonder whether other armel/kirkwood user meet similar issue. Enclosed the dmesg log for kernel 3.16.7-ckt4-3 and 3.16.7-ckt7-1. I found some suspicious part as following. # grep -i gpio dmesg_3.16.7-ckt4-3_USB-OK [ 1.330575] platform gpio_leds: Driver leds-gpio requests probe deferral [ 1.375088] platform gpio_leds: Driver leds-gpio requests probe deferral [ 1.939806] platform gpio_leds: Driver leds-gpio requests probe deferral [ 2.018299] platform gpio_leds: Driver leds-gpio requests probe deferral [ 2.111944] platform gpio_leds: Driver leds-gpio requests probe deferral [ 2.224434] platform gpio_leds: Driver leds-gpio requests probe deferral [ 3.089576] platform gpio_leds: Driver leds-gpio requests probe deferral [ 6.368688] + [ -z of:NgpioT<NULL>Cmarvell,orion-gpio ] [ 6.375236] + printf %.1s of:NgpioT<NULL>Cmarvell,orion-gpio [ 6.387131] + modprobe of:NgpioT<NULL>Cmarvell,orion-gpio [ 6.435552] + [ -z of:NgpioT<NULL>Cmarvell,orion-gpio ] [ 6.442104] + printf %.1s of:NgpioT<NULL>Cmarvell,orion-gpio [ 6.453970] + modprobe of:NgpioT<NULL>Cmarvell,orion-gpio [ 12.451230] platform gpio_keys: Driver gpio-keys requests probe deferral [ 12.702214] platform gpio_leds: Driver leds-gpio requests probe deferral [ 12.797363] platform gpio_keys: Driver gpio-keys requests probe deferral [ 13.901732] platform gpio_leds: Driver leds-gpio requests probe deferral [ 13.941971] platform gpio_keys: Driver gpio-keys requests probe deferral [ 14.010529] platform gpio_leds: Driver leds-gpio requests probe deferral [ 14.028970] platform gpio_keys: Driver gpio-keys requests probe deferral # grep -i gpio dmesg_3.16.7-ckt7-1_USB-NG [ 1.330434] leds-gpio gpio_leds: Skipping unavailable LED gpio -22 (lswxl:blue:func) [ 1.338206] leds-gpio gpio_leds: Skipping unavailable LED gpio -22 (lswxl:red:alarm) [ 6.170632] + [ -z of:NgpioT<NULL>Cmarvell,orion-gpio ] [ 6.177167] + printf %.1s of:NgpioT<NULL>Cmarvell,orion-gpio [ 6.189050] + modprobe of:NgpioT<NULL>Cmarvell,orion-gpio [ 6.237266] + [ -z of:NgpioT<NULL>Cmarvell,orion-gpio ] [ 6.243743] + printf %.1s of:NgpioT<NULL>Cmarvell,orion-gpio [ 6.255639] + modprobe of:NgpioT<NULL>Cmarvell,orion-gpio [ 12.246044] gpio-keys gpio_keys: Failed to get gpio flags, error: -22 [ 12.281961] gpio-keys: probe of gpio_keys failed with error -22 [0]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/kirkwood-lswxl.dts Cheers, Roger
dmesg_LS-WXL_USB-issue.tar.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---On Fri, Jan 15, 2016 at 12:50 AM, Roger Shimizu <rogershim...@gmail.com> wrote: > On Fri, Jan 15, 2016 at 12:26 AM, Arnaud Patard > <arnaud.pat...@rtp-net.org> wrote: >> From a quick look, dts looks broken, if gpio 37 is not for the led: >> label = "lswxl:red:func"; >> gpios = <&gpio1 5 GPIO_ACTIVE_LOW>; >> >> >> btw, this is broken too: >> usb_power: regulator@1 { >> ... >> gpio = <&gpio0 37 GPIO_ACTIVE_HIGH>; >> >> There's no such a thing as gpio 37 on bank 0 as kirkwood bank have 32 >> gpios. I'm supprised nobody ever noticed it. Change it to "gpio1 5" and >> there are chances that export won't be needed anymore. >> >> imho, you should double check all the gpios entries in your dts. Dear Amaud, I submitted my patches to upstream [0][1], with your name in "Reported-by". I really appreciate your guiding! [0]: http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/400699.html [1]: http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/400701.html Cheers, Roger
--- End Message ---
