Hello all.
On my Thunkpad T420i with 3.18.2 and 3.18.3 kernels, I can reproduce
the following behaviour 100% of the time:
1. Connect one of my (NTFS-formatted) WD 1TB 'My Passport' drives via USB.
2. Disconnect the cable.
3. Kernel Ooops.
For last entries of the journal (it actually caught the k
Robert Jarzmik writes:
> I'm not convinced of the "so many issues". So far I see the
> "gpiod_get_optional()" requirement, which is a one liner patch.
Would you try the following patch to see if it fixes all your concerns please ?
Cheers.
--
Robert
---<8---
>From 7b34a3aa2a0717b53cd458611048f
Fabio Estevam writes:
> On Sat, Dec 6, 2014 at 7:05 PM, Robert Jarzmik wrote:
>> Change internal gpio handling from integer gpios into gpio
>> descriptors. This change only addresses the internal API and
>> device-tree/ACPI, while the legacy platform data remains integer space
>> based.
>>
>> Th
The gadget power property will be used at get_status request.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/udc.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
index 540db0e..45914ba 100644
--- a/drivers/usb/chipi
The user can read it through sys entry.
Signed-off-by: Peter Chen
---
drivers/usb/gadget/udc/udc-core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/gadget/udc/udc-core.c
b/drivers/usb/gadget/udc/udc-core.c
index 86d4d19..4f1aed4 100644
--- a/drivers/usb/gadget/udc/udc-core
Whether the gadget is selfpowerwed or not can be determined by composite
core, so we can use a common entry to indicate if the self-powered
is supported by gadget, and the related private variable at individual
udc driver can be deleted.
Signed-off-by: Peter Chen
---
include/linux/usb/gadget.h |
Delete private selfpowered variable, and use common one.
Signed-off-by: Peter Chen
---
drivers/usb/gadget/udc/at91_udc.c | 8
drivers/usb/gadget/udc/at91_udc.h | 1 -
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/gadget/udc/at91_udc.c
b/drivers/usb/gadget/u
Hi Felipe,
We can use a common is_selfpowered flag at usb_gadget to indicate
whether the gadget is self-powered or bus-powered, it can avoid
every udc driver defining a similar flag, and the user can
read it through udc core sys entry.
In the 1st patch, I introduce is_selfpowered for usb_gadget.
On Thu, Jan 22, 2015 at 01:36:33PM -0600, Felipe Balbi wrote:
> Hi Greg,
>
> two more fixes needed from my side. Let me know if you prefer
> to handle them differently.
>
> cheers
>
> The following changes since commit ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc:
>
> Linux 3.19-rc5 (2015-01-18 1
> From: Vincent Pelletier [mailto:plr.vinc...@gmail.com]
> Sent: Friday, January 23, 2015 12:19 AM
>
> On Fri, 23 Jan 2015 02:38:37 +, John Youn
> wrote:
> > Having the __raw functions everywhere is not pretty and probably not a
> > good idea either.
> >
> > I would rather have a dwc2_writel/
On Mon, Jan 26, 2015 at 01:23:47PM -0500, Alan Stern wrote:
> On Mon, 26 Jan 2015, Andy Shevchenko wrote:
>
> > On Mon, 2015-01-26 at 09:21 -0800, Greg KH wrote:
> > > On Mon, Jan 26, 2015 at 07:10:42PM +0200, Andy Shevchenko wrote:
> > > > On some Intel MID platforms the ChipIdea USB controller i
Hi Roger,
On 01/27/2015 01:27 AM, Roger Quadros wrote:
> Hi Chanwoo,
>
> All your comments are valid. Need some clarification on one comment.
>
> On 26/01/15 15:56, Chanwoo Choi wrote:
>> Hi Roger,
>>
>> This patch looks good to me. But I add some comment.
>> If you modify some comment, I'll app
On Tue, 2015-01-27 at 02:14AM +0100, Andreas Färber wrote:
> + linux-gpio, linux-usb, Felipe Balbi
>
> Am 26.01.2015 um 19:44 schrieb Sören Brinkmann:
> > On Mon, 2015-01-26 at 08:23AM -0800, Sören Brinkmann wrote:
> >> On Mon, 2015-01-26 at 05:21PM +0100, Andreas Färber wrote:
> >>> Am 26.01.2015
A reset through a GPIO is optional. Don't fail probing when it is
missing.
Reported-by: Andreas Färber
Signed-off-by: Soren Brinkmann
---
Hi Andreas,
does this do the trick?
Thanks,
Sören
drivers/usb/phy/phy-generic.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-
On Mon, Jan 26, 2015 at 05:38:25PM +, Shevchenko, Andriy wrote:
> On Fri, 2014-11-28 at 14:42 +0200, Andy Shevchenko wrote:
> > On Mon, 2014-11-17 at 09:46 +0800, Peter Chen wrote:
>
> []
>
> > > Rebase my next tree where antoine's generic phy support for chipidea
> > > driver in it, and for
On Sat, Dec 6, 2014 at 7:05 PM, Robert Jarzmik wrote:
> Change internal gpio handling from integer gpios into gpio
> descriptors. This change only addresses the internal API and
> device-tree/ACPI, while the legacy platform data remains integer space
> based.
>
> This change is only build compile
+ linux-gpio, linux-usb, Felipe Balbi
Am 26.01.2015 um 19:44 schrieb Sören Brinkmann:
> On Mon, 2015-01-26 at 08:23AM -0800, Sören Brinkmann wrote:
>> On Mon, 2015-01-26 at 05:21PM +0100, Andreas Färber wrote:
>>> Am 26.01.2015 um 16:50 schrieb Sören Brinkmann:
On Mon, 2015-01-26 at 10:35AM +
On Mon, 2015-01-26 at 23:33 +0100, Henri Manson wrote:
> From lsusb:
>
> Bus 008 Device 013: ID 0830:0002 Palm, Inc. m505
I've blacklisted anything driven by 'visor' upstream in ModemManager,
since most of those appear to be non-phone devices. Yes, 3 are phones
(Samsung and Acer) but they are so
>From lsusb:
Bus 008 Device 013: ID 0830:0002 Palm, Inc. m505
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 2015-01-26 at 22:49 +0100, Henri Manson wrote:
> Indeed /usr/sbin/ModemManager (Ubuntu 14.04) or
> /usr/sbin/modem-manager (Ubuntu 10.04) is the program that is started
> when a Palm is connected and is causing the 'Fatal Exception' on the
> Palm m505. Moving it out of the way is the soluti
The macro EP_MODE_AUTOREG_* should be called EP_MODE_AUTOREQ_*, as they
are used for register AUTOREQ.
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_cppi41.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/musb/musb_cppi41.c b/drivers/usb/musb/musb
1. set AUTOREQ to NONE at the beginning of teardown;
2. add delay for dma pipeline to drain;
3. Do not set USB_TDOWN bit for RX teardown.
The CPPI hw has an issue that when tearing down a RX channel, if
another RX channel is receiving data, the CPPI will lockup.
To workaround the issue, d
I've come across what appears to be another xHCI issue - attempting to
format a disk with gparted is causing a kernel Oops. This may not be
related to the issue you're currently investigating, but wanted to
pass it on in case it is (if it isn't let me know and I'll either keep
quiet or raise it se
Indeed /usr/sbin/ModemManager (Ubuntu 14.04) or
/usr/sbin/modem-manager (Ubuntu 10.04) is the program that is started
when a Palm is connected and is causing the 'Fatal Exception' on the
Palm m505. Moving it out of the way is the solution. How can I update
the blacklist myself?
On Mon, Jan 26, 201
The EHCI controller on the RK3288 SoC is violating basic parts of the
USB spec and thereby unable to properly resume a suspended port. It does
not start SOF generation within 3ms of finishing resume signaling, so
the attached device will drop off the bus again. This is a particular
problem with run
> You should use a sleeping function call, not a delay.
Whoops... yes, of course. Guess too much firmware work made me forget
what multithreading is there for a moment. Will send a v2.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vge
On Mon, 2015-01-26 at 19:17 +0100, Johan Hovold wrote:
> On Mon, Jan 26, 2015 at 04:00:26PM +0100, Henri Manson wrote:
> > Hello,
> >
> > I performed the test using VirtualBox and live cd iso images, so
> > mixing different version of kernel and user-space programs does not
> > happen.
>
> You'd
On Sat, 24 Jan 2015, Jim Keir wrote:
> Yes, confirmed. The description below still holds.
Could you please therefore fix this patch so that it contains proper
changelog on proper place, and resubmit?
Also, the Subject line looks rather strange to me ... to my
understanding, this isn't really s
On Fri, 23 Jan 2015, Benjamin Tissoires wrote:
> With the changes above (or if you fix my typos), the patch is
> Reviewed-by: Benjamin.tissoires
>
> Jiri, could you amend the commit with the above so that Jim won't be
> desperate by submitting a patch?
Done and applied this one. Jim, please mak
On Mon, Jan 26, 2015 at 01:46:10PM +0200, Heikki Krogerus wrote:
> On Fri, Jan 23, 2015 at 10:24:43AM -0600, Felipe Balbi wrote:
> > On Fri, Jan 23, 2015 at 05:12:56PM +0200, Heikki Krogerus wrote:
> > > +int dwc3_ulpi_init(struct dwc3 *dwc)
> > > +{
> > > + u32 reg;
> > > +
> > > + /* First check
Hi Heikki,
On Mon, Jan 26, 2015 at 02:55:03PM +0200, Heikki Krogerus wrote:
> Hi David,
>
> On Sat, Jan 24, 2015 at 03:58:11PM -0800, David Cohen wrote:
> > > +static int tusb1210_power_on(struct phy *phy)
> > > +{
> > > + struct tusb1210 *tusb = phy_get_drvdata(phy);
> > > +
> > > + gpiod_set_va
On Mon, Jan 26, 2015 at 07:46:42AM +0100, Robert Baldyga wrote:
> On 01/23/2015 10:18 PM, Mario Schuknecht wrote:
> > Use if-loop variable 'epfile' instead of start variable 'epfiles'. Now the
> > correct endpoint file name is stored.
> >
> > Signed-off-by: Mario Schuknecht
> > ---
> > drivers/u
On Mon, Jan 26, 2015 at 01:26:19PM +0100, Andrzej Pietrasiewicz wrote:
> W dniu 26.01.2015 o 12:47, Mario Schuknecht pisze:
> >USB vendor type is encoded in field bmRequestType. Make test USB_TYPE_VENDOR
> >with bRequestType instead of bRequest.
> >
> >Signed-off-by: Mario Schuknecht
>
> Acked-by
On Mon, 26 Jan 2015, Andy Shevchenko wrote:
> On Mon, 2015-01-26 at 09:21 -0800, Greg KH wrote:
> > On Mon, Jan 26, 2015 at 07:10:42PM +0200, Andy Shevchenko wrote:
> > > On some Intel MID platforms the ChipIdea USB controller is used. The EHCI
> > > PCI
> > > is in conflict with the proper drive
On Mon, Jan 26, 2015 at 04:00:26PM +0100, Henri Manson wrote:
> Hello,
>
> I performed the test using VirtualBox and live cd iso images, so
> mixing different version of kernel and user-space programs does not
> happen.
You'd probably need to compile your own kernel (e.g. test an old kernel
on yo
On Mon, 2015-01-26 at 09:21 -0800, Greg KH wrote:
> On Mon, Jan 26, 2015 at 07:10:42PM +0200, Andy Shevchenko wrote:
> > On some Intel MID platforms the ChipIdea USB controller is used. The EHCI
> > PCI
> > is in conflict with the proper driver. The patch makes a quick fix to get
> > Intel
> > Me
On Fri, 2014-11-28 at 14:42 +0200, Andy Shevchenko wrote:
> On Mon, 2014-11-17 at 09:46 +0800, Peter Chen wrote:
[]
> > Rebase my next tree where antoine's generic phy support for chipidea
> > driver in it, and for usb phy, the "phy" changes to "usb_phy".
>
> Okay, I'm going to change the name i
On Mon, Jan 26, 2015 at 07:10:42PM +0200, Andy Shevchenko wrote:
> On some Intel MID platforms the ChipIdea USB controller is used. The EHCI PCI
> is in conflict with the proper driver. The patch makes a quick fix to get
> Intel
> Medfield platforms work back.
>
> One would make a proper patch to
On some Intel MID platforms the ChipIdea USB controller is used. The EHCI PCI
is in conflict with the proper driver. The patch makes a quick fix to get Intel
Medfield platforms work back.
One would make a proper patch to address the issue.
Fixes: adfa79d1c06a (USB: EHCI: make ehci-pci a separate
Things just got way worse with this hotplug thing.
When the host power/control is set to `auto`, as soon as I insert the
Unifying receiver one of kworkers starts eating 100% of one of the
cores, according to `htop`. As soon as I `echo on` to power/control of
the relevant USB hub the kworker stops
Hi Chanwoo,
All your comments are valid. Need some clarification on one comment.
On 26/01/15 15:56, Chanwoo Choi wrote:
> Hi Roger,
>
> This patch looks good to me. But I add some comment.
> If you modify some comment, I'll apply this patch on 3.21 queue.
>
> On Mon, Jan 26, 2015 at 9:15 PM, Ro
Hi Sebastian,
On Mon, Jan 26, 2015 at 2:57 AM, Sebastian Andrzej Siewior
wrote:
> On 01/21/2015 06:06 PM, Bin Liu wrote:
>> Hi Sebastian,
>
> Hi Bin,
>
>> With this patch, hubs stop working on TI AM335x EVMs when autosuspend
>> is enabled.
>>
>> I booted the board, connected a hub to the USB1 hos
Hi,
I want to use the usb_debug serial driver as a UART shell on my
(embedded) device, because I just want to use it as a console(without
a complex protocol so I can easily use putchar and getchar functions).
This seems to work pretty good except for two things.
Once upon establishing a connectio
On Mon, Jan 26, 2015 at 01:40:34PM +0100, Johan Hovold wrote:
> On Wed, Jan 21, 2015 at 03:24:27PM -0500, Lennart Sorensen wrote:
> > Added the USB serial console device ID for Siemens Ruggedcom devices
> > which have a USB port for their serial console.
> >
> > Signed-off-by: Len Sorensen
> > --
On Fri, 23 Jan 2015 pras...@anche.no wrote:
> Hi. The device in question is the external usb hdd Seagate Expansion 1TB.
> It claims to be usb 3.0 and also to be usable on usb 2.0 systems.
> Vendor and device ids are 0bc2 and 2312.
>
> I have tested it on the fresh 3.18.3 from kernel.org, on a lap
Hello,
I performed the test using VirtualBox and live cd iso images, so
mixing different version of kernel and user-space programs does not
happen. In 9.04 there is no usb communication until pilot-xfer is
started (a user-space program), in 10.04 usb communication happens
directly after hotsyncing
Hi,
On 26-01-15 16:30, Zhuang Jin Can wrote:
This revert a82b76f7fa6154e8ab2d8071842a3e38b9c0d0ff.
The commit causes an extra reset in remote wakeup as described in:
http://www.spinics.net/lists/linux-usb/msg119080.html
Signed-off-by: Zhuang Jin Can
No objection from me (*) against revertin
This revert a82b76f7fa6154e8ab2d8071842a3e38b9c0d0ff.
The commit causes an extra reset in remote wakeup as described in:
http://www.spinics.net/lists/linux-usb/msg119080.html
Signed-off-by: Zhuang Jin Can
---
drivers/usb/core/hub.c | 34 +-
1 file changed, 9 in
Hi Roger,
This patch looks good to me. But I add some comment.
If you modify some comment, I'll apply this patch on 3.21 queue.
On Mon, Jan 26, 2015 at 9:15 PM, Roger Quadros wrote:
> This driver observes the USB ID pin connected over a GPIO and
> updates the USB cable extcon states accordingly.
On Mon, Jan 19, 2015 at 05:08:07PM +0100, Henri Manson wrote:
> Apparently on 9.04 USB communications happen after invoking pilot-link
> while in 10.04 it happens directly when Hotsync is activated on the
> device. Enclosed the 9.04 syslog file and MenuExample.prc which is
> sent using:
>
> pilot-
Hi David,
On Sat, Jan 24, 2015 at 03:58:11PM -0800, David Cohen wrote:
> > +static int tusb1210_power_on(struct phy *phy)
> > +{
> > + struct tusb1210 *tusb = phy_get_drvdata(phy);
> > +
> > + gpiod_set_value_cansleep(tusb->gpio_reset, 1);
> > + gpiod_set_value_cansleep(tusb->gpio_cs, 1);
>
On 01/23/2015 10:18 PM, Mario Schuknecht wrote:
> Use if-loop variable 'epfile' instead of start variable 'epfiles'. Now the
> correct endpoint file name is stored.
>
> Signed-off-by: Mario Schuknecht
> ---
> drivers/usb/gadget/function/f_fs.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 del
On Wed, Jan 21, 2015 at 03:24:27PM -0500, Lennart Sorensen wrote:
> Added the USB serial console device ID for Siemens Ruggedcom devices
> which have a USB port for their serial console.
>
> Signed-off-by: Len Sorensen
> ---
> drivers/usb/serial/cp210x.c |1 +
> 1 file changed, 1 insertion(+
W dniu 26.01.2015 o 12:47, Mario Schuknecht pisze:
USB vendor type is encoded in field bmRequestType. Make test USB_TYPE_VENDOR
with bRequestType instead of bRequest.
Signed-off-by: Mario Schuknecht
Acked-by: Andrzej Pietrasiewicz
---
drivers/usb/gadget/composite.c | 2 +-
1 file change
The recommended name for USB-Host cable state is "USB-Host" and not
"USB-HOST" as per drivers/extcon/extcon-class.c extcon_cable_name.
Change all instances of "USB-HOST" to "USB-Host".
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
Acked-by: Felipe Balbi
---
drivers/extcon/extcon-palm
On this board USB2 is meant to be used as peripheral only.
The ID pin for USB2 is hardwired HIGH.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/am57xx-beagle-x15.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/am57xx-beagle-x15.dts
b/arch/arm/boot/dts/am57xx-b
Hi,
Still hoping this can make into 3.20 else we have USB peripheral mode broken on
DRA7-evm, DRA72-evm and AM57xx-beagle-x15.
On DRA7 and AM57xx EVMs the USB ID pin is connected to a GPIO line.
The USB drivers (dwc3 + dwc3-omap) depend on extcon framework to get the
USB cable state (USB or USB-H
On this EVM, the USB cable state has to be determined via the
ID pin tied to a GPIO line. We use the gpio-usb-extcon driver
to read the ID pin and the extcon framework to forward
the USB cable state information to the USB driver so the
controller can be configured in the right mode (host/peripheral
On this EVM, the USB cable state has to be determined via the
ID pin tied to a GPIO line. We use the gpio-usb-extcon driver
to read the ID pin and the extcon framework to forward
the USB cable state information to the USB driver so the
controller can be configured in the right mode (host/peripheral
On this EVM, the USB cable state has to be determined via the
ID pin tied to a GPIO line. We use the gpio-usb-extcon driver
to read the ID pin and the extcon framework to forward
the USB cable state information to the USB driver so the
controller can be configured in the right mode (host/peripheral
This driver is needed for USB cable type detection on dra7-evm,
dra72-evm and am57xx-beagle-x15.
Signed-off-by: Roger Quadros
---
arch/arm/configs/omap2plus_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/omap2plus_defconfig
b/arch/arm/configs/omap2plus_defconfig
This driver observes the USB ID pin connected over a GPIO and
updates the USB cable extcon states accordingly.
The existing GPIO extcon driver is not suitable for this purpose
as it needs to be taught to understand USB cable states and it
can't handle more than one cable per instance.
For the USB
On 26.01.2015 05:37, Devin Heitmueller wrote:
> Hi Mathias,
>
> Here's an interesting development: as a result of a related thread on
> linux-media, I came across a patch they are distributing in openelec:
>
> https://github.com/OpenELEC/OpenELEC.tv/commit/b636927dec20652ff020e54ed7838a2e9be51e0
On Fri, Jan 23, 2015 at 10:24:43AM -0600, Felipe Balbi wrote:
> On Fri, Jan 23, 2015 at 05:12:56PM +0200, Heikki Krogerus wrote:
> > +int dwc3_ulpi_init(struct dwc3 *dwc)
> > +{
> > + u32 reg;
> > +
> > + /* First check USB2 PHY interface type */
> > + switch (DWC3_GHWPARAMS3_HSPHY_IFC(dwc->h
Hi Mario,
W dniu 23.01.2015 o 21:52, Mario Schuknecht pisze:
Add missing case USB_EXT_PROP_UNICODE_MULTI to fill_ext_prop.
Type vendor is coded in bRequestType. Compare USB_TYPE_VENDOR with
bRequestType instead of bRequest.
The above seem to be unrelated changes.
Please split into two separa
On Mon, Jan 26, 2015 at 4:37 AM, Devin Heitmueller
wrote:
> Hi Mathias,
>
> Here's an interesting development: as a result of a related thread on
> linux-media, I came across a patch they are distributing in openelec:
>
> https://github.com/OpenELEC/OpenELEC.tv/commit/b636927dec20652ff020e54ed783
On Mon, Jan 19, 2015 at 6:48 PM, Hayes Wang wrote:
> David Miller [mailto:da...@davemloft.net]
>> Sent: Tuesday, January 20, 2015 5:14 AM
> [...]
>> >> - r8152_submit_rx(tp, agg, GFP_ATOMIC);
>> >> + if (!ret) {
>> >> + ret = r8152_submit_rx(tp, a
On 01/21/2015 06:06 PM, Bin Liu wrote:
> Hi Sebastian,
Hi Bin,
> With this patch, hubs stop working on TI AM335x EVMs when autosuspend
> is enabled.
>
> I booted the board, connected a hub to the USB1 host port, it got
> enumerated properly, then connected a thumb drive to the hub, but the
> dri
68 matches
Mail list logo
