On Mon, Dec 17, 2012 at 06:21:16PM +0100, Armando Visconti wrote:
> >Besides that the patch looks fine :)
>
> Do you mean that 'inited' should be changed with 'initialized'?
Yes, I do.
> Oh ... my poor english... :(
Don't worry. Others, including myself, do this from time to time as well :)
>
>
although we can not say it is surely a bug.
it is better to set urb->hcpriv = NULL, after finish calling urb_free_priv.
before kfree urb_priv, better to judge whether urb_priv == NULL, firstly.
Signed-off-by: Chen Gang
---
drivers/usb/host/ohci-q.c |7 ++-
1 file changed, 6 insert
The device comes up with a MAC address of all zeros. We need to read the
initial device MAC from EEPROM so it can be set properly later.
Signed-off-by: Lucas Stach
---
A similar fix was added into U-Boot:
http://patchwork.ozlabs.org/patch/179409/
---
drivers/net/usb/asix_devices.c | 29 +
ASIX AX88772B started to pack data even more tightly. Packets and the ASIX
packet
header may now cross URB boundaries. To handle this we have to introduce
some state between individual calls to asix_rx_fixup().
Signed-off-by: Lucas Stach
---
I've running this patch for some weeks already now and
On Tuesday 18 December 2012 13:10:25 Lucas Stach wrote:
> diff --git a/include/linux/usb/usbnet.h b/include/linux/usb/usbnet.h
> index 9bbeabf..8e9516f 100644
> --- a/include/linux/usb/usbnet.h
> +++ b/include/linux/usb/usbnet.h
> @@ -106,6 +106,7 @@ struct driver_info {
> */
> #define FLAG_MULT
Am Dienstag, den 18.12.2012, 14:11 +0100 schrieb Oliver Neukum:
> On Tuesday 18 December 2012 13:10:25 Lucas Stach wrote:
> > diff --git a/include/linux/usb/usbnet.h b/include/linux/usb/usbnet.h
> > index 9bbeabf..8e9516f 100644
> > --- a/include/linux/usb/usbnet.h
> > +++ b/include/linux/usb/usbne
On Mon, Dec 17, 2012 at 11:39:21PM -0600, ricardo garcia wrote:
> Hello, im using f_loopback.c in the gadget folderits working
> fine...it sends
> back the data that I write...but if the data is longer than 128 bytes
> it does not send it back! ...
> im using kernel 3.0...thanks
How do you tes
On Tuesday 18 December 2012 14:24:32 Lucas Stach wrote:
> Am Dienstag, den 18.12.2012, 14:11 +0100 schrieb Oliver Neukum:
> > On Tuesday 18 December 2012 13:10:25 Lucas Stach wrote:
> > > diff --git a/include/linux/usb/usbnet.h b/include/linux/usb/usbnet.h
> > > index 9bbeabf..8e9516f 100644
> > >
Am Dienstag, den 18.12.2012, 14:33 +0100 schrieb Oliver Neukum:
> On Tuesday 18 December 2012 14:24:32 Lucas Stach wrote:
> > Am Dienstag, den 18.12.2012, 14:11 +0100 schrieb Oliver Neukum:
> > > On Tuesday 18 December 2012 13:10:25 Lucas Stach wrote:
> > > > diff --git a/include/linux/usb/usbnet.h
On Tuesday 18 December 2012 13:10:26 Lucas Stach wrote:
> --- a/drivers/net/usb/asix_devices.c
> +++ b/drivers/net/usb/asix_devices.c
> @@ -495,6 +495,10 @@ static int ax88772_bind(struct usbnet *dev, struct
> usb_interface *intf)
> dev->rx_urb_size = 2048;
> }
>
> +
Business Kid wrote:
> I Imagine 2232 is registered somewhere as a manufacturer
And this might be nothing more than your imagination. ;-)
> but I've no hint who made it. If it's not the webcam, it's
> probably an sd card reader.
What's the output of "lsusb -v" for this device?
> any hints welco
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam
---
Changes from v1:
- Changed the name of property for phy handler from'samsung,usb-phyctrl'
to 'samsung,usb-phyhandle' to make it look more generic.
-
On Tuesday 18 December 2012 14:38:32 Lucas Stach wrote:
> Am Dienstag, den 18.12.2012, 14:33 +0100 schrieb Oliver Neukum:
> > On Tuesday 18 December 2012 14:24:32 Lucas Stach wrote:
> > > Am Dienstag, den 18.12.2012, 14:11 +0100 schrieb Oliver Neukum:
> > > > On Tuesday 18 December 2012 13:10:25 Lu
On 12/17/2012 10:19 PM, Bernd Krumboeck wrote:
> Add support for canbus activity led indicators on usb_8dev devices by
> calling appropriate can_led functions.
>
> These are only enabled when CONFIG_CAN_LEDS is Y, becomes no-op
> otherwise.
>
> Signed-off-by: Bernd Krumboeck
Thx. Fabio, can you
On Tue, Dec 18, 2012 at 10:44:19AM +0800, fangxiaozhi 00110321 wrote:
> diff -uprN linux-3.7_bak/drivers/usb/storage/initializers.c
> linux-3.7/drivers/usb/storage/initializers.c
> --- linux-3.7_bak/drivers/usb/storage/initializers.c 2012-12-11
> 09:56:11.0 +0800
> +++ linux-3.7/drivers/
On Tue, Dec 18, 2012 at 12:01:35AM -0200, Fabio Estevam wrote:
> Booting a 3.7 kernel on a mx6qsabrelite board via NFS and using an
> asix USB/Ethernet adapter and then I try to transfer a 10MB file from
> the target to the host:
That backtrace shows only that nothing is going on. Can you attach t
Hi,
>> > >
>> > > The udc_start() function is being called now. Before this, it was not
>> > > called because of driver->max_speed checking in udc_start(). After
>> > > udc_start(), which function is to be called when the gadget device is
>> > > connected to the host PC?
>> > >
>> > > Thanks. I wi
I re-did the two since the last post:
[PATCH 1/2] usb/core: consider link speed while looking at bMaxPower
- updated description
[PATCH 2/2] usb/core: update power budget for SuperSpeed
- moved "hcd = bus_to_hcd(hdev->bus);" a few lines up so we don't hit the
NULL pointer.
Sebastian
--
To unsu
Sarah pointed out that the USB3.0 spec also updates the amount of power
that may be consumed by the device and quoted 9.2.5.1:
|"The amount of current draw for SuperSpeed devices are increased to 150
|mA for low-power devices and 900 mA for high-power"
This patch tries to update all users to use
The USB 2.0 specification says that bMaxPower is the maximum power
consumption expressed in 2 mA units and the USB 3.0 specification says
that it is expressed in 8 mA units.
This patch adds a helper function usb_get_max_power() which computes the
value based on config & usb_device's speed value. Th
Changes from v4:
- Moved architecture side changes out of this patch-set.
- Added support for multiple usbphy phandle parsing and
doing all pmu_isolation() and phy_cfg_sel() related changes
in samsung-usbphy driver only instead of architecture
as in v4 patch-set.
- Removed unnecessary m
Updating the names of usb-phy types to more generic names:
USB_PHY_TYPE_DEIVCE & USB_PHY_TYPE_HOST; and further update
its dependencies.
Signed-off-by: Praveen Paneri
Signed-off-by: Vivek Gautam
---
drivers/usb/host/ehci-s5p.c |9 +
drivers/usb/host/ohci-exynos.c |9
This patch adds host phy support to samsung-usbphy.c and
further adds support for samsung's exynos5250 usb-phy.
Signed-off-by: Praveen Paneri
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 25 +-
drivers/usb/phy/Kconfig|2 +
Adding the phy driver to ehci-s5p. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
---
drivers/usb/host/ehci-s5p.c | 70 ++-
1 files changed, 49 insertions(+),
Adding the phy-driver to ohci-exynos. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
---
drivers/usb/host/ohci-exynos.c | 70
1 files changed, 49 insertions(
im using a self-made Windows-WinUsb application that handles the g_zero device
it sends simple raw data to it, like "hello" or "bye"nothing
fancybut I dont think
this has something to do with the other side because even when i call
usb_ep_queue()
(with both out and in endpoints), if the ->l
Changes form v1:
- Moved architecture related patch out of this patch-set.
- Replaced unnecessary multi-line macro definitions by
single line definitions.
- Creating new data structure for USB 3.0 phy type and embedding
it in 'samsung_usbphy' structure.
- Adding a flag in 'samsung_usbphy'
Adding support for USB3.0 phy for dwc3 controller on
exynos5250 SOC.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/samsung-usbphy.c | 339 +-
1 files changed, 337 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/phy/samsung-usbphy.c b/drivers/usb/phy
On Mon, 17 Dec 2012, Sarah Sharp wrote:
> Alan, what does the EHCI scheduler do if the HS device's wMaxPacketSize
> is set to 64 bytes? Happily schedule 64 byte transfers? Or will it
> schedule 512 byte packets since that's the only allowed type for HS bulk
> endpoints?
I don't know -- I assume
On 12/18/2012 03:18 PM, Fabio Baltieri wrote:
> On Tue, Dec 18, 2012 at 03:05:12PM +0100, Marc Kleine-Budde wrote:
>> On 12/17/2012 10:19 PM, Bernd Krumboeck wrote:
>>> Add support for canbus activity led indicators on usb_8dev devices by
>>> calling appropriate can_led functions.
>>>
>>> These are
Hi,
(avoid top-posting, please)
On Tue, Dec 18, 2012 at 08:43:52AM -0600, ricardo garcia wrote:
> im using a self-made Windows-WinUsb application that handles the g_zero device
> it sends simple raw data to it, like "hello" or "bye"nothing
> fancybut I dont think
> this has something to d
On Tue, 18 Dec 2012, Chen Gang wrote:
> although we can not say it is surely a bug.
> it is better to set urb->hcpriv = NULL, after finish calling urb_free_priv.
> before kfree urb_priv, better to judge whether urb_priv == NULL, firstly.
>
> Signed-off-by: Chen Gang
> ---
> drivers/usb/ho
On Tue, Dec 18, 2012 at 09:59:16PM +0800, victor yeo wrote:
> Hi,
>
> >> > >
> >> > > The udc_start() function is being called now. Before this, it was not
> >> > > called because of driver->max_speed checking in udc_start(). After
> >> > > udc_start(), which function is to be called when the gadg
ASIX AX88772B started to pack data even more tightly. Packets and the ASIX
packet
header may now cross URB boundaries. To handle this we have to introduce
some state between individual calls to asix_rx_fixup().
Signed-off-by: Lucas Stach
---
I've running this patch for some weeks already now and
The device comes up with a MAC address of all zeros. We need to read the
initial device MAC from EEPROM so it can be set properly later.
Signed-off-by: Lucas Stach
---
A similar fix was added into U-Boot:
http://patchwork.ozlabs.org/patch/179409/
v2: pass flag in the data field instead of clobbe
On Tue, Dec 18, 2012 at 08:40:26PM +0530, Vivek Gautam wrote:
> Adding support for USB3.0 phy for dwc3 controller on
> exynos5250 SOC.
>
> Signed-off-by: Vivek Gautam
> ---
> drivers/usb/phy/samsung-usbphy.c | 339
> +-
let's make the phy names standard from
On Tue, Dec 18, 2012 at 03:05:12PM +0100, Marc Kleine-Budde wrote:
> On 12/17/2012 10:19 PM, Bernd Krumboeck wrote:
> > Add support for canbus activity led indicators on usb_8dev devices by
> > calling appropriate can_led functions.
> >
> > These are only enabled when CONFIG_CAN_LEDS is Y, becomes
This patch-set enables the samsung-usbphy driver on exynos5250,
which enables the support for USB2 type and USB3 type phys.
The corresponding phy driver patches are available at:
1) https://lkml.org/lkml/2012/12/18/201
2)
https://lists.ozlabs.org/pipermail/devicetree-discuss/2012-December/024559
Adding usbphy node for Exynos5250 along with the
necessary device data to be parsed.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi | 22 ++
arch/arm/mach-exynos/include/mach/map.h |1 +
arch/arm/mach-exynos/mach-exynos5-dt.c |2 ++
3 files
Adding base address information required for enabling
USB 3.0 DRD phy on exynos5250 SOC.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts/exynos5250.
于 2012/12/17 0:25, Alan Stern 写道:
On Sun, 16 Dec 2012, Lan Tianyu wrote:
On 2012/12/14 23:44, Alan Stern wrote:
On Fri, 14 Dec 2012, Lan Tianyu wrote:
Hi Alan:
debounce is still needed. If connect status was not stable, resume
operation will fail. So how about following?
Actually, I
On Tue, 18 Dec 2012, lantianyu wrote:
> > What you want here is sort of an alternate debounce routine. The
> > normal routine waits until the connect status has been stable for 100
> > ms. But you want to wait until the status has stable in the
> > "connected" state for 100 ms.
> Yesh.
> > Maybe
On Tue, 18 Dec 2012, Venu Byravarasu wrote:
> As pointer to PHY structure can be stored in struct usb_hcd
> making use of it, to call PHY APIs.
>
> Call to usb_phy_shutdown() is moved up in tegra_ehci_remove(),
> so that to avoid dereferencing of hcd after its freed up.
>
> Signed-off-by: Venu B
I suggest that we remove the CONFIG_USB_SUSPEND option, starting in
3.9. Practically everyone enables it, and the amount of code it
protects is fairly small (just portions of usbcore, nothing in the
drivers).
Basically, if people don't want their kernels to save power then they
should turn off C
On Tuesday 18 December 2012 11:11:15 Alan Stern wrote:
> I suggest that we remove the CONFIG_USB_SUSPEND option, starting in
> 3.9. Practically everyone enables it, and the amount of code it
> protects is fairly small (just portions of usbcore, nothing in the
> drivers).
That works both ways. Wh
On Tue, Dec 18, 2012 at 9:08 AM, Felipe Balbi wrote:
> Hi,
>
> (avoid top-posting, please)
>
> On Tue, Dec 18, 2012 at 08:43:52AM -0600, ricardo garcia wrote:
>> im using a self-made Windows-WinUsb application that handles the g_zero
>> device
>> it sends simple raw data to it, like "hello" or "b
On 12/17/2012 11:21 PM, Venu Byravarasu wrote:
> Using devm_kzalloc for allocating memory needed for PHY
> pointer and hence removing kfree calls to PHY pointer.
Since the kfree() here used to be in tegra_usb_phy_close() rather than
any remove() function, does it actually make sense to use
devm_kz
On Tue, 18 Dec 2012, Oliver Neukum wrote:
> On Tuesday 18 December 2012 11:11:15 Alan Stern wrote:
> > I suggest that we remove the CONFIG_USB_SUSPEND option, starting in
> > 3.9. Practically everyone enables it, and the amount of code it
> > protects is fairly small (just portions of usbcore, no
On Tuesday 18 December 2012 11:38:46 Alan Stern wrote:
> On Tue, 18 Dec 2012, Oliver Neukum wrote:
>
> > On Tuesday 18 December 2012 11:11:15 Alan Stern wrote:
> > > I suggest that we remove the CONFIG_USB_SUSPEND option, starting in
> > > 3.9. Practically everyone enables it, and the amount of c
Hi Alan,
just one short question before holidays (and forgetting it...).
Is this latest patch to be applied on top of all the others, or
should I remove the previous one? Was same file, I think.
Thanks,
bye,
pg
On Mon, Dec 17, 2012 at 02:59:21PM -0500, Alan Stern wrote:
> On Mon, 17 Dec 2012,
On Tue, Dec 18, 2012 at 10:28:18AM -0600, ricardo garcia wrote:
> > try with our test application just to rule out bugs on the host side.
> > Also, which controller are you using ? Why are you sticking to such an
> > old kernel ? Can you try with current stable release, v3.7 ?
That is a good start
On Tue, 18 Dec 2012, Piergiorgio Sartor wrote:
> Hi Alan,
>
> just one short question before holidays (and forgetting it...).
>
> Is this latest patch to be applied on top of all the others, or
> should I remove the previous one? Was same file, I think.
Remove the previous one and keep the othe
In drivers/mmc/host/vub300.c::vub300_probe() we need both
'command_out_urb' and 'command_res_urb'. Currently we fail to free the
former if allocating the latter fails. Fix that and simplify the code
a bit at the same time by just doing both allocations and if either
fails then free both - usb_free_
On Mon, 2012-12-10 at 15:15 -0800, United Seabears Corp. wrote:
> Two months ago I asked for
> assistance with the installation of a Franklin U600 3G/4G modem on the
> above OS. Meanwhile I managed to get the 3G part of the dual modem to
> work reliably.
> I had to discover on my own that this m
Hi Vivek,
On 12/18/2012 02:56 PM, Vivek Gautam wrote:
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam
---
Changes from v1:
- Changed the name of property for phy handler from'samsung,usb-phyctrl'
t
On 12/18/2012 04:39 PM, Vivek Gautam wrote:
Adding base address information required for enabling
USB 3.0 DRD phy on exynos5250 SOC.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/e
On Tue, Dec 18, 2012 at 01:13:05AM -0500, Marius Silaghi wrote:
Hi Marius, thanks for reporting this.
> My USB2.0 cameras are enumerated fine on ehci systems. But not on my new
> Ubuntu
> 12.10:
> $uname -a
> Linux VAIO 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012
> x86_64
> x
(resending, as I forgot to CC list)
Le lundi 17 décembre 2012 23:24:55, vous avez écrit :
> After reading the first message in the thread I realized that you are
> not writing the fx2 device, but are trying to use a device you
> purchased. Sorry.
No problem. Reading more of the doc after I posted
于 2012年12月18日 23:17, Alan Stern 写道:
>> static void urb_free_priv (struct ohci_hcd *hc, urb_priv_t *urb_priv)
>> > {
>> > - int last = urb_priv->length - 1;
>> > + int last;
>> >
>> > + if (!urb_priv)
>> > + return;
>> > +
>> > + last = urb_priv->length - 1;
Le lundi 17 décembre 2012 23:06:55, vous avez écrit :
> It's ironic that a USB bus analyzer doesn't follow the USB 2.0
> specification...
True. Although I would favour the honest descriptor over the compliant one (if
hardware buffer is limited to 64 in both cases). Well, this is not about
person
although we can not say it is surely a bug.
it is better to set urb->hcpriv = NULL, after finish calling urb_free_priv.
Signed-off-by: Chen Gang
---
drivers/usb/host/ohci-q.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/ohci-q.c b/drivers/usb/host/ohci-q.c
index
On Tue, Dec 18, 2012 at 12:32 PM, Sebastian Andrzej Siewior
wrote:
> On Tue, Dec 18, 2012 at 10:28:18AM -0600, ricardo garcia wrote:
>> > try with our test application just to rule out bugs on the host side.
>> > Also, which controller are you using ? Why are you sticking to such an
>> > old kerne
Le lundi 17 décembre 2012 23:30:02, Sarah Sharp a écrit :
> Will you please apply this patch to whatever stable kernel you're
> running and see if the device works under xHCI? Please send the dmesg
> output in either case.
[42363.294837] usb 2-2: new high-speed USB device number 2 using xhci_hcd
Hello Alan Stern
I finished constructing envrionments.
let uhci-debug.c has effect (#define DEBUG, debug = 3 in
drivers/usb/host/uhci-hcd.c)
build kernel and install, and restart machine.
can cat /sys/kernel/debug/usb/uhci/* to get full display contents
for fixing this issue of u
Dear Sebastian:
Please see the comments follows yours.
By the way, I found the kernel is updated to 3.7.1 today. So I have to
update my patch based on 3.7.1, and resubmit it?
Right?
Best Regards,
Franko Fang
> -Original Message-
> From: Sebastian Andrzej
On Mon, 2012-12-17 at 13:28 -0800, Sarah Sharp wrote:
> On Sun, Dec 16, 2012 at 12:37:00AM +, Ben Hutchings wrote:
> > Since Linux 3.2.16, my desktop with an Asus P8Z68-V LX motherboard
> > always wakes up a few seconds after I shutdown. I then have to switch
> > it off a second time. This st
On Tue, Dec 18, 2012 at 10:14:52AM -0500, Alan Stern wrote:
> On Mon, 17 Dec 2012, Sarah Sharp wrote:
>
> > Alan, what does the EHCI scheduler do if the HS device's wMaxPacketSize
> > is set to 64 bytes? Happily schedule 64 byte transfers? Or will it
> > schedule 512 byte packets since that's th
On 12/16/2012 02:13 PM, Business Kid wrote:
This is, I think, a webcam built into the Samsung 350V model
NP350E7C-A05UK. I can't see it in windoze 8's pathetic excuse for a
'control panel' or the latest usb.ids. I Imagine 2232 is registered
somewhere as a manufacturer but I've no hint who made
On Tue, Dec 18, 2012 at 11:11:15AM -0500, Alan Stern wrote:
> I suggest that we remove the CONFIG_USB_SUSPEND option, starting in
> 3.9. Practically everyone enables it, and the amount of code it
> protects is fairly small (just portions of usbcore, nothing in the
> drivers).
>
> Basically, if p
> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Tuesday, December 18, 2012 10:03 PM
> To: Venu Byravarasu
> Cc: ba...@ti.com; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; linux-usb@vger.kernel.org
> Subject: Re: [PATCH] usb: phy: tegra: Usi
CC: Doug Anderson.
On Tue, Dec 18, 2012 at 8:13 PM, Vivek Gautam wrote:
> Adding the phy driver to ehci-s5p. Keeping the platform data
> for continuing the smooth operation for boards which still uses it
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
> ---
> drivers/usb/host/ehci-s5p.
CC: Doug Anderson
On Wed, Dec 19, 2012 at 4:49 AM, Sylwester Nawrocki
wrote:
> Hi Vivek,
>
>
> On 12/18/2012 02:56 PM, Vivek Gautam wrote:
>>
>> Adding support to parse device node data in order to get
>> required properties to set pmu isolation for usb-phy.
>>
>> Signed-off-by: Vivek Gautam
>>
CC: Doug Anderson.
On Tue, Dec 18, 2012 at 8:40 PM, Vivek Gautam wrote:
> Changes form v1:
> - Moved architecture related patch out of this patch-set.
> - Replaced unnecessary multi-line macro definitions by
>single line definitions.
> - Creating new data structure for USB 3.0 phy type an
CC: Doug Anderson
On Tue, Dec 18, 2012 at 8:43 PM, Felipe Balbi wrote:
> On Tue, Dec 18, 2012 at 08:40:26PM +0530, Vivek Gautam wrote:
>> Adding support for USB3.0 phy for dwc3 controller on
>> exynos5250 SOC.
>>
>> Signed-off-by: Vivek Gautam
>> ---
>> drivers/usb/phy/samsung-usbphy.c | 339
CC: Doug Anderson.
On Tue, Dec 18, 2012 at 9:09 PM, Vivek Gautam wrote:
> This patch-set enables the samsung-usbphy driver on exynos5250,
> which enables the support for USB2 type and USB3 type phys.
> The corresponding phy driver patches are available at:
> 1) https://lkml.org/lkml/2012/12/18/
CC: Doug Anderson.
On Tue, Dec 18, 2012 at 8:13 PM, Vivek Gautam wrote:
> Updating the names of usb-phy types to more generic names:
> USB_PHY_TYPE_DEIVCE & USB_PHY_TYPE_HOST; and further update
> its dependencies.
>
> Signed-off-by: Praveen Paneri
> Signed-off-by: Vivek Gautam
> ---
> driver
CC: Doug Anderson.
On Tue, Dec 18, 2012 at 9:09 PM, Vivek Gautam wrote:
> Adding usbphy node for Exynos5250 along with the
> necessary device data to be parsed.
>
> Signed-off-by: Vivek Gautam
> ---
> arch/arm/boot/dts/exynos5250.dtsi | 22 ++
> arch/arm/mach-exynos
CC: Doug Anderson.
On Tue, Dec 18, 2012 at 8:13 PM, Vivek Gautam wrote:
> This patch adds host phy support to samsung-usbphy.c and
> further adds support for samsung's exynos5250 usb-phy.
>
> Signed-off-by: Praveen Paneri
> Signed-off-by: Vivek Gautam
> ---
> .../devicetree/bindings/usb/samsu
CC: Doug Anderson.
On Wed, Dec 19, 2012 at 5:02 AM, Sylwester Nawrocki
wrote:
> On 12/18/2012 04:39 PM, Vivek Gautam wrote:
>>
>> Adding base address information required for enabling
>> USB 3.0 DRD phy on exynos5250 SOC.
>>
>> Signed-off-by: Vivek Gautam
>> ---
>> arch/arm/boot/dts/exynos5250
CC: Doug Anderson.
On Tue, Dec 18, 2012 at 8:13 PM, Vivek Gautam wrote:
> Adding the phy-driver to ohci-exynos. Keeping the platform data
> for continuing the smooth operation for boards which still uses it
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
> ---
> drivers/usb/host/ohci-e
CC: Doug Anderson
On Tue, Dec 18, 2012 at 8:13 PM, Vivek Gautam wrote:
> Changes from v4:
> - Moved architecture side changes out of this patch-set.
> - Added support for multiple usbphy phandle parsing and
>doing all pmu_isolation() and phy_cfg_sel() related changes
>in samsung-usbphy
Hi Felipe,
On Wed, Dec 19, 2012 at 11:14 AM, Vivek Gautam
wrote:
> CC: Doug Anderson
>
>
> On Tue, Dec 18, 2012 at 8:43 PM, Felipe Balbi wrote:
>> On Tue, Dec 18, 2012 at 08:40:26PM +0530, Vivek Gautam wrote:
>>> Adding support for USB3.0 phy for dwc3 controller on
>>> exynos5250 SOC.
>>>
>>> S
Hi,
Sorry for my bad mail content type, re-send again.
2012/12/8 Ilija Hadzic :
> File doc/usbip_bind_driver.8 does not exist any more but it is
> listed in dist_man_MANS. This breaks the build of the userspace.
> Remove the file from the list.
>
That makes sense.
The usbip_bind_driver is no lon
On 2012年12月18日 04:06, Alan Stern wrote:
> On Mon, 17 Dec 2012, Octavio Alvarez wrote:
>
>> On Thu, 13 Dec 2012 00:45:05 -0800, Lan Tianyu
>> wrote:
>>
>>> diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
>>> index f034716..9335f1b 100644
>>> --- a/drivers/usb/core/hcd.c
>>> +++ b/driv
Alan, thank you for your reply. May be in the future this bug will be
fixed. I understand it's not a simple bug. I will not send any
messages concerning this bug anymore.
When I tested the camera on other two machines running Ubuntu it
showed the same log message but it worked:
not running at
Hi Lucas,
On 2012-12-18 16:21, Lucas Stach wrote:
ASIX AX88772B started to pack data even more tightly. Packets and the ASIX
packet
header may now cross URB boundaries. To handle this we have to introduce
some state between individual calls to asix_rx_fixup().
cc'ed Eric Dumazet, he did some
86 matches
Mail list logo
