Re: [PATCH V2 0/6] remove the clock name from pdata

On Wed, Mar 27, 2013 at 9:14 PM, Felipe Balbi wrote: > Hi, > > On Mon, Mar 25, 2013 at 03:06:51AM -0400, Chao Xie wrote: >> The clock is defined by device, so the driver knows how many >> clocks needed by the device. >> The orignal way that passing the clock name by pdata is not correct. >> The fo

Re: [PATCH V2 3/6] usb: ehci: mv_ehci: remove unused clock

hi, Alan This is the patch for EHCI clock fix. Can you help to review and ack it? Thanks. On Mon, Mar 25, 2013 at 3:06 PM, Chao Xie wrote: > The origianl understanding of clock is wrong. The EHCI controller > only have one clock input. > Passing clock name by pdata is wrong. The clock is defined

Re: [PATCH V2 4/6] arm: mmp: remove clock from usb pdata for aspenite

hi, Haojian The patches correct the wrong usage of clock. It finally do not need pass clock by pdata. Can you help to review the patches relates to arch-mmp, and ack it?Thanks. On Mon, Mar 25, 2013 at 3:06 PM, Chao Xie wrote: > The clock name will directly get by driver. Removing > the name from

Re: usb video capture issue due to uvc_complete callback spends more time

On Wed, Mar 27, 2013 at 6:43 PM, B, Ravi wrote: > Hi > > I am observing issue while streaming video from usb camera connected to host > controller based on mentor graphics. The issue is root caused that there are > huge SOF gaps seen between the two isochronous IN token issued by host > control

Re: Renesas sparse errors

Hi Felipe > linux/drivers/usb/renesas_usbhs/common.c:313:17: error: incompatible types in > conditional expression (different base types) > linux/drivers/usb/renesas_usbhs/common.c:322:17: error: incompatible types in > conditional expression (different base types) > linux/drivers/usb/renesas_u

Re: [PATCH V2 4/6] arm: mmp: remove clock from usb pdata for aspenite

On Thu, Mar 28, 2013 at 8:59 AM, Chao Xie wrote: > hi, Haojian > The patches correct the wrong usage of clock. It finally do not need > pass clock by pdata. Can you help to review the patches relates to > arch-mmp, and ack it?Thanks. > > On Mon, Mar 25, 2013 at 3:06 PM, Chao Xie wrote: >> The clo

Re: [PATCH V2 5/6] arm: mmp: remove clock name from usb pdata for ttc

On Mon, Mar 25, 2013 at 3:06 PM, Chao Xie wrote: > The clock name will directly get by driver. Removing > the name from pdata. > > Signed-off-by: Chao Xie > --- > arch/arm/mach-mmp/ttc_dkb.c |6 -- > 1 files changed, 0 insertions(+), 6 deletions(-) > > diff --git a/arch/arm/mach-mmp/ttc_

RE: usb video capture issue due to uvc_complete callback spends more time

Laurent > > Hi Ravi, > > On Wednesday 27 March 2013 10:43:24 B, Ravi wrote: > > Hi > > > > I am observing issue while streaming video from usb camera connected to > host > > controller based on mentor graphics. The issue is root caused that there > > are huge SOF gaps seen between the two isochr

RE: [PATCH V4 1/2] usb: gadget/uvc: Port UVC webcam gadget to use videobuf2 framework

Hi Laurent, > -Original Message- > From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com] > Sent: Wednesday, March 27, 2013 11:25 PM > To: Bhupesh SHARMA > Cc: linux-usb@vger.kernel.org; ba...@ti.com; bhupesh.li...@gmail.com; > m...@pengutronix.de; gang.c...@asianux.com; tipec.

[PATCH V5 0/2] UVC webcam gadget related changes

This patchset tries to enhance the UVC webcam gadget driver and is based on Laurent's git tree available here (head uvc-gadget): git://linuxtv.org/pinchartl/uvcvideo.git Note that to ease review and integration of these patches, I have rebased them on Laurent's repo and all the relevant patches af

[PATCH V5 1/2] usb: gadget/uvc: Port UVC webcam gadget to use videobuf2 framework

This patch reworks the videobuffer management logic present in the UVC webcam gadget and ports it to use the "more apt" videobuf2 framework for video buffer management. To support routing video data captured from a real V4L2 video capture device with a "zero copy" operation on videobuffers (as the

[PATCH V5 2/2] usb: gadget/uvc: Add support for 'get_unmapped_area' for MMUless architectures

This patch adds the support for 'get_unmapped_area' in UVC gadget which is called when the 'mmap' system call is executed on MMUless architectures. Signed-off-by: Bhupesh Sharma Acked-by: Laurent Pinchart --- drivers/usb/gadget/uvc_queue.c | 18 ++ drivers/usb/gadget/uvc_v4l2.

[PATCH v4 4/6] ARM: OMAP: USB: Add phy binding information

In order for controllers to get PHY in case of non dt boot, the phy binding information should be added in the platform specific initialization code using phy_bind. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/mach-omap2/usb-musb.c |7 ++- 1 file changed, 6 insertions(+), 1 deletio

[PATCH v4 1/6] drivers: phy: add generic PHY framework

The PHY framework provides a set of APIs for the PHY drivers to create/destroy a PHY and APIs for the PHY users to obtain a reference to the PHY with or without using phandle. To obtain a reference to the PHY without using phandle, the platform specfic intialization code (say from board file) shoul

[PATCH v4 3/6] usb: otg: twl4030: use the new generic PHY framework

Used the generic PHY framework API to create the PHY. twl4030_usb_suspend and twl4030_usb_resume is added to phy_ops in order to align with the new framework. However using the old USB PHY library cannot be completely removed because OTG is intertwined with PHY and moving to the new framework comp

[PATCH v4 0/6] Generic PHY Framework

Added a generic PHY framework that provides a set of APIs for the PHY drivers to create/destroy a PHY and APIs for the PHY users to obtain a reference to the PHY with or without using phandle. To obtain a reference to the PHY without using phandle, the platform specfic intialization code (say from

[PATCH v4 2/6] usb: phy: omap-usb2: use the new generic PHY framework

Used the generic PHY framework API to create the PHY. omap_usb2_suspend is split into omap_usb_suspend and omap_usb_resume in order to align with the new framework. However using the old USB PHY library cannot be completely removed because OTG is intertwined with PHY and moving to the new framewor

[PATCH v4 6/6] usb: musb: omap2430: use the new generic PHY framework

Use the generic PHY framework API to get the PHY. The usb_phy_set_suspend and usb_phy_set_resume is replaced with phy_suspend and phy_resume to align with the new PHY framework. musb->xceiv can't be removed as of now because musb core uses xceiv.state and xceiv.otg. Once there is a separate state

[PATCH v4 5/6] ARM: dts: omap: update usb_otg_hs data

Updated the usb_otg_hs dt data to include the *phy* and *phy-names* binding in order for the driver to use the new generic PHY framework. Also updated the Documentation to include the binding information. The PHY binding information can be found at Documentation/devicetree/bindings/phy/phy-bindings

Re: Linux USB file storage gadget with new UDC

Hi, >> Here is the gadget log when receiving SCSI_READ_10 from Linux host. >> >> g_file_storage gadget: bulk-out, length 31: >> : 55 53 42 43 0f 00 00 00 00 10 00 00 80 00 0a 28 >> 0010: 00 00 00 00 00 00 00 08 00 00 00 00 e0 f8 02 >> SCSI CDB: 28 00 00 00 00 00 00 00 08 00 >> g_file_s

RE: usb video capture issue due to uvc_complete callback spends more time

> > Laurent > > > > > Hi Ravi, > > > > On Wednesday 27 March 2013 10:43:24 B, Ravi wrote: > > > Hi > > > > > > I am observing issue while streaming video from usb camera connected > to > > host > > > controller based on mentor graphics. The issue is root caused that > there > > > are huge SOF gap

Re: [PATCH v7 0/6] usb: chipidea: udc: bugfixes

Michael Grzeschik writes: > On Wed, Mar 27, 2013 at 10:24:04PM +0200, Alexander Shishkin wrote: >> Michael Grzeschik writes: >> >> > On Wed, Mar 27, 2013 at 06:35:30PM +0200, Alexander Shishkin wrote: >> >> Michael Grzeschik writes: >> >> >> >> > Hi, >> >> > >> >> > this series solve some iss

<    1   2