Hi,
On Sat, Jan 31, 2015 at 01:18:46PM +0200, Antti Seppälä wrote:
This patch switches calls to readl/writel to their
dwc2_readl/dwc2_writel equivalents which preserve platform endianness.
This patch is necessary to access dwc2 registers correctly on big endian
systems such as the mips
Hello,
On Wed, March 11, 2015 2:51 pm, Sascha Hauer wrote:
This driver normally is not used with device tree. Without additional
kernel changes the chipidea driver is used instead.
I'm just forward-porting a patch I made for 2.6.31.14 to workaround
an issue we found. I'm unsure where to fit
Hello Felipe,
On Tue, Mar 10, 2015 at 04:12:14PM -0500, Felipe Balbi wrote:
Hi,
(dropping patch, my only context is subject line)
USB: gadget: atmel_usba_udc: Request an auto disabled Vbus signal IRQ
instead of an auto enabled IRQ request followed by IRQ disable
Holy crap, that's a
Hi Tony,
On Tuesday 10 March 2015 02:21 AM, Tony Lindgren wrote:
Add a minimal driver for dm816x USB. Otherwise we can just use
the existing musb_am335x and musb_dsps on dm816x.
If we can use an existing driver, I'd prefer that.
Cc: Brian Hutchinson b.hutch...@gmail.com
Cc: Felipe Balbi
On 10.03.2015 19:29, Alan Stern wrote:
On Tue, 10 Mar 2015, Mathias Nyman wrote:
Yes, thank you
Seems that It wasn't mature enough, I'll revert it.
From your logs I can see what went wrong,
If you still have some time, could you try out a patch (attached) and see if
it solves the
On Thu, Mar 12, 2015 at 09:39:06AM +0800, Lu Baolu wrote:
When a device with an isochronous endpoint is plugged into the Intel
xHCI host controller, and the driver submits multiple frames per URB,
the xHCI driver will set the Block Event Interrupt (BEI) flag on all
but the last TD for the URB.
On 10/03/2015 at 16:23:53 -0500, Felipe Balbi wrote :
Yeah, let's drop it for now but I have the feeling that this will
break (I actually broke it when switching at91 to multiplatform).
aha, that changes it. So you already have something which makes this
break ? Are you planning on sending
On 11.03.2015 18:16, Jörg Otte wrote:
2015-03-11 12:01 GMT+01:00 Jörg Otte jrg.o...@gmail.com:
2015-03-10 18:04 GMT+01:00 Mathias Nyman mathias.ny...@linux.intel.com:
On 10.03.2015 17:36, Jörg Otte wrote:
I'd suspect one of these two patches:
commit 45ba2154d12fc43b70312198ec47085f10be801a
On 3/9/2015 3:03 PM, Vincent Palatin wrote:
On Thu, Mar 5, 2015 at 11:17 PM, Yunzhi Li l...@rock-chips.com wrote:
When dwc2 controller detects a disconnect interrupt,
dwc2_hcd_disconnect() should be called immediately to do clean-up
jobs and set port_connect_status_change flag to notify usb
On 03/12/2015 04:46 PM, Mathias Nyman wrote:
On 12.03.2015 03:39, Lu Baolu wrote:
When a device with an isochronous endpoint is plugged into the Intel
xHCI host controller, and the driver submits multiple frames per URB,
the xHCI driver will set the Block Event Interrupt (BEI) flag on all
but
On Wed, Mar 11, 2015 at 03:52:53PM +0100, Bas Vermeulen wrote:
Hello,
On Wed, March 11, 2015 2:51 pm, Sascha Hauer wrote:
This driver normally is not used with device tree. Without additional
kernel changes the chipidea driver is used instead.
I'm just forward-porting a patch I made for
Hi Sascha,
On Wed, March 11, 2015 4:46 pm, Sascha Hauer wrote:
On Wed, Mar 11, 2015 at 04:05:31PM +0100, Bas Vermeulen wrote:
On Wed, March 11, 2015 4:01 pm, Sascha Hauer wrote:
On Wed, Mar 11, 2015 at 03:52:53PM +0100, Bas Vermeulen wrote:
Hello,
On Wed, March 11, 2015 2:51 pm, Sascha
* Kishon Vijay Abraham I kis...@ti.com [150311 02:58]:
Hi Tony,
On Tuesday 10 March 2015 02:21 AM, Tony Lindgren wrote:
Add a minimal driver for dm816x USB. Otherwise we can just use
the existing musb_am335x and musb_dsps on dm816x.
If we can use an existing driver, I'd prefer that.
Hmm
On 12.03.2015 03:39, Lu Baolu wrote:
When a device with an isochronous endpoint is plugged into the Intel
xHCI host controller, and the driver submits multiple frames per URB,
the xHCI driver will set the Block Event Interrupt (BEI) flag on all
but the last TD for the URB. This causes the host
On 03/12/2015 03:54 PM, Greg Kroah-Hartman wrote:
On Thu, Mar 12, 2015 at 09:39:06AM +0800, Lu Baolu wrote:
When a device with an isochronous endpoint is plugged into the Intel
xHCI host controller, and the driver submits multiple frames per URB,
the xHCI driver will set the Block Event
Hi Greg,
This is likely my last pull for the -rc, but things may
change. Let me know if you need any changes
Patches tested on platforms I have access to.
cheers
The following changes since commit 9eccca0843205f87c00404b663188b88eb248051:
Linux 4.0-rc3 (2015-03-08 16:09:09 -0700)
are
This patch adds driver data to support for Exynos5433 SoC.
The Exynos5433 has one USB3.0 Host and USB3.0 DRD(Dual Role Device).
Exynos5433 is simplar to Eyxnos7 but Exynos5433 have
one more USB3.0 Host controller.
Signed-off-by: Jaewon Kim jaewon02@samsung.com
---
When a device with an isochronous endpoint is plugged into the Intel
xHCI host controller, and the driver submits multiple frames per URB,
the xHCI driver will set the Block Event Interrupt (BEI) flag on all
but the last TD for the URB. This causes the host controller to place
an event on the
Hello.
On 3/12/2015 6:13 AM, Scott Wood wrote:
Use %pS for actual addresses, otherwise you'll get bad output
%pS or %ps?
on arches like ppc64 where %pF expects a function descriptor.
%pF or %pf? And what is a function descriptor?
Signed-off-by: Scott Wood scottw...@freescale.com
Hello,
I'm affected by the bug described in
https://bugzilla.kernel.org/show_bug.cgi?id=46201 and would like to
help to triage the cause of this bug. Unfortunately I have no
experience in kernel debugging and my programming skills are rather
limited. Is there anything I can do to help?
Regards
On 06.03.2015 10:12, Lu Baolu wrote:
Linux xHCI driver doesn't report and handle port cofig error change.
If Port Configure Error for root hub port occurs, CEC bit in PORTSC
would be set by xHC and remains 1. This happends when the root port
fails to configure its link partner, e.g. the port
On Thu, Mar 12, 2015 at 11:04:09AM -0500, Felipe Balbi wrote:
Hi,
On Thu, Mar 12, 2015 at 10:30:21AM +0800, Li Jun wrote:
From: Li Jun b47...@freescale.com
Peripheral answers OTG status selector request from host according to
host_request_flag of gadget, length is 1.
On Thu, Mar 12, 2015 at 10:30:21AM +0800, Li Jun wrote:
From: Li Jun b47...@freescale.com
Peripheral answers OTG status selector request from host according to
host_request_flag of gadget, length is 1.
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/chipidea/udc.c | 28
On Thu, Mar 12, 2015 at 10:30:20AM +0800, Li Jun wrote:
From: Li Jun b47...@freescale.com
Adds host_request_flag for gadget to store host request information from
application, which can be used to response to HNP polling from host.
typo, %s/response to/respond
Signed-off-by: Li Jun
Serial ports of F81504/F81508/F81512 will failed when wakeup from S3(STR).
It's due to when the system wakeup from S3(STR), this PCI device's
configuration space from 0x40 to 0x40 + max_port * 0x08 should be
re-configured.
We move all initialization from pci_fintek_setup() to pci_fintek_init()
These series patches works for Fintek F81504/F81508/F81512 PCI to Serial Port.
and patch 0002 is following with patch 0001.
patch 0001 is just cleanup non-used source code.
patch 0002 is major patch.
The serial port of our product will failed after wakeup from S3(STR).
It's due to when the
Remove pci_fintek_setup() non-used var with calculation ciobase
Signed-off-by: Peter Hung hpeter+linux_ker...@gmail.com
---
drivers/tty/serial/8250/8250_pci.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_pci.c
Hi Al,
On Fri, 13 Mar 2015 03:56:09 + Al Viro v...@zeniv.linux.org.uk wrote:
On Thu, Mar 12, 2015 at 11:24:26PM -0400, David Miller wrote:
From: Stephen Rothwell s...@canb.auug.org.au
Date: Fri, 13 Mar 2015 13:15:43 +1100
Today's linux-next merge of the net-next tree got a
On Thu, Mar 12, 2015 at 11:24:26PM -0400, David Miller wrote:
From: Stephen Rothwell s...@canb.auug.org.au
Date: Fri, 13 Mar 2015 13:15:43 +1100
Today's linux-next merge of the net-next tree got a conflict in
net/socket.c between commits 005139a14660 (fs: remove ki_nbytes) and
From: Al Viro v...@zeniv.linux.org.uk
Date: Fri, 13 Mar 2015 03:56:09 +
On Thu, Mar 12, 2015 at 11:24:26PM -0400, David Miller wrote:
From: Stephen Rothwell s...@canb.auug.org.au
Date: Fri, 13 Mar 2015 13:15:43 +1100
Today's linux-next merge of the net-next tree got a conflict in
On Thu, Mar 12, 2015 at 10:30:23AM +0800, Li Jun wrote:
Adds HNP polling timer when transits to host state, the OTG status request
will be sent to peripheral after timeout, if host request flag is set, it will
switch to peripheral state, otherwise it will repeat HNP polling every 1.5s
and
On Thu, Mar 12, 2015 at 12:27:07AM -0500, Scott Wood wrote:
On Wed, 2015-03-11 at 23:45 -0500, Felipe Balbi wrote:
On Wed, Mar 11, 2015 at 10:13:53PM -0500, Scott Wood wrote:
Use %pS for actual addresses, otherwise you'll get bad output
on arches like ppc64 where %pF expects a function
On Thu, 12 Mar 2015, Martin Stolpe wrote:
Hello,
I'm affected by the bug described in
https://bugzilla.kernel.org/show_bug.cgi?id=46201 and would like to
help to triage the cause of this bug. Unfortunately I have no
experience in kernel debugging and my programming skills are rather
On Thu, Mar 12, 2015 at 12:13 AM, Scott Wood scottw...@freescale.com wrote:
Use %pS for actual addresses, otherwise you'll get bad output
on arches like ppc64 where %pF expects a function descriptor.
From Documentation/printk-formats.txt:
On ia64, ppc64 and parisc64 architectures function
Hi,
On Thu, Mar 12, 2015 at 10:30:21AM +0800, Li Jun wrote:
From: Li Jun b47...@freescale.com
Peripheral answers OTG status selector request from host according to
host_request_flag of gadget, length is 1.
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/chipidea/udc.c | 28
On Thu, 2015-03-12 at 12:51 -0300, Fabio Estevam wrote:
On Thu, Mar 12, 2015 at 12:13 AM, Scott Wood scottw...@freescale.com wrote:
Use %pS for actual addresses, otherwise you'll get bad output
on arches like ppc64 where %pF expects a function descriptor.
From
On Thu, 2015-03-12 at 15:36 +0300, Sergei Shtylyov wrote:
Hello.
On 3/12/2015 6:13 AM, Scott Wood wrote:
Use %pS for actual addresses, otherwise you'll get bad output
%pS or %ps?
on arches like ppc64 where %pF expects a function descriptor.
%pF or %pf? And what is a
On Thu, Mar 12, 2015 at 1:40 PM, Scott Wood scottw...@freescale.com wrote:
No. __builtin_return_address() returns a pointer to an instruction, not
a function pointer descriptor. If you use %pF on the former, it'll
print instruction opcodes as if they were the address.
Then you should
This patch switches calls to readl/writel to their
dwc2_readl/dwc2_writel equivalents which preserve platform endianness.
This patch is necessary to access dwc2 registers correctly on big endian
systems such as the mips based SoCs made by Lantiq. Then dwc2 can be
used to replace ifx-hcd driver
Here are two patches needed to add support for mips based
big-endian SoCs made by Lantiq to dwc2 driver.
The first patch converts the readl/writel io-accessors of dwc2 to
big-endian friendly versions and was discussed on the linux-usb ml
already earlier.
The second patch adds default fifo
Lantiq SoCs define the total_fifo_size to be 552 dwords which is too
small for algorithm in dwc2_calculate_dynamic_fifo to work properly.
This patch provides sensible defaults for fifo sizes for Lantiq SoCs
to be used in dwc2 driver. The default values are taken from original
ifx-hcd driver.
* Rusty Russell ru...@rustcorp.com.au [150311 18:15]:
Tony Lindgren t...@atomide.com writes:
* Paul Bolle pebo...@tiscali.nl [150311 04:16]:
Oh, it should be just GPL v2 like most of the kernel. Probably copied
the header from some other phy driver, will update that instead.
Well, all my
The dwc2-pci driver requires the generic PHY. This fixes undefined
reference issues when it is not selected.
Reported-by: kbuild test robot fengguang...@intel.com
Signed-off-by: John Youn johny...@synopsys.com
---
This fixes issue with commit 9024c495 on -next.
John
drivers/usb/dwc2/Kconfig |
Hi,
On Thu, Mar 12, 2015 at 05:40:56AM +, yoshihiro shimoda wrote:
Hi,
On Thu, Mar 12, 2015 at 04:33:41AM +, yoshihiro shimoda wrote:
Hi Geert-san again,
Hi Geert-san,
Thank you for the reply again!
Hi Shimoda-san,
On Mon, Feb 16, 2015 at 2:52 AM,
On Thu, Mar 12, 2015 at 6:15 AM, Lu Baolu baolu...@linux.intel.com wrote:
When a device with an isochronous endpoint is plugged into the Intel
xHCI host controller, and the driver submits multiple frames per URB,
the xHCI driver will set the Block Event Interrupt (BEI) flag on all
but the last
Please kindly read my message
Hello
it is with tears that i am writing to you i need your help and
assistance am an aging widow suffering from long time cancer of the
throat and I inherited from my late husband, the sum of 9. 5 Millions
Nine Million Five Hundred Thousand Dollars and I
On Thu, Mar 12, 2015 at 11:15 AM, Lu Baolu baolu...@linux.intel.com wrote:
When a device with an isochronous endpoint is plugged into the Intel
xHCI host controller, and the driver submits multiple frames per URB,
the xHCI driver will set the Block Event Interrupt (BEI) flag on all
but the
Hi,
On Thu, Mar 12, 2015 at 3:40 PM, Jaewon Kim jaewon02@samsung.com wrote:
Exynos5 series SoC does not have usb2-phy on USB3.0 Controller.
It is controlled by only usb3-phy. So, this patch remove usb2-phy
property.
Why would you want to remove the usb2-phy property ?
The usb2-phy
When a device with an isochronous endpoint is plugged into the Intel
xHCI host controller, and the driver submits multiple frames per URB,
the xHCI driver will set the Block Event Interrupt (BEI) flag on all
but the last TD for the URB. This causes the host controller to place
an event on the
This patchset adds independent registration of gadgets
and gadget drivers to udc-core. This is very useful for
built-in modules into kernel case since it's possible
situation that gadget driver is probing at a time
when no gadgets are registered in udc-core.
In this case instead of silently
Now when last user of usb_udc_attach_driver() is switched
to passing UDC name via usb_gadget_driver struct, it's safe
to remove this function
Signed-off-by: Ruslan Bilovol ruslan.bilo...@gmail.com
---
drivers/usb/gadget/udc/udc-core.c | 26 --
include/linux/usb/gadget.h
Change behavior during registration of gadgets and
gadget drivers in udc-core. Instead of previous
approach when for successful probe of usb gadget driver
at least one usb gadget should be already registered
use another one where gadget drivers and gadgets
can be registered in udc-core
Introduce new 'udc_name' member to usb_gadget_driver structure.
The 'udc_name' is a name of UDC that usb_gadget_driver should
be bound to. If udc_name is NULL, it will be bound to any
available UDC.
Signed-off-by: Ruslan Bilovol ruslan.bilo...@gmail.com
---
drivers/usb/gadget/udc/udc-core.c | 24
Now when udc-core supports binding to specific UDC by passing
its name via 'udc_name' member of usb_gadget_driver struct,
switch to this generic approach.
Signed-off-by: Ruslan Bilovol ruslan.bilo...@gmail.com
---
drivers/usb/gadget/configfs.c | 27 ++-
1 file changed, 14
In order to prepare to independent gadgets and
gadget drivers registration in udc-core, some of the
functions can't have __init/__exit attributes (almost
only bind/unbind callbacks are affected)
Signed-off-by: Ruslan Bilovol ruslan.bilo...@gmail.com
---
drivers/usb/gadget/legacy/acm_ms.c |
Use %ps for actual addresses, otherwise you'll get bad output
on arches like ppc64 where %pf expects a function descriptor
(which is not what __builtin_return_address returns).
Signed-off-by: Scott Wood scottw...@freescale.com
Cc: linux-usb@vger.kernel.org
Cc: Felipe Balbi ba...@ti.com
Cc: Fabio
On Thu, Mar 12, 2015 at 6:46 PM, Scott Wood scottw...@freescale.com wrote:
Use %ps for actual addresses, otherwise you'll get bad output
on arches like ppc64 where %pf expects a function descriptor
(which is not what __builtin_return_address returns).
Signed-off-by: Scott Wood
Proposal,
Respond to my personal email; mrs.zhangxiao1962@outlook.
com
Yours Sincerely.
Mrs. Zhang Xiao (Accounts book Keeper)
Angang
Steel Company Limited
396 Nan Zhong Hua Lu, Tie Dong District Anshan,
Liaoning 114021, China.
--
To unsubscribe from this list: send the line unsubscribe
Exynos5 series SoC does not have usb2-phy on USB3.0 Controller.
It is controlled by only usb3-phy. So, this patch remove usb2-phy
property.
Signed-off-by: Jaewon Kim jaewon02@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi |4 ++--
arch/arm/boot/dts/exynos5420.dtsi |8
2
Hi,
Hi,
On Thu, Mar 12, 2015 at 05:40:56AM +, yoshihiro shimoda wrote:
Hi,
snip
try something like below:
diff --git a/drivers/usb/renesas_usbhs/mod_gadget.c
b/drivers/usb/renesas_usbhs/mod_gadget.c
index e0384af77e56..e9d75d85be59 100644
---
2015-03-10 15:03 GMT+01:00 Jörg Otte jrg.o...@gmail.com:
2015-03-10 14:06 GMT+01:00 Mathias Nyman mathias.ny...@linux.intel.com:
On 10.03.2015 11:40, Jörg Otte wrote:
If I plug in my USB DVB-T stick I get the following in dmesg:
dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver'
Some Renesas SoCs have the USB-DMAC. It is able to terminate transfers
when a short packet is received, even if less bytes than the transfer
counter size have been received. Also, it is able to send a short
packet even if the packet size is not multiples of 8bytes.
Since the previous code has
This patch fixes the setup sequence in xfer_work(). Otherwise,
sometimes a usb transaction will get stuck.
Signed-off-by: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
---
drivers/usb/renesas_usbhs/fifo.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
This patch set is based on Felipe's usb.git / testing/next branch.
(commit id = 9024c495f35be735a917571406fab30a789c27d1)
To use the USB-DMAC, we have to add some device nodes for USB-DMAC
in dts file. If we don't have such device nodes, this driver will
use PIO.
Changes from v2:
- Remove patch
To connect the channel of USB-DMAC to USBHS DnFIFO number, this patch
adds this channel/FIFO number in dma-names. Otherwise, this driver
needs to add analysis code for device tree.
Signed-off-by: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
---
.../devicetree/bindings/usb/renesas_usbhs.txt
65 matches
Mail list logo
