On Mon, 2016-02-15 at 18:49 -0800, Keith Packard wrote:
> Call signal_pending before reading a chunk of data from the device so
> that long read operations can be interrupted with a signal.
Hi,
why is this needed? You are doing this right after a
mutex_lock_interruptible().
Regards
From: Peter Chen
Although most of USB devices are hot-plug's, there are still some devices
are hard wired on the board, eg, for HSIC and SSIC interface USB devices.
If these kinds of USB devices are multiple functions, and they can supply
other interfaces like i2c, gpios for other devices, we may
On Mon, 2016-02-15 at 16:43 -0800, Greg KH wrote:
> On Tue, Feb 16, 2016 at 12:37:57AM +, fx IWATA NOBUO wrote:
> > My requirement is more device can be attached than 31 to connect
> > many IoT devices.
>
> That's an odd requirement to use the USB protocol for, especially when
> that is a har
On Sat, Feb 06, 2016 at 10:57:06PM +0800, weiyj...@163.com wrote:
> From: Wei Yongjun
>
> In case of error, the function usb_phy_generic_register()
> returns ERR_PTR() and never returns NULL. The NULL test in
> the return value check should be replaced with IS_ERR().
>
> Signed-off-by: Wei Yongj
Hi,
On Mon, Feb 15, 2016 at 04:30:18PM +0100, Oliver Neukum wrote:
> On Thu, 2016-02-11 at 15:50 +0200, Heikki Krogerus wrote:
> > Because USB Type-C ports (DRP ones) will select the data role randomly
> > when you connect (to an other DRP port). USB Type-C spec defines that
> > you can "prefer" h
Arnd Bergmann writes:
> The barriers on a spinlock synchronize between CPUs but not an external
> bus, so (on some architectures) a spinlock protecting an MMIO register
> does not guarantee that two CPUs doing
>
> spin_lock();
> __raw_writel(address);
> __raw_writel(data);
>
Hi,
in this commit you introduce a poll method that bails
out if you poll a disconnected device. That is good
but a bit insufficient. Poll needs to learn that a device
is going away. usbtmc_disconnect() needs to call wakeup_all()
on data->waitq
Regards
Oliver
--
To unsub
Hi,
Do you have any feedback on this change?
Regards,
Thang Q. Nguyen -
-Original Message-
From: Thang Q. Nguyen [mailto:tqngu...@apm.com]
Sent: Monday, January 25, 2016 9:26 PM
To: Felipe Balbi; Greg Kroah-Hartman; linux-usb@vger.kernel.org;
linux-o...@vger.kernel.org; linux-ker...@vger.k
Hi,
Do you have any more feedback on this patch?
Thanks,
Thang Q. Nguyen -
-Original Message-
From: Thang Q. Nguyen [mailto:tqngu...@apm.com]
Sent: Monday, January 25, 2016 9:26 PM
To: Felipe Balbi; Greg Kroah-Hartman; linux-usb@vger.kernel.org;
linux-o...@vger.kernel.org; linux-ker...@vge
Hi,
you make USB_APPLEDISPLAY depend on HAS_IOMEM.
I am afraid you got it the wrong way round. There
is really no reason for a high level USB driver
to access memory.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a
On Tuesday 16 February 2016 10:26:14 Krzysztof Hałasa wrote:
> Arnd Bergmann writes:
>
> > The barriers on a spinlock synchronize between CPUs but not an external
> > bus, so (on some architectures) a spinlock protecting an MMIO register
> > does not guarantee that two CPUs doing
> >
> > sp
On 02/16/2016 12:00 PM, Oliver Neukum wrote:
Hi,
you make USB_APPLEDISPLAY depend on HAS_IOMEM.
I am afraid you got it the wrong way round. There
is really no reason for a high level USB driver
to access memory.
Alright, let's have a look. The warning I was fixing in this patch was:
warni
On 02/15/2016 09:38 PM, Vegard Nossum wrote:
On 02/15/2016 01:28 PM, Geert Uytterhoeven wrote:
On Mon, Feb 15, 2016 at 12:49 PM, Vegard Nossum
wrote:
On 02/15/2016 12:21 PM, Geert Uytterhoeven wrote:
[...]
Assuming this still lets the platform actually run USB drivers (which it
looks like
Arnd Bergmann writes:
> Both writes leave the CPU core within the spinlock but are not serialized
> with anything else, so there is no ordering between the CPUs when they
> enter the shared bus, other than having address before data. You'd
> expect to see address0, data0, address1, data1, but it
On Tue, 2016-02-16 at 11:22 +0200, Heikki Krogerus wrote:
> > That question has not been answered. It would be awkward for the OS
> > to find itself in the slave role, which it is ill equipped for. So
> > the data role should be switched before the new device is announced
> > to user space. How is
On Tuesday 16 February 2016 14:24:10 Krzysztof Hałasa wrote:
> Arnd Bergmann writes:
>
> > Both writes leave the CPU core within the spinlock but are not serialized
> > with anything else, so there is no ordering between the CPUs when they
> > enter the shared bus, other than having address befor
Hi
Most of my concerns are due to the early printk restrictions.
As you say in the documentation:
"Keep in mind that things such as interrupt, system memory, DMA memory,
PCI configure space access, etc., are all different from a normal device
driver."
I don't know the details of these subsystems
Hi,
John Youn writes:
> On 2/12/2016 2:05 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> John Youn writes:
>>> On 2/10/2016 1:07 PM, Felipe Balbi wrote:
John Youn writes:
>>> Basically assign all the resources in advance.
>>
>> I thought about that, but wouldn't this, essentially,
Hi Greg,
Some platforms don't have DMA, but we should still be able to build USB
drivers for these platforms. They could still be used through vhci_hcd,
usbip_host, or maybe something like USB passthrough in UML from a
capable host.
This patch series allows to compile USB on platforms whe
Some platforms don't have DMA, but we should still be able to build USB
drivers for these platforms. They could still be used through vhci_hcd,
usbip_host, or maybe something like USB passthrough in UML from a
capable host.
If NO_DMA=y:
ERROR: "dma_pool_destroy" [drivers/usb/core/usbcore.ko]
If NO_DMA=y:
ERROR: "bad_dma_ops" [drivers/usb/host/xhci-plat-hcd.ko] undefined!
ERROR: "bad_dma_ops" [drivers/usb/host/xhci-mtk.ko] undefined!
ERROR: "dma_pool_destroy" [drivers/usb/host/xhci-hcd.ko] undefined!
ERROR: "bad_dma_ops" [drivers/usb/host/xhci-hcd.ko] undefined!
ERR
If NO_DMA=y:
ERROR: "usb_gadget_map_request" [drivers/usb/dwc2/dwc2.ko] undefined!
ERROR: "usb_gadget_unmap_request" [drivers/usb/dwc2/dwc2.ko] undefined!
ERROR: "bad_dma_ops" [drivers/usb/dwc2/dwc2.ko] undefined!
Add a dependency on HAS_DMA to fix this.
Signed-off-by: Geert Uytterho
On Tue, 2016-02-16 at 13:12 +0100, Vegard Nossum wrote:
> Alright, let's have a look. The warning I was fixing in this patch
> was:
>
> warning: (USB_APPLEDISPLAY) selects BACKLIGHT_LCD_SUPPORT which
> has
> unmet direct dependencies (HAS_IOMEM)
>
> The problem is that USB_APPLEDISPLAY has
Hello Rob,
is there any follow-up on this one?
Thanks
Petr
On 12.02.2016 18:24, Petr Kulhavy wrote:
On 12.02.2016 17:21, Rob Herring wrote:
On Thu, Feb 11, 2016 at 12:01:06PM +0100, Petr Kulhavy wrote:
+ - mentor,power : Specifies the maximum current in milliamperes the
controller can
+
I get some warnings at boot on all kernels I've tried. On 4.5-rc4, I see:
[0.229429] usbcore: registered new interface driver usbfs
[0.229436] usbcore: registered new interface driver hub
[0.229451] usbcore: registered new device driver usb
[1.057998] xhci_hcd :00:14.0: xHCI H
Hello,
2016-02-16 15:10 GMT-03:00 Tiago Natel de Moura :
> Hello folks,
>
> The patch have some problem with the c-mode-hook setup, in the usage of
> c-cleanup-list. On my emacs24 it throw the following error:
>
> "Invalid indentation setting for symbol c-cleanup-list"
>
> After talk with Geyslan,
This patch adds kernel-dot-emacs.txt (elisp) which deliver best
indentation, comments and white space highlighting functionalities.
This also changes the CodingStyle and 00-INDEX files by referencing
the new kernel-dot-emacs.
Signed-off-by: Geyslan G. Bem
Reviewed-by: Tiago Natel de Moura
---
Oliver Neukum writes:
> why is this needed? You are doing this right after a
> mutex_lock_interruptible().
When the device isn't contended, this mutex will never block and so
mutex_lock_interruptible will never check for a signal.
I had mistakenly assumed that usb_bulk_msg would abort when a si
On Fri, Feb 12, 2016 at 11:26 AM, Sergei Shtylyov
wrote:
> Hello.
>
>
> On 02/12/2016 07:21 PM, Rob Herring wrote:
>
>>> This adds DT support for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver.
>>>
>>> Signed-off-by: Petr Kulhavy
>>> ---
>>> .../devicetree/bindings/usb/da8xx-usb.txt |
On Fri, Feb 12, 2016 at 11:24 AM, Petr Kulhavy wrote:
>
> On 12.02.2016 17:21, Rob Herring wrote:
>>
>> On Thu, Feb 11, 2016 at 12:01:06PM +0100, Petr Kulhavy wrote:
>>>
>>> + - mentor,power : Specifies the maximum current in milliamperes the
>>> controller can
>>> + supply in host mode.
>>
>>
Hi,
John Youn writes:
> The assignement of EP transfer resources was not handled properly in the
> dwc3 driver. Commit aebda6187181 ("usb: dwc3: Reset the transfer
> resource index on SET_INTERFACE") previously fixed one aspect of this
> where resources may be exhausted with multiple calls to SE
On 2016-02-08 15:31, Mathias Nyman wrote:
> Hi
>
> On 06.02.2016 19:08, Mike Murdoch wrote:
>> Bug ID: 111251
>>
>> Hello,
>>
>> I have a NEC uPD720200 USB3.0 controller in a Thinkpad W520 laptop on
>> kernel 4.4.1-gentoo.
>>
>> 0e:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host
>> Co
On 2/16/2016 1:28 PM, Felipe Balbi wrote:
>
> Hi,
>
> John Youn writes:
>> The assignement of EP transfer resources was not handled properly in the
>> dwc3 driver. Commit aebda6187181 ("usb: dwc3: Reset the transfer
>> resource index on SET_INTERFACE") previously fixed one aspect of this
>> wher
This series contains two fixes for the host in Descriptor DMA mode.
Tang, Jianqiang (1):
usb: dwc2: host: fix the data toggle error in full speed descriptor
dma
Vardan Mikayelyan (1):
usb: dwc2: host: fix logical omissions in dwc2_process_non_isoc_desc
drivers/usb/dwc2/hcd_ddma.c | 23 +
From: Vardan Mikayelyan
Fixes memory manipulation issues and makes Host DDMA bulk transfers
work.
dwc2_process_non_isoc_desc() must return non zero value ONLY when
failure happens in one of the queued descriptors. After receiving
non zero value the caller must stop processing of remaining
QTDs a
From: Vardan Mikayelyan
Fixes memory manipulation issues and makes Host DDMA bulk transfers
work.
dwc2_process_non_isoc_desc() must return non zero value ONLY when
failure happens in one of the queued descriptors. After receiving
non zero value the caller must stop processing of remaining
QTDs a
From: Tang, Jianqiang
There will be data toggle error happen for full speed buld-out transfer.
The data toggle bit is saved in qh for non-control transfers, it is wrong
to check the qtd for that case.
Also fix one static analysis tool issue after fix the data toggle error.
John Youn:
* Added W
Sorry, messed up the emails. V2 is just a resend with e-mails fixed up.
This series contains two fixes for the host in Descriptor DMA mode.
v2:
* Resend with proper e-mails
Tang, Jianqiang (1):
usb: dwc2: host: fix the data toggle error in full speed descriptor
dma
Vardan Mikayelyan (1):
On Sun, Feb 14, 2016 at 05:20:21PM -0800, Greg Kroah-Hartman wrote:
> On Wed, Feb 10, 2016 at 04:13:43PM -0800, Victor Dodon wrote:
> > The US_DEBUGPX macro uses printk without specifying a kernel log level, so
> > the default kernel log level is used, which may not match LOGLEVEL_DEBUG
> > used in
On Tue, Feb 16, 2016 at 03:45:39PM -0800, Victor Dodon wrote:
> On Sun, Feb 14, 2016 at 05:20:21PM -0800, Greg Kroah-Hartman wrote:
> > On Wed, Feb 10, 2016 at 04:13:43PM -0800, Victor Dodon wrote:
> > > The US_DEBUGPX macro uses printk without specifying a kernel log level, so
> > > the default ke
From: Bjørn Mork
Date: Fri, 12 Feb 2016 16:42:14 +0100
> Thomas reports:
>
> T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=05c6 ProdID=6001 Rev=00.00
> S: Manufacturer=USB Modem
> S: Product=USB Mod
On Tue, Feb 16, 2016 at 10:01:13AM -0800, Andy Lutomirski wrote:
> I get some warnings at boot on all kernels I've tried. On 4.5-rc4, I see:
>
> [0.229429] usbcore: registered new interface driver usbfs
> [0.229436] usbcore: registered new interface driver hub
> [0.229451] usbcore: re
On Wed, Feb 10, 2016 at 11:33:18AM +0100, Oliver Neukum wrote:
> Some devices I got show an inability to operate right after
> power on if they are already connected. They are beyond recovery
> if the descriptors are requested multiple times. So in case of
> a timeout we rather bail early and reset
The assignement of EP transfer resources was not handled properly in the
dwc3 driver. Commit aebda6187181 ("usb: dwc3: Reset the transfer
resource index on SET_INTERFACE") previously fixed one aspect of this
where resources may be exhausted with multiple calls to SET_INTERFACE.
However, it introduc
On Tue, Feb 16, 2016 at 6:33 PM, Greg Kroah-Hartman
wrote:
> On Tue, Feb 16, 2016 at 10:01:13AM -0800, Andy Lutomirski wrote:
>> I get some warnings at boot on all kernels I've tried. On 4.5-rc4, I see:
>>
>> [0.229429] usbcore: registered new interface driver usbfs
>> [0.229436] usbcore:
Hi All,
I would like to contribute to Linux USB kernel but i am confused on
where to start,
If possible can you guys guide me regarding where to find the TODO
list, so that I can start on with small patches.
Thanking All.
--
Regards,
Anil Nair
--
To unsubscribe from this list: send the line "un
On Wed, Feb 17, 2016 at 11:47:56AM +0530, Anil Nair wrote:
> Hi All,
>
> I would like to contribute to Linux USB kernel but i am confused on
> where to start,
If you don't know where to start, or what to do, why do you want to
contribute?
> If possible can you guys guide me regarding where to fi
Hi,
On Wed, Feb 17, 2016 at 12:00 PM, Greg KH wrote:
> On Wed, Feb 17, 2016 at 11:47:56AM +0530, Anil Nair wrote:
>> Hi All,
>>
>> I would like to contribute to Linux USB kernel but i am confused on
>> where to start,
>
> If you don't know where to start, or what to do, why do you want to
> contr
On Tue, Feb 16, 2016 at 02:39:47PM +0100, Oliver Neukum wrote:
> On Tue, 2016-02-16 at 11:22 +0200, Heikki Krogerus wrote:
> > > That question has not been answered. It would be awkward for the OS
> > > to find itself in the slave role, which it is ill equipped for. So
> > > the data role should be
49 matches
Mail list logo
