Re: query on DWC3

2014-12-13 Thread sundeep subbaraya
Hi Paul, As per my understanding, for BULK OUT we do queue a request with 512 bytes length since we do not know the length of the transfer Host is going to send. For Control OUT we know the length in wLength of Setup packet, hence I assumed there is no difference in programming model of Control IN

Re: [PATCH v5 2/3] i2c: add support for Cypress CYUSBS234 USB-I2C adapter

2014-12-13 Thread Varka Bhadram
On Saturday 13 December 2014 05:17 PM, Muthu Mani wrote: Adds support for USB-I2C interface of Cypress Semiconductor CYUSBS234 USB-Serial Bridge controller. The read/write operation is setup using vendor command through control endpoint and actual data transfer happens through bulk in/out endpo

Re: [PATCH v5 3/3] gpio: add support for Cypress CYUSBS234 USB-GPIO adapter

2014-12-13 Thread Varka Bhadram
On Saturday 13 December 2014 05:17 PM, Muthu Mani wrote: Adds support for USB-GPIO interface of Cypress Semiconductor CYUSBS234 USB-Serial Bridge controller. The GPIO get/set can be done through vendor command on control endpoint for the configured gpios. Details about the device can be found

RE: query on DWC3

2014-12-13 Thread Paul Zimmerman
> From: linux-usb-ow...@vger.kernel.org > [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of sundeep subbaraya > Sent: Friday, December 12, 2014 9:13 PM > > Hi Felipe, > > In DWC3 driver, for three stage Control OUT transfer there is a check: > >else if (!IS_ALIGNED(req->request.length,

Re: [PATCH v7 2/5] phy: add a driver for the Rockchip SoC internal USB2.0 PHY

2014-12-13 Thread Doug Anderson
Hi, On Fri, Dec 12, 2014 at 11:24 PM, Kishon Vijay Abraham I wrote: > hi, > > On Saturday 13 December 2014 05:49 AM, Doug Anderson wrote: >> Yunzhi, >> >> On Fri, Dec 12, 2014 at 7:07 AM, Yunzhi Li wrote: >>> This patch to add a generic PHY driver for ROCKCHIP usb PHYs, >>> currently this driver

Re: Re: ch341.c does not work with new ch34x devices

2014-12-13 Thread Karl Palsson
I'm seeing this as well, I've got some work in progress towards this, but not finding the time I'd hoped. CH340 devices work "fine" with the current linux driver, but CH341, very very very flaky, if at all.

Re: How do I begin?

2014-12-13 Thread Greg KH
On Sat, Dec 13, 2014 at 11:23:23PM +0530, Vedant Nevetia wrote: > Thanks a lot! How would you recommend I then go on to submit > full-scale drivers? Should I read through the whole of LDD3 or is > there another means to acquire the knowledge? Why not try working on tiny things first, the odds of y

Re: How do I begin?

2014-12-13 Thread Vedant Nevetia
Thanks a lot! How would you recommend I then go on to submit full-scale drivers? Should I read through the whole of LDD3 or is there another means to acquire the knowledge? On Sat, Dec 13, 2014 at 9:06 PM, Greg KH wrote: > On Sat, Dec 13, 2014 at 08:45:28PM +0530, Vedant Nevetia wrote: > > > > F

Re: ch341.c does not work with new ch34x devices

2014-12-13 Thread Liangent
I'm connecting it to an external modem on the RS232 side. If I use some other program to connect to the modem, it reports "modem not responding". To debug further I'm minicom'ing to it. Once connected, I type "AT" then press Enter. Screen output is pasted below (with Local Echo set to No and Hex Di

usb2 and usb3 ports drop samples while recording from airspy to /dev/null

2014-12-13 Thread Udo van den Heuvel
Hello, I noticed an usb related issue when recording from my airspy device; so I created a bug in the bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=89671 Please let me know what info I should add to help find the root cause. Kind regards, Udo -- To unsubscribe from this list: send the li

Re: ch341.c does not work with new ch34x devices

2014-12-13 Thread Greg KH
On Sat, Dec 13, 2014 at 01:15:07PM +0800, Liangent wrote: > Hello, > > I bought a new USB-RS232 cable and the system loads ch341.ko for me > (Debian with kernel 3.14-2-amd64 and 3.16.0-4-amd64). However this > module does not work with my cable (/dev/ttyUSB0 appears but the > serial device doesn't

Re: How do I begin?

2014-12-13 Thread Greg KH
On Sat, Dec 13, 2014 at 01:04:48PM +0530, Vedant Nevetia wrote: > Hello, > > I am sorry if this has been posted by someone else before. I'd really > like some help. > > So a little background: I'm a 17 year old Linux enthusiast. I've > always wanted to contribute in any way to the kernel. Now I f

Re: [PATCH v4 2/3] i2c: add support for Cypress CYUSBS234 USB-I2C adapter

2014-12-13 Thread Wolfram Sang
> For repeated start (Sr) scenario, the STOP bit will not be set. For > dummy write scenario (writing EEPROM address from I2C EEPROM slave), > the STOP bit should not be set. But, for normal I2C write, the STOP > bit should be set. We provide control to user to control when to > STOP/NAK to handle

[PATCH v5 2/3] i2c: add support for Cypress CYUSBS234 USB-I2C adapter

2014-12-13 Thread Muthu Mani
Adds support for USB-I2C interface of Cypress Semiconductor CYUSBS234 USB-Serial Bridge controller. The read/write operation is setup using vendor command through control endpoint and actual data transfer happens through bulk in/out endpoints. Details about the device can be found at: http://www.

[PATCH v5 1/3] mfd: add support for Cypress CYUSBS234 USB Serial Bridge controller

2014-12-13 Thread Muthu Mani
Adds support for USB-I2C/GPIO interfaces of Cypress Semiconductor CYUSBS234 USB-Serial Bridge controller. Details about the device can be found at: http://www.cypress.com/?rID=84126 Separate cell drivers are available for I2C and GPIO. SPI and UART are not supported yet. Signed-off-by: Muthu Man

[PATCH v5 3/3] gpio: add support for Cypress CYUSBS234 USB-GPIO adapter

2014-12-13 Thread Muthu Mani
Adds support for USB-GPIO interface of Cypress Semiconductor CYUSBS234 USB-Serial Bridge controller. The GPIO get/set can be done through vendor command on control endpoint for the configured gpios. Details about the device can be found at: http://www.cypress.com/?rID=84126 Signed-off-by: Muthu