Hi,
> > AM33xx has two musb controller and they have one NOP PHY each.
> > Added the device tree data for NOP PHY.
>
> > Signed-off-by: Ajay Kumar Gupta
> > ---
> > arch/arm/boot/dts/am33xx.dtsi |8
> > 1 files changed, 8 insertions(+), 0 deletions(-)
>
> > diff --git a/arch/arm
On Tuesday 17 July 2012 14:52:51 Sarah Sharp wrote:
> 2. If an internal USB port is suspended with remote wakeup disabled,
> power off the port. Add code to the USB core to ignore the device
> disconnect in this special case, so the driver thinks the device is
> still suspended. Issue a reset-res
On Tuesday 17 July 2012 15:00:08 Alan Stern wrote:
> Furthermore, what happens if you power down a port when the attached
> device is active (not suspended)? Again it will look like a physical
> disconnect. So again, you don't want to power off such ports -- even
> though they don't have remo
Il 06/07/2012 19:41, Greg KH ha scritto:
On Wed, Jun 27, 2012 at 06:01:39PM +0200, Claudio Scordino wrote:
Hi Olav,
please find below a patch for the isp1362-hcd.c driver to always
save the message in case of underrun. More information is provided
inside the patch comment. Let us know i
On 07/18/2012 02:05 AM, Nicholas A. Bellinger wrote:
index 02ace18..9ddf315 100644
--- a/drivers/usb/gadget/tcm_usb_gadget.c
+++ b/drivers/usb/gadget/tcm_usb_gadget.c
@@ -1060,7 +1060,10 @@ static void usbg_cmd_work(struct work_struct *work)
tpg = cmd->fu->tpg;
tv_nexus = tpg->tpg
hi all:
2012/7/18 loody :
> hi:
>
> 2012/7/18 Greg KH :
>> On Wed, Jul 18, 2012 at 11:22:49AM +0800, loody wrote:
>>> Dear all:
>>> in usb_serial_probe, we create tty_port based on max_endpoints.
>>
>> Or based on the number that the driver said to create.
>>
>>> My questions are:
>>> 1. some call
On Mon, Jul 16, 2012 at 02:50:29PM +0200, Fabio Porcedda wrote:
> PROBLEM:
> 1.
> usb: gadget: at91_udc: kernel oops regression when connecting the usb cable
>
> 2.
> Every time i connect the usb cable the kernel got a oops
Don't really see the difference to 1
> 3.
> usb gadget arm atmel at91_udc
Hi,
> On 17-07-2012 13:13, Ajay Kumar Gupta wrote:
>
> > Added device tree data for usbss on am33xx. There are two musb
> controllers
> > on am33xx platform so have port0_mode and port1_mode additional data.
>
> > Signed-off-by: Ajay Kumar Gupta
> > ---
> > arch/arm/boot/dts/am33xx.dtsi | 11
usbmisc driver handles the SoC specific non-core usb registers.
It's based on Greg's usb-next.
Changes since last version:
- rework to let usb-imxXXX drivers register ops callbacks
Richard Zhao (2):
USB: chipidea: add imx usbmisc support
ARM: dts: imx6q-sabrelite: add usbmisc device
.../d
i.MX usb controllers shares non-core registers, which may include
SoC specific controls. We take it as a usbmisc device and usbmisc
driver set operations needed by ci13xxx_imx driver.
For example, Sabrelite board has bad over-current design, we can
usbmisc to disable over-current detect.
Signed-o
Signed-off-by: Richard Zhao
---
arch/arm/boot/dts/imx6q-sabrelite.dts |4
arch/arm/boot/dts/imx6q.dtsi | 19 +++
arch/arm/mach-imx/clk-imx6q.c |1 +
3 files changed, 20 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/imx6q-sabrelite.dt
Add twl4030-usb data node in twl4030 device tree file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/twl4030.dtsi | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index 22f4
Add omap-usb2 data node in omap4 device tree file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 29c6243..15f1890 100644
--- a/a
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes to
Add device tree support for twl6030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/usb/twl-usb.txt| 22 +++
drivers/usb/otg/twl6030-usb.c | 39 +-
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree support for usb2 phy driver and
the documentation with device tree binding information is
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
ID detection.
Writing to control module which is now handled in omap2430.c should be
This patch series adds device tree support for MUSB and device
tree support for all the related modules to get MUSB working in
OMAP platform.
A new omap-usb2 phy driver has been added (with only dt suppport)
to perform phy configurations. Previously this configuration was
performed by twl6030, usi
Add twl6030-usb data node in twl6030 device tree file
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4-panda.dts |4
arch/arm/boot/dts/omap4-sdp.dts |4
arch/arm/boot/dts/twl6030.dtsi|6 ++
3 files changed, 14 insertions(+), 0 deletions(-)
diff -
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 34 -
drivers/usb/musb/omap2430.c| 55
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-.dts file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3-evm.dts|6 ++
arch/arm/boot/dts/omap3.dtsi
Add device tree support for twl4030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/usb/twl-usb.txt| 19 ++
drivers/usb/otg/twl4030-usb.c | 26 +++
All the unnessary functions in omap-phy-internal is removed.
These functionality are now handled by omap-usb2 phy driver.
Cc: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Tony Lindgren
---
arch/arm/mach-omap2/omap_phy_internal.c | 138 ---
arch/arm/
On Wed, Jul 18, 2012 at 06:29:06PM +0800, Richard Zhao wrote:
> i.MX usb controllers shares non-core registers, which may include
> SoC specific controls. We take it as a usbmisc device and usbmisc
> driver set operations needed by ci13xxx_imx driver.
>
> For example, Sabrelite board has bad over-
On Wed, Jul 18, 2012 at 06:29:07PM +0800, Richard Zhao wrote:
> Signed-off-by: Richard Zhao
> ---
> arch/arm/boot/dts/imx6q-sabrelite.dts |4
> arch/arm/boot/dts/imx6q.dtsi | 19 +++
> arch/arm/mach-imx/clk-imx6q.c |1 +
> 3 files changed, 20 insert
On Wed, Jul 18, 2012 at 12:52:04PM +0200, Sascha Hauer wrote:
> On Wed, Jul 18, 2012 at 06:29:06PM +0800, Richard Zhao wrote:
> > i.MX usb controllers shares non-core registers, which may include
> > SoC specific controls. We take it as a usbmisc device and usbmisc
> > driver set operations needed
On Wed, Jul 18, 2012 at 12:54:31PM +0200, Sascha Hauer wrote:
> On Wed, Jul 18, 2012 at 06:29:07PM +0800, Richard Zhao wrote:
> > Signed-off-by: Richard Zhao
> > ---
> > arch/arm/boot/dts/imx6q-sabrelite.dts |4
> > arch/arm/boot/dts/imx6q.dtsi | 19 +++
> > ar
On Wed, Jul 18, 2012 at 07:19:17PM +0800, Richard Zhao wrote:
> > > +
> > > +struct imx6q_usbmisc {
> > > + void __iomem *base;
> > > + struct clk *clk;
> > > + struct device *usb_dev[USB_DEV_MAX];
> > > + spinlock_t lock;
> > > +
> > > + int disable_oc:USB_DEV_MAX;
> > > +};
> >
> > Please add a
Hi
> > On 17-07-2012 13:13, Ajay Kumar Gupta wrote:
> >
> > > Added device tree data for usbss on am33xx. There are two musb
> > controllers
> > > on am33xx platform so have port0_mode and port1_mode additional
> data.
> >
> > > Signed-off-by: Ajay Kumar Gupta
> > > ---
> > > arch/arm/boot/dts/a
Hi,
Here's a second version of the Logitech UVC devices RESET_RESUME quirk patches.
As interface information is not available at the time usb_detect_quirks() is
called, I've added a new usb_detect_interface_quirks() function that is called
later during the enumeration process.
The patches have be
When a whole class of devices (possibly from a specific vendor, or
across multiple vendors) require a quirk, explictly listing all devices
in the class make the quirks table unnecessarily large. Fix this by
allowing matching devices based on interface information.
Signed-off-by: Laurent Pinchart
Most Logitech UVC webcams (both early models that don't advertise UVC
compatibility and newer UVC-advertised devices) require the RESET_RESUME
quirk. Instead of listing each and every model, match the devices based
on the UVC interface information.
Signed-off-by: Laurent Pinchart
---
drivers/usb
Laurent Pinchart writes:
> static const struct usb_device_id usb_interface_quirk_list[] = {
> + /* Logitech UVC Cameras */
> + { .match_flags = USB_DEVICE_ID_MATCH_VENDOR
> + | USB_DEVICE_ID_MATCH_INT_INFO,
> + .idVendor = 0x046d,
>
On 2012/7/18 12:43, Oliver Neukum wrote:
On Tuesday 17 July 2012 14:52:51 Sarah Sharp wrote:
2. If an internal USB port is suspended with remote wakeup disabled,
power off the port. Add code to the USB core to ignore the device
disconnect in this special case, so the driver thinks the device is
Hello Sarah, Hello Alan,
just to describe what I experienced on the ASM1402
On 17.07.2012 22:22, Alan Stern wrote:
> The events in the email message mentioned above did not involve a race.
> It's clear that no data got transferred at all, and yet usbmon reported
> actual_length equal to transfe
Hi Bjørn,
On Wednesday 18 July 2012 14:47:35 Bjørn Mork wrote:
> Laurent Pinchart writes:
> > static const struct usb_device_id usb_interface_quirk_list[] = {
> >
> > + /* Logitech UVC Cameras */
> > + { .match_flags = USB_DEVICE_ID_MATCH_VENDOR
> > + | US
On Wed, Jul 18, 2012 at 03:16:57PM +0200, Laurent Pinchart wrote:
> Hi Bjørn,
>
> On Wednesday 18 July 2012 14:47:35 Bjørn Mork wrote:
> > Laurent Pinchart writes:
> > > static const struct usb_device_id usb_interface_quirk_list[] = {
> > >
> > > + /* Logitech UVC Cameras */
> > > + { .match_fl
Hi,
Here's a third version of the Logitech UVC devices RESET_RESUME quirk patches.
Compared to v2, the brand new USB_VENDOR_AND_INTERFACE_INFO() macro is now
used.
The patches have been tested with a Logitech C905 webcam and with a non-Logitech
UVC webcam. The RESET_RESUME quirk gets enabled for
When a whole class of devices (possibly from a specific vendor, or
across multiple vendors) require a quirk, explictly listing all devices
in the class make the quirks table unnecessarily large. Fix this by
allowing matching devices based on interface information.
Signed-off-by: Laurent Pinchart
Most Logitech UVC webcams (both early models that don't advertise UVC
compatibility and newer UVC-advertised devices) require the RESET_RESUME
quirk. Instead of listing each and every model, match the devices based
on the UVC interface information.
Signed-off-by: Laurent Pinchart
---
drivers/usb
[snip]
> > > static struct ci13xxx_platform_data ci13xxx_imx_platdata __devinitdata
> > > = {
> > > .name = "ci13xxx_imx",
> > > .flags = CI13XXX_REQUIRE_TRANSCEIVER |
> > > @@ -120,6 +140,9 @@ static int __devinit ci13xxx_imx_probe(struct
> > > platform_d
On Wednesday 18 July 2012 21:06:39 Lan Tianyu wrote:
> On 2012/7/18 12:43, Oliver Neukum wrote:
> > On Tuesday 17 July 2012 14:52:51 Sarah Sharp wrote:
> >> That policy would be safe, because for 1) we would never see a USB
> >> device connection, and thus wouldn't miss the connection when we powe
On 07/18/2012 03:39 PM, Richard Zhao wrote:
> [snip]
static struct ci13xxx_platform_data ci13xxx_imx_platdata __devinitdata =
{
.name = "ci13xxx_imx",
.flags = CI13XXX_REQUIRE_TRANSCEIVER |
@@ -120,6 +140,9 @@ static int __devinit
On Wed, Jul 18, 2012 at 03:43:00PM +0200, Marc Kleine-Budde wrote:
> On 07/18/2012 03:39 PM, Richard Zhao wrote:
> > [snip]
> static struct ci13xxx_platform_data ci13xxx_imx_platdata __devinitdata
> = {
> .name = "ci13xxx_imx",
> .flags
On Wed, 18 Jul 2012, loody wrote:
> hi all:
>
> 2012/7/18 loody :
> > hi:
> >
> > 2012/7/18 Greg KH :
> >> On Wed, Jul 18, 2012 at 11:22:49AM +0800, loody wrote:
> >>> Dear all:
> >>> in usb_serial_probe, we create tty_port based on max_endpoints.
> >>
> >> Or based on the number that the driver
On Wed, 18 Jul 2012, Oliver Neukum wrote:
> On Tuesday 17 July 2012 15:00:08 Alan Stern wrote:
>
> > Furthermore, what happens if you power down a port when the attached
> > device is active (not suspended)? Again it will look like a physical
> > disconnect. So again, you don't want to power
On Wed, 18 Jul 2012, Oliver Neukum wrote:
> > I have a question that reset-resume still can not resolve firmware
> > problem? I think this depend on driver. right?
>
> Right, but this is not really useful information. We can infer from
> a lack of support for reset_resume() that we must not
On 2012/7/18 22:19, Alan Stern wrote:
An alternative to her suggestion would be to disconnect the device when
the port goes off. When the port is powered back on, the device will
be rediscovered and probed again.
hi alan:
Reprobe may cause the devnum change. Userspace will treat it a
di
On Wed, Jul 18, 2012 at 06:29:07PM +0800, Richard Zhao wrote:
> Signed-off-by: Richard Zhao
> ---
> arch/arm/boot/dts/imx6q-sabrelite.dts |4
> arch/arm/boot/dts/imx6q.dtsi | 19 +++
> arch/arm/mach-imx/clk-imx6q.c |1 +
It seems that the patch is m
On Wednesday 18 July 2012 10:21:27 Alan Stern wrote:
> On Wed, 18 Jul 2012, Oliver Neukum wrote:
>
> > > I have a question that reset-resume still can not resolve firmware
> > > problem? I think this depend on driver. right?
> >
> > Right, but this is not really useful information. We can infe
On Wed, 18 Jul 2012, Oliver Neukum wrote:
> On Wednesday 18 July 2012 10:21:27 Alan Stern wrote:
> > On Wed, 18 Jul 2012, Oliver Neukum wrote:
> >
> > > > I have a question that reset-resume still can not resolve
> > > > firmware
> > > > problem? I think this depend on driver. right?
>
On Wed, 18 Jul 2012, Lan Tianyu wrote:
> On 2012/7/18 22:19, Alan Stern wrote:
> > An alternative to her suggestion would be to disconnect the device when
> > the port goes off. When the port is powered back on, the device will
> > be rediscovered and probed again.
> hi alan:
> Reprobe may
On Wed, 18 Jul 2012, Laurent Pinchart wrote:
> When a whole class of devices (possibly from a specific vendor, or
> across multiple vendors) require a quirk, explictly listing all devices
> in the class make the quirks table unnecessarily large. Fix this by
> allowing matching devices based on int
Hi Alan,
On Wednesday 18 July 2012 10:59:41 Alan Stern wrote:
> On Wed, 18 Jul 2012, Laurent Pinchart wrote:
> > When a whole class of devices (possibly from a specific vendor, or
> > across multiple vendors) require a quirk, explictly listing all devices
> > in the class make the quirks table unn
On Wed, 18 Jul 2012, Laurent Pinchart wrote:
> > This is not good, because it ignores usb_authorize_device(). That's
> > why I said earlier that the interface quirks should be detected at the
> > end of usb_enumerate_device().
>
> My bad, sorry.
>
> Is there any chance the device can return dif
On Wednesday 18 July 2012 10:54:20 Alan Stern wrote:
> On Wed, 18 Jul 2012, Lan Tianyu wrote:
>
> > On 2012/7/18 22:19, Alan Stern wrote:
> > > An alternative to her suggestion would be to disconnect the device when
> > > the port goes off. When the port is powered back on, the device will
> > >
On Wed, 18 Jul 2012, Oliver Neukum wrote:
> On Wednesday 18 July 2012 10:54:20 Alan Stern wrote:
> > On Wed, 18 Jul 2012, Lan Tianyu wrote:
> >
> > > On 2012/7/18 22:19, Alan Stern wrote:
> > > > An alternative to her suggestion would be to disconnect the device when
> > > > the port goes off. W
On Wednesday 18 July 2012 11:42:50 Alan Stern wrote:
> On Wed, 18 Jul 2012, Oliver Neukum wrote:
>
> > On Wednesday 18 July 2012 10:54:20 Alan Stern wrote:
> > > On Wed, 18 Jul 2012, Lan Tianyu wrote:
> > >
> > > > On 2012/7/18 22:19, Alan Stern wrote:
> > > > > An alternative to her suggestion w
Alan Stern writes:
> Any attempt to use a suspended device will return an error, whether the
> port is powered off or not. The driver has to resume the device before
> using it, and Sarah is proposing that this should cause the port to
> power back on.
Assuming that "powering off" a port means
From: Bjørn Mork
Date: Tue, 17 Jul 2012 23:14:32 +0200
> The usbnet API use the device ID table to store a pointer to
> a minidriver. Setting a generic pointer for dynamic device
> IDs will in most cases make them work as expected. usbnet
> will otherwise treat the dynamic IDs as blacklisted. Th
On Wed, 18 Jul 2012, Oliver Neukum wrote:
> On Wednesday 18 July 2012 11:42:50 Alan Stern wrote:
> > On Wed, 18 Jul 2012, Oliver Neukum wrote:
> >
> > > On Wednesday 18 July 2012 10:54:20 Alan Stern wrote:
> > > > On Wed, 18 Jul 2012, Lan Tianyu wrote:
> > > >
> > > > > On 2012/7/18 22:19, Alan
From: Bjørn Mork
Date: Thu, 12 Jul 2012 13:18:26 +0200
> Sold by O2 (telefonica germany) under the name "LTE4G"
>
> Tested-by: Thomas Schäfer
> Signed-off-by: Bjørn Mork
Applied to net-next, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a messa
On Wed, 18 Jul 2012, Bjørn Mork wrote:
> Alan Stern writes:
>
> > Any attempt to use a suspended device will return an error, whether the
> > port is powered off or not. The driver has to resume the device before
> > using it, and Sarah is proposing that this should cause the port to
> > power
Hello All,
I see that there are no tracing options (e.g. traceevents) defined in
the USB subsystem. Like, they have been defined for scsi, scheduler,
workqueues etc (include/trace/events/*). I am fairly new to Linux and I
am trying to study the debugging options available. Just wanted to
unde
On Wed, Jul 18, 2012 at 09:57:30AM +0300, Denis Turischev wrote:
> On 07/17/2012 07:54 AM, Sarah Sharp wrote:
> > On Mon, Jul 16, 2012 at 07:46:06PM +0300, Denis Turischev wrote:
> >> Intense-PC is Compulab's mini-desktop with Intel Panther Point
> >> chipset.
> >>
> >> Unconditional ports switchin
On Wed, Jul 18, 2012 at 10:52:22AM -0400, Alan Stern wrote:
> On Wed, 18 Jul 2012, Oliver Neukum wrote:
>
> > On Wednesday 18 July 2012 10:21:27 Alan Stern wrote:
> > > On Wed, 18 Jul 2012, Oliver Neukum wrote:
> > >
> > > > > I have a question that reset-resume still can not resolve
> > >
Hi Bala,
On Wed, Jul 18, 2012 at 7:45 PM, Balakumar wrote:
> Hello All,
>
> I see that there are no tracing options (e.g. traceevents) defined in the
> USB subsystem. Like, they have been defined for scsi, scheduler, workqueues
> etc (include/trace/events/*). I am fairly new to Linux and I am try
Sarah Sharp writes:
> On Wed, Jul 18, 2012 at 10:52:22AM -0400, Alan Stern wrote:
>> On Wed, 18 Jul 2012, Oliver Neukum wrote:
>>
>> > On Wednesday 18 July 2012 10:21:27 Alan Stern wrote:
>> > > On Wed, 18 Jul 2012, Oliver Neukum wrote:
>> > >
>> > > > > I have a question that reset-resume
On Wed, Jul 18, 2012 at 12:40:38PM -0400, Alan Stern wrote:
> On Wed, 18 Jul 2012, Oliver Neukum wrote:
>
> > On Wednesday 18 July 2012 11:42:50 Alan Stern wrote:
> > > On Wed, 18 Jul 2012, Oliver Neukum wrote:
> > >
> > > > On Wednesday 18 July 2012 10:54:20 Alan Stern wrote:
> > > > > On Wed, 1
On Wed, 18 Jul 2012, Balakumar wrote:
> Hello All,
>
> I see that there are no tracing options (e.g. traceevents) defined in
> the USB subsystem. Like, they have been defined for scsi, scheduler,
> workqueues etc (include/trace/events/*). I am fairly new to Linux and I
> am trying to study the
On Wednesday 18 July 2012 12:40:38 Alan Stern wrote:
> Oliver, you seem to be arguing both sides of this discussion. You
But there are more than two sides in this discussion.
> point out the the power-off operation is too dangerous in general for
> the kernel to do it, and now you say that it
On Wed, Jul 18, 2012 at 09:03:59PM +0200, Oliver Neukum wrote:
> On Wednesday 18 July 2012 12:40:38 Alan Stern wrote:
>
> > Oliver, you seem to be arguing both sides of this discussion. You
>
> But there are more than two sides in this discussion.
>
> > point out the the power-off operation is
The lockdep hunter mentions a non consistent usage of spin_lock and
spin_lock_irqsafe in the composite_disconnect and usb_function_activate
function:
[ 15.700897] =
[ 15.705255] [ INFO: inconsistent lock state ]
[ 15.709617] 3.5.0-rc5+ #413 Not tainted
[ 15.
This patch removes the limitation of having only one
instance of the ci13xxx-imx. Each instance of the ci13xxx-imx
could have different flags to be configured with, so we also
move this settings to the devicetree properties.
Signed-off-by: Michael Grzeschik
---
.../devicetree/bindings/usb/ci13xx
On Wed, 2012-07-18 at 11:10 +0200, Sebastian Andrzej Siewior wrote:
> On 07/18/2012 02:05 AM, Nicholas A. Bellinger wrote:
> >> index 02ace18..9ddf315 100644
> >> --- a/drivers/usb/gadget/tcm_usb_gadget.c
> >> +++ b/drivers/usb/gadget/tcm_usb_gadget.c
> >> @@ -1060,7 +1060,10 @@ static void usbg_cm
On Wed, Jul 18, 2012 at 11:00:38PM +0800, Shawn Guo wrote:
> On Wed, Jul 18, 2012 at 06:29:07PM +0800, Richard Zhao wrote:
> > Signed-off-by: Richard Zhao
> > ---
> > arch/arm/boot/dts/imx6q-sabrelite.dts |4
> > arch/arm/boot/dts/imx6q.dtsi | 19 +++
> > arch/
On Mon, Jul 16, 2012 at 05:40:57PM -0700, Greg KH wrote:
> On Thu, Jul 12, 2012 at 03:01:40PM +0800, Richard Zhao wrote:
> > The patch set is tested on imx6q_sabrelite board.
> >
> > The patch can also be found at
> > https://github.com/riczhao/kernel-imx/commits/topics/usb-driver
> >
> > For tes
On Tue, Jul 17, 2012 at 02:30:17PM +0200, Dirk Behme wrote:
> On 13.06.2012 14:34, Richard Zhao wrote:
> >Sometimes, boards have gpios that don't own by any driver or owner
> >by a generic driver that don't like hacks. Such gpios is normally
> >output and need setup once on boot. So I introduce the
Hi:
2012/7/18 Alan Stern :
> On Wed, 18 Jul 2012, loody wrote:
>
>> hi all:
>>
>> 2012/7/18 loody :
>> > hi:
>> >
>> > 2012/7/18 Greg KH :
>> >> On Wed, Jul 18, 2012 at 11:22:49AM +0800, loody wrote:
>> >>> Dear all:
>> >>> in usb_serial_probe, we create tty_port based on max_endpoints.
>> >>
>> >
Hi,
Yesterday I was surprised to see that with *another* external USB disk
happening to be connected before boot,
the system booted with root partition device sdb1 assigned rather than sda1.
Not thinking much, I then proceeded putting the system into suspend,
only to be even more surprised to then
AM33xx has two musb controller and they have one NOP PHY each.
Added the device tree data for NOP PHY.
Signed-off-by: Ajay Kumar Gupta
---
arch/arm/boot/dts/am33xx.dtsi |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/d
Moved global variable "musb_debugfs_root" and static variable
"old_state" to 'struct musb' to help support multi instance of
musb controller as present on AM335x platform.
Also removed the global variable "orig_dma_mask" and filled the
dev->dma_mask with parent device's dma_mask.
Signed-off-by: A
Added NOP PHY phandle to usbss device node as same will be used
to get the phy from otg framework.
Signed-off-by: Ajay Kumar Gupta
---
arch/arm/boot/dts/am33xx.dtsi |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.
Currently we have one single nop transceiver support as same is
defined as a global variable in drivers/usb/otg/nop-usb-xceiv.c.
This need to be changed to support multiple otg controller each
using nop transceiver on a platform such as am335x.
Signed-off-by: Ajay Kumar Gupta
---
arch/arm/mach-o
Added 'id' field within 'struct musb' which can be used to determine
the current instance of musb controller.
Also defined musb_ida in musb_core.c to manage the core ids.
Signed-off-by: Ajay Kumar Gupta
---
drivers/usb/musb/am35x.c | 42 --
drivers/
As NOP device node is now added in am33xx tree so remove the call
which creates the NOP platform_device.
Signed-off-by: Ajay Kumar Gupta
---
drivers/usb/musb/musb_dsps.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/mus
This series of patches adds,
a) Multi instances support in musb driver
b) DT support for musb_dsps glue layer
c) DT support for NOP transceiver
AM33xx and TI81xx has dual musb controller and has two usb PHY of same type.
This patch series uses 'phandle' based API devm_usb_get_phy_by_phandle() to
g
AM33xx has two PHY of same type used by each musb controller so
use phandle of phy nodes to get the phy pointer.
Signed-off-by: Ajay Kumar Gupta
---
.../devicetree/bindings/usb/am33xx-usb.txt |2 ++
drivers/usb/musb/musb_dsps.c |4 +++-
2 files changed, 5 in
Added device tree support for nop transceiver driver and updated the
Documentation with device tree binding information for am33xx platform.
Signed-off-by: Ajay Kumar Gupta
---
.../devicetree/bindings/usb/am33xx-usb.txt |3 +++
drivers/usb/otg/nop-usb-xceiv.c| 1
Added device tree support for dsps musb glue driver and updated the
Documentation with device tree binding information.
Signed-off-by: Ajay Kumar Gupta
---
.../devicetree/bindings/usb/am33xx-usb.txt | 14 +
drivers/usb/musb/musb_dsps.c | 62 +
AM335x and TI81xx platform has dual musb controller so updating the
musb_dspc.c to support the same.
Changes:
- Moved otg_workaround timer to glue structure
- Moved static local variable last_timer to glue structure
- PHY on/off related cleanups
Signed-off-by: Ajay Kumar G
Added device tree data for usbss on am33xx. There are two musb controllers
on am33xx platform so have port0_mode and port1_mode additional data.
Signed-off-by: Ajay Kumar Gupta
---
arch/arm/boot/dts/am33xx.dtsi | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/a
92 matches
Mail list logo
