Hi Andy,
On Sun, Nov 15, 2015 at 10:04:10PM +0200, Andy Shevchenko wrote:
> On Sun, Nov 15, 2015 at 8:39 PM, Dave Penkler wrote:
snip
> > +
>
> Redundant empty line.
>
ok
>
> > + data->iin_bTag = 2;
>
> Hmm??? Why 2?
> A-ha, below I found a comment. Something might be good to
On Sun, Nov 15, 2015 at 10:10:35PM +0200, Andy Shevchenko wrote:
> On Sun, Nov 15, 2015 at 8:40 PM, Dave Penkler wrote:
> > These ioctls provide support for the USBTMC-USB488 control requests
> > for REN_CONTROL, GO_TO_LOCAL and LOCAL_LOCKOUT
> >
> > +
> > + dev = &data->intf->dev;
>
> Coul
Implement support for the USB488 defined READ_STATUS_BYTE ioctl (1/5)
and SRQ notifications with fasync (2/5) and poll/select (3/5) in order
to be able to synchronize with variable duration instrument
operations.
Add ioctls for other USB488 requests: REN_CONTROL, GOTO_LOCAL and
LOCAL_LOCKOUT. (4/5
Background:
In many situations operations on multiple instruments need to be
synchronized. poll/select provide a convenient way of waiting on a
number of different instruments and other peripherals
simultaneously.
Signed-off-by: Dave Penkler
---
drivers/usb/class/usbtmc.c | 23 ++
This is a convenience function to obtain an instrument's
capabilities from its file descriptor without having to access sysfs
from the user program.
Signed-off-by: Dave Penkler
---
drivers/usb/class/usbtmc.c | 12
include/uapi/linux/usb/tmc.h | 21 ++---
2 files ch
On Wed, Sep 16, 2015 at 03:52:33PM +0800, Li Jun wrote:
> From: Peter Chen
>
> Add "fsl,imx6ul-usbphy" compatible string for iMX6ul usb phy
>
> Signed-off-by: Peter Chen
> Signed-off-by: Li Jun
> ---
> drivers/usb/phy/phy-mxs-usb.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git
These ioctls provide support for the USBTMC-USB488 control requests
for REN_CONTROL, GO_TO_LOCAL and LOCAL_LOCKOUT
Signed-off-by: Dave Penkler
---
drivers/usb/class/usbtmc.c | 71
include/uapi/linux/usb/tmc.h | 6
2 files changed, 77 insertion
Background:
By configuring an instrument's event status register various
conditions can be reported via an SRQ notification. This complements
the synchronous polling approach using the READ_STATUS_BYTE ioctl
with an asynchronous notification.
Signed-off-by: Dave Penkler
---
drivers/usb/class/usb
Background:
When performing a read on an instrument that is executing a function
that runs longer than the USB timeout the instrument may hang and
require a device reset to recover. The READ_STATUS_BYTE operation
always returns even when the instrument is busy permitting to poll
for the appropriate
Hi Greg
These xhci fixes for usb-linus resolve a link power management race
preventing USB 2 devices from suspending again.
The CFC fix is for the newly added Contiguous Frame ID (CFC) capability,
fixing an audio noise issue with Isoch transfers on CFC capable hosts.
The last fix is a grace period
From: Rajmohan Mani
Existing Intel xHCI controllers require a delay of 1 mS,
after setting the CMD_RESET bit in command register, before
accessing any HC registers. This allows the HC to complete
the reset operation and be ready for HC register access.
Without this delay, the subsequent HC regist
Clear device initiated resume variables once device is fully up and running
in U0 state.
Resume needs to be signaled for 20ms for usb2 devices before they can be
moved to U0 state.
An interrupt is triggered if a device initiates resume. As we handle the
event in interrupt context we can not sleep
From: Lu Baolu
Function ep_ring_is_processing() checks the dequeue pointer
in endpoint context to know whether an endpoint is busy with
processing TRBs. This is not correct since dequeue pointer
field in an endpoint context is only valid when the endpoint
is in Halted or Stopped states. This bugg
On Wed, Nov 18, 2015 at 4:15 AM, Baolin Wang wrote:
> On 17 November 2015 at 21:34, Andy Shevchenko
> wrote:
>> On Mon, Nov 16, 2015 at 9:05 AM, Baolin Wang wrote:
>>> It dose not work when we want to use the usb-to-serial port based
>>> on one usb gadget as a console. Thus this patch adds the
On Wed, Nov 18, 2015 at 10:38 AM, Dave Penkler wrote:
> These ioctls provide support for the USBTMC-USB488 control requests
> for REN_CONTROL, GO_TO_LOCAL and LOCAL_LOCKOUT
Couple of comments below.
> diff --git a/drivers/usb/class/usbtmc.c b/drivers/usb/class/usbtmc.c
> index 2358991..d416a5f 1
Now the function of complicated_callback is not only used for iso
transfer, improve the error message to reflect it.
Signed-off-by: Peter Chen
---
Changes for v2:
- Typo for "fo" -> "for" at subject
drivers/usb/misc/usbtest.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --gi
On Wed, Nov 18, 2015 at 10:38:18AM +0100, Arnd Bergmann wrote:
> On Wednesday 18 November 2015 11:17:50 Peter Chen wrote:
> > From 3a6918dae038aadc200dcf0263f4440acc2353d4 Mon Sep 17 00:00:00 2001
> > From: Peter Chen
> > Date: Wed, 18 Nov 2015 11:06:34 +0800
> > Subject: [PATCH 1/1] usb: kconfig:
On Wednesday 18 November 2015 11:17:50 Peter Chen wrote:
> From 3a6918dae038aadc200dcf0263f4440acc2353d4 Mon Sep 17 00:00:00 2001
> From: Peter Chen
> Date: Wed, 18 Nov 2015 11:06:34 +0800
> Subject: [PATCH 1/1] usb: kconfig: fix warning of select USB_OTG
>
> When choose randconfig for kernel bui
Hi Hans,
Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
> On 16-11-15 18:01, Philipp Zabel wrote:
> > If there are two devices sharing the same reset line that is initially
> > held asserted, do the two drivers somehow have to synchronize before
> > releasing the reset together?
>
On Wed, Nov 18, 2015 at 10:37 AM, Dave Penkler wrote:
> Background:
> When performing a read on an instrument that is executing a function
> that runs longer than the USB timeout the instrument may hang and
> require a device reset to recover. The READ_STATUS_BYTE operation
> always returns even w
On Wed, Nov 18, 2015 at 10:46:52AM +0100, Philipp Zabel wrote:
> Hi Hans,
>
> Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
> > On 16-11-15 18:01, Philipp Zabel wrote:
> > > If there are two devices sharing the same reset line that is initially
> > > held asserted, do the two drive
Hi All,
On Wed, Nov 18, 2015 at 9:18 PM, Maxime Ripard
wrote:
> On Wed, Nov 18, 2015 at 10:46:52AM +0100, Philipp Zabel wrote:
>> Hi Hans,
>>
>> Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
>> > On 16-11-15 18:01, Philipp Zabel wrote:
>> > > If there are two devices sharing the s
Hi,
On 18-11-15 10:46, Philipp Zabel wrote:
Hi Hans,
Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
On 16-11-15 18:01, Philipp Zabel wrote:
If there are two devices sharing the same reset line that is initially
held asserted, do the two drivers somehow have to synchronize befor
Am Mittwoch, den 18.11.2015, 21:20 +1100 schrieb Julian Calaby:
> Hi All,
>
> On Wed, Nov 18, 2015 at 9:18 PM, Maxime Ripard
> wrote:
> > On Wed, Nov 18, 2015 at 10:46:52AM +0100, Philipp Zabel wrote:
> >> Hi Hans,
> >>
> >> Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
> >> > On
Hi,
On 18-11-15 11:38, Philipp Zabel wrote:
Am Mittwoch, den 18.11.2015, 21:20 +1100 schrieb Julian Calaby:
Hi All,
On Wed, Nov 18, 2015 at 9:18 PM, Maxime Ripard
wrote:
On Wed, Nov 18, 2015 at 10:46:52AM +0100, Philipp Zabel wrote:
Hi Hans,
Am Montag, den 16.11.2015, 18:13 +0100 schrieb H
On 18 November 2015 at 17:32, Andy Shevchenko wrote:
> On Wed, Nov 18, 2015 at 4:15 AM, Baolin Wang wrote:
>> On 17 November 2015 at 21:34, Andy Shevchenko
>> wrote:
>>> On Mon, Nov 16, 2015 at 9:05 AM, Baolin Wang wrote:
It dose not work when we want to use the usb-to-serial port based
>
Hi,
On 11/17/2015 06:28 PM, Dmitry Malkin wrote:
On Mon, 16 Nov 2015 10:18:42 +0800, Lu Baolu wrote:
This quirk works as well if debug host doesn't have DBC. I didn't try a
DBC-capable debug host yet.
Hi,
I went through it again, with your v3 patch series on top of vanilla v4.3.0.
Two target
Hi,
On 18-11-15 11:38, Hans de Goede wrote:
Hi,
On 18-11-15 10:46, Philipp Zabel wrote:
Hi Hans,
Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
On 16-11-15 18:01, Philipp Zabel wrote:
If there are two devices sharing the same reset line that is initially
held asserted, do the
Hi Hans,
Am Mittwoch, den 18.11.2015, 11:38 +0100 schrieb Hans de Goede:
> Hi,
>
> On 18-11-15 10:46, Philipp Zabel wrote:
> > Hi Hans,
> >
> > Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
> >> On 16-11-15 18:01, Philipp Zabel wrote:
> >>> If there are two devices sharing the sam
Hi,
On 18-11-15 12:59, Philipp Zabel wrote:
Hi Hans,
Am Mittwoch, den 18.11.2015, 11:38 +0100 schrieb Hans de Goede:
Hi,
On 18-11-15 10:46, Philipp Zabel wrote:
Hi Hans,
Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
On 16-11-15 18:01, Philipp Zabel wrote:
If there are two
From: Baolin Wang
> Sent: 18 November 2015 10:45
> On 18 November 2015 at 17:32, Andy Shevchenko
> wrote:
> > On Wed, Nov 18, 2015 at 4:15 AM, Baolin Wang wrote:
> >> On 17 November 2015 at 21:34, Andy Shevchenko
> >> wrote:
> >>> On Mon, Nov 16, 2015 at 9:05 AM, Baolin Wang
> >>> wrote:
> >
Hi,
On Wed, Nov 18, 2015 at 9:38 PM, Hans de Goede wrote:
> Hi,
>
> On 18-11-15 10:46, Philipp Zabel wrote:
>>
>> Hi Hans,
>>
>> Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
>>>
>>> On 16-11-15 18:01, Philipp Zabel wrote:
If there are two devices sharing the same reset
On 18 November 2015 at 20:05, David Laight wrote:
> From: Baolin Wang
>> Sent: 18 November 2015 10:45
>> On 18 November 2015 at 17:32, Andy Shevchenko
>> wrote:
>> > On Wed, Nov 18, 2015 at 4:15 AM, Baolin Wang
>> > wrote:
>> >> On 17 November 2015 at 21:34, Andy Shevchenko
>> >> wrote:
>> >
Hi Julian,
Am Mittwoch, den 18.11.2015, 23:32 +1100 schrieb Julian Calaby:
[...]
> Assuming board designers are sufficiently ... stupid, won't most
> drivers eventually need to use the _shared variants? Wouldn't it be
> (horrifically more complicated and) better to just build this into the
> gener
This patch adds glue driver for DWC3 core in Xilinx ZynqMP SOC.
DWC3 glue layer is hardware layer around Synopsys DesignWare
USB3 core. Its purpose is to supply Synopsys IP with required clocks
and interface it with the rest of the SoC.
Signed-off-by: Subbaraya Sundeep Bhatta
---
drivers/usb/dwc
This patch adds binding doc for Xilinx DWC3 glue driver.
Signed-off-by: Subbaraya Sundeep Bhatta
---
.../devicetree/bindings/usb/dwc3-xilinx.txt| 33 ++
1 file changed, 33 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/dwc3-xilinx.txt
diff --
On Tue, Nov 17, 2015 at 02:07:58PM -0500, Alan Stern wrote:
> If we really want to do zerocopy I/O then we should not use a bounce
> buffer. But the only way to avoid bounce buffers may be to give user
> programs a way of allocating memory pages below 4 GB, because lots of
> USB hardware can on
On Wed, Nov 18, 2015 at 3:02 PM, Christoph Hellwig wrote:
> On Tue, Nov 17, 2015 at 02:07:58PM -0500, Alan Stern wrote:
>> If we really want to do zerocopy I/O then we should not use a bounce
>> buffer. But the only way to avoid bounce buffers may be to give user
>> programs a way of allocating m
Hi,
On 18-11-15 13:32, Julian Calaby wrote:
Hi,
On Wed, Nov 18, 2015 at 9:38 PM, Hans de Goede wrote:
Hi,
On 18-11-15 10:46, Philipp Zabel wrote:
Hi Hans,
Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
On 16-11-15 18:01, Philipp Zabel wrote:
If there are two devices sha
From: Christoph Hellwig
> Sent: 18 November 2015 14:02
> On Tue, Nov 17, 2015 at 02:07:58PM -0500, Alan Stern wrote:
> > If we really want to do zerocopy I/O then we should not use a bounce
> > buffer. But the only way to avoid bounce buffers may be to give user
> > programs a way of allocating me
Hi Baolin,
On 11/16/2015 02:05 AM, Baolin Wang wrote:
> It dose not work when we want to use the usb-to-serial port based
> on one usb gadget as a console. Thus this patch adds the console
> initialization to support this request.
I have some high level concerns.
1. I would defer registering the
On Tue, Nov 17, 2015 at 12:21 PM, Alan Stern wrote:
> On Tue, 17 Nov 2015, Michael Reutman wrote:
>> Ran 1 million operations of launch+cancel usb transfers last night
>> without getting into the stuck state. I'll bump up the iterations to
>> 10 million or so and run it again tonight just to be ce
use safe copy_*_user instead of unsafe __copy_*_user
functions when accessing userland memory.
Signed-off-by: Daniel Walter
---
drivers/usb/gadget/function/f_fs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget/function/f_fs.c
b/drivers/usb/gadget/fu
On Wed, 18 Nov 2015, Peter Stuge wrote:
> Alan Stern wrote:
> > if we can directly map the user-provided buffer for DMA.
>
> Given a memory buffer either kernel or userspace has to apply the
> hardware constraints to find out what part if any is usable for DMA.
>
> I think it's fine to push this
The CPPI-4.1 driver selects TI_CPPI41, which is a dmaengine
driver and that may not be available when CONFIG_DMADEVICES
is not set:
warning: (USB_TI_CPPI41_DMA) selects TI_CPPI41 which has unmet direct
dependencies (DMADEVICES && ARCH_OMAP)
This adds an extra dependency to avoid generating warni
On Wed, 18 Nov 2015, Michael Reutman wrote:
> On Tue, Nov 17, 2015 at 12:21 PM, Alan Stern
> wrote:
> > On Tue, 17 Nov 2015, Michael Reutman wrote:
> >> Ran 1 million operations of launch+cancel usb transfers last night
> >> without getting into the stuck state. I'll bump up the iterations to
>
Memory management folk:
People have been complaining about memory-related problems with their
userspace USB drivers. There are two basic issues:
Memory fragmentation eventually prevents the kernel from
allocating contiguous buffers large enough to hold the I/O
data. S
On Wed, Nov 18, 2015 at 03:43:58PM +0800, Peter Chen wrote:
> The following changes since commit aa05cfa95f686be5d1485094402ebc7b03729e0e:
>
> Merge tag 'fixes-for-v4.4-rc2' of
> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus
> (2015-11-17 14:48:24 -0800)
>
> are avail
Hi,
Subbaraya Sundeep Bhatta writes:
> This patch adds glue driver for DWC3 core in Xilinx ZynqMP SOC.
> DWC3 glue layer is hardware layer around Synopsys DesignWare
> USB3 core. Its purpose is to supply Synopsys IP with required clocks
> and interface it with the rest of the SoC.
>
> Signed-off
"Steinar H. Gunderson" writes:
> On Tue, Nov 17, 2015 at 03:16:55PM -0500, Alan Stern wrote:
>> xHCI always uses 64-bit addresses. But many EHCI controllers don't,
>> and only a few of the EHCI platform drivers support 64-bit DMA.
>
> OK, sure. But are systems with USB2 only and more than 4GB of
Hi,
On Wed, Nov 18, 2015 at 10:18 AM, Arnd Bergmann wrote:
> The CPPI-4.1 driver selects TI_CPPI41, which is a dmaengine
> driver and that may not be available when CONFIG_DMADEVICES
> is not set:
>
> warning: (USB_TI_CPPI41_DMA) selects TI_CPPI41 which has unmet direct
> dependencies (DMADEVICE
The critical section protected by usbhid->lock in hid_ctrl() is too
big and in rare cases causes a recursive deadlock because of its call
to hid_input_report().
This deadlock reproduces on newer wacom tablets like 056a:033c because
the wacom driver in its irq handler ends up calling hid_hw_request
For simple platforms which merely enable some clocks
and populate its children, we can use this generic
glue layer to avoid boilerplate code duplication.
For now this supports Qcom and Xilinx, but if we
find a way to add generic handling of regulators and
optional PHYs, we can absorb exynos as wel
Hi,
Bin Liu writes:
> On Wed, Nov 18, 2015 at 10:18 AM, Arnd Bergmann wrote:
>> The CPPI-4.1 driver selects TI_CPPI41, which is a dmaengine
>> driver and that may not be available when CONFIG_DMADEVICES
>> is not set:
>>
>> warning: (USB_TI_CPPI41_DMA) selects TI_CPPI41 which has unmet direct
Here are some images with more information on this deadlock, might be helpful.
First part of lockdep report:
http://imgur.com/clLsCWe
Second part:
http://imgur.com/Wa2PzRl
Here are some printk's of mine while reproducing + debugging the issue:
http://imgur.com/SETOHT7
--
To unsubscribe from this
Thomas reports
"
4gsystems sells two total different LTE-surfsticks under the same name.
..
The newer version of XS Stick W100 is from "omega"
..
Under windows the driver switches to the same ID, and uses MI03\6 for
network and MI01\6 for modem.
..
echo "1c9e 9b01" > /sys/bus/usb/drivers/qmi_wwan/n
Thomas reports
"
4gsystems sells two total different LTE-surfsticks under the same name.
..
The newer version of XS Stick W100 is from "omega"
..
Under windows the driver switches to the same ID, and uses MI03\6 for
network and MI01\6 for modem.
..
echo "1c9e 9b01" > /sys/bus/usb/drivers/qmi_wwan/n
Hi,
On Wed, Nov 18, 2015 at 1:27 PM, Felipe Balbi wrote:
>
> Hi,
>
> Bin Liu writes:
>> On Wed, Nov 18, 2015 at 10:18 AM, Arnd Bergmann wrote:
>>> The CPPI-4.1 driver selects TI_CPPI41, which is a dmaengine
>>> driver and that may not be available when CONFIG_DMADEVICES
>>> is not set:
>>>
>>>
On Wednesday 18 November 2015 12:29:27 Bin Liu wrote:
> > diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
> > index 1f2037bbeb0d..45c83baf675d 100644
> > --- a/drivers/usb/musb/Kconfig
> > +++ b/drivers/usb/musb/Kconfig
> > @@ -159,7 +159,7 @@ config USB_TI_CPPI_DMA
> >
> > config
On Wed, 18 Nov 2015, Ioan-Adrian Ratiu wrote:
> The critical section protected by usbhid->lock in hid_ctrl() is too
> big and in rare cases causes a recursive deadlock because of its call
> to hid_input_report().
>
> This deadlock reproduces on newer wacom tablets like 056a:033c because
> the wac
Hi,
Bin Liu writes:
>> Bin Liu writes:
>>> On Wed, Nov 18, 2015 at 10:18 AM, Arnd Bergmann wrote:
The CPPI-4.1 driver selects TI_CPPI41, which is a dmaengine
driver and that may not be available when CONFIG_DMADEVICES
is not set:
warning: (USB_TI_CPPI41_DMA) selects TI
Hi,
On Wed, Nov 18, 2015 at 2:27 PM, Arnd Bergmann wrote:
> On Wednesday 18 November 2015 12:29:27 Bin Liu wrote:
>> > diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
>> > index 1f2037bbeb0d..45c83baf675d 100644
>> > --- a/drivers/usb/musb/Kconfig
>> > +++ b/drivers/usb/musb/Kcon
Hi,
Arnd Bergmann writes:
> On Wednesday 18 November 2015 12:29:27 Bin Liu wrote:
>> > diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
>> > index 1f2037bbeb0d..45c83baf675d 100644
>> > --- a/drivers/usb/musb/Kconfig
>> > +++ b/drivers/usb/musb/Kconfig
>> > @@ -159,7 +159,7 @@ co
On Wed, Nov 18, 2015 at 2:38 PM, Felipe Balbi wrote:
>
> Hi,
>
> Bin Liu writes:
>>> Bin Liu writes:
On Wed, Nov 18, 2015 at 10:18 AM, Arnd Bergmann wrote:
> The CPPI-4.1 driver selects TI_CPPI41, which is a dmaengine
> driver and that may not be available when CONFIG_DMADEVICES
>>
ARCH_SHMOBILE is coming to arm64, which creates new warnings in allmodconfig:
drivers/staging/emxx_udc/emxx_udc.c: In function '_nbu2ss_out_dma':
drivers/staging/emxx_udc/emxx_udc.c:843:45: warning: cast from pointer to
integer of different size [-Wpointer-to-int-cast]
_nbu2ss_writel(&preg->EP_
On Wed, 18 Nov 2015 21:37:42 +0100 (CET)
Jiri Kosina wrote:
> On Wed, 18 Nov 2015, Ioan-Adrian Ratiu wrote:
>
> > The critical section protected by usbhid->lock in hid_ctrl() is too
> > big and in rare cases causes a recursive deadlock because of its call
> > to hid_input_report().
> >
> > This
On Wednesday 18 November 2015 14:39:10 Bin Liu wrote:
> > Ideally we should remove the 'select TI_CPPI41' here as well, but
> > what we could do instead is to make that a silent symbol and remove
> > the prompt so it always gets enabled implicitly when USB_TI_CPPI41_DMA
> > and DMADEVICES are both
Hi,
Robert Jarzmik writes:
> Hi Robert and Felipe,
>
> I experience a regression in the 4.4-rc1 kernel which appeared between v4.3
> and
> v4.4-rc1.
> The test :
> - boot the mioa701 kernel (ie. pxa27x_udc driver)
> - echo mem > /sys/power/state
> - resume from "Suspend to RAM" with a key
Hi Robert and Felipe,
I experience a regression in the 4.4-rc1 kernel which appeared between v4.3 and
v4.4-rc1.
The test :
- boot the mioa701 kernel (ie. pxa27x_udc driver)
- echo mem > /sys/power/state
- resume from "Suspend to RAM" with a key press
- try to use the udc (in my case, g_eth
Felipe Balbi writes:
> Hi,
>
> without any sort of logs it a bit difficult :-) Care to send some output
> of the failure ? Are there any oopses or what exactly happens ?
Ah well, the UDC is the only way to "speak" to the board (no UART), so I don't
have any written feedback available. All I have
Robert Jarzmik writes:
> Felipe Balbi writes:
>
>> Hi,
>>
>> without any sort of logs it a bit difficult :-) Care to send some output
>> of the failure ? Are there any oopses or what exactly happens ?
> Ah well, the UDC is the only way to "speak" to the board (no UART), so I don't
> have any wri
Hi,
Robert Jarzmik writes:
> Felipe Balbi writes:
>
>> Hi,
>>
>> without any sort of logs it a bit difficult :-) Care to send some output
>> of the failure ? Are there any oopses or what exactly happens ?
>
> Ah well, the UDC is the only way to "speak" to the board (no UART), so
> I don't have
"Badhri Jagan Sridharan (Gerrit)"
Hi,
writes:
> Hello Felipe Balbi,
>
> I'd like you to do a code review. Please visit
>
> https://android-review.googlesource.com/183164
>
> to review the following change.
>
> Change subject: usb: gadget: configfs: Fix interfaces array NULL-termination
> .
Felipe Balbi writes:
> Hi,
> you can increase fbcon verbosity, right ? I guess that was
> CONFIG_MESSAGE_LOGLEVEL_DEFAULT.
Sure.
> Set it to 9 and you should get everything. Another option is to change
> dev_* to dev_crit() and KERN_* to KERN_CRIT.
>
>> I know there is not panic/crash, as the sc
Hi,
Robert Jarzmik writes:
> Robert Jarzmik writes:
>
>> Felipe Balbi writes:
>>
>>> Hi,
>>>
>>> without any sort of logs it a bit difficult :-) Care to send some output
>>> of the failure ? Are there any oopses or what exactly happens ?
>> Ah well, the UDC is the only way to "speak" to the bo
Hi,
Robert Jarzmik writes:
>>> that "ping mioa701" doesn't work anymore.
>>
>> that's kind of expected considering pxa27x disabled the UDC and
>> disconnects from the bus on suspend:
>
> Euh it's expected to work _after resume_.
sure is, but you can't expect it to have a proper IP. From host's
On Wed, Nov 18, 2015 at 06:20:31PM +0530, Subbaraya Sundeep Bhatta wrote:
> This patch adds binding doc for Xilinx DWC3 glue driver.
>
> Signed-off-by: Subbaraya Sundeep Bhatta
I really dislike how the DWC3 binding has been done. The sub-node here
is pointless. The only thing the outer node doe
By the way QNAP NAS systems are shipped with a 64bit kernel but a
32bit system environment.
Those systems support USB 2.0 and USB 3.0.
You can expect any kind of combination out there.
On Wed, Nov 18, 2015 at 7:23 PM, Bjørn Mork wrote:
> "Steinar H. Gunderson" writes:
>> On Tue, Nov 17, 2015 a
Felipe Balbi writes:
> Hi,
>
> this could be a bug in either g_ether or pxa27x... Seems like something
> is enabling endpoints which were already enabled. Not sure if this is
> pxa27x not _really_ disabling endpoints or g_ether being stupid.
You're probably right.
>From what I remember, g_ether i
Hi,
Rob Herring writes:
> On Wed, Nov 18, 2015 at 06:20:31PM +0530, Subbaraya Sundeep Bhatta wrote:
>> This patch adds binding doc for Xilinx DWC3 glue driver.
>>
>> Signed-off-by: Subbaraya Sundeep Bhatta
>
> I really dislike how the DWC3 binding has been done. The sub-node here
> is pointle
On Wed, Nov 18, 2015 at 03:39:47PM +0800, Zhangfei Gao wrote:
> Support hisilicon,hi6220-usb for HiKey board
>
> Signed-off-by: Zhangfei Gao
> ---
> Documentation/devicetree/bindings/usb/dwc2.txt | 1 +
For the binding:
Acked-by: Rob Herring
> drivers/usb/dwc2/platform.c
On Wed, Nov 18, 2015 at 03:35:23PM +0800, Zhangfei Gao wrote:
> Support hi6220 use phy for HiKey board
>
> Signed-off-by: Zhangfei Gao
> ---
> .../devicetree/bindings/phy/phy-hi6220-usb.txt | 16 ++
For the binding:
Acked-by: Rob Herring
> drivers/phy/Kconfig
Hi,
Robert Jarzmik writes:
> Felipe Balbi writes:
>
>> Hi,
>>
>> this could be a bug in either g_ether or pxa27x... Seems like something
>> is enabling endpoints which were already enabled. Not sure if this is
>> pxa27x not _really_ disabling endpoints or g_ether being stupid.
> You're probably
Felipe Balbi writes:
> Hi,
>
>> Euh it's expected to work _after resume_.
>
> sure is, but you can't expect it to have a proper IP. From host's
> perspective this is a brand new usb0 network interface. Unless you have
> dhcp client running on the phone and a server on your PC, you can't
> assume
On Wed, Nov 18, 2015 at 11:05:44PM +0200, Ioan-Adrian Ratiu wrote:
> On Wed, 18 Nov 2015 21:37:42 +0100 (CET)
> Jiri Kosina wrote:
>
> > On Wed, 18 Nov 2015, Ioan-Adrian Ratiu wrote:
> >
> > > The critical section protected by usbhid->lock in hid_ctrl() is too
> > > big and in rare cases causes
On Wed, Nov 18, 2015 at 5:02 PM, Felipe Balbi wrote:
>
> Hi,
>
> Rob Herring writes:
>> On Wed, Nov 18, 2015 at 06:20:31PM +0530, Subbaraya Sundeep Bhatta wrote:
>>> This patch adds binding doc for Xilinx DWC3 glue driver.
>>>
>>> Signed-off-by: Subbaraya Sundeep Bhatta
>>
>> I really dislike ho
On 11/16/2015 9:22 AM, Doug Anderson wrote:
> Felipe,
>
> On Mon, Nov 16, 2015 at 8:28 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Douglas Anderson writes:
>>> In general it is wise to clear interrupts before processing them. If
>>> you don't do that, you can get:
>>> 1. Interrupt happens
>>> 2.
On 11/17/2015 11:39 PM, Zhangfei Gao wrote:
> Support hisilicon,hi6220-usb for HiKey board
>
> Signed-off-by: Zhangfei Gao
> ---
> Documentation/devicetree/bindings/usb/dwc2.txt | 1 +
> drivers/usb/dwc2/platform.c| 32
> ++
> 2 files changed, 33 ins
On 18 November 2015 at 23:32, Peter Hurley wrote:
> Hi Baolin,
>
> On 11/16/2015 02:05 AM, Baolin Wang wrote:
>> It dose not work when we want to use the usb-to-serial port based
>> on one usb gadget as a console. Thus this patch adds the console
>> initialization to support this request.
>
> I ha
Hi,
If this isn't the correct mailing list for this question, do let me know
if there's a better one where I could ask.
I have a C language program that talks to modems and these days it is
almost always a USB modem. For diagnostic purposes, I would like to be
able to pass the modem's file p
On Wed, 2015-11-18 at 18:56 -0800, ToddA wrote:
> Hi,
>
> If this isn't the correct mailing list for this question, do let me
> know
> if there's a better one where I could ask.
>
> I have a C language program that talks to modems and these days it is
> almost always a USB modem. For diagnostic
Hi,
On Tue, 2015-11-17 at 13:58 +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 11/17/2015 12:18 PM, Chunfeng Yun wrote:
>
> > add a DT binding documentation of xHCI host controller for the
> > MT8173 SoC from Mediatek.
> >
> > Signed-off-by: Chunfeng Yun
> > ---
> > .../devicetree/bindings/usb/
When choose randconfig for kernel build, it reports below warning:
"warning: (USB_OTG_FSM && FSL_USB2_OTG && USB_MV_OTG) selects USB_OTG
which has unmet direct dependencies (USB_SUPPORT && USB && PM)"
In fact, USB_OTG is visible symbol and depends on PM, so the driver
needs to depend on it to redu
From: Bjørn Mork
Date: Wed, 18 Nov 2015 21:13:07 +0100
> Thomas reports
...
> Reported-by: Thomas Schäfer
> Signed-off-by: Bjørn Mork
Applied and queued up for -stable, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.k
Hi,
Rob Herring writes:
> On Wed, Nov 18, 2015 at 5:02 PM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Rob Herring writes:
>>> On Wed, Nov 18, 2015 at 06:20:31PM +0530, Subbaraya Sundeep Bhatta wrote:
This patch adds binding doc for Xilinx DWC3 glue driver.
Signed-off-by: Subbaraya Sund
On Wed, Oct 21, 2015 at 10:39:00AM +0800, Peter Chen wrote:
> On Tue, Oct 20, 2015 at 02:09:38PM -0200, Fabio Estevam wrote:
> > Hi Peter,
> >
> > On Mon, Oct 19, 2015 at 12:50 AM, Peter Chen
> > wrote:
> >
> > > Add linux-usb.
> > >
> > > Patryk, your problem is you may need to open 24M OSC fo
On Wed, 18 Nov 2015 17:58:56 -0600
Josh Cartwright wrote:
> On Wed, Nov 18, 2015 at 11:05:44PM +0200, Ioan-Adrian Ratiu wrote:
> > On Wed, 18 Nov 2015 21:37:42 +0100 (CET)
> > Jiri Kosina wrote:
> >
> > > On Wed, 18 Nov 2015, Ioan-Adrian Ratiu wrote:
> > >
> > > > The critical section prot
>
>> +{
>> + struct gscons_info *info = gserial_cons.data;
>> + int port_num = gserial_cons.index;
>> + struct usb_request *req;
>> + struct gs_port *port;
>> + struct usb_ep *ep;
>> +
>> + if (port_num >= MAX_U_SERIAL_PORTS || port_num < 0) {
>> + pr_err("%s: po
Hi Felipe and others,
This patch set adds multiple queue support for gadget sourcesink
function, it adds additional two parameters for both bulk and iso
transfer, the default value is current setting.
Changes for v2:
- Rebase to latest v4.4-rc1
- Agree Krzysztof's suggestion, and add patch 4/4 to
Add both bulk and iso depth of queue entries.
Signed-off-by: Peter Chen
---
Documentation/ABI/testing/configfs-usb-gadget-sourcesink | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/ABI/testing/configfs-usb-gadget-sourcesink
b/Documentation/ABI/testing/configfs-usb-gadget-sou
1 - 100 of 103 matches
Mail list logo
