On Fri, Feb 17, 2017 at 10:07:11AM +0200, Felipe Balbi wrote:
> Janusz Dziedzic writes:
> > This reverts commit ac670a3a650b899fc020b81f63e810d06015b865.
> >
> > This introduce bug we already fixed in
> > commit 53642399aa71 ("usb: gadget: f_fs: Fix wrong check
On Fri, Feb 17, 2017 at 06:05:08PM +0100, Pavel Machek wrote:
> On Fri 2017-02-17 17:37:47, Thomas Gleixner wrote:
> > On Fri, 17 Feb 2017, Frederic Weisbecker wrote:
> > > On Thu, Feb 16, 2017 at 08:34:45PM +0100, Thomas Gleixner wrote:
> > > > On Thu, 16 Feb 2017, Frederic Weisbecker wrote:
> >
On Fri, Feb 17, 2017 at 08:35:35PM +0530, Sriram V wrote:
> Hi Greg,
>
> I am planning to buy multiple devices. Therefore, I wanted to find out
> if there exists a universal driver or we need to do customisations.
Again, it all depends on the device itself. There is a standard spec,
but not all
On Fri 2017-02-17 17:37:47, Thomas Gleixner wrote:
> On Fri, 17 Feb 2017, Frederic Weisbecker wrote:
> > On Thu, Feb 16, 2017 at 08:34:45PM +0100, Thomas Gleixner wrote:
> > > On Thu, 16 Feb 2017, Frederic Weisbecker wrote:
> > > > On Thu, Feb 16, 2017 at 10:20:14AM -0800, Linus Torvalds wrote:
>
On Fri, 17 Feb 2017, Frederic Weisbecker wrote:
> On Thu, Feb 16, 2017 at 08:34:45PM +0100, Thomas Gleixner wrote:
> > On Thu, 16 Feb 2017, Frederic Weisbecker wrote:
> > > On Thu, Feb 16, 2017 at 10:20:14AM -0800, Linus Torvalds wrote:
> > > > On Thu, Feb 16, 2017 at 10:13 AM, Frederic Weisbecker
On 17/02/2017 at 16:12:50 +0100, Romain Izard wrote:
> This reverts commit cab43282682e ("ARM: at91/dt: sama5d2: Use new
> compatible for ohci node")
>
> It depends from commit 7150bc9b4d43 ("usb: ohci-at91: Forcibly suspend
> ports while USB suspend") which was reverted and implemented
>
This reverts commit cab43282682e ("ARM: at91/dt: sama5d2: Use new
compatible for ohci node")
It depends from commit 7150bc9b4d43 ("usb: ohci-at91: Forcibly suspend
ports while USB suspend") which was reverted and implemented
differently. With the new implementation, the compatible string must
Hi Greg,
I am planning to buy multiple devices. Therefore, I wanted to find out
if there exists a universal driver or
we need to do customisations.
The driver sources lists only 17 devices which are supported.
Therefore, the question.
I thought there is a standard like the keyboard/mouse. which
On Fri, Feb 17, 2017 at 04:56:38PM +0530, Sriram V wrote:
> Hi,
>
> I wanted to check if the linux kernel support
> (drivers/input/touchscreen/usbtouchscreen.c) supports all the usb
> based touch screen
> like the standard usb mouse/keyboard
>
> Or is there any vendor specific drivers need to be
On Thu, Feb 16, 2017 at 08:06:04PM +0100, Pavel Machek wrote:
> On Thu 2017-02-16 18:25:35, Pavel Machek wrote:
> > Hi!
> >
> > > > > 4.10-rc4 broken
> > > > > 4.10-rc3 ok
> > > >
> > > > Hmm. If those actually end up being reliable, then there's not a whole
> > > > lot in between them wrt PCI
On Thu, Feb 16, 2017 at 08:34:45PM +0100, Thomas Gleixner wrote:
> On Thu, 16 Feb 2017, Frederic Weisbecker wrote:
> > On Thu, Feb 16, 2017 at 10:20:14AM -0800, Linus Torvalds wrote:
> > > On Thu, Feb 16, 2017 at 10:13 AM, Frederic Weisbecker
> > > wrote:
> > > >
> > > > I
Move usb_phy_generic_register() function call to the top, to simplify
error handling.
Replace kzalloc() with devm_kzalloc().
After platform_device_add(), if we error out, we must do
platform_device_unregister(), which also does the put. So lets move
devm_kzalloc() to simplify error handling and
On 17 February 2017 at 14:01, Vardan Mikayelyan
wrote:
> Move usb_phy_generic_register() function call to the top, to simplify
> error handling.
>
> Replace kzalloc() with devm_kzalloc().
>
> After platform_device_add(), if we error out, we must do
>
Move usb_phy_generic_register() function call to the top, to simplify
error handling.
Replace kzalloc() with devm_kzalloc().
After platform_device_add(), if we error out, we must do
platform_device_unregister(), which also does the put. So lets move
devm_kzalloc() to simplify error handling and
Hi,
I wanted to check if the linux kernel support
(drivers/input/touchscreen/usbtouchscreen.c) supports all the usb
based touch screen
like the standard usb mouse/keyboard
Or is there any vendor specific drivers need to be supported.
Regards,
Sriram
--
To unsubscribe from this list: send the
The code was fixed in
commit 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 wof
OS_DESC_EXT_COMPAT")
but the in-header documentation kept referencing 0 as the expected value.
Reference 1 instead as per original commit message.
Signed-off-by: Vincent Pelletier
Add device tree probing for fotg2-hcd driver
This device in a dual role hcd/otg device and it's used on Gemini Soc.
Currently all Gemini Soc based devices uses only the hcd part.
v2:
fix wrong name in MODULE_DEVICE_TABLE()
v3:
better commit message
remove dma_coerce_mask_and_coherent()
Hi Linus
On Fri, 10 Feb 2017, Linus Walleij wrote:
> On Thu, Feb 9, 2017 at 3:20 PM, Hans Ulli Kroll
> wrote:
>
> > Add device tree probe for fotg2 driver
> >
> > v2:
> > fix in wrong MODULE_DEVICE_TABLE
> >
> > Signed-off-by: Hans Ulli Kroll
If request was already started, this means we had to
stop the transfer. With that we also need to ignore
all TRBs used by the request, however TRBs can only
be modified after completion of END_TRANSFER
command. So what we have to do here is wait for
END_TRANSFER completion and only after that jump
On 02/17/2017 01:25 AM, Alexey Klimov wrote:
This patch creates new driver that supports StreamLabs usb watchdog
device. This device plugs into 9-pin usb header and connects to
reset pin and reset button on common PC.
USB commands used to communicate with device were reverse
engineered using
Hi Rob,
On Wed, 15 Feb 2017, Rob Herring wrote:
> On Wed, Feb 08, 2017 at 09:00:09PM +0100, Hans Ulli Kroll wrote:
> > This adds DT bindings for the Faraday FOTG2 host controller.
> >
> > Signed-off-by: Hans Ulli Kroll
> > ---
> >
This patch creates new driver that supports StreamLabs usb watchdog
device. This device plugs into 9-pin usb header and connects to
reset pin and reset button on common PC.
USB commands used to communicate with device were reverse
engineered using usbmon.
Signed-off-by: Alexey Klimov
Hi,
Baolin Wang writes:
>>> (One possible approach would be to have the setup routine return
>>> different values for explicit and implicit status stages -- for
>>> example, return 1 if it wants to submit an explicit status request.
>>> That wouldn't be very different
23 matches
Mail list logo