Remove 'start_new' variable from dwc3_endpoint_transfer_complete(),
since this variable has not been used.
Signed-off-by: Jingoo Han
---
drivers/usb/dwc3/gadget.c |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
i
At Thu, 3 Jul 2014 20:15:28 +0200,
Sebastian Reimers wrote:
>
> The pcm playback and capture sample size format was fixed
> SNDRV_PCM_FMTBIT_S16_LE.
>
> This patch respects also 16, 24 and 32 bit p_ssize and c_ssize values.
>
> Signed-off-by: Sebastian Reimers
In general, this driver should c
> > >
> >
> > Yes, it has already implemented at ci_usc_vbus_session.
> >
> > > I see the code path in ci_udc_vbus_session of udc.c to trigger such
> > > an event, but unfortunately it was never possible to run into that
> code.
> > >
> > > The function ci_otg_work in otg.c is prepared to do that
Hi all,
Here's a second version of the probe order issue series. This time I've
added the USB1 resets to the PHYs, thus replacing the really ugly parts
with something slightly better. Old device trees will still probe
successfully, but instead of this bugfix they'll get a dev_warn().
The reset co
The Tegra USB complex has a particularly annoying misdesign: some of the
UTMI pad configuration registers are global for all the 3 USB controllers
on the chip, but those registers are located in the first controller's
register space and will be cleared when the reset to the first
controller is asse
tegra_usb_phy_close() is supposed to undo the effects of
tegra_usb_phy_init(). It is also currently added as the USB PHY shutdown
callback, which is wrong, since tegra_usb_phy_init() is only called
during probing wheras the shutdown callback can get called multiple
times. This then leads to warning
Add new properties to all of the Tegra PHYs that are now required
according to the binding.
In order to stay compatible with old device trees, the USB drivers
will still function without these reset properties but with the old,
potentially buggy behaviour.
Signed-off-by: Tuomas Tynkkynen
---
v2
When Tegra was converted to use the standard reset bindings, the PHY was
forgotten, probably because all the resetting of the USB blocks were
done in the EHCI driver. What also went unnoticed is that resetting the
1st on-chip USB module also wipes some of the UTMI pad configuration
registers that a
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.16-rc4
for you to fetch changes up to e4adcff09ca39ecbcc4
Hello.
On 06/25/2014 12:44 PM, Vivek Gautam wrote:
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
index 9ffecd5..453d89e 100644
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
@@ -1582,6 +1582,9 @@ struct xhci_hcd {
u32 port_status_u0;
On Thu, 3 Jul 2014, Vladimir Zapolskiy wrote:
> This change makes two more one-time per HCD allocations to be done
> from non-atomic DMA pool, the main purpose of the change is to save
> some bits of space in coherent atomic DMA pool, which is 256KB by
> default on ARM platform.
>
> Vladimir Zapo
uhci_start() is executed one time during usb_add_hcd() call and by
default UHCI frame list is allocated from atomic DMA pool.
Do non-atomic allocation of uhci->frame and free some space in
coherent atomic DMA pool.
Cc: Alan Stern
Cc: Greg Kroah-Hartman
Signed-off-by: Vladimir Zapolskiy
---
dr
OHCI HCCA memory region is allocated from atomic DMA pool one time
during usb_add_hcd() and deallocated by usb_remove_hcd().
Do non-atomic allocation of OHCI HCCA and free some space in
coherent atomic DMA pool.
Cc: Alan Stern
Cc: Greg Kroah-Hartman
Signed-off-by: Vladimir Zapolskiy
---
drive
This change makes two more one-time per HCD allocations to be done
from non-atomic DMA pool, the main purpose of the change is to save
some bits of space in coherent atomic DMA pool, which is 256KB by
default on ARM platform.
Vladimir Zapolskiy (2):
USB: OHCI: don't allocate HCCA atomically
US
On 03.07.2014 19:38, Alan Stern wrote:
On Thu, 3 Jul 2014, Vladimir Zapolskiy wrote:
ehci_mem_init() is executed one time during ehci_init() and by default
all memory allocations but ehci->periodic are done not atomically,
GFP_KERNEL is passed as flags parameter.
Do similar allocation for ehci
2014-07-03 21:17 GMT+03:00 Bryan Wu :
> On Thu, Jul 3, 2014 at 10:40 AM, Johan Hovold wrote:
>> On Thu, Jul 03, 2014 at 08:17:09PM +0300, Janne Kanniainen wrote:
>>> Move led_mode attribute from HID device to led-class devices and rename
>>> it msi_mode. This will also fix race condition by using
On Thu, Jul 3, 2014 at 10:40 AM, Johan Hovold wrote:
> On Thu, Jul 03, 2014 at 08:17:09PM +0300, Janne Kanniainen wrote:
>> Move led_mode attribute from HID device to led-class devices and rename
>> it msi_mode. This will also fix race condition by using
>
> There's a typo here (s/msi_mode/mode) b
The pcm playback and capture sample size format was fixed
SNDRV_PCM_FMTBIT_S16_LE.
This patch respects also 16, 24 and 32 bit p_ssize and c_ssize values.
Signed-off-by: Sebastian Reimers
---
drivers/usb/gadget/f_uac2.c | 24 ++--
1 file changed, 22 insertions(+), 2 deletions
On Thu, Jul 3, 2014 at 10:34 AM, Johan Hovold wrote:
> On Thu, Jul 03, 2014 at 08:17:08PM +0300, Janne Kanniainen wrote:
>> This will fix race condition noticed by Oliver Neukum. Sysfs files are
>> created before mutex and work are initialized.
>>
>> Signed-off-by: Janne Kanniainen
>
> Reviewed-b
Hi Fabio,
On Thu, Jul 03, 2014 at 02:04:07PM -0300, Fabio Estevam wrote:
> Hi Michael,
>
> On Thu, Jul 3, 2014 at 1:06 PM, Michael Grzeschik wrote:
>
> > I validated this with two different imx25 boards and realized,
> > that we have this external vbus divider errata for that SoC.
> >
> > Errat
On Thu, Jul 03, 2014 at 08:17:09PM +0300, Janne Kanniainen wrote:
> Move led_mode attribute from HID device to led-class devices and rename
> it msi_mode. This will also fix race condition by using
There's a typo here (s/msi_mode/mode) but perhaps Bryan can just fix
that up before applying?
> att
On Thu, Jul 03, 2014 at 08:17:08PM +0300, Janne Kanniainen wrote:
> This will fix race condition noticed by Oliver Neukum. Sysfs files are
> created before mutex and work are initialized.
>
> Signed-off-by: Janne Kanniainen
Reviewed-by: Johan Hovold
> ---
> drivers/hid/hid-gt683r.c | 6 +++---
Move led_mode attribute from HID device to led-class devices and rename
it msi_mode. This will also fix race condition by using
attribute-groups.
Signed-off-by: Janne Kanniainen
---
Changes in v3:
- Style fixes
- Rename sysfs-class-hid-driver-gt683r to sysfs-class-leds-driver-gt6
This will fix race condition noticed by Oliver Neukum. Sysfs files are
created before mutex and work are initialized.
Signed-off-by: Janne Kanniainen
---
drivers/hid/hid-gt683r.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/hid/hid-gt683r.c b/drivers/hid/hid-
Hi Michael,
On Thu, Jul 3, 2014 at 1:06 PM, Michael Grzeschik wrote:
> I validated this with two different imx25 boards and realized,
> that we have this external vbus divider errata for that SoC.
>
> Errata: ENGcm09152
>
> Its likely that the issue is related to this problem as the vbus was
> n
Julius, I finally managed to generate some sensible (I hope) logs.
The kernel is 3.2.60-rc3 with modifications as you requested.
http://pastebin.com/6as4beZ3
This is an excerpt from syslog, showing messages logged immediately
after a USB3 device (Areca ARC-5040) was plugged in. The OS was booted
w
On 07/03/2014 04:31 PM, Kishon Vijay Abraham I wrote:
> Hi Roger,
>
> On Wednesday 02 July 2014 05:33 PM, Roger Quadros wrote:
>> If probe fails then we need to call pm_runtime_disable() to balance
>> out the previous pm_runtime_enable() call. Else it will cause
>> unbalanced pm_runtime_enable() c
On Thu, 3 Jul 2014, Vladimir Zapolskiy wrote:
> ehci_mem_init() is executed one time during ehci_init() and by default
> all memory allocations but ehci->periodic are done not atomically,
> GFP_KERNEL is passed as flags parameter.
>
> Do similar allocation for ehci->periodic and free some space i
On Thu, Jul 03, 2014 at 01:19:21AM +, Peter Chen wrote:
>
> >
> > Is it possible to get the chipidea to generate an event on udc unplugging?
> >
>
> Yes, it has already implemented at ci_usc_vbus_session.
>
> > I see the code path in ci_udc_vbus_session of udc.c to trigger such an
> > eve
ehci_mem_init() is executed one time during ehci_init() and by default
all memory allocations but ehci->periodic are done not atomically,
GFP_KERNEL is passed as flags parameter.
Do similar allocation for ehci->periodic and free some space in
coherent atomic DMA pool by default.
Cc: Alan Stern
C
On Tue, Jul 01, 2014 at 04:50:21AM +, Peter Chen wrote:
>
> > On Sun, May 18, 2014 at 03:19:01PM +0800, Peter Chen wrote:
> > > The probe function may be probed deferal and called after .init
> > > section has freed.
> > >
> > > Peter Chen (6):
> > > usb: gadget: atmel_usba_udc: delete __in
On Thu, 3 Jul 2014, Lu, Baolu wrote:
> Hi,
>
> I am using an ASUS T100TA with dock attached. I installed Ubuntu Linux
> on eMMC and customized the kernel.
>
> I started from "echo mem > /sys/power/state". Kernel starts its
> processes to put the system into suspend mode. Before kernel executes
On Thu, 3 Jul 2014, Stefan Klug wrote:
> >> Questions/Notes:
> >> - I'm quite unhappy with the added member async::is_user_mem. Is there a
> >> better place
> >> where I could store this information?
> > No, async is the right place. Why are you unhappy about it?
> A whole byte for this flag
Hi Roger,
On Wednesday 02 July 2014 05:33 PM, Roger Quadros wrote:
> If probe fails then we need to call pm_runtime_disable() to balance
> out the previous pm_runtime_enable() call. Else it will cause
> unbalanced pm_runtime_enable() call in the succeding probe call.
>
> This anomaly was observed
On Thu, 2014-07-03 at 18:19 +0530, arun wrote:
> Hello,
> I am on Ubuntu 12.04, and am trying to install a USB dongle with a
> 3-g simcard. I have D-link 156 dongle.
>
> I do the following 2:
> - dpkg -i .deb
> - usb_modeswitch ...
>
> after this, i am not able to locate the driver in Net
Hello,
I am on Ubuntu 12.04, and am trying to install a USB dongle with a
3-g simcard. I have D-link 156 dongle.
I do the following 2:
- dpkg -i .deb
- usb_modeswitch ...
after this, i am not able to locate the driver in Network Manager.
If i do dmesg, it says:
usbserial_generic 1-1.3:1.
Hi Niyazi,
Niyazi Sırt wrote:
> I had kernel-3.4.52, libusb-0.1.12 and usbutils-0.71
> on my centos and lsusb command was working properly.
> After I upgraded kernel-3.14.9 and also upgraded
> libusb-static-1.0.9, libusb-1.0.9, libusb-devel-1.0.9
> and usbutils-006 rpm packages, lsusb command stop
Hi,
I had kernel-3.4.52, libusb-0.1.12 and usbutils-0.71
on my centos and lsusb command was working properly.
After I upgraded kernel-3.14.9 and also upgraded
libusb-static-1.0.9, libusb-1.0.9, libusb-devel-1.0.9
and usbutils-006 rpm packages, lsusb command stopped
working and I started getting a
On Wednesday 02 July 2014 04:56 PM, Roger Quadros wrote:
> Sekhar,
>
> On 06/18/2014 02:19 PM, Rajendra Nayak wrote:
>> On Wednesday 18 June 2014 04:40 PM, Roger Quadros wrote:
>>> + Nishant and Rajendra for review.
>>>
>>> On 05/05/2014 12:54 PM, Roger Quadros wrote:
Add the sysconfig class
Hi,
I am using an ASUS T100TA with dock attached. I installed Ubuntu Linux
on eMMC and customized the kernel.
I started from "echo mem > /sys/power/state". Kernel starts its
processes to put the system into suspend mode. Before kernel executes to
xhci_bus_suspend(), xHC USB 2 root hub port (
From: Roger Quadros
Some PHYs can be powered by an external power regulator.
e.g. USB_HS PHY on DRA7 SoC. Make the PHY core support a
power regulator.
Signed-off-by: Roger Quadros
---
drivers/phy/phy-core.c | 27 +++
include/linux/phy/phy.h | 2 ++
2 files changed, 29
From: Roger Quadros
After clarification from the hardware team it was found that
this 1.8V PHY supply can't be switched OFF when SoC is Active.
Since the PHY IPs don't contain isolation logic built in the design to
allow the power rail to be switched off, there is a very high risk
of IP reliabil
Dear johan&Williams
As we discuss about the question of zte_ev.c, are you sure how to modify.
Looking forward to your reply. thanks.
lei.liu
At 2014-06-25 04:35:28, "刘磊" wrote:
>
>
>At 2014-06-24 09:46:01, "Johan Hovold" wrote:
>>On Tue, Jun 24, 2014 at 08:43:36PM +0800, 刘磊 wrote:
>>> A
From: Stefan Klug
...
> Is there any way to check if the host controller supports arbitrary
> alignment?
> If I read the xhci spec correctly arbitrary alignment is explicitly
> permitted.
Not entirely.
The xhci spec has a few limits on the alignment of transfer buffer.
They seem to be designed to
On Wed, Jul 02, 2014 at 08:37:59PM +0300, Janne Kanniainen wrote:
> Move led_mode attribute from HID device to led-class devices. This will also
> fix race condition by using attribute-groups.
>
> Signed-off-by: Janne Kanniainen
Looks good now. Thanks!
Perhaps you can resend both patches as a
On 02.07.2014 21:38, Alan Stern wrote:
On Wed, 2 Jul 2014, Oliver Neukum wrote:
Stefan Klug
Software Developer
Basler AG
An der Strusbek 60-62
22926 Ahrensburg
Germany
Tel. +49 4102 463 582
Fax +49 4102 463 46 582
stefan.k...@baslerweb.com
www.baslerweb.com
Vorstand: Dr.-Ing. Dietmar Le
On 07/02/2014 03:32 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 07/02/2014 04:03 PM, Roger Quadros wrote:
>
>> Some PHYs can be powered by an external power regulator.
>> e.g. USB_HS PHY on DRA7 SoC. Make the PHY core support a
>> power regulator.
>
>> Signed-off-by: Roger Quadros
>> ---
>> dr
On 02.07.2014 20:24, Alan Stern wrote:
Overall this implementation seems quite straightforward. However, it
appears that your email client has mangled the whitespace in the patch.
The patch contains many style violations; you should run it through
checkpatch.pl. It also has one or two mistake
On 02.07.2014 19:55, Greg KH wrote:
Very nice.
Thanks.
Minor non-technical issues here, your patch is corrupted (linewrapped
and tabs converted to spaces) and can't be applied at all. Can you fix
your email client and try again? Look at
Documentation/email_clients.txt for hints on how to do
49 matches
Mail list logo
