I am looking forward to a new blog post in this excellent series :)
http://www.kroah.com/log/linux/maintainer.html
http://www.kroah.com/log/linux/maintainer-02.html
http://www.kroah.com/log/linux/maintainer-03.html
http://www.kroah.com/log/linux/maintainer-04.html
Hi,
On Tue, Apr 09, 2013 at 02:36:51AM +, Paul Zimmerman wrote:
I'm getting a crash when I rmmod the dwc3-pci driver in latest Linus, and
also in 3.8.6 and 3.8.0.
Screenshot (two parts) are here:
http://ompldr.org/vaTFibQ/IMG1.jpg
http://ompldr.org/vaTFicA/IMG2.jpg
Hi Roger,
On Mon, Mar 25, 2013 at 12:42:04PM +0200, Roger Quadros wrote:
Hi Samuel,
I've rebased this now on top of 3.9-rc4. Please pull this into your
next branch when appropriate. Thanks.
The following changes since commit 8bb9660418e05bb1845ac1a2428444d78e322cc7:
Linux 3.9-rc4
On Tue, Apr 09, 2013 at 01:10:49AM +0400, Sergei Shtylyov wrote:
Hello.
Here's the set of 9 patches against the Simon Horman's 'renesas.git' repo,
'renesas-next-20130405v2' tag. It was created to fix the shortcomings in the
R8A7779/Marzen USB platform code and R8A7779 USB common PHY
PHY reset GPIO handling will be done in the PHY driver
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Acked-by: Samuel Ortiz sa...@linux.intel.com
---
drivers/mfd/omap-usb-host.c | 28
1 files changed, 0 insertions(+), 28
Allows the OMAP HS USB host controller to be specified
via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
Reviewed-by: Mark Rutland mark.rutl...@arm.com
---
.../devicetree/bindings/mfd/omap-usb-host.txt | 80 ++
drivers/mfd/omap-usb-host.c| 161
Samuel,
You had the conflicts because a patch [*] was introduced and is not
required since the reset logic is being removed from the driver.
Anyways, I've rebased the 2 patches on top of mfd-next, so now it
shouldn't matter.
cheers,
-roger
[*]
commit 71f4b9cdfccfb82cff702fe61f4ace97a1dfb0e0
This patchset tries to enhance the UVC gadget test application and is based on
Laurent's git tree available here (project: uvc-gadget.git):
git://git.ideasonboard.org/uvc-gadget.git
The patch 2/2 in this patchset also adds a README file describing the UVC
gadget test application, it's possible
This patch adds a README file describing the UVC gadget test application,
it's possible use-case scenarios and IO method support in detail.
Signed-off-by: Bhupesh Sharma bhupesh.sha...@st.com
---
README | 209
1 files changed, 209
7edb3da makes ehci-s5p as a separate driver. But,
it raised an issue with its driver data.
Now that 's5p_ehci_hcd' doesn't maintain pointer to 'usb_hcd'
and s5p_ehci is nothing but a pointer to hcd-priv;
add hcd to the driver data rather than s5p_ehci.
This fixes issues with null pointer
Adding support for a Mediatek based device labelled as
D-Link Model: DWM-156, H/W Ver: A7
Also adding two other device IDs found in the Debian(!)
packages included on the embedded device driver CD.
This is a composite MBIM + serial ports + card reader device:
T: Bus=04 Lev=01 Prnt=01 Port=00
On 04/05/2013 06:58 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130405 03:44]:
On 04/04/2013 07:41 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130404 00:39]:
On 04/04/2013 02:42 AM, Tony Lindgren wrote:
For v3.10, let's just make sure that USB works with DT as then
On 04/05/2013 08:56 PM, Grygorii Strashko wrote:
On 04/04/2013 07:41 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130404 00:39]:
On 04/04/2013 02:42 AM, Tony Lindgren wrote:
--- a/arch/arm/mach-omap2/cclock44xx_data.c
+++ b/arch/arm/mach-omap2/cclock44xx_data.c
@@ -27,6 +27,7 @@
Hi,
can someone provide a MinGW 32bits built of the last working RC,
thanx in advance,
best regards,
Nicolas
Le 04/04/13 21:12, nico a écrit :
Hi,
merci beaucoup to everyone for your work...
Le 04/04/13 20:35, Pete Batard a écrit :
On 2013.04.04 09:27, nico wrote:
Making all in libusb
CC
Hello.
On 05-04-2013 6:01, Kuninori Morimoto wrote:
Here's the set of 4 patches against the Simon Horman's 'renesas.git' repo,
'renesas-next-20130404v2' tag and the 2 Ether patches I've reposted yesterday.
It was created to fix the shortcomings in the R8A7779/Marzen USB platform code
and
Thist patch removes the depends on USB_EHCI_HCD that the various USB
EHCI HCD drivers use and encloses every driver within an if USB_EHCI_HCD
/ endif block. The EHCI HCD platform and Octeon drivers have been moved
around to remain enclosed within this block.
Acked-by: Alan Stern
This patch removes the various depends on USB_OHCI_HCD from the OHCI HCD
drivers and enclose them within an if USB_OHCI_HCD / endif block. The
Octeon OHCI HCD driver has been moved around to remain in this block.
Acked-by: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Florian Fainelli
This patch removes the depends on USB from all config symbols in
drivers/usb/host/Kconfig and replace that with an if USB / endif block
as suggested by Alan Stern. Some source ... Kconfig lines have been
shuffled around to permit a better regroupment of the Kconfig files
depending on config USB
This patch encloses all symbols depending on USB_XHCI_HCD within an if
USB_XHCI_HCD / endif block.
Acked-by: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Florian Fainelli flor...@openwrt.org
---
Changes in v4:
- refreshed against latest usb-next
Changes in v3:
- added Alan's Acked-by tag
These 5 patches contain my Kconfig cleanup on which I based the removal
of the USB_ARCH_HAS_* patches. They have been suggested by Alan Stern
as part of an earlier conversations.
Let me know what you think about it so I can post subsequent work based
on it.
Florian Fainelli (5):
USB: regroup
Just like the OHCI counter part we just can remove the architecture
specific symbols which prevent these configuration symbols from being
selected by platforms/architectures requiring it. The original
implementation did not scale at all since it required each and every
single architecture to be
Hello.
On 09-04-2013 13:21, Vivek Gautam wrote:
7edb3da makes ehci-s5p as a separate driver. But,
Please also provide the summary line of that commit in parens.
it raised an issue with its driver data.
Now that 's5p_ehci_hcd' doesn't maintain pointer to 'usb_hcd'
and s5p_ehci is nothing
Hello.
On 09-04-2013 9:58, Kuninori Morimoto wrote:
Here's the set of 9 patches against the Simon Horman's 'renesas.git' repo,
'renesas-next-20130405v2' tag. It was created to fix the shortcomings in the
R8A7779/Marzen USB platform code and R8A7779 USB common PHY driver, and so
spans both
Hello.
On 09-04-2013 3:42, Greg KH wrote:
Sometimes there is a need to initialize some non-standard
registers mapped to
the EHCI region before accessing the standard EHCI registers.
Add pre_setup()
method with 'struct usb_hcd *' parameter to be called just
before ehci_setup()
to the
Hi,
On Tue, Apr 9, 2013 at 6:01 PM, Sergei Shtylyov
sergei.shtyl...@cogentembedded.com wrote:
Hello.
On 09-04-2013 13:21, Vivek Gautam wrote:
7edb3da makes ehci-s5p as a separate driver. But,
Please also provide the summary line of that commit in parens.
Sure, will add the commit
7edb3da: (USB: EHCI: make ehci-s5p a separate driver)
raised an issue with ehci-s5p's driver data.
Now that 's5p_ehci_hcd' doesn't maintain pointer to 'usb_hcd'
and s5p_ehci is nothing but a pointer to hcd-priv;
add hcd to the driver data rather than s5p_ehci.
This fixes issues with null pointer
This adds a config option USB_DWC2_DEBUG_PERIODIC that allows debugging
output be suppressed for periodic transfers. This helps when debugging
non-periodic transfers while there are also periodic transfers going on
(both to make the debug output less polluted and to prevent all CPU time
going to
On Tue, Apr 09, 2013 at 04:00:15PM +0400, Sergei Shtylyov wrote:
Hello.
On 05-04-2013 6:01, Kuninori Morimoto wrote:
Here's the set of 4 patches against the Simon Horman's 'renesas.git'
repo,
'renesas-next-20130404v2' tag and the 2 Ether patches I've reposted
yesterday.
It was
On Tue, 9 Apr 2013, Sergei Shtylyov wrote:
--- renesas.orig/include/linux/usb/ehci_pdriver.h
+++ renesas/include/linux/usb/ehci_pdriver.h
@@ -19,6 +19,8 @@
#ifndef __USB_CORE_EHCI_PDRIVER_H
#define __USB_CORE_EHCI_PDRIVER_H
+#include linux/usb/hcd.h
This isn't needed in the .h
On Tue, 9 Apr 2013, victor yeo wrote:
Hi,
Earlier, you complained that your gadget was able to read the boot
sector but not the MBR! :-)
How do you know the reads were sending all zeros? The usbmon output
shows only the first 32 bytes of each transfer, and the gadget
debugging
On Tue, 9 Apr 2013, victor yeo wrote:
Another usbmon trace showing 3 SCSI_READ_10 command.
This trace shows that the READ(10) commands worked correctly. Good.
But it also shows that the gadget did not respond correctly to the 0xA1
command near the end. The UDC was supposed to set the Halt
It sounds like u-boot already has basic xHCI support, and you should
contact the u-boot developers for further support of interrupt
transfers.
http://lists.denx.de/mailman/listinfo/u-boot
or
https://lists.sourceforge.net/lists/listinfo/u-boot-users
Disregard my comments about bit-banging the
* Roger Quadros rog...@ti.com [130409 03:00]:
On 04/05/2013 06:58 PM, Tony Lindgren wrote:
Well your approach is fine as a first step moving all the clock
code, but it needs to be a real driver under drivers/clock/omap.
And the DT binding needs to stay the same for the driver(s) in the
Hello.
On 04/09/2013 07:27 PM, Alan Stern wrote:
--- renesas.orig/include/linux/usb/ehci_pdriver.h
+++ renesas/include/linux/usb/ehci_pdriver.h
@@ -19,6 +19,8 @@
#ifndef __USB_CORE_EHCI_PDRIVER_H
#define __USB_CORE_EHCI_PDRIVER_H
+#include linux/usb/hcd.h
This isn't needed in the .h
On Tue, Apr 09, 2013 at 05:01:36PM +0200, Matthijs Kooijman wrote:
This adds a config option USB_DWC2_DEBUG_PERIODIC that allows debugging
output be suppressed for periodic transfers. This helps when debugging
non-periodic transfers while there are also periodic transfers going on
(both to
Hi,
On Mon, Apr 08, 2013 at 03:59:00PM -0500, Daniel Santos wrote:
My bother I are working on a project where we're planning on using
these inexpensive Microchip MCP2210 USB to SPI bridge w/ GPIO
devices. Mathew King at Trilithic started a driver and kindly
released it on github
On Tue, 9 Apr 2013 09:31:18 -0700
Sarah Sharp sarah.a.sh...@linux.intel.com wrote:
It sounds like u-boot already has basic xHCI support, and you should
contact the u-boot developers for further support of interrupt
transfers.
http://lists.denx.de/mailman/listinfo/u-boot
This is the correct
On Mon, Apr 8, 2013 at 9:09 PM, Fabio Estevam feste...@gmail.com wrote:
I know that I have to use the driver ULPI but with my configuration, I
get these errors :
ehci-mxc: Freescale On-Chip EHCI Host driver
mxc-ehci mxc-ehci.0: initializing i.MX USB Controller
timeout polling for ULPI
Hi Felipe,
This adds a config option USB_DWC2_DEBUG_PERIODIC that allows debugging
output be suppressed for periodic transfers. This helps when debugging
non-periodic transfers while there are also periodic transfers going on
(both to make the debug output less polluted and to prevent all
* Tony Lindgren t...@atomide.com [130409 09:54]:
* Roger Quadros rog...@ti.com [130409 03:00]:
On 04/05/2013 06:58 PM, Tony Lindgren wrote:
Can't you just use the clock name there to get it?
In device tree we don't pass around clock names. You can either get
a phandle or an index
Hi,
subject:
Power supply interrupted on USB port (normal and Always-on) when performing
reboot from any Windows version but not when rebooting from Linux or BIOS
(Lenovo ThinkPad T4xx). Why the difference?
According to my research there is no standard describing the power state
(power
On 04/09/2013 12:15 AM, Greg KH wrote:
On Mon, Apr 08, 2013 at 03:59:00PM -0500, Daniel Santos wrote:
1. Discover that the kernel already contains an abstraction layer
for an x to SPI bridge device and that I just need to write an
MCP2210 driver for it!
We have lots of SPI drivers in the
If for whatever reason we fall into fail path in xhci_mem_init()
before bw table gets initialized we may access the uninitialized lists
in xhci_mem_cleanup().
Check for bw table before traversing lists in cleanup routine.
Reported-by: Sergey Dyasly dse...@gmail.com
Tested-by: Sergey Dyasly
On Tue, Apr 09, 2013 at 01:24:55PM -0500, Daniel Santos wrote:
On 04/09/2013 12:15 AM, Greg KH wrote:
On Mon, Apr 08, 2013 at 03:59:00PM -0500, Daniel Santos wrote:
1. Discover that the kernel already contains an abstraction layer
for an x to SPI bridge device and that I just need to write an
On Tue, Apr 09, 2013 at 02:00:51PM +, Blaz Malnersic wrote:
Is it possible to influence USB power on OS reboot? Linux and BIOS don't
interrupt the power of USB port on reboot, only Windows (all versions we
tested do). This along with different times of power lack leads me to
On 04/09/2013 12:07 PM, Felipe Balbi wrote:
Hi,
On Mon, Apr 08, 2013 at 03:59:00PM -0500, Daniel Santos wrote:
My bother I are working on a project where we're planning on using
these inexpensive Microchip MCP2210 USB to SPI bridge w/ GPIO
devices. Mathew King at Trilithic started a driver
On Tue, Apr 09, 2013 at 02:00:46PM -0500, Daniel Santos wrote:
Well, we don't have the $3500 for a vendor id. :( I presume that
others may do the same thing, hopefully mostly with DIY-type of
projects.
Do you know this one:
From: Matthijs Kooijman [mailto:matth...@stdin.nl]
Sent: Tuesday, April 09, 2013 8:02 AM
This adds a config option USB_DWC2_DEBUG_PERIODIC that allows debugging
output be suppressed for periodic transfers. This helps when debugging
non-periodic transfers while there are also periodic
Hi,
These patches add support for Tahvo USB transceiver and allow using both
host and peripheral modes on Nokia 770.
Patches are currently based on top of Felipe's next branch
(git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git,
9b192de60b5a584ee4ed967fb6758773c75e4643). To make them
Tahvo is a multi-function device on Nokia 770, implementing USB
transceiver and charge/battery control.
It's so close to Retu that a single driver can support both.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Samuel Ortiz sa...@linux.intel.com
---
drivers/mfd/Kconfig |6 ++--
Add Tahvo USB transceiver driver.
Based on old code from linux-omap tree. The original driver was written
by Juha Yrjölä, Tony Lindgren, and Timo Teräs.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
---
drivers/usb/phy/Kconfig | 14 ++
drivers/usb/phy/Makefile|1 +
Transceivers need to manage OTG controller state on OMAP1 to enable
switching between peripheral and host modes. Provide a driver for that.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
---
drivers/usb/phy/Kconfig| 10
drivers/usb/phy/Makefile |1 +
On 10:43-20130409, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [130409 09:54]:
* Roger Quadros rog...@ti.com [130409 03:00]:
On 04/05/2013 06:58 PM, Tony Lindgren wrote:
Can't you just use the clock name there to get it?
In device tree we don't pass around clock
Hi,
For some time now (at least since 3.0) I have been having issues with an
USB3 to Sata enclosure and xHCI. The device (174c:55aa ASMedia
Technology Inc) works perfectly fine on USB2 ports in Linux, as well as
on the NEC/Renesas uPD720200(A) USB3 controller in Windows, but not so
on any
On 15:49-20130409, Nishanth Menon wrote:
On 10:43-20130409, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [130409 09:54]:
* Roger Quadros rog...@ti.com [130409 03:00]:
On 04/05/2013 06:58 PM, Tony Lindgren wrote:
Can't you just use the clock name there to get
On 04/09/2013 02:06 PM, Robert Schwebel wrote:
On Tue, Apr 09, 2013 at 02:00:46PM -0500, Daniel Santos wrote:
Well, we don't have the $3500 for a vendor id. :( I presume that
others may do the same thing, hopefully mostly with DIY-type of
projects.
Do you know this one:
Hello.
Here's the set of 9 patches against the Simon Horman's 'renesas.git' repo,
'renesas-next-20130410' tag. It was created to fix the shortcomings in the
R8A7779/Marzen USB platform code and R8A7779 USB common PHY driver, and so
spans both arch/arm/mach-shmobile/ and drivers/usb/ subtrees
USB EHCI, OHCI, and common PHY are the SoC devices but are wrongly defined and
registered in the Marzen board file. Move the data and code to their proper
place in setup-r8a7779.c; while at it, we have to rename 8a7779_late_devices[]
to 8a7779_standard_devices[] -- this seems legitimate since
Sometimes there is a need to initialize some non-standard registers mapped to
the EHCI region before accessing the standard EHCI registers. Add pre_setup()
method with 'struct usb_hcd *' parameter to be called just before ehci_setup()
to the 'ehci-platform' driver's platform data for this
Setup the EHCI internal buffer (before EHCI driver has a chance to touch the
registers) using the pre_setup() method in 'struct usb_ehci_pdata'.
The patch has been tested on the Marzen board.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
Acked-by: Kuninori Morimoto
Now that the EHCI internal buffer setup is done by the platform code, we can
remove such code from this driver as it never really belonged here. We also
no longer need the 2nd memory region now (2nd EHCI controller is simply missing
in e.g. R8A7778 SoC).
The patch has been tested on the
Now that 'drivers/usb/phy/rcar-phy.c' doesn't require the second memory resource
anymore, we can remove it from the R8A7779's USB PHY platform device.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
Acked-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
Acked-by: Simon
The memory region that is used by the driver overlaps EHCI and OHCI register
regions for absolutely no reason now -- fix it by adding offset of 0x800 to
the base address, changing the register #define's accordingly. This has extra
positive effect that we now can use devm_ioremap_resource()...
Currently the driver hard-codes USBPCTRL0 register to 0. It is wrong since this
register contains board-specific USB ports configuration and so its value should
be somehow passed via the platform data. Add linux/usb/rcar-phy.h file with
the USBPCTRL0 bit #define's and 'struct
Since we're now going to setup the USBPCTRL0 register using the USB PHY device's
platform data, we now need a way to pass those platform data from the board file
to the device which is situated in setup-r8a7779.c -- and what I'm suggesting is
r8a7779_add_usb_phy_device() that will register USB PHY
Set the USBPCTRL0 register from the passed platform data in rcar_usb_phy_init();
don't reset it to 0 in rcar_usb_phy_shutdown() anymore as that does not make
sense. Also, don't allow the driver's probe to succeed when the platform data
are not supplied with a device.
The patch has been tested
Hello.
Here's the set of 4 patches against the Simon Horman's 'renesas.git' repo,
'renesas-next-20130410' tag. It was created to add support of R8A7778/BOCK-W
USB to the platform code and the USB common PHY driver, and so spans both
arch/arm/mach-shmobile/ and drivers/usb/phy/ subtrees.
The driver currently only supports R8A7779 SoC. Compared to it, R8A7778 USB-PHY
has extra register range containing two high-speed signal quality characteristic
control registers which should be set up during USB-PHY startup depending on
whether a ferrite bead is in use or not. So, we now
Add USB clock and EHCI, OHCI, and USB PHY platform devices for R8A7778 SoC; add
a function to register PHY device with board-specific platform data and register
EHCI and OHCI platfrom devices from the init_late() board method.
Also, don't forget to enable CONFIG_ARCH_HAS_[EO]HCI options for
Register the USB PHY device from bockw_init(), passing the platform data to it.
Set machine's init_late() method to r8a7778_init_late() in order for [EO]HCI to
get registered too...
The patch has been tested on the BOCK-W board.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
Enable USB platform EHCI/OHCI and common PHY drivers in 'bockw_defconfig'.
Enable USB storage driver and SCSI disk driver that it needs as well...
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
arch/arm/configs/bockw_defconfig | 11 ++-
1 file changed, 10
Some drivers (sierra_net) need the status interrupt URB
active even when the device is closed, because they receive
custom indications from firmware. Add functions to refcount
the status interrupt URB submit/kill operation so that
sub-drivers and the generic driver don't fight over whether
the
The driver and firmware sync up through SYNC messages, and the
firmware's affirmative reply to these SYNC messages appears to be the
Reset indication received via the status interrupt endpoint. Thus the
driver needs the status interrupt endpoint always active so that the
Reset indication can be
On 2013.04.09 11:39, nico wrote:
can someone provide a MinGW 32bits built of the last working RC,
Sure. Please have a look at the -win download from:
https://sourceforge.net/projects/libusbx/files/releases/1.0.15/binaries/
The Windows binary contains the 32 and 64 bit versions of both the
Hi Sergei
Please add this tested on xxx comment on each patch's log area, not only
on [0/x].
We need it on git log
I'm going to post R8A7778/BOCK-W series following this one, and all the
patches in 1st series should additionally be tested on BOCK-W. Well, I
probably can hold up
i have posted the query on the u-boot mailing list. Waiting for their
response on it.
Thanks
Puneet
On Tue, 2013-04-09 at 22:01 +0530, Sarah Sharp wrote:
It sounds like u-boot already has basic xHCI support, and you should
contact the u-boot developers for further support of interrupt
On Wed, Apr 10, 2013 at 02:26:08AM +0400, Sergei Shtylyov wrote:
Hello.
Here's the set of 9 patches against the Simon Horman's 'renesas.git' repo,
'renesas-next-20130410' tag. It was created to fix the shortcomings in the
R8A7779/Marzen USB platform code and R8A7779 USB common PHY
77 matches
Mail list logo
