On 04/10/2014 10:36 PM, James Bottomley wrote:
> On Thu, 2014-04-10 at 19:52 +0200, Hannes Reinecke wrote:
>> On 04/10/2014 05:31 PM, Alan Stern wrote:
>>> On Thu, 10 Apr 2014, Hannes Reinecke wrote:
>>>
On 04/10/2014 12:58 PM, Andreas Reis wrote:
> That patch appears to work in preventing
On Thu, Apr 10, 2014 at 11:24:49PM +0300, Philippe De Swert wrote:
> Hi all,
>
> On first sight it seems that the two things in the subject have
> nothing to do with each other, so I will quickly explain why they do
> (at least for me). So for some time already I have been working on
> usb_moded,
> > >
> > > +int ci_otg_fsm_work(struct ci_hdrc *ci) {
> > > + /*
> > > + * Don't do fsm transition for B device
> > > + * when there is no gadget class driver
> > > + */
> > > + if (ci->fsm.id && !(ci->driver) &&
> > > + ci->transceiver->state < OTG_STATE_A_IDLE)
> > > + retu
On Fri, Apr 11, 2014 at 02:41:02AM +, Yanan, SUO(MBB-SZ-TCT) wrote:
> Hi :
>
> We have check the linux kernel patch list ,but We can’t find ours
> USB-PID&VID
> patch .
What specific patch is this? And what patch list did you check? We
deal with many thousands of patches every month, y
On Thu, Apr 10, 2014 at 07:08:22PM +, Ebright, Dave wrote:
>Hi Peter,
>
>
>
>I’m not sure what mailing list to post this to, but maybe you know…
Linux usb mail list is the best place to ask linux usb questions.
>
>
>
>I am looking at the i.MX51 USB device functionali
On Fri, Apr 11, 2014 at 08:18:42AM +0800, Peter Chen wrote:
> On Thu, Apr 10, 2014 at 07:36:08PM +0800, Li Jun wrote:
> > From: Li Jun
> >
> > USB OTG interrupt handling and fsm transitions according to USB OTG
> > and EH 2.0.
> >
> > Signed-off-by: Li Jun
> > ---
> > drivers/usb/chipidea/core
Hi Balbi,
At first, thank you to help give the response in patience.
> Hi,
>
> On Wed, Apr 09, 2014 at 02:08:32PM +0800, Wang, Yu wrote:
> > Glad to see the OTG mode is prepare to support in your
> > dwc3-role-switch branch. But it is not fit for intel
> > Merrfield/Moorfield platforms. :(
>
> th
On Fri, Apr 11, 2014 at 08:10:43AM +0800, Peter Chen wrote:
> On Thu, Apr 10, 2014 at 07:36:08PM +0800, Li Jun wrote:
> > From: Li Jun
> >
> > USB OTG interrupt handling and fsm transitions according to USB OTG
> > and EH 2.0.
> >
> > Signed-off-by: Li Jun
> > ---
> > drivers/usb/chipidea/core
On 04/10/2014 09:02 PM, Paul Zimmerman wrote:
From: dingu...@altera.com [mailto:dingu...@altera.com]
Sent: Friday, March 14, 2014 11:52 AM
From: Dinh Nguyen
Modify the dwc2 Kconfig and Makefile so that it will build the dwc2_gadget
driver when peripheral only mode is selected. The dwc_platfo
> From: dingu...@altera.com [mailto:dingu...@altera.com]
> Sent: Friday, March 14, 2014 11:52 AM
>
> From: Dinh Nguyen
>
> Modify the dwc2 Kconfig and Makefile so that it will build the dwc2_gadget
> driver when peripheral only mode is selected. The dwc_platform.ko and dwc2.ko
> will get built w
On Thu, Apr 10, 2014 at 07:36:08PM +0800, Li Jun wrote:
> From: Li Jun
>
> USB OTG interrupt handling and fsm transitions according to USB OTG
> and EH 2.0.
>
> Signed-off-by: Li Jun
> ---
> drivers/usb/chipidea/core.c| 23 ++--
> drivers/usb/chipidea/otg.c |9 +-
> drivers/usb/c
On Thu, Apr 10, 2014 at 07:36:08PM +0800, Li Jun wrote:
> From: Li Jun
>
> USB OTG interrupt handling and fsm transitions according to USB OTG
> and EH 2.0.
>
> Signed-off-by: Li Jun
> ---
> drivers/usb/chipidea/core.c| 23 ++--
> drivers/usb/chipidea/otg.c |9 +-
> drivers/usb/c
Thanks for your input. I tried the following:
I created the file /etc/modprobe.d/io_ti.conf with the contents of
options io_ti default_uart_mode=9
This successfully started the io_ti module with the default_uart_mode=9.
I verified this by cat /sys/module/io_ti/parameters/default_uart_mode which
Hi, Oliver,
On 04/10/2014 04:02 PM, Oliver Neukum wrote:
On Wed, 2014-04-09 at 22:57 +0800, Xiao Jin wrote:
Thanks all for the review. We meet with the problems when developing
product. I would like to explain my understanding.
On 04/08/2014 11:05 AM, Xiao Jin wrote:
We find two problems on
On Thu, Apr 10 2014, Alan Stern wrote:
> I should have guessed... :-(
Next time, we can try some guesses before bisecting, right?
--
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
On Wed, Apr 02 2014, Alan Stern wrote:
> Below is 0aa2832dd0d9d860 back-ported to 3.9. Please try testing a 3.9
> kernel with this patch installed (and also the first diagnostic patch,
> if it applies with no errors), with CONFIG_USB_SUSPEND _enabled_ and
> the mouse plugged into the rear port.
>
On Thu, Apr 10, 2014 at 11:24:49PM +0300, Philippe De Swert wrote:
> Hi all,
>
> On first sight it seems that the two things in the subject have
> nothing to do with each other, so I will quickly explain why they do
> (at least for me). So for some time already I have been working on
> usb_moded,
On Thu, 2014-04-10 at 19:52 +0200, Hannes Reinecke wrote:
> On 04/10/2014 05:31 PM, Alan Stern wrote:
> > On Thu, 10 Apr 2014, Hannes Reinecke wrote:
> >
> >> On 04/10/2014 12:58 PM, Andreas Reis wrote:
> >>> That patch appears to work in preventing the crashes, judged on one
> >>> repeated appeara
Hi all,
On first sight it seems that the two things in the subject have nothing
to do with each other, so I will quickly explain why they do (at least
for me). So for some time already I have been working on usb_moded,
which is a small daemon which handles setting up gadget drivers, so that
a
Hi,
On Thu, Apr 10, 2014 at 03:16:43PM +0200, Robert Baldyga wrote:
> +struct extcon_cable *extcon_get_cable_by_name(struct device *dev,
> + const char *name)
> +{
> + return of_extcon_get_cable_by_name(dev->of_node, name);
> +}
> +EXPORT_SYMBOL_GPL
On 04/10/2014 05:31 PM, Alan Stern wrote:
On Thu, 10 Apr 2014, Hannes Reinecke wrote:
On 04/10/2014 12:58 PM, Andreas Reis wrote:
That patch appears to work in preventing the crashes, judged on one
repeated appearance of the bug.
dmesg had the usual
[ 215.229903] usb 4-2: usb_disable_lpm cal
On Thu, Apr 10, 2014 at 07:59:38AM +, Narasimharao Bolisetti wrote:
>
> Hi,
>
> I have checked the same in the recent kernel versions also. Issue is still
> remain.
What versions have you tried, and what are the logs from those versions?
> ::DISCLAIMER::
> -
On Thu, 10 Apr 2014, Peter Münster wrote:
> On Tue, Apr 01 2014, Alan Stern wrote:
>
> >> Should I do another git-bisect?
> >
> > Yes, that would be a good idea.
>
> Hi Alan,
>
> Here is the result:
>
> e583d9db9960cf40e0bc8afee4946baa9d71596e is the first bad commit
> commit e583d9db9960cf40e
On Thu, 10 Apr 2014, Hannes Reinecke wrote:
> On 04/10/2014 12:58 PM, Andreas Reis wrote:
> > That patch appears to work in preventing the crashes, judged on one
> > repeated appearance of the bug.
> >
> > dmesg had the usual
> > [ 215.229903] usb 4-2: usb_disable_lpm called, do nothing
> > [ 2
On Thu, 10 Apr 2014, Vivek Gautam wrote:
> Patch 'b8efdaf USB: EHCI: add check for wakeup/suspend race'
> adds a check for possible race between suspend and wakeup interrupt,
> and thereby it returns -EBUSY as error code if there's a wakeup
> interrupt.
> So the platform host controller should not
On Thu, 10 Apr 2014, David Laight wrote:
> You also definitely don't want to cancel an isoc urb.
> Doing so is likely to corrupt the kernel heap.
>
> If an isoc urb generates multiple TRB the code allocates a little
> structure 'per TRB' and links it to the urb.
> This seems to be done so that it
On Thu, 10 Apr 2014, Vivek Gautam wrote:
> Patch 'b8efdaf USB: EHCI: add check for wakeup/suspend race'
> adds a check for possible race between suspend and wakeup interrupt,
> and thereby it returns -EBUSY as error code if there's a wakeup
> interrupt.
> So the platform host controller should not
On Tue, Apr 01 2014, Alan Stern wrote:
>> Should I do another git-bisect?
>
> Yes, that would be a good idea.
Hi Alan,
Here is the result:
e583d9db9960cf40e0bc8afee4946baa9d71596e is the first bad commit
commit e583d9db9960cf40e0bc8afee4946baa9d71596e
Author: Alan Stern
Date: Thu Jul 11 14:5
Hi Felipe,
On 08.04.2014 16:31, Felipe Balbi wrote:
>>> diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c
>>> index 819a7cd..d369bf1 100644
>>> --- a/drivers/usb/musb/omap2430.c
>>> +++ b/drivers/usb/musb/omap2430.c
>>> @@ -316,7 +316,13 @@ static void omap_musb_mailbox_work(s
Wir bieten privaten und gewerblichen Darlehen ohne Sicherheiten (nur
Identifikation) bei 3% Zinssatz, ab € 10.000 bis € 90.000.000 in 1 Jahr
bis 20 Jahren Laufzeit überall in der Welt..
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@
This patch modifies extcon-adc-jack driver to use initialization data from
devicetree, when platform data is not available. It allows to define cable list
with ADC value ranges for each of them in devicetree bindings.
Signed-off-by: Robert Baldyga
---
drivers/extcon/extcon-adc-jack.c | 74
This patch adds extcon devicetree bindings. Documentation describes in general
client and provider bindings, and contains detailed desctiprion of bindings
for each extcon provider.
Signed-off-by: Robert Baldyga
---
.../devicetree/bindings/extcon/extcon-adc-jack.txt | 60 +++
..
This patch modifies extcon_get_edev_by_phandle() function, to match
extcon device by devicetree node. This modification needed to add
field 'node' in extcon_dev structure, and fill it in probe function
of each extcon provider driver.
This patch replaces also extcon_get_extcon_dev() function with
o
Add support to consume phy provided by Generic phy framework.
Keeping the support for older usb-phy intact right now, in order
to prevent any functionality break in absence of relevant
device tree side change for ohci-exynos.
Once we move to new phy in the device nodes for ohci, we can
remove the s
Added check if pointer to edev is not NULL, and updated documentation of index
parameter. Function extcon_find_cable_index() has been deleted and cannot be
used to retrieve cable number.
Signed-off-by: Robert Baldyga
---
drivers/extcon/extcon-class.c |9 ++---
1 file changed, 6 insertion
This patch removes two functions, extcon_find_cable_index() and
extcon_get_edev_by_phandle(). They are not longer needed, since
extcon client API has changed to be oriented on extcon_cable instead
of extcon_dev.
Signed-off-by: Robert Baldyga
---
drivers/extcon/extcon-class.c | 67 -
This patch modifies extcon-gpio driver to use initialization data from
devicetree if platform data is not available. It allows to set controller
and cable names, and another parameters from devicetree bindings.
Signed-off-by: Robert Baldyga
---
drivers/extcon/extcon-gpio.c | 63 +
This patch removes cable array example form extcon code, to avoid
littering driver namespace. Now it's located in extcon documentation.
Signed-off-by: Robert Baldyga
---
Documentation/extcon/extcon.txt | 108 +++
drivers/extcon/extcon-class.c | 32 ---
This patch adds check if pdata is NULL, to avoid NULL pointer dereference
when platform data is not available. After this changes, in described
situation driver will be configured with default values.
Signed-off-by: Robert Baldyga
---
drivers/extcon/extcon-max77693.c |2 +-
1 file changed, 1
This patch adds check if pdata is NULL, to avoid NULL pointer dereference
when platform data is not available. After this changes, in described
situation driver will be configured with default values.
Signed-off-by: Robert Baldyga
---
drivers/extcon/extcon-max8997.c |2 +-
1 file changed, 1
This patch simplifies extcon_updata_state() function. There is greatly
simplified kobject_uevent preparation. Also meaning of variable passed
to raw_notifier_call_chain() (and in effect to _call_per_cable()) has
changed. Now positions on ones in variable 'val' in _call_per_cable()
indicates numbers
This patch removes extcon_set_cable_state() and replace all calls of
this function witch extcon_set_cable_state_(), which is faster version.
This is first step of changing extcon API to faster and safer.
Signed-off-by: Robert Baldyga
---
drivers/extcon/extcon-class.c| 17
drivers/
This patch improves extcon client API to get rid of ugly functions operating
on name strings. It gives independency from naming convention in extcon
provider drivers. Names given at provider registration are now used only
for sysfs, debugs, and to support platforms using legacy devicetree bindings.
This patch changes charger-manager bindings to be compatible with
new extcon bindings.
Signed-off-by: Robert Baldyga
---
.../bindings/power_supply/charger-manager.txt | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/power_su
This patchset adds many improvements to extcon class driver and extcon
provider drivers. It changes extcon API to faster and safer by replaceing
function taking extcon and cable names with functions working with
structures representing this objects.
It adds more advanced devicetree support which a
From: Li Jun
This patch adds sys input to control and show OTG fsm inputs by application,
user can do host and preipheral role switch by change these inputs.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/otg.c |2 +
drivers/usb/chipidea/otg_fsm.c | 173 +++
This patch adds OTG fsm related initialization when do otg init,
add a seperate file for OTG fsm related utilities.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/Makefile |1 +
drivers/usb/chipidea/ci.h | 17 +++
drivers/usb/chipidea/otg.c |4 +++
drivers/usb/chipide
Add OTG HNP and SRP operation functions implementation:
- charge vbus
- drive vbus
- connection signaling
- drive sof
- start data pulse
- add fsm timer
- delete fsm timer
- start host
- start gadget
Signed-off-by: Li Jun
---
drivers/usb/chipidea/bits.h|9 ++
drivers/usb/chipidea/ci.h
From: Li Jun
USB OTG interrupt handling and fsm transitions according to USB OTG
and EH 2.0.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/core.c| 23 ++--
drivers/usb/chipidea/otg.c |9 +-
drivers/usb/chipidea/otg_fsm.c | 232
drivers/u
From: Li Jun
This patchset adds USB OTG HNP and SRP support on chipidea usb driver,
existing OTG port role swtich function by ID pin status kept unchanged,
based on that, if select CONFIG_USB_OTG_FSM, OTG HNP and SRP will be
supported.
Reference to:
"On-The-Go and Embedded Host Supplement to the
From: Li Jun
This patch adds sysfs interface description for chipidea USB OTG HNP and SRP.
Signed-off-by: Li Jun
---
.../ABI/testing/sysfs-platform-chipidea-usb-otg| 56
1 file changed, 56 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-platform-chipidea-
Add b_hnp_enable request handling and enable gadget->is_otg
Acked-by: Peter Chen
Signed-off-by: Li Jun
---
drivers/usb/chipidea/udc.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
index f58857d..cba7fd6
From: Li Jun
This patch adds OTG fsm timers initialization, which use controller's 1ms
interrupt as timeout counter, also adds some local timers which are not
in otg_fsm_timer list.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/bits.h|1 +
drivers/usb/chipidea/otg_fsm.c | 189 +++
From: Li Jun
This patch adds a debug file for OTG vairables show.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/debug.c | 84 ++
1 file changed, 84 insertions(+)
diff --git a/drivers/usb/chipidea/debug.c b/drivers/usb/chipidea/debug.c
index 5b890c1..
From: Li Jun
This patch adds a file chipidea.txt for how to demo chipidea usb OTG HNP and SRP
functions via sysfs input files, any other possible information should be
documented for chipidea usb driver in future can be added into this file.
Signed-off-by: Li Jun
---
Documentation/usb/chipidea
Leave vbus on/off hanlded by OTG fsm if in OTG mode.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/host.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/chipidea/host.c b/drivers/usb/chipidea/host.c
index a8ac6c1..ffb4168 100644
--- a/drivers/usb/ch
Init otg_port number of otg capable host to be 1 at host start.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/host.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/chipidea/host.c b/drivers/usb/chipidea/host.c
index ffb4168..a93d950 100644
--- a/dr
On 10-04-2014 15:14, David Laight wrote:
It doesn't do any pin muxing. It switches SoC internal USB
signals between
USB controllers. The pins remain the same.
Doesn't something like that already happen for the companion USB1
controllers for USB2 ports?
Did you mean USB 1.1 and U
On 04/10/2014 02:26 PM, Andreas Reis wrote:
> Only your 0/3 patch to which Alan linked, along with two other
> patches by Mathias Nyman ("disable usb3 on intel hosts" and "disable
> all lpm related control transfers", one of which is the source of
> the "do nothing"s).
>
> I'll revert the latter t
Adds product ID for the Novatel E371 PCI Express Mini Card.
$ lsusb
Bus 001 Device 024: ID 1410:9011 Novatel Wireless
$ usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 24 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1410 ProdID=9011 Rev=00.03
Only your 0/3 patch to which Alan linked, along with two other patches
by Mathias Nyman ("disable usb3 on intel hosts" and "disable all lpm
related control transfers", one of which is the source of the "do
nothing"s).
I'll revert the latter two and apply the rest of the set. Which I'm
guessin
On Thu, Apr 10, 2014 at 04:09:31PM +0800, Peter Chen wrote:
> On Wed, Apr 09, 2014 at 08:29:30PM +0800, Li Jun wrote:
> > From: Li Jun
> >
> > This patchset adds USB OTG HNP and SRP support on chipidea usb driver,
> > existing OTG port role swtich function by ID pin status kept unchanged,
> > bas
On Wed, Apr 9, 2014 at 7:03 PM, Tomasz Figa wrote:
> On 09.04.2014 13:49, Vivek Gautam wrote:
>>
>> Hi,
>>
>>
>> On Wed, Apr 9, 2014 at 4:36 PM, Tomasz Figa wrote:
>>>
>>> Hi Vivek,
>>>
>>> Please see my comments inline.
>>>
>>>
>>> On 08.04.2014 16:36, Vivek Gautam wrote:
Add a ne
On 04/10/2014 12:58 PM, Andreas Reis wrote:
> That patch appears to work in preventing the crashes, judged on one
> repeated appearance of the bug.
>
> dmesg had the usual
> [ 215.229903] usb 4-2: usb_disable_lpm called, do nothing
> [ 215.336941] usb 4-2: reset SuperSpeed USB device number 3 us
On 10/04/14 12:14, David Laight wrote:
From: Ben Dooks
On 10/04/14 11:49, Sergei Shtylyov wrote:
On 10-04-2014 13:20, David Laight wrote:
It doesn't do any pin muxing. It switches SoC internal USB
signals between
USB controllers. The pins remain the same.
Doesn't something like that
From: Ben Dooks
> On 10/04/14 11:49, Sergei Shtylyov wrote:
> > On 10-04-2014 13:20, David Laight wrote:
> >
> >>> It doesn't do any pin muxing. It switches SoC internal USB
> >>> signals between
> >>> USB controllers. The pins remain the same.
> >
> >> Doesn't something like that already happ
Greg KH writes:
> On Wed, Apr 09, 2014 at 10:02:53PM +, Jim Bockerstette wrote:
>> I have been using the Edgeport 8s MEI to talk RS232 to my devices with
>> good success. However, I cannot get it to talk RS485.
>
> Does that hardware even support 485?
It does, according to http://www.digi.com
Hi,
On Wed, Apr 9, 2014 at 6:08 PM, Tomasz Figa wrote:
> Hi,
>
>
> On 09.04.2014 14:24, Vivek Gautam wrote:
>>
>> Hi Sylwester,
>>
>>
>> On Wed, Apr 9, 2014 at 5:41 PM, Sylwester Nawrocki
>> wrote:
>>>
>>> Hi Vivek,
>>>
>>> On 09/04/14 13:54, Vivek Gautam wrote:
Adding support to enab
On 10/04/14 11:49, Sergei Shtylyov wrote:
On 10-04-2014 13:20, David Laight wrote:
It doesn't do any pin muxing. It switches SoC internal USB
signals between
USB controllers. The pins remain the same.
Doesn't something like that already happen for the companion USB1
controllers for USB2
That patch appears to work in preventing the crashes, judged on one
repeated appearance of the bug.
dmesg had the usual
[ 215.229903] usb 4-2: usb_disable_lpm called, do nothing
[ 215.336941] usb 4-2: reset SuperSpeed USB device number 3 using xhci_hcd
[ 215.350296] xhci_hcd :00:14.0: xHC
On 10-04-2014 13:20, David Laight wrote:
It doesn't do any pin muxing. It switches SoC internal USB signals between
USB controllers. The pins remain the same.
Doesn't something like that already happen for the companion USB1
controllers for USB2 ports?
Did you mean USB 1.1 and USB 2
Hi Kishon,
On Thu, Apr 10, 2014 at 2:39 PM, Kishon Vijay Abraham I wrote:
> Hi.
>
> On Wednesday 09 April 2014 05:24 PM, Vivek Gautam wrote:
>> Adding support to enable/disable VBUS hooked to a gpio
>> to enable vbus supply on the port.
>>
>> Signed-off-by: Vivek Gautam
>> ---
>>
>> Based on 'p
Patch 'b8efdaf USB: EHCI: add check for wakeup/suspend race'
adds a check for possible race between suspend and wakeup interrupt,
and thereby it returns -EBUSY as error code if there's a wakeup
interrupt.
So the platform host controller should not proceed further with
its suspend callback, rather s
Patch 'b8efdaf USB: EHCI: add check for wakeup/suspend race'
adds a check for possible race between suspend and wakeup interrupt,
and thereby it returns -EBUSY as error code if there's a wakeup
interrupt.
So the platform host controller should not proceed further with
its suspend callback, rather s
From: Sergei Shtylyov
> It doesn't do any pin muxing. It switches SoC internal USB signals between
> USB controllers. The pins remain the same.
Doesn't something like that already happen for the companion USB1
controllers for USB2 ports?
That also doesn't sound like you are changing the PHY.
On Wed, Apr 09, 2014 at 08:29:30PM +0800, Li Jun wrote:
> From: Li Jun
>
> This patchset adds USB OTG HNP and SRP support on chipidea usb driver,
> existing OTG port role swtich function by ID pin status kept unchanged,
> based on that, if select CONFIG_USB_OTG_FSM, OTG HNP and SRP will be
> supp
Hi.
On Wednesday 09 April 2014 05:24 PM, Vivek Gautam wrote:
> Adding support to enable/disable VBUS hooked to a gpio
> to enable vbus supply on the port.
>
> Signed-off-by: Vivek Gautam
> ---
>
> Based on 'phy-exynos5-usbdrd' patches:
> [PATCH V4 0/5] Add Exynos5 USB 3.0 phy driver based on ge
From: Alan Stern
...
> Furthermore, I clearly recall Sarah Sharp (the original maintainer for
> xhci-hcd) saying that the support for isochronous transfers needed
> attention. This may well be an example.
You also definitely don't want to cancel an isoc urb.
Doing so is likely to corrupt the kern
On Thu, Apr 10, 2014 at 12:05:52AM -0700, narasimharo bolisetti wrote:
> My kernel version is:
> 2.6.35.6-45.fc14.i686
Maintenance for this kernel has been dropped years ago, so it very
likely contains many bugs that were fixed in more recent ones. You
should definitely upgrade.
Hoping this he
On Wed, 2014-04-09 at 22:57 +0800, Xiao Jin wrote:
> Thanks all for the review. We meet with the problems when developing
> product. I would like to explain my understanding.
>
> On 04/08/2014 11:05 AM, Xiao Jin wrote:
> >
> > We find two problems on acm tty write delayed mechanism.
> > (1) When
Hi,
I have checked the same in the recent kernel versions also. Issue is still
remain.
Regards,
Narasimharao B
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: 10 April 2014 13:26
To: narasimharo bolisetti
Cc: linux-ker...@vger.kernel.org; kernelnewb...@nl.linux.org;
Hi Greg/All,
This is Narasimharao working for a s/wcompany HCLT..
I am working a issue and
the description is below:
system stops booting and
needs a series of console inputs (space bar or return) to
continue booting. Each input advances the process a little
bit.
Actuall
82 matches
Mail list logo
