Thanks Peter.
My problem is that I can not hear any sound if playing wav from Ubuntu Host.
I can hear sound if I play wav for the real sound card at the device side.
For UAC1 (file u_uac1.c), usb audio stream is hard-coded to be directed to
"/dev/snd/pcmC0D0p". I am wondering for UAC2, should
On Fri, Aug 15, 2014 at 7:55 AM, Xuebing Wang wrote:
>
> On 08/15/2014 08:55 AM, Peter Chen wrote:
>>
>>
>
> At device side, in driver/usb/gadget/Kconfig, it says before for
> CONFIG_USB_AUDIO
> -
> This driver doesn't expect any real Audio c
On 08/15/2014 08:55 AM, Peter Chen wrote:
At device side, in driver/usb/gadget/Kconfig, it says before for
CONFIG_USB_AUDIO
-
This driver doesn't expect any real Audio codec to be
present
on the device - the audio streams are simply sinked to
Hi, All,
As described in runtime_pm.txt for pm_wq:
The power management work queue pm_wq in which bus types and device
drivers can put their PM-related work items. It is strongly recommended that
pm_wq be used for queuing all work items related to runtime PM, because
this allows them to be synchron
>
> On Wed, 13 Aug 2014, David Laight wrote:
>
> > We are seeing some transient USB disconnects, these cause serious
> > grief if we use the xhci driver, so the ports are all forced to use
> ehci (bios config).
> > Even with ehci they are slightly problematic, partially resolved by
> > using a
>
> >> At device side, in driver/usb/gadget/Kconfig, it says before for
> >> CONFIG_USB_AUDIO
> >> -
> >>This driver doesn't expect any real Audio codec to be
> present
> >>on the device - the audio streams are simply sinked to and
> >>
On Tue, Aug 12, 2014 at 09:13:47AM -0700, Tim Bird wrote:
> On Mon, Aug 11, 2014 at 5:28 PM, Peter Chen wrote:
> > The OTG FSM at /usb/common/usb-otg-fsm.c is a software OTG FSM
> > implementation
> > which follows On-The-Go and Embedded Host Supplement to the USB Revision
> > 2.0 Specification
On Thu, Aug 14, 2014 at 11:54:02AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Thu, Aug 14, 2014 at 09:53:10AM -0700, Tim Bird wrote:
> > Ping. Anybody know the status of this patch? Is it queued in someone's
> > tree?
> > Without it the USB driver for the Qualcomm 8974 (hsusb phy) doesn't
> > work
Adding Mathias Nyman. He is now the USB 3.0 maintainer.
Sarah Sharp
On Thu, Aug 14, 2014 at 11:46:33AM +0200, Hans de Goede wrote:
> Hi,
>
> On 08/14/2014 10:39 AM, Claudio Bizzarri wrote:
> > Ciao,
> >
> > thank you very much for replay, you are right: it's UAS module. Now I'm
> > using Ubunt
Hi,
On Thu, Aug 14, 2014 at 06:15:30PM +, Paul Zimmerman wrote:
> > From: Felipe Balbi [mailto:ba...@ti.com]
> > Sent: Thursday, August 14, 2014 8:00 AM
> > To: Paul Zimmerman; Linux USB Mailing List
> > Cc: George Cherian
> > Subject: DWC3 xHCI suspend
> >
> > Hi Paul,
> >
> > We noticed th
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Thursday, August 14, 2014 8:00 AM
> To: Paul Zimmerman; Linux USB Mailing List
> Cc: George Cherian
> Subject: DWC3 xHCI suspend
>
> Hi Paul,
>
> We noticed that on some of our platforms XHCI takes longer to suspend
> and we only reach suspend if
[ Please try to avoid top-posting. ]
On Wed, Aug 13, 2014 at 09:59:35AM -0600, Kirk Madsen wrote:
> I can try a patch, but the testing will have to fit in between the
> primary uses of the machine (we have entirely too few Linux boxes at
> work, and far too many Windows ones), so there might be a
Hi,
On Thu, Aug 14, 2014 at 09:53:10AM -0700, Tim Bird wrote:
> Ping. Anybody know the status of this patch? Is it queued in someone's tree?
> Without it the USB driver for the Qualcomm 8974 (hsusb phy) doesn't
> work (at least for me).
> It looks like it got dropped from Ivan's original patch s
Ping. Anybody know the status of this patch? Is it queued in someone's tree?
Without it the USB driver for the Qualcomm 8974 (hsusb phy) doesn't
work (at least for me).
It looks like it got dropped from Ivan's original patch series, back in May.
-- Forwarded message --
From: Tim
Hi Paul,
We noticed that on some of our platforms XHCI takes longer to suspend
and we only reach suspend if we set XHCI_SLOW_SUSPEND quirk.
Do you have any idea what would make DWC3 (as host) take longer to
complete STS_HALT command ?
thanks
--
balbi
signature.asc
Description: Digital signat
Hi Bartlomiej Zolnierkiewicz,
On Thursday, August 14, 2014 7:55 PM, Bartlomiej Zolnierkiewicz
wrote
Subject: [PATCH 3/5] usb: phy: samsung: remove old USB 2.0 PHY driver
I would say it co-incidence that both of us sent the patch-series for
similar cleanup at the same time. ;)
There's one
Removing this older USB 3.0 DRD controller PHY driver, since
a new driver based on generic phy framework is now available.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/Kconfig|8 -
drivers/usb/phy/Makefile |1 -
drivers/usb/phy/phy-samsung-usb.h | 80 -
Hi Alan,
On Tue, Aug 5, 2014 at 7:41 PM, Alan Stern wrote:
> On Tue, 5 Aug 2014, Vivek Gautam wrote:
>
>> Since we want to keep support for both older usb-phys as well as the
>> newer generic phys, lets first get the generic PHYs and fallback to
>> older USB-PHYs only when we fail to get the for
- This series is based on 'usb-next' branch.
Now that we have support for USB PHY controllers for Exynos SoC series,
we are free to remove the older usb-phy support.
In the process, we are removing the entire phy-samsung-usb3 driver, and
besides that all support for Exynos4x and Exynos5 from phy-s
Now that we have moved to new PHY driver for Exynos4210's USB 2.0
controller, which is based on generic phy framework; so removing
the code for Exyno4210.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/phy-samsung-usb.c | 35 ---
drivers/usb/phy/phy-samsung-us
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.
Cc: Kamil Debski
Cc: Vivek Gautam
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
---
drivers/usb/phy/Kconfig
drivers/usb/phy/phy-samsung-usb3 driver got replaced by
drivers/phy/phy-samsung-usb3 one and is no longer used.
Cc: Kamil Debski
Cc: Vivek Gautam
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
---
drivers/usb/phy/Kconfig| 8 -
drivers/usb/phy/Makefile
Now that we have moved to new PHY driver for Exynos5250's USB 2.0
controller, which is based on generic phy framework; we no longer
need to keep support of the same in older usb-phy based driver.
So removing this entire code for Exyno5250.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/phy-sams
Now that we have moved to new PHY driver for Exynos4X12's USB 2.0
controller, which is based on generic phy framework; so removing
this entire code for Exyno4X12.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/phy-samsung-usb.c | 42
drivers/usb/phy/phy-s
drivers/usb/phy/phy-samsung-usb2 driver got replaced by
drivers/phy/phy-samsung-usb2 one and is no longer used.
Cc: Kamil Debski
Cc: Vivek Gautam
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
---
drivers/usb/phy/Kconfig| 8 -
drivers/usb/phy/Makefile
drivers/usb/phy/phy-samsung-usb2 driver got replaced by
drivers/phy/phy-samsung-usb2 one. Remove the leftover
USB2 PHY node (EHCI/OHCI USB nodes are using the new one
already) from Exynos5250 dtsi file.
Cc: Mark Brown
Cc: Kamil Debski
Cc: Vivek Gautam
Signed-off-by: Bartlomiej Zolnierkiewicz
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
This should fix the issue on ehci-exynos, wherein in the absence of
SAMSUNG_USB
drivers/usb/phy/phy-samsung-usb2 driver got replaced by
drivers/phy/phy-samsung-usb2 one. Remove the leftover hook
from Arndale dts file.
Cc: Mark Brown
Cc: Kamil Debski
Cc: Vivek Gautam
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
---
arch/arm/boot/dts/exynos5250-arndal
Hi,
This patch series removes the old Samsung USB PHY drivers that
got replaced by the new ones using the generic PHY layer.
Depends on:
- next-20140813 branch of linux-next kernel
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
Bartlomiej Zolnierkie
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
This should fix the issue on ohci-exynos, wherein in the absence of
SAMSUNG_USB
Cleaning up the driver further to enable only S3C64XX phy support,
while the support for rest all SoCs is removed in previous patches.
Signed-off-by: Vivek Gautam
---
- In the changes that have been left for S3C64XX, we have added DT based
pmu-isolation support for S3C64XX boards too, wherein
On Wed, 13 Aug 2014, Paul Zimmerman wrote:
> This thread seems to have wandered pretty far off-topic. I just wanted
> to make the point that if you create another API function for this
> issue, please be aware that not all controllers/phys will need it or
> be able to support it. In fact, I think
Dirk,
On Thu, Aug 14, 2014 at 1:52 AM, Dirk Gouders wrote:
> Bin Liu writes:
>
>> All,
>>
>> On Mon, Nov 18, 2013 at 12:08 PM, Yann E. MORIN
>> wrote:
>>> Dirk, All,
>>>
>>> On 2013-11-07 15:05 +0100, Dirk Gouders spake thusly:
If choices consist of choice_values that depend on symbols se
On 08/12/2014 07:31 PM, Udo van den Heuvel wrote:
> On 2014-08-12 18:27, Hans Verkuil wrote:
>> It was a bit confusing, but he has two problems: one pwc, one (the warning)
>> for
>> uvc.
>
> Indeed.
> Do I need to provide additional info to help find the root cause(s)?
>
>
Could you help me tak
Hi Michael,
Thank you for the patch.
On Thursday 14 August 2014 13:09:44 Michael Grzeschik wrote:
> As the driver is mainline we can remove the version numbers.
>
> Signed-off-by: Michael Grzeschik
Acked-by: Laurent Pinchart
> ---
> drivers/usb/gadget/function/uvc.h | 3 ---
> drivers/
As the driver is mainline we can remove the version numbers.
Signed-off-by: Michael Grzeschik
---
drivers/usb/gadget/function/uvc.h | 3 ---
drivers/usb/gadget/function/uvc_v4l2.c | 2 +-
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/usb/gadget/function/uvc.h
b/driv
Hello,
On Monday 11 August 2014 09:20:47 Felipe Balbi wrote:
> On Mon, Aug 11, 2014 at 03:50:08PM +0200, Michael Grzeschik wrote:
> > > > As the driver is mainline we can remove the version numbers.
> > > >
> > > > Signed-off-by: Michael Grzeschik
> > > > ---
> > > >
> > > > drivers/usb/gadget
Hi,
On 08/12/2014 05:29 PM, Udo van den Heuvel wrote:
> On 2014-08-12 17:07, Hans de Goede wrote:
>> lspci -nn
>
> # lspci -nn
> 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family
> 15h (Models 10h-1fh) Processor Root Complex [1022:1410]
> 00:00.2 IOMMU [0806]: Advanced Micro D
Hi,
On 08/14/2014 10:39 AM, Claudio Bizzarri wrote:
> Ciao,
>
> thank you very much for replay, you are right: it's UAS module. Now I'm
> using Ubuntu 14.04 with kernel 3.16.1 from
> http://kernel.ubuntu.com/~kernel-ppa/mainline/, there is no /proc/config.gz,
> but but there is a config file in /
On Mon, Aug 11, 2014 at 09:20:47AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Mon, Aug 11, 2014 at 03:50:08PM +0200, Michael Grzeschik wrote:
> > > > As the driver is mainline we can remove the version numbers.
> > > >
> > > > Signed-off-by: Michael Grzeschik
> > > > ---
> > > > drivers/usb/gadget
At device side, in driver/usb/gadget/Kconfig, it says before for
CONFIG_USB_AUDIO
-
This driver doesn't expect any real Audio codec to be present
on the device - the audio streams are simply sinked to and
sourced from a virtual ALSA sound
Bin Liu writes:
> All,
>
> On Mon, Nov 18, 2013 at 12:08 PM, Yann E. MORIN
> wrote:
>> Dirk, All,
>>
>> On 2013-11-07 15:05 +0100, Dirk Gouders spake thusly:
>>> If choices consist of choice_values that depend on symbols set to 'm',
>>> those choice_values are not set to 'n' if the choice is ch
42 matches
Mail list logo
