On Thu, Jun 15, 2017 at 08:08:19AM -0700, Guenter Roeck wrote:
> On Mon, Jun 12, 2017 at 05:40:08PM +0300, Heikki Krogerus wrote:
> > UCSI - USB Type-C Connector System Software Interface - is a
> > specification that defines set of registers and data
> > structures for controlling the USB Type-C p
Hi,
This moves the current ucsi driver from drivers/usb/misc/ucsi.c to the
new USB Type-C class (drivers/usb/typec/). That allows us to finally do
role swapping.
The driver is now split into core library part, and ACPI driver. That
should make it easy to add support for other interface methods (f
UCSI - USB Type-C Connector System Software Interface - is a
specification that defines set of registers and data
structures for controlling the USB Type-C ports. It's
designed for systems where an embedded controller (EC) is in
charge of the USB Type-C PHY or USB Power Delivery
controller. It is d
Driver for ACPI UCSI interface method. This driver replaces
the previous UCSI driver drivers/usb/misc/ucsi.c.
Signed-off-by: Heikki Krogerus
Reviewed-by: Guenter Roeck
---
drivers/usb/misc/Kconfig | 26 --
drivers/usb/misc/Makefile | 1 -
drivers/usb/misc/ucsi.c
On 15.06.2017 23:53, Ian Pilcher wrote:
On 06/15/2017 03:17 PM, Greg KH wrote:
wait_usec is a count here:
Well ... I was trying to convert it into a parameter that was less
confusing. I've eliminated it in "suggestion v2" below.
You aren't sleeping any :(
Oh $DIETY!
Always return real e
On 6/9/2017 4:15 PM, Mathias Nyman wrote:
> I think it's valid to check if the endpoint is already stopped from the
> endpoint context, and not
> queue a stop endpoint command for a already stopped endpoint. Especially as
> your hardware can't handle it.
> That code makes sense.
>
Thank you Ma
On 16.06.2017 11:58, Shyam Sundar S K wrote:
On 6/9/2017 4:15 PM, Mathias Nyman wrote:
I think it's valid to check if the endpoint is already stopped from the
endpoint context, and not
queue a stop endpoint command for a already stopped endpoint. Especially as
your hardware can't handle it.
commit 46ddd79e893b ("usb: gadget: udc: atmel: Remove AVR32 bits from the
driver") left the accessor macros introduced by commit a3dd3befd7cb ("usb:
gadget: atmel_usba: use endian agnostic IO on ARM"). They can now be
removed.
Signed-off-by: Alexandre Belloni
---
drivers/usb/gadget/udc/atmel_usb
The following changes since commit 32c1431eea4881a6b17bd7c639315010aeefa452:
Linux 4.12-rc5 (2017-06-11 16:48:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git
tags/usb-serial-4.12-rc6
for you to fetch changes up to 996fab5
commit b3addcf0d1f04f53fcc302577d5a5e964c18531a upstream.
Currently VBUS is turned off while a usb device is detached, and turned
on again by the polling routine. This short period VBUS loss prevents
usb modem to switch mode.
VBUS should be constantly on for host-only mode, so this changes the
dr
From: Hayes Wang
Date: Fri, 16 Jun 2017 03:29:01 +
> David Miller [mailto:da...@davemloft.net]
>> Sent: Wednesday, June 14, 2017 1:02 AM
>> > v2:
>> > For #1, replace GFP_KERNEL with GFP_NOIO for usb_submit_urb().
>> >
>> > v1:
>> > Improve the flow about runtime suspend/resume and make the c
From: Peter Ujfalusi
Instead of requesting the DMA channel in tusb_omap_dma_allocate() do it
when the controller is created and in runtime work from the DMA channel
pool.
This change is needed for the DMAengine conversion of the driver since the
tusb_omap_dma_allocate() is called in interrupt co
From: Peter Ujfalusi
Having one musb_ep_select() instead the two calls in if/else is the same
thing, but makes the code a bit simpler to follow.
Signed-off-by: Peter Ujfalusi
Tested-by: Tony Lindgren
Signed-off-by: Bin Liu
---
drivers/usb/musb/tusb6010_omap.c | 3 +--
1 file changed, 1 inser
From: Peter Ujfalusi
When the port_window support was verified it was done on setup where only
the MEM_TO_DEV direction was enabled. This got un-noticed and thus only
this direction worked.
Now that I have managed to get a setup to verify both direction it turned
out that the setup was incorrect
From: Peter Ujfalusi
For the DMA we have ch (channel), dmareq and sync_dev parameters both
within the tusb_omap_dma_ch and tusb_omap_dma struct.
By creating a common struct the code can be simplified when selecting
between the shared or multichannel DMA parameters.
Signed-off-by: Peter Ujfalusi
Hi Greg,
These musb patches are for next v4.13-rc1. Most of them are for converting to
use DMAengine API in tmusb6010_omap, but one is to clarify a log message in
musb-cppi41. Please let me know if any change is needed.
Regards,
-Bin.
---
Alexandre Bailon (1):
usb: musb: musb_cppi41: Defer pro
From: Peter Ujfalusi
For tusb6010 the DMA functionality only possible if the buffer is 32bit
aligned (SYNC access to FIFO) since with ASYNC access the TX/RX offset
registers will corrupt eventually.
The MUSB_G_NO_SKB_RESERVE will set the quirk_avoids_skb_reserve flag in
usb_gadget struct to provi
From: Peter Ujfalusi
When using the g_ncm for networking this flag will make sure that the
buffer is aligned to 32bit so the DMA can be used to offload the data
movement.
Signed-off-by: Peter Ujfalusi
Tested-by: Tony Lindgren
Signed-off-by: Bin Liu
---
drivers/usb/musb/tusb6010.c | 3 ++-
1
From: Peter Ujfalusi
The external request lines are used by tusb6010 on OMAP24xx platforms.
Update the map so the driver can use dmaengine API to request the DMA
channel. At the same time add temporary map containing only the external
DMA request numbers for DT booted case on omap24xx since the t
From: Peter Ujfalusi
With the port_window support in DMAengine and the sDMA driver we can
convert the driver to DMAengine.
Signed-off-by: Peter Ujfalusi
Tested-by: Tony Lindgren
Signed-off-by: Bin Liu
---
drivers/usb/musb/tusb6010_omap.c | 201 ---
1 file
From: Peter Ujfalusi
Handle the DMA TX in a similar way as we do for the RX: in the DMA
completion callback.
Since we are no longer using DMA completion interrupt for the TX we can as
wall keep these interrupts disabled, but keep the handler for debug
purposes.
Signed-off-by: Peter Ujfalusi
Te
From: Alexandre Bailon
If dma_request_slave_channel() failed to return a channel,
then the driver will print an error and request to defer probe,
regardless of the cause of the failure.
Defer if the DMA is not ready yet otherwise print an error.
Signed-off-by: Alexandre Bailon
Reviewed-by: Joha
On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng
wrote:
> On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern
> wrote:
>> Those documents refer to a hardware bug with a workaround in the BIOS.
>> Have you checked to see if your BIOS is up to date?
>
> Yes, it's up to date.
>
Alan, I re-sent a patch but
On Sat, 17 Jun 2017, Kai-Heng Feng wrote:
> On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng
> wrote:
> > On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern
> > wrote:
> >> Those documents refer to a hardware bug with a workaround in the BIOS.
> >> Have you checked to see if your BIOS is up to date?
>
On 06/15/2017 02:09 AM, Srinath Mannam wrote:
> Corrected the register to check the 64-bit pointer
> capability state. 64-bit pointer implementation capability
> was checking in wrong register, which causes the BDC
> enumeration failure in 64-bit memory address.
>
> Fixes: efed421a94e6 ("usb: gadg
On Fri, Jun 16, 2017 at 11:21:24AM +0300, Heikki Krogerus wrote:
> UCSI - USB Type-C Connector System Software Interface - is a
> specification that defines set of registers and data
> structures for controlling the USB Type-C ports. It's
> designed for systems where an embedded controller (EC) is
26 matches
Mail list logo
