Hi,
On Thu, Mar 07, 2013 at 03:14:23PM -0800, a...@linux-foundation.org wrote:
>
> The patch titled
> Subject: drivers/usb/dwc3/ep0.c: fix sparc64 build
> has been added to the -mm tree. Its filename is
> drivers-usb-dwc3-ep0c-fix-sparc64-build.patch
>
> Before you just go and hit "re
On Fri, Mar 08, 2013 at 12:51:13PM +0530, Venu Byravarasu wrote:
> > -Original Message-
> > From: linux-tegra-ow...@vger.kernel.org [mailto:linux-tegra-
> > ow...@vger.kernel.org] On Behalf Of Stephen Warren
> > Sent: Friday, March 08, 2013 2:07 AM
> > To: Felipe Balbi; Venu Byravarasu
> >
Hi,
On Fri, Mar 08, 2013 at 02:27:58PM +0800, Peter Chen wrote:
> > > > > For boards which have board level vbus control (eg, gpio), we
> > > > > need to operation vbus according to below rules:
> > > > > - For host, the vbus should always be on.
> > > > > - For otg, the vbus needs to be turned on
> -Original Message-
> From: linux-tegra-ow...@vger.kernel.org [mailto:linux-tegra-
> ow...@vger.kernel.org] On Behalf Of Stephen Warren
> Sent: Friday, March 08, 2013 2:07 AM
> To: Felipe Balbi; Venu Byravarasu
> Cc: Linux USB Mailing List; Greg KH; linux-te...@vger.kernel.org;
> s.ha...@p
Hi,
On Fri, Mar 08, 2013 at 09:28:34AM +0800, Peter Chen wrote:
> > > > > diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
> > > > > index e82dae4..70f9f2d 100644
> > > > > --- a/drivers/usb/chipidea/udc.c
> > > > > +++ b/drivers/usb/chipidea/udc.c
> > > > > @@ -91,8 +91,10 @@
Hi,
On Thu, Mar 07, 2013 at 02:20:36PM -0700, Stephen Warren wrote:
> On 03/07/2013 02:35 AM, Felipe Balbi wrote:
> > Hi folks,
> >
> > inspired by Paul's DWC2 patchset which added usb_otg_state_string()
> > (a copy of otg_state_string()) I have now renamed otg_state_string()
> > to usb_otg_state
On Thu, Mar 07, 2013 at 01:54:53PM -0700, Stephen Warren wrote:
> On 03/07/2013 02:36 AM, Felipe Balbi wrote:
> > CONFIG_USB_OTG_UTILS will be removed very
> > soon, so we should check CONFIG_USB_PHY
> > instead.
>
> The Tegra EHCI driver isn't very useful without the Tegra PHY driver.
> Perhaps i
On Thu, Mar 07, 2013 at 01:37:17PM -0700, Stephen Warren wrote:
> On 03/07/2013 08:45 AM, Felipe Balbi wrote:
> > this will make sure that we have sensible names
> > for all phy drivers. Current situation was already
> > quite bad with too generic names being used.
>
> Is phy-$name specific enough
On Thu, Mar 07, 2013 at 09:15:49PM +, Paul Zimmerman wrote:
> > From: Felipe Balbi [mailto:ba...@ti.com]
> > Sent: Wednesday, March 06, 2013 11:52 PM
> >
> > On Wed, Mar 06, 2013 at 11:26:08PM +, Paul Zimmerman wrote:
> > > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > > Sent: Wednesday
On Thu, Mar 07, 2013 at 02:46:23PM +0100, Michael Grzeschik wrote:
> > > > + mReq->req.actual += reqnodesize;
> > > > +
> > > > + if (length > TD_COUNT * CI13XXX_PAGE_SIZE) {
> > > > + int rest = length - mReq->req.actual;
> > > > + while (rest > 0) {
> > > >
On Thu, Mar 07, 2013 at 11:52:48AM +0200, Felipe Balbi wrote:
> On Thu, Mar 07, 2013 at 10:41:03AM +0800, Peter Chen wrote:
> > On Wed, Mar 06, 2013 at 01:29:16PM +0200, Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Wed, Mar 06, 2013 at 05:56:37PM +0800, Peter Chen wrote:
> > > > For boards which h
AB8500 versions preceding 2.0 were only used internally by ST-Ericsson
and are not supported anymore. This patch drops all v1.0 and v1.1
support code.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/otg/ab8500-usb.c | 139 ---
1 fil
Add ux500_musb_set_vbus() implementation for ux500.
This is based on the version originally developed inside ST-Ericsson.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500.c | 64
1 file changed, 64 insertions(+)
Add transceiver notifier event handling to the ux500 driver to set vbus
on specific transceiver events.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500.c | 42 ++
1 file changed, 42 insertions(+)
diff --git a/drivers/usb/
From: Virupax Sadashivpetimath
Fix dma_controller_create() fail path in case memory resource is
missing.
Acked-by: Linus Walleij
Signed-off-by: Virupax Sadashivpetimath
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500_dma.c | 12 +++-
1 file changed, 11 insertions(+), 1 dele
Hello Felipe,
this is the v2 of my initial update series for ux500's musb.
Changes from v1:
- turn off vbus on USB_EVENT_VBUS event
Thanks,
Fabio
Fabio Baltieri (4):
usb: musb: ux500: implement musb_set_vbus
usb: musb: ux500: add otg notifier support
usb: otg: ab8500-usb: drop support fo
Update irq handling code to notify all possible link status changes of
AB8500 and AB8505 to the ux500-musb glue driver. The additional event
codes will be used for pm-runtime implementation, and are defined in a
separate ux500-specific header.
This also modify the irq registration code to use dev
On Thu, Mar 07, 2013 at 11:50:54AM +0200, Felipe Balbi wrote:
> Hi,
>
> On Thu, Mar 07, 2013 at 10:36:13AM +0800, Peter Chen wrote:
> > > > diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
> > > > index e82dae4..70f9f2d 100644
> > > > --- a/drivers/usb/chipidea/udc.c
> > > > ++
On Fri, Mar 08, 2013 at 12:16:08AM +0100, Jiri Kosina wrote:
> On Fri, 8 Mar 2013, Ming Lei wrote:
>
> > If suspend callback fails in system sleep context, usb core will
> > ignore the failure and let the system sleep go ahead further, so this
> > patch doesn't recover device under this situation,
On Thu, Mar 07, 2013 at 11:46:23AM -0600, Seth Forshee wrote:
> Hi Sarah,
>
> Just wondering if you've had a chance to take a look at this yet.
>
> Thanks,
> Seth
I have the device sitting in my cube, but I haven't had a chance to hook
it up to the analyzer yet. I'm going to be out mid-next wee
On Thu, Mar 07, 2013 at 03:28:07PM -0500, David Miller wrote:
> From: Ming Lei
> Date: Fri, 8 Mar 2013 00:15:17 +0800
>
> > This patch adds comments on interface driver suspend callback
> > to emphasize that the failure return value is ignored by
> > USB core in system sleep context, so do not t
The Rigblaster Advantage is an amateur radio interface sold by West Mountain
Radio. It contains a cp210x serial interface but the device ID is not in
the driver.
Signed-off-by: Steve Conklin
---
drivers/usb/serial/cp210x.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial
On Fri, 8 Mar 2013, Ming Lei wrote:
> If suspend callback fails in system sleep context, usb core will
> ignore the failure and let the system sleep go ahead further, so this
> patch doesn't recover device under this situation, otherwise
> may cause resume() confused.
>
> Cc: Jiri Kosina
> Signe
Add debugging to say exactly which command addresses are getting
canceled, when we can't find a command that needed to be canceled, and
add some debugging when commands or watchdog timers choose not to cancel
a command due to not being the first command on the command ring.
Signed-off-by: Sarah Sh
The function xhci_cmd_to_noop does two things: it turns a canceled
command into a no-op command, and it calls the command's completion
structure.
However, if buggy code leads us to not find the command in the command
ring, we can leave a canceled command waiting on a completion. This is
unlikely
If we get a command ring completion, but our command ring dequeue
pointer isn't on the command that completed, print a warning.
Signed-off-by: Sarah Sharp
---
drivers/usb/host/xhci-ring.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c
Add debugging for Set Address and No-op commands.
Signed-off-by: Sarah Sharp
---
drivers/usb/host/xhci-ring.c |4
drivers/usb/host/xhci.c |6 ++
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index
This patch added some code to the xHCI driver to make it stall every
other Set Address command, and stop ringing the doorbells of bulk
endpoints after two URBs were submitted to the host.
This made it easy to test the command cancellation code, to ensure that:
1. Commands that weren't at the dequ
The TLDR version: we need to turn command TRBs into a no-op command,
even if the command dequeue pointer points to them on a command ring
stop completion event.
When the xHCI host controller is in the middle of a command, and
software writes the command abort bit in the CRCR register, the host
wil
Refactor copy-paste code to use the new function to find the next
enqueue pointer.
Signed-off-by: Sarah Sharp
---
drivers/usb/host/xhci.c | 18 ++
1 files changed, 2 insertions(+), 16 deletions(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index b3ff5d9..6d
"One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them"
- J. R. R. Tolkien
There is only one command ring for each xHCI host, and all commands flow
through that ring. However, when a tricksy little USB device fails to
respond to the Set Addre
xhci_abort_cmd_ring() spins for up to five seconds while waiting for a
register read to show that the command ring is stopped. It is holding
the xhci->spinlock with IRQs disabled, which is not good on xHCI hosts
that share legacy PCI interrupts with other PCI devices.
Make the xhci_abort_cmd_ring
When the command ring is halted, xhci_cmd_to_noop() is called with an
xHCI command that needs to be canceled. The struct xhci_cd contains a
pointer to the xhci_trb that needs to be removed from the command ring.
That function will turn the TRB into a no-op command.
Currently, the code that stores
This patchset attempts to fix a particularly nasty bug that causes the
xHCI host to be marked as 'dying' and all USB devices to be
disconnected.
The bug happens when some USB device (say a VIA USB 3.0 hub) refuses to
answer to the Set Address command in a timely manner, while other
commands are qu
Hey Alex,
On Thu, Jan 24, 2013 at 11:42:53AM +0200, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > On Tue, Nov 27, 2012 at 05:16:55PM +0100, Michael Grzeschik wrote:
> >> Nearly every SoC from Freescale has this non-core usb registers. This
> >> series
> >> adds support for more users of
Hello.
On 03/08/2013 01:01 AM, Steve Conklin wrote:
The Rigblaster Advantage is an amateur radio interface sold by West Mountain
Radio. It contains a cp210x serial interface but the device ID is not in the
driver.
Wrap your changelog lines at about 76 (80 max) characters please.
Signed
The Rigblaster Advantage is an amateur radio interface sold by West Mountain
Radio. It contains a cp210x serial interface but the device ID is not in the
driver.
Signed-off-by: Steve Conklin
---
drivers/usb/serial/cp210x.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/seri
On Thu, 2013-03-07 at 10:43 +0100, Johan Hovold wrote:
> On Wed, Mar 06, 2013 at 02:14:56PM -0500, Peter Hurley wrote:
> > On Wed, 2013-03-06 at 17:52 +0100, Johan Hovold wrote:
> > > Yes, I did. First, the order should not matter for blocked opens as they
> > > will exit their wait loops based on
On 03/07/2013 02:35 AM, Felipe Balbi wrote:
> Hi folks,
>
> inspired by Paul's DWC2 patchset which added usb_otg_state_string()
> (a copy of otg_state_string()) I have now renamed otg_state_string()
> to usb_otg_state_string(), moved it to usb-common, then moved all
> phy drivers to drivers/usb/ph
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Wednesday, March 06, 2013 11:52 PM
>
> On Wed, Mar 06, 2013 at 11:26:08PM +, Paul Zimmerman wrote:
> > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > Sent: Wednesday, March 06, 2013 12:05 AM
> >
> > ...
> >
> > > looking at that loop, is it
On Thu, 7 Mar 2013, Alan Stern wrote:
> On Thu, 7 Mar 2013, Paul Zimmerman wrote:
>
> > Hi Alan,
> >
> > I was talking about uhci_hcd_endpoint_disable(). It drops the spinlock,
> > reacquires it, but doesn't reload qh from hep->hcpriv before continuing.
> > Maybe that's not required for uhci, I
On 03/07/2013 02:36 AM, Felipe Balbi wrote:
> CONFIG_USB_OTG_UTILS will be removed very
> soon, so we should check CONFIG_USB_PHY
> instead.
The Tegra EHCI driver isn't very useful without the Tegra PHY driver.
Perhaps its Kconfig should simply "select USB_PHY", and the ifdefs be
removed rather th
On 03/07/2013 08:45 AM, Felipe Balbi wrote:
> this will make sure that we have sensible names
> for all phy drivers. Current situation was already
> quite bad with too generic names being used.
Is phy-$name specific enough? There are other types of PHY such as
Ethernet, etc. What about phy-usb-$na
From: Ming Lei
Date: Fri, 8 Mar 2013 00:15:17 +0800
> This patch adds comments on interface driver suspend callback
> to emphasize that the failure return value is ignored by
> USB core in system sleep context, so do not try to recover
> device for this case, otherwise the recovery things may co
On Fri, 8 Mar 2013, Ming Lei wrote:
> This patch adds comments on interface driver suspend callback
> to emphasize that the failure return value is ignored by
> USB core in system sleep context, so do not try to recover
> device for this case and let resume/reset_resume callback
> handle the suspe
On Thu, 7 Mar 2013, Paul Zimmerman wrote:
> Hi Alan,
>
> I was talking about uhci_hcd_endpoint_disable(). It drops the spinlock,
> reacquires it, but doesn't reload qh from hep->hcpriv before continuing.
> Maybe that's not required for uhci, I didn't look any deeper.
No, it's not required. hep-
On Thu, 7 Mar 2013, Jenya Y wrote:
> // sorry for double-post I was advised to use 'reply to all' and wasn't
> sure if the prev. message was forwarded to linux-usb
>
> Thank you for the reply.
> I'd be bold enough to categorize this as a problem, since the usb hub
> doesn't work.
> It could b
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Thursday, March 07, 2013 7:35 AM
>
> On Wed, 6 Mar 2013, Paul Zimmerman wrote:
>
> > > BTW, you _do_ have a race because you don't check ep->hcpriv when
> > > ->urb_enqueue() is called. This means that you could queue to an
> > > endpo
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Wednesday, March 06, 2013 11:39 PM
>
> On Wed, Mar 06, 2013 at 08:14:34PM +, Paul Zimmerman wrote:
> > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > Sent: Wednesday, March 06, 2013 12:11 PM
> > > On Wed, Mar 06, 2013 at 07:22:33PM +, Pa
// sorry for double-post I was advised to use 'reply to all' and wasn't
sure if the prev. message was forwarded to linux-usb
Thank you for the reply.
I'd be bold enough to categorize this as a problem, since the usb hub
doesn't work.
It could be 'expected' if it were a RC version of the ke
Ming Lei writes:
> If suspend callback fails in system sleep context, usb core will
> ignore the failure and let system sleep go ahead further, so
> this patch comments on the case and requires that both
> usbnet_suspend() and subdriver->suspend() MUST return 0 in
> system sleep context.
>
> Cc:
Ming Lei writes:
> If suspend callback fails in system sleep context, usb core will
> ignore the failure and let system sleep go ahead further, so
> this patch comments on the case and requires that both
> usbnet_suspend() and subdriver->suspend() MUST return 0 in
> system sleep context.
>
> Cc:
Please use Reply-To-All, so that your message gets sent to the mailing
list as well as to me.
On Thu, 7 Mar 2013, Jenya Y wrote:
> Thank you Alan for the reply.
> I'd be bold enough to categorize this as a problem, since the usb hub
> doesn't work.
> It could be 'expected' if it were a RC ve
Hi,
On Thu, Mar 07, 2013 at 04:51:59PM +0200, Felipe Balbi wrote:
> why is this otg_dev even needed ? Can you refresh my memory ?
If you want to handle OTG controller interrupt you need it... Though looks
like tahvo does not really need it, and it can be disabled.
A.
--
To unsubscribe from this
On Tue, Feb 26, 2013 at 10:50:21AM -0600, Seth Forshee wrote:
> On Tue, Feb 26, 2013 at 12:30:58AM +0100, Christian Lamparter wrote:
> > On Monday, February 25, 2013 09:19:03 PM Alan Stern wrote:
> > > On Mon, 25 Feb 2013, Seth Forshee wrote:
> > > > > > >88012fe19500 1519981417 S Bo:3:003:1 -1
On Thu, Mar 07, 2013 at 07:03:38PM +0200, Alexander Shishkin wrote:
> On 7 March 2013 18:47, Felipe Balbi wrote:
> > Hi,
> >
> > On Fri, Feb 22, 2013 at 10:24:41AM +0200, Felipe Balbi wrote:
> >> chipidea's ffs_nr() is pretty much what __ffs() does.
> >>
> >> Use that one instead.
> >>
> >> Signed
* Aaro Koskinen [130307 06:44]:
> +#include
We should be getting rid of the plat and mach includes for
drivers for omap1 also, so let's not make it harder by adding
more of it. We should have just the following:
include/linux/platform_data/usb-omap.h this contains just minimal pdata
include/li
On 7 March 2013 18:47, Felipe Balbi wrote:
> Hi,
>
> On Fri, Feb 22, 2013 at 10:24:41AM +0200, Felipe Balbi wrote:
>> chipidea's ffs_nr() is pretty much what __ffs() does.
>>
>> Use that one instead.
>>
>> Signed-off-by: Felipe Balbi
>
> it has been almost 2 weeks, just a gentle ping here.
It's
Hi,
On Fri, Feb 22, 2013 at 10:24:41AM +0200, Felipe Balbi wrote:
> chipidea's ffs_nr() is pretty much what __ffs() does.
>
> Use that one instead.
>
> Signed-off-by: Felipe Balbi
it has been almost 2 weeks, just a gentle ping here.
cheers
--
balbi
signature.asc
Description: Digital signa
On Thu, Mar 07, 2013 at 11:01:47AM -0500, Alan Stern wrote:
> On Thu, 7 Mar 2013, Felipe Balbi wrote:
>
> > Hi folks,
> >
> > inspired by Paul's DWC2 patchset which added usb_otg_state_string()
> > (a copy of otg_state_string()) I have now renamed otg_state_string()
> > to usb_otg_state_string(),
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Also add comments on this case.
Cc: Steve Glendinning
Signed-off-by: Ming Lei
---
drivers/net/usb/smsc75xx.c |
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Also add comments on the case.
Cc: Steve Glendinning
Signed-off-by: Ming Lei
---
drivers/net/usb/smsc95xx.c |
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch comments on the case and requires that both
usbnet_suspend() and subdriver->suspend() MUST return 0 in
system sleep context.
Cc: Bjørn Mork
Signed-off-by: Ming
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch comments on the case and requires that both
usbnet_suspend() and subdriver->suspend() MUST return 0 in
system sleep context.
Cc: Bjørn Mork
Signed-off-by: Ming
If suspend callback fails in system sleep context, usb core will
ignore the failure and let the system sleep go ahead further, so this
patch doesn't recover device under this situation, otherwise
may cause resume() confused.
Cc: Jiri Kosina
Signed-off-by: Ming Lei
---
drivers/hid/usbhid/hid-cor
This patch kills traffic even though type->suspend returns
failure inside usb_serial_suspend from system sleep context
because USB core ignores the failiure and lets system sleep
go ahread, so the serial URB traffic need to be killed
in this case.
Cc: Johan Hovold
Signed-off-by: Ming Lei
---
dr
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case and let resume/reset_resume callback
handle the suspend failure if needed.
Also kerneldoc for usb_s
Hi,
Sorry for my broken email client just now.
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case, otherwise the recovery things may confuse
resume()
This patch kills traffic even though type->suspend returns
failure inside usb_serial_suspend from system sleep context
because USB core ignores the failiure and lets system sleep
go ahread, so the serial URB traffic need to be killed
in this case.
Cc: Johan Hovold
Signed-off-by: Ming Lei
---
dr
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case and let resume/reset_resume callback
handle the suspend failure if needed.
Also kerneldoc for usb_s
Hi,
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case, otherwise the recovery things may confuse
resume().
Also fixes the USB serial, HID and severa
On Thu, 7 Mar 2013, Jenya Y wrote:
>
> UPDATE correction to the name of the device Apple Cinema HD Display (
> A1082)
>
> Since kernel 3.8 Apple Cinema Display's usb hub spits errors randomly at
> boot. (their count seems to be random, but the type of the error is
> always the same)
>
> As so
On Thu, 7 Mar 2013, Felipe Balbi wrote:
> Hi folks,
>
> inspired by Paul's DWC2 patchset which added usb_otg_state_string()
> (a copy of otg_state_string()) I have now renamed otg_state_string()
> to usb_otg_state_string(), moved it to usb-common, then moved all
> phy drivers to drivers/usb/phy/
On Thu, Mar 07, 2013 at 05:45:26PM +0200, Felipe Balbi wrote:
> this will make sure that we have sensible names
> for all phy drivers. Current situation was already
> quite bad with too generic names being used.
>
> Signed-off-by: Felipe Balbi
Hi, I compiled what I could with allmodconfig and al
this will make sure that we have sensible names
for all phy drivers. Current situation was already
quite bad with too generic names being used.
Signed-off-by: Felipe Balbi
---
drivers/usb/phy/Makefile | 42 +++---
drivers/usb/phy/{ab8500-usb.c => phy-ab8
On Wed, 6 Mar 2013, Paul Zimmerman wrote:
> > BTW, you _do_ have a race because you don't check ep->hcpriv when
> > ->urb_enqueue() is called. This means that you could queue to an
> > endpoint which is in the process of getting disabled. The urb would
> > either be lost or completed before being
Move port drain-delay handling to a separate function.
Signed-off-by: Johan Hovold
---
drivers/tty/tty_port.c | 27 ---
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/drivers/tty/tty_port.c b/drivers/tty/tty_port.c
index cd65f7e..048cc85 100644
--- a/driv
Make sure to check ASYNC_INITIALISED before raising DTR when waking up
from blocked open in tty_port_block_til_ready.
Currently DTR could get raised at hang up as a blocked process would
raise DTR unconditionally before checking for hang up and returning.
Signed-off-by: Johan Hovold
---
drivers
Untangle port-shutdown logic and make sure the initialised flag is
always cleared for non-console ports.
Signed-off-by: Johan Hovold
---
drivers/tty/tty_port.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/tty_port.c b/drivers/tty/tty_port.c
index b7ff5
These patches against 3.9-rc1 fix a few issues with tty-port hangup and
close.
The first and fifth patch are essentially clean ups.
The second and third patch fix the fact that DTR could get raised
(rather than dropped) at hangup if there are blocked opens. [ Note that
the second patch has been s
Move HUPCL handling to port shutdown so that DTR is dropped also on hang
up (tty_port_close is a noop for hung-up ports).
Also do not try to drop DTR for uninitialised ports where it has never
been raised (e.g. after a failed open).
Note that this is also the current behaviour of serial-core.
Ni
Make sure we do not make tty-driver callbacks or wait for port to drain
on uninitialised ports (e.g. when open failed) in
tty_port_close_start().
No callback, such as flush_buffer or wait_until_sent, needs to be made
on a port that has never been opened. Neither does it make much sense to
add drai
Move wake up of processes on blocked-open and modem-status wait queues
to after port shutdown at hangup.
This way the woken up processes can use the ASYNC_INITIALIZED flag to
detect port shutdown.
Note that this is the order currently used by serial-core.
Signed-off-by: Johan Hovold
---
driver
On Thu, Mar 07, 2013 at 04:40:21PM +0200, Aaro Koskinen wrote:
> Add Tahvo USB transceiver driver.
>
> Based on old code from linux-omap tree. The original driver was written
> by Juha Yrjölä, Tony Lindgren, and Timo Teräs.
>
> Signed-off-by: Aaro Koskinen
> ---
> drivers/usb/otg/Kconfig |
On Thu, Mar 07, 2013 at 04:40:20PM +0200, Aaro Koskinen wrote:
> omap-otg platform device will be needed also by other transceivers.
> It's not possible to have multiple instances of the driver, so it needs
> to be moved into a separate file so that other drivers can hook into it.
>
> Start this c
Hi,
On Thu, Mar 07, 2013 at 04:40:18PM +0200, Aaro Koskinen wrote:
> Tahvo is a multi-function device on Nokia 770, implementing USB
> transceiver and charge/battery control.
>
> It's so close to Retu that a single driver can support both.
>
> Signed-off-by: Aaro Koskinen
> Cc: Samuel Ortiz
>
there are no more users of CONFIG_USB_OTG_UTILS
left in tree, we can remove it just fine.
Signed-off-by: Felipe Balbi
---
v1 -> v2:
. removed a few extra instances which my original (and stupid)
grep didn't find
drivers/power/Kconfig | 2 +-
drivers/usb/dwc3/Kconf
Tahvo is a multi-function device on Nokia 770, implementing USB
transceiver and charge/battery control.
It's so close to Retu that a single driver can support both.
Signed-off-by: Aaro Koskinen
Cc: Samuel Ortiz
---
drivers/mfd/Kconfig |6 +--
drivers/mfd/retu-mfd.c | 95 ++
Hi,
These patches add support for Tahvo USB transceiver and allow use both
host and peripheral modes on Nokia 770.
Patches work with 3.9-rc1, but the following fixes must be also applied:
ARM: OMAP1: fix USB host on 1710
http://marc.info/?l=linux-omap&m=135906630828618&w=2
omap-otg platform device will be needed also by other transceivers.
It's not possible to have multiple instances of the driver, so it needs
to be moved into a separate file so that other drivers can hook into it.
Start this change with a very simplest implementation, much of the
OMAP OTG code in i
Add Tahvo USB transceiver driver.
Based on old code from linux-omap tree. The original driver was written
by Juha Yrjölä, Tony Lindgren, and Timo Teräs.
Signed-off-by: Aaro Koskinen
---
drivers/usb/otg/Kconfig | 16 ++
drivers/usb/otg/Makefile|1 +
drivers/usb/otg/tahvo-usb.c | 6
Add platform data for Tahvo.
Signed-off-by: Aaro Koskinen
---
arch/arm/mach-omap1/board-nokia770.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/mach-omap1/board-nokia770.c
b/arch/arm/mach-omap1/board-nokia770.c
index 62a15e2..91449c5 100644
--- a/arch/arm/mach-omap
Am 07.03.2013 13:19, schrieb Bjørn Mork:
it looks like your app will need to be a member of the "usb" group to do
this. I assume there is a way for an app to request such permissions in
Android. Josh has obviously managed to get it.
Actually, the PPP Widget app requires access to a root shell
On Thu, Mar 07, 2013 at 09:25:34AM +0100, Michael Grzeschik wrote:
> On Tue, Mar 05, 2013 at 05:13:54PM +0800, Peter Chen wrote:
> > On Fri, Mar 01, 2013 at 03:42:27PM +0100, Michael Grzeschik wrote:
> > > This patch removes the limitation of having a limited amount of only
> > > four active tds on
Hi Benoit,
Here are the dt data patches to get usb device functional in OMAP platforms.
All the patches deal with modifying arch/arm/boot except one which modifies
Documentation/../usb/omap-usb.txt
Changes from v2:
* squashed the dt data for dwc3-omap with dwc3 core into a single patch.
Changes
Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
---
arch/a
Add omap-usb3 and omap-usb2 data node in omap5 device tree file.
The information for the node added here is available @
Documentation/devicetree/bindings/usb/usb-phy.txt
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap5.dtsi | 14 ++
1 file changed, 14 insertions(+)
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox. The information about this data node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
---
arch
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vija
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host mode.
The
1 - 100 of 141 matches
Mail list logo
