This USB 3.0 PHY controller is also present on Exynos7
platform, so adding the dependency on ARCH_EXYNOS7 for this driver.
Signed-off-by: Vivek Gautam
---
drivers/phy/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
index 0d
Exynos7 also has a separate special gate clock going to the IP
apart from the usual AHB clock. So add support for the same.
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/dwc3-exynos.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/usb/dwc3/dwc3-exynos.c b/driv
Some Exynos SoCs have a separate regulator controlling a
Boost 5V supply which goes as input for VBUS regulator.
So adding a control for the same in driver, to enable
vbus supply on the port.
Signed-off-by: Vivek Gautam
---
drivers/phy/phy-exynos5-usbdrd.c | 27 +--
1 f
The Exynos-DWC3 USB 3.0 DRD controller is also present on
Exynos7 platform, so adding the dependency on ARCH_EXYNOS7
for this driver.
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/Kconfig b/drivers
Exynos7 SoC has now separate gate control for 125MHz pipe3 phy
clock, as well as 60MHz utmi phy clock.
So get the same and control in the phy-exynos5-usbdrd driver.
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/phy/samsung-phy.txt|4
drivers/phy/phy-exynos5-usbdrd.c
Adding required support for clocks and additional VBUS regulators
to enable USB 3.0 support on Exynos7 SoC.
This series depends for ACRH_EXYNOS7 support on following series:
[PATCH 00/14] Support 64bit Cortex A57 based Exynos7 SoC
https://www.mail-archive.com/devicetree@vger.kernel.org/msg39392.ht
On Wed, Aug 27, 2014 at 10:42 AM, wrote:
> From: Yegor Yefremov
>
> Using $(PWD) breaks builds when make was invoked from outside
> of the kernel tree.
Some details: I've experienced this issue with Buildroot. I don't
know, if this will happen with OpenEmbedded, but it is also possible.
So far
On Wed, Aug 27, 2014 at 02:09:04PM -0500, Felipe Balbi wrote:
> On Tue, Aug 26, 2014 at 10:55:18AM +0800, Peter Chen wrote:
> > Add compatible string for imx6sx-usbphy.
> >
> > Signed-off-by: Peter Chen
>
> do I need to take this one as well or will DT folks take care of patch 2 ?
>
It is DT c
On Wed, Aug 27, 2014 at 02:22:30PM -0500, Felipe Balbi wrote:
> On Wed, Aug 20, 2014 at 01:30:40PM +0800, Peter Chen wrote:
> > On Tue, Aug 19, 2014 at 09:02:54PM +, Paul Zimmerman wrote:
> > > > From: linux-usb-ow...@vger.kernel.org
> > > > [mailto:linux-usb-ow...@vger.kernel.org] On Behalf O
On Wed, Aug 27, 2014 at 02:37:35PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Tue, Aug 26, 2014 at 03:30:32PM +0800, Peter Chen wrote:
> > On Mon, Aug 25, 2014 at 11:27:47AM -0400, Alan Stern wrote:
> > > On Mon, 25 Aug 2014, Peter Chen wrote:
> > >
> > > > Hi Felipe & Alan,
> > > >
> > > > It is t
On Wed, Aug 27, 2014 at 04:20:25PM -0400, Alan Stern wrote:
> On Wed, 27 Aug 2014, Felipe Balbi wrote:
>
> > > Hi Alan & Felipe,
> > >
> > > During the changing UDC drivers process, I find we can't simply move
> > > usb_gadget_disconnect to usb_gadget_driver.disconnect, some UDC
> > > drivers (li
On Wed, Aug 27, 2014 at 03:29:20PM -0500, Felipe Balbi wrote:
> On Wed, Aug 27, 2014 at 04:20:25PM -0400, Alan Stern wrote:
> > On Wed, 27 Aug 2014, Felipe Balbi wrote:
> >
> > > > Hi Alan & Felipe,
> > > >
> > > > During the changing UDC drivers process, I find we can't simply move
> > > > usb_g
On Wed, Aug 27, 2014 at 10:39 PM, Daniel Mack wrote:
> The UAC2 function driver currently responds to all packets at all times
> with wMaxPacketSize packets. That results in way too fast audio
> playback as the function driver (which is in fact supposed to define
> the audio stream pace) delivers
On 08/28/2014 12:02 AM, Greg KH wrote:
> On Wed, Aug 27, 2014 at 12:23:39PM -0700, Greg KH wrote:
>> On Wed, Aug 27, 2014 at 03:11:10PM +0300, Roger Quadros wrote:
>>> If user specifies that USB autosuspend must be disabled by module
>>> parameter "usbcore.autosuspend=-1" then we must prevent
>>> a
From: Todd Poynor
USB: OTG: Hold wakeupsource when VBUS present
Purpose of this is to prevent the system to enter into
suspend state from USB peripheral traffic by hodling a
wakeupsource when USB(otg) is connected and enumerated
in peripheral mode(say adb).
Disabled by default, can enable with:
From: Todd Poynor
usb: otg: Temporarily hold wakeupsource on charger and disconnect events
Allow other parts of the system to react to the charger connect/disconnect
event without allowing the system to suspend before the other parts can process
the event. This wakeup_source times out after 2 se
From: Todd Poynor
usb: otg: Temporarily hold wakeupsource on charger and disconnect events
Allow other parts of the system to react to the charger connect/disconnect
event without allowing the system to suspend before the other parts can process
the event. This wakeup_source times out after 2 se
On 08/28/2014 11:33 AM, Jassi Brar wrote:
> On Wed, Aug 27, 2014 at 10:39 PM, Daniel Mack wrote:
>> diff --git a/drivers/usb/gadget/function/f_uac2.c
>> b/drivers/usb/gadget/function/f_uac2.c
>> index 246a778..a5a27a5 100644
>> --- a/drivers/usb/gadget/function/f_uac2.c
>> +++ b/drivers/usb/gadg
From: Todd Poynor
usb: otg: Temporarily hold wakeupsource on charger connect and disconnect
events
Allow other parts of the system to react to the charger connect/disconnect
event without allowing the system to suspend before the other parts can process
the event. This wakeup_source times out af
On Thu, Aug 28, 2014 at 3:33 PM, Daniel Mack wrote:
> On 08/28/2014 11:33 AM, Jassi Brar wrote:
>> On Wed, Aug 27, 2014 at 10:39 PM, Daniel Mack wrote:
>
>>> diff --git a/drivers/usb/gadget/function/f_uac2.c
>>> b/drivers/usb/gadget/function/f_uac2.c
>>> index 246a778..a5a27a5 100644
>>> --- a/d
On 08/28/2014 12:10 PM, Jassi Brar wrote:
> On Thu, Aug 28, 2014 at 3:33 PM, Daniel Mack wrote:
>> It's still superior to a number of unnecessary calculations done every
>> millisecond which will come up with the same result every time. So I
>> clearly favor that approach. Three more ints in a st
On 08/28/2014 12:17 PM, Daniel Mack wrote:
> Felipe, could you already merge patch 1-5 of the last series (v6)?
1-4, of course. Jassi's changes will only affect patch 5/5.
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger
On Thu, Aug 28, 2014 at 3:47 PM, Daniel Mack wrote:
> On 08/28/2014 12:10 PM, Jassi Brar wrote:
>> On Thu, Aug 28, 2014 at 3:33 PM, Daniel Mack wrote:
>
>>> It's still superior to a number of unnecessary calculations done every
>>> millisecond which will come up with the same result every time. S
On 08/27/2014 07:10 PM, Ricardo Ribalda Delgado wrote:
> Perhaps we could apply both patches to current tree and backport mine
> to older kernels?
>
The already applied patch fixes many other issues than just this one.
backporting it to stable < 3.13 turned out to not be that difficult, stable
m
On Thu, Aug 28, 2014 at 11:25:30AM +0800, 刘磊 wrote:
> Dear Johan:
> Thanks for you reply.
> i had been find the pid of 0x9008 and 0x3197 was in moto-modem and
> qcserial drivers.
> but the pid from 0xfff6 to 0xfffb and 0xffee/0xffec had been delete in
> new patch, that pid was not in
Add back some PIDs that were mistakingly remove when reverting commit
73228a0538a7 ("USB: option,zte_ev: move most ZTE CDMA devices to
zte_ev"), which apparently did more than its commit message claimed in
that it not only moved some PIDs from option to zte_ev but also added
some new ones.
Fixes:
Hello
On Thu, Aug 28, 2014 at 12:41 PM, Mathias Nyman wrote:
> On 08/27/2014 07:10 PM, Ricardo Ribalda Delgado wrote:
>> Perhaps we could apply both patches to current tree and backport mine
>> to older kernels?
>>
>
> The already applied patch fixes many other issues than just this one.
> backpo
Daniel Mack wrote:
> [...]
> Please note, however, that you can't do the divison 'uac2->p_residue /
> uac2->p_interval' in a pre-calucated value, as that won't cover cases
> with a per-packet residual value that isn't a multiple of the frame
> size.
Partial frames are not allowed (neither in ALSA
Hi Andrzej,
On Wednesday 27 August 2014 17:33:16 Andrzej Pietrasiewicz wrote:
> W dniu 18.08.2014 o 21:45, Laurent Pinchart pisze:
> > Hi Andrzej,
> >
> > Thank you for the patches. The series looks good, I only had a few
> > comments.
> >
> > I have rebased the patches on top of my UVC gadget b
Hi Andrzej,
Thank you for the patch.
On Wednesday 27 August 2014 17:16:38 Andrzej Pietrasiewicz wrote:
> UVC video node is a TX device from the point of view of the gadget,
> so we cannot rely on the video struct being filled with zeros, because
> VFL_DIR_TX is actually 1.
>
> Suggested-by: Sylw
drivers/usb/phy/phy-samsung-usb[2,3] drivers got replaced by
drivers/phy/phy-samsung-usb[2,3] ones and the old common Samsung
USB PHY code is no longer used.
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
Reviewed-by: Vivek Gautam
Reviewed-by: Jingoo Han
Acked-by: Kishon Vija
Sierra Wireless Direct IP devices using the 68A3 product ID
can be configured for modes including a CDC ECM class function.
The known example uses interface numbers 12 and 13 for the ECM
control and data interfaces respectively, consistent with CDC
MBIM function interface numbering on other Sierra
Hello Mathias
This is the dmesg output after your patch. No WARN(), no crash :), but
still some weird messages:
[ 146.511623] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 146.531652] usb 2-2: New USB device found, idVendor=0525, idProduct=a4a5
[ 146.531661] usb 2-2: New USB dev
This VID:PID is used for some Direct IP devices behaving
identical to the already supported 0F3D:68AA devices.
Cc:
Reported-by: Lars Melin
Signed-off-by: Bjørn Mork
---
This should be applied on top of my 'USB: sierra: avoid CDC class
functions on "68A3" devices' to avoid unnecessary conflicts.
Hi,
first of all, always keep linux-usb in Cc
On Thu, Aug 28, 2014 at 02:48:20PM +0530, shishir tiwari wrote:
> As your are author of USB DRD controller drvier . we using DW USB3
> DRD controller in our project , But when usb device is connected to
> Linux host machice and we run regression test
Hi,
On Thu, Aug 28, 2014 at 03:25:10PM +0530, Kiran Kumar Raparthy wrote:
> +bool enabled = false;
> +
> +static DEFINE_SPINLOCK(otgws_spinlock);
> +static struct usb_phy *get_phy_hook(void);
> +
> +/* Only one lock, but since these 2 fields are associated with each other...
> */
> +
> +struct ot
On Wed, Aug 27, 2014 at 01:56:36PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Mon, Aug 25, 2014 at 04:49:12PM +0800, Li Jun wrote:
> > As Felipe suggested, dequeue the cdev->req before free its buffer.
> >
> > Suggested-by: Felipe Balbi
> > Signed-off-by: Li Jun
>
> please read Documentation/Subm
commit f226708(usb: gadget: composite: dequeue cdev->req before free it in
composite_dev_cleanup) fixed a bug: free the usb request(i.e. cdev->req) but
does not dequeue it beforehand. This fix is not proper enough because it
dequeues the request after free its data buffer, considering the hardware
W dniu 28.08.2014 o 13:28, Laurent Pinchart pisze:
diff --git a/drivers/usb/gadget/function/f_uvc.c
b/drivers/usb/gadget/function/f_uvc.c index 5209105..95dc1c6 100644
--- a/drivers/usb/gadget/function/f_uvc.c
+++ b/drivers/usb/gadget/function/f_uvc.c
@@ -411,6 +411,7 @@ uvc_register_video(str
On Thu, Aug 28, 2014 at 04:39:27PM +0200, Andrzej Pietrasiewicz wrote:
> W dniu 28.08.2014 o 13:28, Laurent Pinchart pisze:
>
>
>
> >>diff --git a/drivers/usb/gadget/function/f_uvc.c
> >>b/drivers/usb/gadget/function/f_uvc.c index 5209105..95dc1c6 100644
> >>--- a/drivers/usb/gadget/function/f_u
Hi,
On Thu, Aug 28, 2014 at 05:08:08PM +0800, Peter Chen wrote:
> On Wed, Aug 27, 2014 at 02:37:35PM -0500, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Aug 26, 2014 at 03:30:32PM +0800, Peter Chen wrote:
> > > On Mon, Aug 25, 2014 at 11:27:47AM -0400, Alan Stern wrote:
> > > > On Mon, 25 Aug 2014
Hi,
On Thu, Aug 28, 2014 at 04:46:41PM +0800, Peter Chen wrote:
> On Wed, Aug 27, 2014 at 02:22:30PM -0500, Felipe Balbi wrote:
> > On Wed, Aug 20, 2014 at 01:30:40PM +0800, Peter Chen wrote:
> > > On Tue, Aug 19, 2014 at 09:02:54PM +, Paul Zimmerman wrote:
> > > > > From: linux-usb-ow...@vger
On Thu, 28 Aug 2014, Peter Chen wrote:
> > DWC3 doesn't really have a pullup bit. It's got a RUN/STOP bit. Sure, it
> > controls the pullups but it also kills the internal DMA and quite a bit
> > of other internal blocks.
>
> It is the same with chipidea, it has RUN/STOP bit at usbcmd, and its
>
2014-08-28 10:02 GMT+02:00 Vivek Gautam:
> This USB 3.0 PHY controller is also present on Exynos7
> platform, so adding the dependency on ARCH_EXYNOS7 for this driver.
> +++ b/drivers/phy/Kconfig
> @@ -186,7 +186,7 @@ config PHY_EXYNOS5250_USB2
>
> config PHY_EXYNOS5_USBDRD
> tristate "E
On 08/28/2014 03:36 PM, Ricardo Ribalda Delgado wrote:
> Hello Mathias
>
> This is the dmesg output after your patch. No WARN(), no crash :), but
> still some weird messages:
>
> [ 146.511623] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
> [ 146.531652] usb 2-2: New USB device fou
Sure, but the hw leaves my desk until next monday in 30 minutes.
So unless you send the patch right now you will have to wait for
results until next Monday
Thanks!
On Thu, Aug 28, 2014 at 5:20 PM, Mathias Nyman wrote:
> On 08/28/2014 03:36 PM, Ricardo Ribalda Delgado wrote:
>> Hello Mathias
>
On Thu, 28 Aug 2014, Alan Stern wrote:
> Okay, so we need to add a "vbus_is_on" flag to the usb_gadget
> structure. The gadget driver will set this flag in its connect
> callback and clear the flag in its disconnect callback. If the UDC
> driver doesn't have a Vbus handler, it will invoke the co
[ added Alan and Greg to cc: ]
Hi,
On Wednesday, August 27, 2014 11:42:25 PM Vivek Gautam wrote:
> Hi Baltlomiej,
>
>
> On Wed, Aug 27, 2014 at 1:22 PM, Bartlomiej Zolnierkiewicz
> wrote:
> > dwc3 driver is using the new Exynos5 SoC series USB DRD PHY driver
> > (PHY_EXYNOS5_USBDRD which sele
* Felipe Balbi [140827 19:21]:
> Hi,
>
> On Wed, Aug 27, 2014 at 04:28:07PM -0700, Tony Lindgren wrote:
> > It's not being used any longer.
> >
> > Signed-off-by: Tony Lindgren
> > ---
> > drivers/phy/phy-twl4030-usb.c | 2 --
> > drivers/usb/phy/phy-twl6030-usb.c | 2 --
> > 2 files chang
It's not being used any longer.
Signed-off-by: Tony Lindgren
---
Felipe, here's the twl6030 only version for you to pick.
--- a/drivers/usb/phy/phy-twl6030-usb.c
+++ b/drivers/usb/phy/phy-twl6030-usb.c
@@ -104,7 +104,6 @@ struct twl6030_usb {
int irq2;
enum
On Thu, Aug 28, 2014 at 09:01:56AM +0100, Vivek Gautam wrote:
> Exynos7 also has a separate special gate clock going to the IP
> apart from the usual AHB clock. So add support for the same.
>
> Signed-off-by: Vivek Gautam
> ---
> drivers/usb/dwc3/dwc3-exynos.c | 16
> 1 file c
On Thu, Aug 28, 2014 at 09:01:57AM +0100, Vivek Gautam wrote:
> Exynos7 SoC has now separate gate control for 125MHz pipe3 phy
> clock, as well as 60MHz utmi phy clock.
> So get the same and control in the phy-exynos5-usbdrd driver.
>
> Signed-off-by: Vivek Gautam
> ---
> .../devicetree/bindings
hi,
On Thu, Aug 28, 2014 at 01:31:58PM +0530, Vivek Gautam wrote:
> @@ -457,11 +458,19 @@ static int exynos5_usbdrd_phy_power_on(struct phy *phy)
> clk_prepare_enable(phy_drd->ref_clk);
>
> /* Enable VBUS supply */
> + if (phy_drd->vbus_boost) {
> + ret = regulator_en
On Thu, Aug 28, 2014 at 01:31:59PM +0530, Vivek Gautam wrote:
> The Exynos-DWC3 USB 3.0 DRD controller is also present on
> Exynos7 platform, so adding the dependency on ARCH_EXYNOS7
> for this driver.
>
> Signed-off-by: Vivek Gautam
> ---
> drivers/usb/dwc3/Kconfig |2 +-
> 1 file changed,
On Thu, Aug 28, 2014 at 08:11:04PM +0200, Bartlomiej Zolnierkiewicz wrote:
>
> [ added Alan and Greg to cc: ]
>
> Hi,
>
> On Wednesday, August 27, 2014 11:42:25 PM Vivek Gautam wrote:
> > Hi Baltlomiej,
> >
> >
> > On Wed, Aug 27, 2014 at 1:22 PM, Bartlomiej Zolnierkiewicz
> > wrote:
> > > dw
Hi Ricardo,
On Wednesday 27 August 2014 18:09:13 Ricardo Ribalda Delgado wrote:
> Hello
>
> Is somebody using/supporting g_webcam?
I believe so, as I get kernel patches from time to time.
> The only reference userland server is uvc-gadget from
> http://git.ideasonboard.org/?p=uvc-gadget.git;a=s
On Thu, Aug 28, 2014 at 09:56:06AM -0500, Felipe Balbi wrote:
> Hi,
>
> > > > For other three stages (no need to control at bus_reset), we can
> > > > control dp
> > > > at two gadget driver's API relies on flag pullup_on_vbus.
> > >
> > > I also can't get what you mean here.
> >
> > If the UDC
> On Thu, 28 Aug 2014, Alan Stern wrote:
>
> > Okay, so we need to add a "vbus_is_on" flag to the usb_gadget
> > structure. The gadget driver will set this flag in its connect
> > callback and clear the flag in its disconnect callback. If the UDC
> > driver doesn't have a Vbus handler, it wil
hi all:
I have read the article below and try to do the same operation on my device.
http://lwn.net/Articles/143397/
My environment:
1. my kernel is 3.16
2. device descriptor is attached.
3. below are my operation logs:
# echo -n "4-2:1.0" > /sys/bus/usb/drivers/uas/unbind
# echo -n "4-2:1.0
This full-speed USB device generates spurious remote wakeup event
as soon as USB_DEVICE_REMOTE_WAKEUP feature is set. As the result,
Linux can't enter system suspend and S0ix power saving modes once
this keyboard is used.
This patch tries to introduce USB_QUIRK_IGNOR_REMOTE_WAKEUP quirk.
With this
Felipe,
I just checked your testing/next branch. 'git log' of that branch
doesn't show the complete commit log of this patch.
On 8/22/2014 2:36 PM, Amit VIRDI wrote:
Two simple test cases for interrupt endpoints are added to the usbtest.c file.
These are simple non-queued interrupt IN and int
The UAC2 function driver currently responds to all packets at all times
with wMaxPacketSize packets. That results in way too fast audio
playback as the function driver (which is in fact supposed to define
the audio stream pace) delivers as fast as it can.
We need data rate to match, as accurately
On Fri, Aug 29, 2014 at 11:43 AM, Jassi Brar wrote:
> The UAC2 function driver currently responds to all packets at all times
> with wMaxPacketSize packets. That results in way too fast audio
> playback as the function driver (which is in fact supposed to define
> the audio stream pace) delivers a
63 matches
Mail list logo
