On 09/08/2014 03:47 PM, Felipe Balbi wrote:
Hi,
On Mon, Sep 08, 2014 at 09:57:00AM +0200, Robert Baldyga wrote:
This patch introduces virtual endpoint address mapping. It separates
function logic form physical endpoint addresses making it more hardware
independent.
Following modifications
On 9/8/2014 7:18 PM, Felipe Balbi wrote:
Hi,
On Mon, Sep 08, 2014 at 04:05:33PM +0530, Amit Virdi wrote:
The kbuild test bot generated the warning:
drivers/usb/gadget/function/f_sourcesink.c:1498: warning: comparison is
always false due to limited range of data type
This patch
This patch introduces virtual endpoint address mapping. It separates
function logic form physical endpoint addresses making it more hardware
independent.
Following modifications changes user space API, so to enable them user
have to switch on the FUNCTIONFS_VIRTUAL_ADDR flag in descriptors.
Up to now, when endpoint addresses in descriptors were non-consecutive,
there were created redundant files, which could cause problems in kernel,
when user tried to read/write to them. It was result of fact that maximum
endpoint address was taken as total number of endpoints in funciton.
This
This patch introduces ioctl named FUNCTIONFS_ENDPOINT_DESC, which
returns endpoint descriptor to userspace. It works only if function
is active.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
Acked-by: Michal Nazarewicz min...@mina86.com
---
drivers/usb/gadget/function/f_fs.c | 23
The kbuild test bot generated the warning:
drivers/usb/gadget/function/f_sourcesink.c:1498: warning: comparison is
always false due to limited range of data type
This patch fixes it.
Reported-by: kbuild test robot fengguang...@intel.com
Signed-off-by: Amit Virdi amit.vi...@st.com
Hi to all,
I've installed new 3.16.2 kernel, and now:
- if I use an USB 3.0 cable I've same crash as said using 3.16.1 version;
- if I use an USB 2.0 cable works, I've made a complete backup without
any problem.
As told, tell me if I can help your works to determine how to resolve this bug.
On 09/09/2014 01:15 AM, Paul Zimmerman wrote:
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Monday, September 08, 2014 4:01 PM
On Mon, Sep 08, 2014 at 10:52:06PM +, Paul Zimmerman wrote:
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Monday, September 08, 2014 3:49 PM
On Mon, 08 Sep 2014, Octavian Purdila wrote:
On Mon, Sep 8, 2014 at 7:30 PM, Johan Hovold jo...@kernel.org wrote:
On Mon, Sep 08, 2014 at 06:57:29PM +0300, Octavian Purdila wrote:
On Mon, Sep 8, 2014 at 5:44 PM, Johan Hovold jo...@kernel.org wrote:
snip
Hi Johan,
Again, thanks
On 8 September 2014 18:22, Andrew Bresticker abres...@chromium.org wrote:
On Mon, Sep 8, 2014 at 8:34 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
On 2 September 2014 23:34, Andrew Bresticker abres...@chromium.org wrote:
Tested on Venice2, Jetson TK1, and Big with a variety of USB2.0 and
Hi Matwey,
On 09/09/2014 01:58 PM, Matwey V. Kornilov wrote:
Hi,
Can you add a few printks around drivers/usb/musb/musb_cppi41.c to
further narrow down where the problem is ? I ran v3.17-rc1 on my
beaglebone black (a while back) and didn't have any issues.
Now I am rebuilding the kernel to
Hi,
I have splitted my patchset usb: dwc2/gadget: fix series into two series.
This patch series contains fixes for dwc2/gadget driver. It's intended
for 3.17-final. I will also send this patches backported for stable.
Best regard
Robert Baldyga
Kamil Debski (2):
usb: dwc2/gadget: fix phy
Endpoint 0 should not be disabled, so we start loop counter from number 1.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
index
From: Andrzej Pietrasiewicz andrze...@samsung.com
Adjust the debug text to the name of the printed variable.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1
Because we have not enough memory to have each TX FIFO of size at least
3072 bytes (the maximum single packet size with 3 transactions per
microframe), we create four FIFOs of lenght 1024, and four of length
3072 bytes, and assing them to endpoints dynamically according to
maxpacket size value of
When device is stopped or suspended clock is not needed so we
can disable it for this time.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
index
From: Marek Szyprowski m.szyprow...@samsung.com
Print warning if FIFOs are configured in such a way that they don't fit
into the SPRAM available on the s3c hsotg module.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
Hi,
This patch series contains fixes for dwc2/gadget driver. It's intended
for 3.16-stable.
Best regards
Robert Baldyga
Kamil Debski (2):
usb: dwc2/gadget: fix phy disable sequence
usb: dwc2/gadget: fix phy initialization sequence
Marek Szyprowski (3):
usb: dwc2/gadget: break infinite
From: Marek Szyprowski m.szyprow...@samsung.com
This patch fixes kernel panic/interrupt storm/etc issues if bootloader
left s3c-hsotg module in enabled state. Now interrupt handler is enabled
only after proper configuration of hardware registers.
Cc: sta...@vger.kernel.org # 3.16.x
Endpoint 0 should not be disabled, so we start loop counter from number 1.
Cc: sta...@vger.kernel.org # 3.16.x
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc2/gadget.c
From: Kamil Debski k.deb...@samsung.com
In the Generic PHY Framework a NULL phy is considered to be a valid phy
thus the if (hsotg-phy) check does not give us the information whether
the Generic PHY Framework is used.
In addition to the above this patch also removes phy_init from probe and
From: Kamil Debski k.deb...@samsung.com
When the driver is removed s3c_hsotg_phy_disable is called three times
instead of once. This results in decreasing of the phy reference counter
below zero and thus consecutive inserts of the module fails.
This patch removes calls to s3c_hsotg_phy_disable
From: Marek Szyprowski m.szyprow...@samsung.com
This patch fixes possible freeze caused by infinite loop in interrupt
context.
Cc: sta...@vger.kernel.org # 3.16.x
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
From: Marek Szyprowski m.szyprow...@samsung.com
This leads to potential spinlock recursion in composite framework, other
udc drivers also don't call it directly from pullup method.
Cc: sta...@vger.kernel.org # 3.16.x
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Robert
Hi,
I have splitted my patchset usb: dwc2/gadget: fix series into two series.
This patch series contains improvements for dwc2/gadget driver. It's intended
for 3.18.
Andrzej Pietrasiewicz (1):
usb: dwc2/gadget: Fix comment text
Kamil Debski (1):
usb: dwc2/gadget: move phy bus legth
From: Marek Szyprowski m.szyprow...@samsung.com
Some DWC2/s3c-hsotg debug messages are really useless for typical user,
so hide them behind dev_dbg().
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 4
From: Kamil Debski k.deb...@samsung.com
This patch moves the part of code that initializes the PHY bus width.
This results in simpler code and removes the need to check whether
the Generic PHY Framework is used.
Signed-off-by: Kamil Debski k.deb...@samsung.com
Signed-off-by: Marek Szyprowski
From: Marek Szyprowski m.szyprow...@samsung.com
This patch fixes kernel panic/interrupt storm/etc issues if bootloader
left s3c-hsotg module in enabled state. Now interrupt handler is enabled
only after proper configuration of hardware registers.
Signed-off-by: Marek Szyprowski
From: Kamil Debski k.deb...@samsung.com
In the Generic PHY Framework a NULL phy is considered to be a valid phy
thus the if (hsotg-phy) check does not give us the information whether
the Generic PHY Framework is used.
In addition to the above this patch also removes phy_init from probe and
From: Kamil Debski k.deb...@samsung.com
When the driver is removed s3c_hsotg_phy_disable is called three times
instead of once. This results in decreasing of the phy reference counter
below zero and thus consecutive inserts of the module fails.
This patch removes calls to s3c_hsotg_phy_disable
From: Marek Szyprowski m.szyprow...@samsung.com
This leads to potential spinlock recursion in composite framework, other
udc drivers also don't call it directly from pullup method.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
From: Marek Szyprowski m.szyprow...@samsung.com
This patch fixes possible freeze caused by infinite loop in interrupt
context.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 1 +
1 file changed, 1
Hello Amit Virdi,
The patch ef11982dd7a6: usb: gadget: zero: Add support for interrupt
EP from Aug 22, 2014, leads to the following static checker warning:
drivers/usb/gadget/function/f_sourcesink.c:1498
f_ss_opts_int_interval_store()
warn: impossible condition '(num 4096) =
Hi George,
Many thanks for the hint. Am I right that we can not have multiple
MUSB DMA modes within the same kernel? It is a pity.
2014-09-09 12:40 GMT+04:00 George Cherian george.cher...@ti.com:
Hi Matwey,
On 09/09/2014 01:58 PM, Matwey V. Kornilov wrote:
Hi,
Can you add a few printks
Hi All,
While working on making error handling in the uas driver more robust,
I noticed that all the commands being send to a sata ssd hooked up
over uas were untagged, where I would expect tcq to be used, as that
is the big advantage of uas over usb-storage / bot.
Taking the uas.c file from
Hi George,
Why dma_controller_create can not be set in struct musb_platform_ops?
Then each module would be able to set dma_controller_create it wants,
and musb_init_controller would use musb-ops-dma_controller_create
instead of just dma_controller_create.
2014-09-09 13:15 GMT+04:00 Matwey V.
On Fri, Sep 05, 2014 at 07:04:51PM +0300, Octavian Purdila wrote:
On Fri, Sep 5, 2014 at 6:38 PM, Johan Hovold jo...@kernel.org wrote:
On Fri, Sep 05, 2014 at 06:17:59PM +0300, Octavian Purdila wrote:
In general, how well have these patches been tested with disconnect
events? At least
On Fri, Sep 05, 2014 at 09:30:11AM +0800, Wang YanQing wrote:
On Thu, Sep 04, 2014 at 06:44:31PM +0200, Benjamin Henrion wrote:
On Thu, Sep 4, 2014 at 6:14 PM, Benjamin Henrion zoo...@gmail.com wrote:
I have subscribed to the lkml.
Can you make me a favour, send me your email as you
On Tue, Sep 09, 2014 at 12:08:56PM +0200, Johan Hovold wrote:
On Fri, Sep 05, 2014 at 09:30:11AM +0800, Wang YanQing wrote:
On Thu, Sep 04, 2014 at 06:44:31PM +0200, Benjamin Henrion wrote:
On Thu, Sep 4, 2014 at 6:14 PM, Benjamin Henrion zoo...@gmail.com wrote:
I have subscribed to the
On Mon, 2014-09-08 at 10:56 -0400, Alan Stern wrote:
On Mon, 8 Sep 2014, Oliver Neukum wrote:
On Fri, 2014-09-05 at 10:15 -0400, Alan Stern wrote:
And even if there is a pending reset, all that will happen is the reset
will cause the port to power up again, and then the reset will
Hello,
Sorry for bother you!
We are testing USB host 2.0 on Lager(R8a7790 SoC),
We realize that there is only a master USB HOST configured on default
config.
Slave devices is not configured on default config.
Could you please enable these CONFIGs?
For Hub:
CONFIG_USB_EHCI_ROOT_HUB_TT=y
For
On 09/09/2014 07:16 PM, カオ ミン ヒェップ wrote:
Hello,
Sorry for bother you!
We are testing USB host 2.0 on Lager(R8a7790 SoC),
We realize that there is only a master USB HOST configured on default
config.
Slave devices is not configured on default config.
Could you please enable these CONFIGs?
On Tue, Sep 9, 2014 at 12:36 PM, Johan Hovold jo...@kernel.org wrote:
On Fri, Sep 05, 2014 at 07:04:51PM +0300, Octavian Purdila wrote:
On Fri, Sep 5, 2014 at 6:38 PM, Johan Hovold jo...@kernel.org wrote:
On Fri, Sep 05, 2014 at 06:17:59PM +0300, Octavian Purdila wrote:
In general, how well
On Tue, Sep 09, 2014 at 06:21:31PM +0800, Wang YanQing wrote:
On Tue, Sep 09, 2014 at 12:08:56PM +0200, Johan Hovold wrote:
On Fri, Sep 05, 2014 at 09:30:11AM +0800, Wang YanQing wrote:
On Thu, Sep 04, 2014 at 06:44:31PM +0200, Benjamin Henrion wrote:
On Thu, Sep 4, 2014 at 6:14 PM,
We need idx to be signed for the error handling to work.
Fixes: 6d5c1c77bbf9 ('usb: gadget: f_fs: fix the redundant ep files problem')
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
---
Btw, there is a sparse warning:
drivers/usb/gadget/function/f_fs.c:401:44: warning: Variable length
On 09/07/2014, 10:27 PM, Vincent Stehlé wrote:
Commit 6a04d05acfb51355 (USB: OHCI: fix bugs in debug routines) has removed
the unused `verbose' argument of the debug function ohci_dump(); adapt
ohci-spear accordingly.
This fixes the following compilation error:
Hi all,
I've backported some commits to my kernel (3.4) to get gadget state
tracking.
I think that I missed something or there is a small error on this one
that hasn't been spotted:
On Tue, Sep 09 2014, Dan Carpenter dan.carpen...@oracle.com wrote:
We need idx to be signed for the error handling to work.
Fixes: 6d5c1c77bbf9 ('usb: gadget: f_fs: fix the redundant ep files problem')
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
Acked-by: Michal Nazarewicz
Hi,
On 09/07/2014 04:36 PM, Laszlo T. wrote:
2014-08-04 20:07 GMT+02:00 Hans de Goede hdego...@redhat.com:
Hi Laszlo,
On 08/03/2014 12:40 AM, Laszlo T. wrote:
*) usb devices return different descriptors at different speeds
All tests were on usb2.
I don't have usb3 ports but I will try
On Tue, Sep 09, 2014 at 12:43:56PM +0200, Johan Hovold wrote:
On Tue, Sep 09, 2014 at 06:21:31PM +0800, Wang YanQing wrote:
On Tue, Sep 09, 2014 at 12:08:56PM +0200, Johan Hovold wrote:
On Fri, Sep 05, 2014 at 09:30:11AM +0800, Wang YanQing wrote:
On Thu, Sep 04, 2014 at 06:44:31PM
On 09/03/2014 10:51 PM, Andrew Bresticker wrote:
Mathias,
On Tue, Aug 19, 2014 at 10:01 AM, Andrew Bresticker
abres...@chromium.org wrote:
It was suggested in the review of the Tegra xHCI driver [1] that we
allow xHCI drivers to be built as individual modules (like EHCI) instead
of
On Tue, Sep 09, 2014 at 03:57:26PM +0200, Michal Nazarewicz wrote:
On Tue, Sep 09 2014, Dan Carpenter dan.carpen...@oracle.com wrote:
Btw, there is a sparse warning:
drivers/usb/gadget/function/f_fs.c:401:44: warning: Variable length array
is used.
The risk here is that the array
On Tue, 9 Sep 2014, Peter Chen wrote:
Hi Felipe Alan,
It is the first step for our discussion for adding reset,
vbus, activation handler for udc framework. This patchset
just adds .reset API at usb_gadget_driver, and the four
gadget drivers still call disconnect handler at .reset.
On 08/22/2014 08:16 PM, Dan Williams wrote:
v1.0 hosts require that TD-fragments (portions of a TD that do not end
on a MPB boundary) not cross a TRB segment boundary. This constraint is
in addition to the constraint that a TRB may not specify a transfer that
crosses a 64K boundary. This
On Tue, 9 Sep 2014, Oliver Neukum wrote:
On Mon, 2014-09-08 at 10:56 -0400, Alan Stern wrote:
On Mon, 8 Sep 2014, Oliver Neukum wrote:
On Fri, 2014-09-05 at 10:15 -0400, Alan Stern wrote:
And even if there is a pending reset, all that will happen is the reset
will cause the
On Tue, Sep 09, 2014 at 07:19:50AM +0530, Vivek Gautam wrote:
Hi,
On Mon, Sep 8, 2014 at 7:14 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Sep 08, 2014 at 09:53:09AM +0530, Vivek Gautam wrote:
On Fri, Sep 5, 2014 at 11:26 PM, Felipe Balbi ba...@ti.com wrote:
On Thu, Sep 04,
On Tue, Sep 09, 2014 at 08:02:16AM +0200, Robert Baldyga wrote:
On 09/08/2014 03:47 PM, Felipe Balbi wrote:
Hi,
On Mon, Sep 08, 2014 at 09:57:00AM +0200, Robert Baldyga wrote:
This patch introduces virtual endpoint address mapping. It separates
function logic form physical endpoint
On Tue, Sep 09, 2014 at 01:28:55PM +0400, Matwey V. Kornilov wrote:
Hi George,
Why dma_controller_create can not be set in struct musb_platform_ops?
Then each module would be able to set dma_controller_create it wants,
and musb_init_controller would use musb-ops-dma_controller_create
Building with the attached random configuration file,
drivers/usb/dwc2/platform.o: In function `dwc2_platform_driver_init':
platform.c:(.init.text+0x0): multiple definition of `init_module'
drivers/usb/dwc2/gadget.o:gadget.c:(.init.text+0x0): first defined here
drivers/usb/dwc2/platform.o: In
On Tue, Sep 09, 2014 at 12:02:43PM +0300, Dan Carpenter wrote:
Hello Amit Virdi,
The patch ef11982dd7a6: usb: gadget: zero: Add support for interrupt
EP from Aug 22, 2014, leads to the following static checker warning:
drivers/usb/gadget/function/f_sourcesink.c:1498
Hi,
On Tue, Sep 09, 2014 at 03:20:58PM +0200, François MULLER wrote:
Hi all,
I've backported some commits to my kernel (3.4) to get gadget state
tracking.
I think that I missed something or there is a small error on this one that
hasn't been spotted:
asm1051e usb - sata bridges hang when receiving a report opcodes scsi cmnd.
Take a page out of the usb-storage book, and simple disable no_report_opcodes
outright.
Cc: sta...@vger.kernel.org # 3.16
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/usb/storage/uas.c | 2 ++
1 file
Hi Greg,
I've received a number of bug-reports from users related to uas on ASM1051
chipset using devices. After some searching around I've managed to get myself
an ASM1051 device.
As a result I've spend the last 4 days trying to get the ASM1051 chipset to
work. After some initial success which
Even with REPORT SUPPORTED OPERATION CODES blacklisted the ASM1051 chipset
still does not work when combined with some disks, e.g. a Crucial M500 ssd.
When used with a troublesome disk, the chipset throws all kinds of USB errors,
and eventually hangs, where as in BOT mode it works fine.
To make
2014-09-09 18:45 GMT+04:00 Felipe Balbi ba...@ti.com:
On Tue, Sep 09, 2014 at 01:28:55PM +0400, Matwey V. Kornilov wrote:
Hi George,
Why dma_controller_create can not be set in struct musb_platform_ops?
Then each module would be able to set dma_controller_create it wants,
and
Hello linux-usb,
I've been testing surprise device hotlug removal with RHEL7 on Stratus
hardware (fully redundant PCI branches) and ran into a crashing NULL-ptr
bug during device initialization. The code looks the same upstream, so
I'm reporting it here.
Trace 1 (khubd)
===
PID: 93
Hello linux-usb,
I'd like to report another USB bug that appeared during surprise hotplug
device removal. With slub_debug=FZPU set, I would occasionally see the
following writes to a poison pattern:
=
BUG kmalloc-2048
Hi,
Johan's patch means that for the affected touchscreen the port
can never be powered off. It seems to me that this needs a special
flag. What do you think?
Regards
Oliver
From a4d154ead29c0c7d1e11d29d8202c33526e08558 Mon Sep 17 00:00:00 2001
From: Oliver Neukum
On Tue, Sep 09, 2014 at 08:23:15AM +0200, Robert Baldyga wrote:
Up to now, when endpoint addresses in descriptors were non-consecutive,
there were created redundant files, which could cause problems in kernel,
when user tried to read/write to them. It was result of fact that maximum
endpoint
On Tue, Sep 09, 2014 at 10:04:26AM -0500, Felipe Balbi wrote:
On Tue, Sep 09, 2014 at 08:23:15AM +0200, Robert Baldyga wrote:
Up to now, when endpoint addresses in descriptors were non-consecutive,
there were created redundant files, which could cause problems in kernel,
when user tried to
On Tue, Sep 09, 2014 at 07:00:10PM +0400, Matwey V. Kornilov wrote:
2014-09-09 18:45 GMT+04:00 Felipe Balbi ba...@ti.com:
On Tue, Sep 09, 2014 at 01:28:55PM +0400, Matwey V. Kornilov wrote:
Hi George,
Why dma_controller_create can not be set in struct musb_platform_ops?
Then each module
On Tue, 9 Sep 2014, Oliver Neukum wrote:
Hi,
Johan's patch means that for the affected touchscreen the port
can never be powered off. It seems to me that this needs a special
flag. What do you think?
Why can't the port be powered off?
Alan Stern
--
To unsubscribe from this list: send the
On Tue, 9 Sep 2014, Hans de Goede wrote:
Even with REPORT SUPPORTED OPERATION CODES blacklisted the ASM1051 chipset
still does not work when combined with some disks, e.g. a Crucial M500 ssd.
When used with a troublesome disk, the chipset throws all kinds of USB errors,
and eventually
On Tue, Sep 09, 2014 at 11:15:24AM +0200, Hans de Goede wrote:
Taking the uas.c file from 3.17, and building it for 3.16 restores
the use of tcq (debugged by adding a printk blk_rq_tagged + request-tag).
So either uas is doing something wrong which happened to work in
3.16, or something has
On Tue, 9 Sep 2014, Joe Lawrence wrote:
Hello linux-usb,
I've been testing surprise device hotlug removal with RHEL7 on Stratus
hardware (fully redundant PCI branches) and ran into a crashing NULL-ptr
bug during device initialization. The code looks the same upstream, so
I'm reporting it
On Tue, 9 Sep 2014, Joe Lawrence wrote:
...
hub_events does later go on to check for hub-disconnected, but that's
outside the hub_event_lock and *after* the call to usb_lock_device. In
my traces, that's too late as its already been freed and poisoned.
There's probably a better way to
On Tue, 9 Sep 2014, Alan Stern wrote:
The fix is almost correct. Take the reference when hub_events removes
the hub from hub_event_list, while the hub_event_lock is still held.
That way the get and put occur in the same subroutine, and there's
opportunity for them to become unbalanced.
2014-09-09 19:11 GMT+04:00 Felipe Balbi ba...@ti.com:
the proper way would be to move everything to dma_engine. OMAP already
has support for DMA engine and both CPPI and Ux500 are already using
that.
If so, ux500_dma.c and musb_cppi41.c should be almost identically
wrapping dmaengine, but they
On Tue, Sep 09, 2014 at 04:59:59PM +0200, Hans de Goede wrote:
asm1051e usb - sata bridges hang when receiving a report opcodes scsi cmnd.
Take a page out of the usb-storage book, and simple disable no_report_opcodes
outright.
Given that this device also seems broken in other ways can we wait
On Tue, Sep 09, 2014 at 07:52:59PM +0400, Matwey V. Kornilov wrote:
2014-09-09 19:11 GMT+04:00 Felipe Balbi ba...@ti.com:
the proper way would be to move everything to dma_engine. OMAP already
has support for DMA engine and both CPPI and Ux500 are already using
that.
If so, ux500_dma.c
On Tue, 2014-09-09 at 11:23 -0400, Alan Stern wrote:
On Tue, 9 Sep 2014, Oliver Neukum wrote:
Hi,
Johan's patch means that for the affected touchscreen the port
can never be powered off. It seems to me that this needs a special
flag. What do you think?
Why can't the port be
2014-09-09 20:09 GMT+04:00 Felipe Balbi ba...@ti.com:
On Tue, Sep 09, 2014 at 07:52:59PM +0400, Matwey V. Kornilov wrote:
2014-09-09 19:11 GMT+04:00 Felipe Balbi ba...@ti.com:
the proper way would be to move everything to dma_engine. OMAP already
has support for DMA engine and both CPPI and
On Tue, Sep 09 2014, Dan Carpenter dan.carpen...@oracle.com wrote:
On Tue, Sep 09, 2014 at 03:57:26PM +0200, Michal Nazarewicz wrote:
On Tue, Sep 09 2014, Dan Carpenter dan.carpen...@oracle.com wrote:
Btw, there is a sparse warning:
drivers/usb/gadget/function/f_fs.c:401:44: warning:
Hi,
On Tue, Sep 09, 2014 at 08:17:32PM +0400, Matwey V. Kornilov wrote:
2014-09-09 20:09 GMT+04:00 Felipe Balbi ba...@ti.com:
On Tue, Sep 09, 2014 at 07:52:59PM +0400, Matwey V. Kornilov wrote:
2014-09-09 19:11 GMT+04:00 Felipe Balbi ba...@ti.com:
the proper way would be to move
Hi,
On Tue, Sep 09, 2014 at 06:37:02PM +0200, Michal Nazarewicz wrote:
On Tue, Sep 09 2014, Dan Carpenter dan.carpen...@oracle.com wrote:
On Tue, Sep 09, 2014 at 03:57:26PM +0200, Michal Nazarewicz wrote:
On Tue, Sep 09 2014, Dan Carpenter dan.carpen...@oracle.com wrote:
Btw, there is a
On Tue, 9 Sep 2014, Oliver Neukum wrote:
On Tue, 2014-09-09 at 11:23 -0400, Alan Stern wrote:
On Tue, 9 Sep 2014, Oliver Neukum wrote:
Hi,
Johan's patch means that for the affected touchscreen the port
can never be powered off. It seems to me that this needs a special
flag.
On Tue, Sep 9, 2014 at 1:21 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
On 8 September 2014 18:22, Andrew Bresticker abres...@chromium.org wrote:
On Mon, Sep 8, 2014 at 8:34 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
On 2 September 2014 23:34, Andrew Bresticker abres...@chromium.org wrote:
On Tue, Sep 09, 2014 at 10:48:10AM +0200, Robert Baldyga wrote:
Hi,
This patch series contains fixes for dwc2/gadget driver. It's intended
for 3.16-stable.
That's not how stable patch submission works :(
The patches need to be in Linus's tree first, then, if they don't apply
to a stable
On Tue, 9 Sep 2014, Alan Stern wrote:
On Tue, 9 Sep 2014, Oliver Neukum wrote:
On Tue, 2014-09-09 at 11:23 -0400, Alan Stern wrote:
On Tue, 9 Sep 2014, Oliver Neukum wrote:
Hi,
Johan's patch means that for the affected touchscreen the port
can never be powered off. It
On Tue, 2014-09-09 at 12:53 -0400, Alan Stern wrote:
On Tue, 9 Sep 2014, Oliver Neukum wrote:
On Tue, 2014-09-09 at 11:23 -0400, Alan Stern wrote:
On Tue, 9 Sep 2014, Oliver Neukum wrote:
Hi,
Johan's patch means that for the affected touchscreen the port
can never be
On 09/09/14 07:46, Jim Davis wrote:
Building with the attached random configuration file,
drivers/usb/dwc2/platform.o: In function `dwc2_platform_driver_init':
platform.c:(.init.text+0x0): multiple definition of `init_module'
drivers/usb/dwc2/gadget.o:gadget.c:(.init.text+0x0): first defined
On Tue, 2014-09-09 at 13:25 -0400, Alan Stern wrote:
On Tue, 9 Sep 2014, Alan Stern wrote:
On Tue, 9 Sep 2014, Oliver Neukum wrote:
On Tue, 2014-09-09 at 11:23 -0400, Alan Stern wrote:
On Tue, 9 Sep 2014, Oliver Neukum wrote:
Hi,
Johan's patch means that for the
Hi,
On Tue, Sep 09, 2014 at 09:16:50PM +0400, Matwey V. Kornilov wrote:
I am still running 3.16.1 no BeagleBone Black and after I sorted out
the configuration nothing oopses, but there is another problem.
I can't attach any device (including but not limited to USB-hub with
external power) to
2014-09-09 21:49 GMT+04:00 Felipe Balbi ba...@ti.com:
Hi,
On Tue, Sep 09, 2014 at 09:16:50PM +0400, Matwey V. Kornilov wrote:
I am still running 3.16.1 no BeagleBone Black and after I sorted out
the configuration nothing oopses, but there is another problem.
I can't attach any device
Hi Paul,
On 09/08/2014 05:50 PM, Greg KH wrote:
On Tue, Aug 26, 2014 at 11:19:54AM -0500, dingu...@opensource.altera.com
wrote:
From: Dinh Nguyen dingu...@opensource.altera.com
Adds the gadget data structure and appropriate data structure pointers
to the common dwc2_hsotg data structure.
Specifying these attributes in both the prototype and the function
definition is unnecessary and could cause confusion or bugs if they are
inconsistent. As such, __init should only be specified at the function
definition.
Keith Owens suggested this as a janitorial task on LKML several years
ago:
Now that ehci-dbgp has its own header, use it rather than duplicating
the declarations, etc.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
drivers/usb/host/fusbh200.h | 40 ++--
1 file changed, 2 insertions(+), 38 deletions(-)
diff --git
The FUSBH200 debug port has a EHCI-compatible register layout so there
is no need to define a custom struct.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
drivers/usb/host/fotg210.h | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/usb/host/fotg210.h
Now that ehci-dbgp has its own header, use it rather than duplicating
the declarations, etc.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
drivers/usb/host/fotg210.h | 40 ++--
1 file changed, 2 insertions(+), 38 deletions(-)
diff --git
On Tue, 9 Sep 2014 11:30:24 -0400
Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 9 Sep 2014, Joe Lawrence wrote:
In summary, khubd has initialized the usb_device maxchild to 8 and
provided backing-store for the usb_hub ports[] array. However, before
it gets to fill in pointers for
1 - 100 of 127 matches
Mail list logo
