On 07.02.2013 07:05, Greg KH wrote:
> On Thu, Feb 07, 2013 at 02:42:05PM +0100, Matthias Schniedermeyer wrote:
> > Hi
> >
> >
> > After updating from 3.7.2 to 3.7.6 disconnecting a USB3 device from a
> > xhci-port isn't detected properly anymore. After removing a 32GB stick
> > the only line in
From: supriya karanth
Generic changes for enabling DMA Mode1.
Cleanup of rxtsate function making programming
same for all platforms
Handles:
1) Known transfer length
a) Non multiple of packet size
b) Multiple of packet size
2) Unknown transfer lengths
- Short packet indicates
From: supriya karanth
Added pause, resume, tx_status and check_status functions
Signed-off-by: Supriya Karanth
Signed-off-by: Praveena NADAHALLY
Acked-by: Linus Walleij
---
drivers/usb/musb/musbhsdma.c | 72 ++
1 files changed, 72 insertions(+), 0 de
From: supriya karanth
Added support for enabling DMA Mode1. tusb will continue to
work in mode0. If needed DMA mode1 can be enabled
Signed-off-by: Supriya Karanth
Signed-off-by: Praveena NADAHALLY
Acked-by: Linus Walleij
---
drivers/usb/musb/tusb6010_omap.c | 67 +++
From: supriya karanth
Added pause, resume, tx_status and check_status functions
RNDIS and ECM require 2 byte aligned addresses, change
bus width of the DMA slave to 2 bytes.
Signed-off-by: supriya karanth
Signed-off-by: Praveena NADAHALLY
Acked-by: Linus Walleij
---
drivers/usb/musb/ux500_dm
Hi Felipe,
Here are the patches for enabling DMA Mode1 for different platforms
and also to have DMA programming more or less common.
These patches are based and apply cleanly on
http://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
Tested and working on: ux500 platform
Platforms using m
On 02/08/2013 07:55 AM, Onteddu Slreddy wrote:
> Hello All,
>
>
> I recently joined this group the group.
>
> Can anybody suggest me places where I can get Documents which will explain
> wifi Architecture in brief i would like to know details like
>
> In Linux for embedded systems:
> W
Hi Felipe,
Here are the patches for enabling DMA Mode1 for different platforms
and also to have DMA programming more or less common.
These patches are based and apply cleanly on
http://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
Tested and working on: ux500 platform
Platforms using m
On 02/08/2013 09:42 AM, Felipe Balbi wrote:
> HI,
>
> On Thu, Feb 07, 2013 at 11:03:59PM +0530, manjunath.gou...@linaro.org wrote:
>> From: Manjunath Goudar
>>
>> Separate the OMAP host controller driver from ehci-hcd host code
>> into its own driver module.
>>
>> Signed-off-by: Manjunath Goudar
On 02/08/2013 10:53 AM, sl reddy wrote:
> any successions will be helpful for me
My *suggestion* would be:
http://wireless.kernel.org/en/developers/Documentation
For what it is worth, below is some terrible ascii art.
Gr. AvS
Fullmac model:
user-space (libnl)
> > +struct ax88179_rx_pkt_header {
> > + u8 l4_csum_err:1,
> > + l3_csum_err:1,
> > + l4_type:3,
> > + l3_type:2,
> > + ce:1;
> > +
> > + u8 vlan_ind:3,
> > + rx_ok:1,
> > + pri:3,
> > + bmc:1;
> > +
> > + u16
Hello Manjunath,
On 02/07/2013 06:34 PM, manjunath.gou...@linaro.org wrote:
From: Manjunath Goudar
Separate the Marvell Orion host controller driver from ehci-hcd host code
into its own driver module.
[snip]
The changes you introduce in ehci-hcd.c would certainly deserve their
own prelimin
Hi Laurent,
On Fri, Feb 08, 2013 at 12:32:44AM +0100, Laurent Pinchart wrote:
> Hi Bhupesh,
>
> On Thursday 07 February 2013 23:39:07 Laurent Pinchart wrote:
> > On Wednesday 30 January 2013 15:56:52 Bhupesh SHARMA wrote:
> > > On Monday, January 21, 2013 6:16 PM Laurent Pinchart wrote:
> > > > O
On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
> On Tue, 5 Feb 2013, Peter Hurley wrote:
>
> > With -next-20130204:
> >
> > [ 33.855570] irq 18: nobody cared (try booting with the "irqpoll" option)
> > [ 33.855580] Pid: 0, comm: swapper/4 Not tainted 3.8.0-next-20130204-xeon
> > #20130
there's really no need for that message. It's
been a while since it printed something useful.
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/musb_core.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
index 60b41cc..a68ff27 10064
this will make sure that request_memory_region() will
be called and that we don't need to manually call
iounmap() on ->remove().
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/musb_core.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/musb/musb_core
Those comments haven't been updated for a long
time, so much that they don't make sense anymore.
Best to remove them.
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/musb_gadget.c | 108 -
1 file changed, 108 deletions(-)
diff --git a/drivers/usb/musb/m
MUSB still needs lots of work on the DMA part
if we want to enable multiple DMA engines on
a multiplatform kernel. Meanwhile, we're forcing
PIO-only so that we, at least, have a working
driver.
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff -
those two glues are still including
headers and no active developement has been
going on those glues for quite some time.
Apparently, for da8xx glue, only initial commit
3ee076de (usb: musb: introduce DA8xx/OMAP-L1x
glue layer) has been tested. All other patches
seem to have been compile-tested o
Fix the following compile warnings:
drivers/usb/musb/ux500_dma.c: In function ‘ux500_configure_channel’:
drivers/usb/musb/ux500_dma.c:96:2: warning: format ‘%x’ expects argument of
type ‘unsigned int’, but argument 6 has type ‘dma_addr_t’ [-Wformat]
drivers/usb/musb/ux500_dma.c: In function ‘ux50
is the header defining SZ_4
and SZ_16M, we shouldn't depend on indirect
inclusion so let's explicitly include it.
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/musb_dsps.c | 1 +
drivers/usb/musb/ux500_dma.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/usb/musb/musb_dsps.c b
if CONFIG_OF is disabled, np will be unused
and that will give us a compile warning. This
patch just avoids it.
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/musb_dsps.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/musb_
Fix the following compile warning:
drivers/usb/musb/musb_gadget.c: In function ‘rxstate’:
drivers/usb/musb/musb_gadget.c:714:22: warning: comparison of distinct pointer
types lacks a cast [enabled by default]
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/musb_gadget.c | 13 -
1
those glues can build cleanly anywhere.
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/Kconfig | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
index 1f0f9fb..920b4f5 100644
--- a/drivers/usb/musb/Kconfig
+++ b/drivers/usb/musb/Kconfig
@
Hello.
On 02/08/2013 04:02 PM, Felipe Balbi wrote:
> this will make sure that request_memory_region() will
> be called and that we don't need to manually call
> iounmap() on ->remove().
> Signed-off-by: Felipe Balbi
> ---
> drivers/usb/musb/musb_core.c | 11 ++-
> 1 file changed, 2 ins
Hello.
On 02/08/2013 04:02 PM, Felipe Balbi wrote:
> those two glues are still including
Frankly speaking, I see no way out of it for DA8xx beside duplicating the
definitions from there.
> headers and no active developement has been
> going on those glues for quite some time.
> Apparently,
Hi folks,
this patchset implements the bare minimum PM
support for dwc3. We're not even playing with
the PHYs yet.
Please give this a good round of test as PM
always tends to break things apart.
I haven't thoroughly tested this yet, but I
thought that I should give people enough time
to run all
commit 3921426 (usb: dwc3: core: move
event buffer allocation out of
dwc3_core_init()) introduced a memory leak
of the coherent memory we use as event
buffers on dwc3 driver.
If the driver is compiled as a dynamically
loadable module and use constantly loads
and unloads the driver, we will continu
Make the call to dwc3_event_buffers_setup()
and dwc3_event_buffers_cleanup() explicit,
so it's easier to implement PM.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 32 +---
1 file changed, 17 insertions(+), 15 deletions(-)
diff --git a/drivers/usb/dwc3/c
we don't need to enable IRQs until we have
a gadget driver loaded and ready to work,
so let's delay IRQ enable to ->udc_start()
and IRQ disable to ->udc_stop().
While at that, also move the related use of
request_irq() and free_irq().
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c |
Add support for basic power management on
the dwc3 driver. While there is still lots
to improve for full PM support, this minimal
patch will already make sure that we survive
suspend-to-ram and suspend-to-disk without
major issues.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 104
Hi,
On Fri, Feb 08, 2013 at 06:04:03PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 02/08/2013 04:02 PM, Felipe Balbi wrote:
>
> > this will make sure that request_memory_region() will
> > be called and that we don't need to manually call
> > iounmap() on ->remove().
>
> > Signed-off-by: Felip
On Fri, Feb 08, 2013 at 06:10:41PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 02/08/2013 04:02 PM, Felipe Balbi wrote:
>
> > those two glues are still including
>
>Frankly speaking, I see no way out of it for DA8xx beside duplicating the
> definitions from there.
temporarily duplicating
Commit 8a424bf40d772fedacc91862ecc86f10541fabb3 (tools/usb: remove last USBFS
user) removed 'usbfs' files from the source but retained mentions of 'usbfs'
all over the place, most importantly in the misleading error messages printed
in case USB device files are not there. Remove all the mentions
On Thu, 7 Feb 2013 manjunath.gou...@linaro.org wrote:
> From: Manjunath Goudar
>
>
> Separate the SOC On-Chip host controller driver from ehci-hcd
> host code into its own driver module.
>
> Manjunath Goudar (10):
> USB:Changed omap2plus_defconfig to support OMAP USB static driver
> USB: E
Commit 8a424bf40d772fedacc91862ecc86f10541fabb3 (tools/usb: remove last USBFS
user) removed 'usbfs' files from the source but retained mentions of 'usbfs'
all over the place, most importantly in the misleading error messages printed
in case USB device files are not there. Remove all the mentions
Hi Michel and Laurent,
> Hi Laurent,
>
> On Fri, Feb 08, 2013 at 12:32:44AM +0100, Laurent Pinchart wrote:
> > Hi Bhupesh,
> >
> > On Thursday 07 February 2013 23:39:07 Laurent Pinchart wrote:
> > > On Wednesday 30 January 2013 15:56:52 Bhupesh SHARMA wrote:
> > > > On Monday, January 21, 2013 6:
Hi Laurent,
> Hi Bhupesh,
>
> Thanks for the patch.
>
> On Thursday 17 January 2013 16:23:49 Bhupesh Sharma wrote:
> > This patch corrects the VS_INPUT_HEADER.bEndpointAddress and Video
> > Streaming.bEndpointAddress values which were incorrectly set to 0 in
> > UVC function driver.
> >
> > As '
Hi,
On Fri, Feb 08, 2013 at 04:20:04PM +0200, Felipe Balbi wrote:
> Hi folks,
>
> this patchset implements the bare minimum PM
> support for dwc3. We're not even playing with
> the PHYs yet.
>
> Please give this a good round of test as PM
> always tends to break things apart.
>
> I haven't thor
Hi folks,
this patchset implements the bare minimum PM
support for dwc3. We're not even playing with
the PHYs yet.
Please give this a good round of test as PM
always tends to break things apart.
I haven't thoroughly tested this yet, but I
thought that I should give people enough time
to run all
commit 3921426 (usb: dwc3: core: move
event buffer allocation out of
dwc3_core_init()) introduced a memory leak
of the coherent memory we use as event
buffers on dwc3 driver.
If the driver is compiled as a dynamically
loadable module and use constantly loads
and unloads the driver, we will continu
we don't need to enable IRQs until we have
a gadget driver loaded and ready to work,
so let's delay IRQ enable to ->udc_start()
and IRQ disable to ->udc_stop().
While at that, also move the related use of
request_irq() and free_irq().
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c |
Make the call to dwc3_event_buffers_setup()
and dwc3_event_buffers_cleanup() explicit,
so it's easier to implement PM.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 32 +---
1 file changed, 17 insertions(+), 15 deletions(-)
diff --git a/drivers/usb/dwc3/c
This will be used during resume to verify
if we should reconnect our pullups or not.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.h | 1 +
drivers/usb/dwc3/gadget.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index 11a77f0..
Add support for basic power management on
the dwc3 driver. While there is still lots
to improve for full PM support, this minimal
patch will already make sure that we survive
suspend-to-ram and suspend-to-disk without
major issues.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 104
On 02/08/2013 07:23 PM, Felipe Balbi wrote:
> This will be used during resume to verify
> if we should reconnect our pullups or not.
> Signed-off-by: Felipe Balbi
> ---
> drivers/usb/dwc3/core.h | 1 +
> drivers/usb/dwc3/gadget.c | 2 ++
> 2 files changed, 3 insertions(+)
> diff --git a/driv
On Thu, Feb 07, 2013 at 01:46:27PM -0800, Joe Perches wrote:
> alloc failures already get standardized OOM
> messages and a dump_stack.
>
> For the affected mallocs around these OOM messages:
>
> Converted kmallocs with multiplies to kmalloc_array.
> Converted a kmalloc/memcpy to kmemdup.
> Remov
On Fri, Feb 08, 2013 at 08:27:32PM +0300, Sergei Shtylyov wrote:
> On 02/08/2013 07:23 PM, Felipe Balbi wrote:
>
> > This will be used during resume to verify
> > if we should reconnect our pullups or not.
>
> > Signed-off-by: Felipe Balbi
> > ---
> > drivers/usb/dwc3/core.h | 1 +
> > driver
On Fri, Feb 08, 2013 at 09:22:09AM +0100, Matthias Schniedermeyer wrote:
> On 07.02.2013 07:05, Greg KH wrote:
> > On Thu, Feb 07, 2013 at 02:42:05PM +0100, Matthias Schniedermeyer wrote:
> > > Hi
> > >
> > >
> > > After updating from 3.7.2 to 3.7.6 disconnecting a USB3 device from a
> > > xhci-
On 02/08/2013 07:32 PM, Felipe Balbi wrote:
>>> This will be used during resume to verify
>>> if we should reconnect our pullups or not.
>>> Signed-off-by: Felipe Balbi
>>> ---
>>> drivers/usb/dwc3/core.h | 1 +
>>> drivers/usb/dwc3/gadget.c | 2 ++
>>> 2 files changed, 3 insertions(+)
>>> d
From: "David Laight"
Date: Fri, 8 Feb 2013 10:23:08 -
> It is much better to define constants for the bit values and
> explicitly mask them as required.
Yes, __be32/__le32 along with bit define macros is the only reasonable
way to do this kind of stuff.
--
To unsubscribe from this list: send
On 08.02.2013 08:35, Greg KH wrote:
> On Fri, Feb 08, 2013 at 09:22:09AM +0100, Matthias Schniedermeyer wrote:
> > On 07.02.2013 07:05, Greg KH wrote:
> > > On Thu, Feb 07, 2013 at 02:42:05PM +0100, Matthias Schniedermeyer wrote:
> > > > Hi
> > > >
> > > >
> > > > After updating from 3.7.2 to 3.7
Hi,
On Fri, Feb 08, 2013 at 08:35:09PM +0300, Sergei Shtylyov wrote:
> >>> @@ -1425,8 +1425,10 @@ static int dwc3_gadget_run_stop(struct dwc3 *dwc,
> >>> int is_on)
> >>> if (dwc->revision >= DWC3_REVISION_194A)
> >>> reg &= ~DWC3_DCTL_KEEP_CONNECT;
> >>> reg
On Fri, Feb 08, 2013 at 08:36:24PM +0100, Matthias Schniedermeyer wrote:
> On 08.02.2013 08:35, Greg KH wrote:
> > On Fri, Feb 08, 2013 at 09:22:09AM +0100, Matthias Schniedermeyer wrote:
> > > On 07.02.2013 07:05, Greg KH wrote:
> > > > On Thu, Feb 07, 2013 at 02:42:05PM +0100, Matthias Schniederm
On 08.02.2013 11:58, Greg KH wrote:
> On Fri, Feb 08, 2013 at 08:36:24PM +0100, Matthias Schniedermeyer wrote:
> > On 08.02.2013 08:35, Greg KH wrote:
> > > On Fri, Feb 08, 2013 at 09:22:09AM +0100, Matthias Schniedermeyer wrote:
> > > > On 07.02.2013 07:05, Greg KH wrote:
> > > > > On Thu, Feb 07,
On Fri, 21 Dec 2012 10:13:50 -0800, Doug Anderson wrote:
> Vivek,
>
>
> On Fri, Dec 21, 2012 at 12:16 AM, Vivek Gautam
> wrote:
> > Hi all,
> >
> >
> > On Wed, Dec 19, 2012 at 7:20 PM, Vivek Gautam
> > wrote:
> >> CC: Doug Anderson
> >>
> >>
> >> On Sat, Dec 15, 2012 at 12:53 PM, Grant Likely
Vivek Gautam wrote:
>
> Adding EHCI device tree node for Exynos5250 along with
> the device base adress and gpio line for vbus.
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
> Acked-by: Grant Likely
> ---
>
> Changes from v4:
> - Added gpio line for VBUS of USB2.0 on snow board.
>
From: Joe Perches
Date: Thu, 07 Feb 2013 13:46:27 -0800
> alloc failures already get standardized OOM
> messages and a dump_stack.
>
> For the affected mallocs around these OOM messages:
>
> Converted kmallocs with multiplies to kmalloc_array.
> Converted a kmalloc/memcpy to kmemdup.
> Removed
Those optional operations are used to release and reacquire the queue
lock when videobuf2 needs to perform operations that sleep for a long
time, such as waiting for a buffer to be complete. Implement them to
avoid blocking qbuf or streamoff calls when a dqbuf is in progress.
Signed-off-by: Michae
Hi all,
With the release of the 3.8-rc7 kernel, I think it's time to close the
USB tree for new features / cleanups for 3.9. So I'm closing my
tree, and will only be applying obvious bugfixes or regressions to it
until 3.9-rc1 comes out.
You can keep sending me patches for the tree that don't fi
On Fri, 2013-02-08 at 17:45 -0500, David Miller wrote:
> From: Joe Perches
> Date: Thu, 07 Feb 2013 13:46:27 -0800
> > alloc failures already get standardized OOM
> > messages and a dump_stack.
Does anyone know if all the other alloc's like
dma_alloc_coherent, dma_alloc_noncoherent,
pci_alloc_con
On Fri, Feb 08, 2013 at 04:29:59PM -0800, Joe Perches wrote:
> On Fri, 2013-02-08 at 17:45 -0500, David Miller wrote:
> > From: Joe Perches
> > Date: Thu, 07 Feb 2013 13:46:27 -0800
> > > alloc failures already get standardized OOM
> > > messages and a dump_stack.
>
> Does anyone know if all the
62 matches
Mail list logo
