Daniel
Hi all,
here are some patches to separate the HCD and gadget part of the musb
driver so they can be deselected in Kconfig. They also make the driver
keep track of the configured port mode that is set from DT, so the
actual runtime configuration can be selected dynamically.
One
Hi Ravi,
On 08.04.2013 09:57, B, Ravi wrote:
Hi all,
here are some patches to separate the HCD and gadget part of the musb
driver so they can be deselected in Kconfig. They also make the driver
keep track of the configured port mode that is set from DT, so the
actual runtime configuration
Hi Arshad,
The driver used by the USB controller is MUSB_HDRC.
Looking at musb_core.c, I've found the following comment:
* * Control and bulk use dedicated endpoints, and there's as
*yet no mechanism to either (a) reclaim the hardware when
*peripherals are NAKing, which
On Sat, Apr 06, 2013 at 08:43:51PM +0400, Sergei Shtylyov wrote:
Before, the value of the hcchar register was shifted and masked and then
the debug output extracted the individual values out of the complete
hcchar register again. This commit makes the debug prints directly use
the original
Hi Paul,
But you really need to split this into a more manageable series of
patches. It's really difficult to review when you have so many different
things all munged together like this. It's also discouraging to potential
reviewers to see one set of 41 patches, where if it was four series of
Daniel
On 08.04.2013 09:57, B, Ravi wrote:
Hi all,
here are some patches to separate the HCD and gadget part of the musb
driver so they can be deselected in Kconfig. They also make the driver
keep track of the configured port mode that is set from DT, so the
actual runtime
Hi,
On Mon, Apr 08, 2013 at 12:25:38PM +0200, B, Ravi wrote:
Daniel
On 08.04.2013 09:57, B, Ravi wrote:
Hi all,
here are some patches to separate the HCD and gadget part of the musb
driver so they can be deselected in Kconfig. They also make the driver
keep track of the
Felipe
Hi,
On Mon, Apr 08, 2013 at 12:25:38PM +0200, B, Ravi wrote:
Daniel
On 08.04.2013 09:57, B, Ravi wrote:
Hi all,
here are some patches to separate the HCD and gadget part of the
musb
driver so they can be deselected in Kconfig. They also make the
driver
keep
Daniel
Subject: [PATCH v2 09/11] usb: musb: re-introduce musb-port_mode
Define MUSB_PORT_MODE_{HOST,GADGET,DUAL_ROLE} and store the
platform-specified value in struct musb.
Note that MUSB_PORT_MODE_HOST has to be set to 1 in order to match
existing device tree bindings which are already
Daniel
Subject: [PATCH v2 07/11] usb: musb: add Kconfig options for HOST, GAGDET
or DUAL_ROLE modes
This makes building the actual object files optional to the selected
mode, which saves users who know which kind of USB mode support they
need some binary size.
Unimplemented functions
Hi Jean-Philippe,
On Wednesday 06 March 2013 14:21:14 jean-philippe francois wrote:
Hi,
The company I work for is doing USB cameras, for which
I wrote the drivers (out of tree).
Just out of curiosity, was there any shortcoming in the UVC specification that
pushed your company to
Hi Ravi,
On 08.04.2013 12:42, B, Ravi wrote:
Subject: [PATCH v2 07/11] usb: musb: add Kconfig options for HOST, GAGDET
or DUAL_ROLE modes
This makes building the actual object files optional to the selected
mode, which saves users who know which kind of USB mode support they
need some
On 08.04.2013 12:39, B, Ravi wrote:
Subject: [PATCH v2 09/11] usb: musb: re-introduce musb-port_mode
Define MUSB_PORT_MODE_{HOST,GADGET,DUAL_ROLE} and store the
platform-specified value in struct musb.
Note that MUSB_PORT_MODE_HOST has to be set to 1 in order to match
existing device tree
Hi Tony,
On 04/05/2013 05:43 PM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [130405 03:00]:
On 04/05/2013 10:30 AM, Benoit Cousson wrote:
...
ARM: dts: OMAP4: Add HS USB Host IP nodes
ARM: dts: OMAP3: Add HS USB Host IP nodes
ARM: dts: omap3-beagle: Add USB Host support
Hello.
On 08-04-2013 6:33, Simon Horman 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
Hi Daniel
On 08.04.2013 12:42, B, Ravi wrote:
Subject: [PATCH v2 07/11] usb: musb: add Kconfig options for HOST,
GAGDET
or DUAL_ROLE modes
This makes building the actual object files optional to the selected
mode, which saves users who know which kind of USB mode support they
need
Hi Ravi,
On 08.04.2013 14:48, B, Ravi wrote:
On 08.04.2013 12:42, B, Ravi wrote:
Subject: [PATCH v2 07/11] usb: musb: add Kconfig options for
HOST,
GAGDET
or DUAL_ROLE modes
This makes building the actual object files optional to the
selected mode, which saves users who know which kind
Daniel
On 08.04.2013 12:39, B, Ravi wrote:
Subject: [PATCH v2 09/11] usb: musb: re-introduce musb-port_mode
Define MUSB_PORT_MODE_{HOST,GADGET,DUAL_ROLE} and store the
platform-specified value in struct musb.
Note that MUSB_PORT_MODE_HOST has to be set to 1 in order to match
On 2013/3/30 4:24, Alan Stern wrote:
On Fri, 29 Mar 2013, Sarah Sharp wrote:
Also, bear in mind that the proposed patch does not give userspace a
way to power off ports via usbfs. What the new code does is a
power-off reset -- it turns off power to the port, waits a short time,
and then turns
On 08.04.2013 14:55, B, Ravi wrote:
Daniel
On 08.04.2013 12:39, B, Ravi wrote:
Subject: [PATCH v2 09/11] usb: musb: re-introduce musb-port_mode
Define MUSB_PORT_MODE_{HOST,GADGET,DUAL_ROLE} and store the
platform-specified value in struct musb.
Note that MUSB_PORT_MODE_HOST has to be set
Hi,
On Thursday 04 April 2013 05:24 AM, Stephen Warren wrote:
On 04/03/2013 06:53 AM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To
On Mon, Apr 08, 2013 at 08:58:09PM +0800, Lan Tianyu wrote:
On 2013/3/30 4:24, Alan Stern wrote:
On Fri, 29 Mar 2013, Sarah Sharp wrote:
Also, bear in mind that the proposed patch does not give userspace a
way to power off ports via usbfs. What the new code does is a
power-off reset -- it
Hi everyone,
I need some help to understand how USB is configured.
I am updating an old kernel (2.6.32 !) to the version 3.8.2. I am
self-taught on Linux kernel so, sometimes, I need the help of the
community to understand it :)
The SoC is a IMX27. For the USB side, we have a NXP ISP1504.
I
On 2013/4/1 23:12, Alan Stern wrote:
On Mon, 1 Apr 2013, Lan Tianyu wrote:
On 2013年03月30日 01:23, Alan Stern wrote:
On Fri, 29 Mar 2013, Sarah Sharp wrote:
However, what happens if you echo 0 to pm_qos_no_power_off, the
power/control is set to auto, and there's a suspended USB device
attached
On Mon, Apr 08, 2013 at 08:18:44AM -0700, Sarah Sharp wrote:
On Fri, Apr 05, 2013 at 08:52:53AM -0700, Aguirre Rodriguez, Sergio A wrote:
On Fri, Apr 05, 2013 at 06:51:21AM +0400, Vladimir Murzin wrote:
On Thu, Apr 04, 2013 at 12:29:25PM -0700, Sarah Sharp wrote:
What about picking up
On Thu, Apr 04, 2013 at 02:03:04PM -0700, Julius Werner wrote:
When CONFIG_XHCI_HCD_DEBUGGING is activated, the XHCI driver can dump
device and input contexts to the console. The endpoint contexts in that
dump are labeled Endpoint N Context, where N is DCI - 1... this is
very confusing,
Applied, thanks!
On Fri, Apr 05, 2013 at 02:27:07PM -0400, Tony Camuso wrote:
There are no functional changes in this patch. However, because the
compliance mode timer can be deleted in more than one function, it
seemed expedient to include the function name in the debug strings.
Also
On Fri, Apr 05, 2013 at 08:01:03PM +0300, Petko Manolov wrote:
On Wed, 27 Mar 2013, Petko Manolov wrote:
On Tue, 26 Mar 2013, Sarah Sharp wrote:
The new driver actually compiles and runs fine with Pegasus-II based
device. Please let me know if you run into problems.
I'm away for a week, so I
On Mon, Apr 08, 2013 at 06:29:36AM -0700, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:58:09PM +0800, Lan Tianyu wrote:
On 2013/3/30 4:24, Alan Stern wrote:
On Fri, 29 Mar 2013, Sarah Sharp wrote:
Also, bear in mind that the proposed patch does not give userspace a
way to power off ports
On Mon, Apr 08, 2013 at 08:57:43AM -0700, Sarah Sharp wrote:
On Mon, Apr 08, 2013 at 06:29:36AM -0700, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:58:09PM +0800, Lan Tianyu wrote:
On 2013/3/30 4:24, Alan Stern wrote:
On Fri, 29 Mar 2013, Sarah Sharp wrote:
Also, bear in mind that the
Hi Aaro,
On Thu, Mar 07, 2013 at 04:40:18PM +0200, Aaro Koskinen wrote:
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
On Thu, Apr 04, 2013 at 05:57:23PM +0200, Florian Fainelli wrote:
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
On Mon, 8 Apr 2013, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:57:43AM -0700, Sarah Sharp wrote:
On Mon, Apr 08, 2013 at 06:29:36AM -0700, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:58:09PM +0800, Lan Tianyu wrote:
On 2013/3/30 4:24, Alan Stern wrote:
On Fri, 29 Mar 2013, Sarah Sharp
If the xHCI spec is contradictory, please contact xhcisupp...@intel.com.
Sarah Sharp
On Mon, Apr 01, 2013 at 10:48:35AM +, Ankit wrote:
With respect to latest xHCI spec :
Revision 1.0
with errata to 8/14/12
Page 114:
Note: Consider the case where there are multiple TDs posted for
On Mon, 8 Apr 2013, victor yeo wrote:
Hi,
Now i insmod g_file_storage gadget with file=/mnt/sd/backing_file, the
SCSI_READ_10 command is still not working properly.
What makes you think that?
Because the SCSI_READ_10 is able to read the MBR from the backing
file, and after that,
On Tue, Apr 02, 2013 at 06:23:58PM +0200, Arnd Bergmann wrote:
Hi Greg,
Here are the EHCI patches that I think are good for inclusion in 3.10,
I hope you are willing to include them after the debacle over these
patches in 3.9.
The patches are all logically independent but sorted by
On Mon, 8 Apr 2013, Lan Tianyu wrote:
Hi Alan:
I think current code can't achieve that power off port(whose
child device was already suspended but it was not powered off due to
NO_POWER_OFF flag setting.) via clearing NO_POWER_OFF flag. Because
at that moment, its usage count can't be
On Mon, 8 Apr 2013, Greg KH wrote:
On Tue, Apr 02, 2013 at 06:23:58PM +0200, Arnd Bergmann wrote:
Hi Greg,
Here are the EHCI patches that I think are good for inclusion in 3.10,
I hope you are willing to include them after the debacle over these
patches in 3.9.
The patches are
* Benoit Cousson b-cous...@ti.com [130408 05:11]:
Hi Tony,
On 04/05/2013 05:43 PM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [130405 03:00]:
On 04/05/2013 10:30 AM, Benoit Cousson wrote:
...
ARM: dts: OMAP4: Add HS USB Host IP nodes
ARM: dts: OMAP3: Add HS USB
On Monday 08 April 2013, Greg KH wrote:
On Tue, Apr 02, 2013 at 06:23:58PM +0200, Arnd Bergmann wrote:
Hi Greg,
Here are the EHCI patches that I think are good for inclusion in 3.10,
I hope you are willing to include them after the debacle over these
patches in 3.9.
The patches
Hi Ryan,
I'm the xHCI driver author. It helps if you Cc maintainers (listed in
the MAINTAINERS file), otherwise emails do get lost:
http://lxr.linux.no/#linux/MAINTAINERS
Comments below.
On Tue, Mar 26, 2013 at 02:55:48PM -0700, Ryan Press wrote:
I'm working to get the 3.9-rc1 kernel working
On Mon, Apr 08, 2013 at 09:01:44AM -0700, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:57:43AM -0700, Sarah Sharp wrote:
On Mon, Apr 08, 2013 at 06:29:36AM -0700, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:58:09PM +0800, Lan Tianyu wrote:
Hi Alan Sarah:
I just recall why I put
Cc-ing the linux-pm list and some Intel power devs, as I think this
specific discussion could benefit from a broader audience.
On Mon, Apr 08, 2013 at 12:33:00PM -0400, Alan Stern wrote:
On Mon, 8 Apr 2013, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:57:43AM -0700, Sarah Sharp wrote:
On
Le 08/04/2013 18:32, Greg KH a écrit :
On Thu, Apr 04, 2013 at 05:57:23PM +0200, Florian Fainelli wrote:
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
On Mon, Apr 08, 2013 at 08:16:46PM +0200, Florian Fainelli wrote:
Le 08/04/2013 18:32, Greg KH a écrit :
On Thu, Apr 04, 2013 at 05:57:23PM +0200, Florian Fainelli wrote:
These 5 patches contain my Kconfig cleanup on which I based the removal
of the USB_ARCH_HAS_* patches. They have been
Receiving unhandled notifications is most certainly not an error
and should not be logged as one. Knowing that the device sends
notifications we don't handle is useful for developers, but there
is very little a user can do about this. The message is therefore
just annoying noise to most users
On Monday, April 08, 2013 10:33:54 AM Sarah Sharp wrote:
On Mon, Apr 08, 2013 at 09:01:44AM -0700, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:57:43AM -0700, Sarah Sharp wrote:
On Mon, Apr 08, 2013 at 06:29:36AM -0700, Greg KH wrote:
On Mon, Apr 08, 2013 at 08:58:09PM +0800, Lan Tianyu
On Mon, 8 Apr 2013, Sarah Sharp wrote:
That could work. However, we have to think about future platform power
changes as well. Coming up with a USB specific way to work around the
runtime PM core will hurt us in the long run, if we end up having to
change the runtime PM core for another
On Monday, April 08, 2013 10:55:19 AM Sarah Sharp wrote:
Cc-ing the linux-pm list and some Intel power devs, as I think this
specific discussion could benefit from a broader audience.
On Mon, Apr 08, 2013 at 12:33:00PM -0400, Alan Stern wrote:
On Mon, 8 Apr 2013, Greg KH wrote:
On
On Mon, Apr 08, 2013 at 09:39:07PM +0200, Rafael J. Wysocki wrote:
On Monday, April 08, 2013 10:55:19 AM Sarah Sharp wrote:
Cc-ing the linux-pm list and some Intel power devs, as I think this
specific discussion could benefit from a broader audience.
On Mon, Apr 08, 2013 at 12:33:00PM
From: Bjørn Mork bj...@mork.no
Date: Mon, 8 Apr 2013 20:26:23 +0200
Receiving unhandled notifications is most certainly not an error
and should not be logged as one. Knowing that the device sends
notifications we don't handle is useful for developers, but there
is very little a user can do
Hello!
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 (https://github.com/MathewKing/mcp2210-linux), but he wont be
using
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 driver, and so
spans both arch/arm/mach-shmobile/ and drivers/usb/
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'.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
Changes since the original posting:
- changed from init() platform device method
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).
Signed-off-by: Sergei Shtylyov
On Tue, Apr 09, 2013 at 01:20:00AM +0400, Sergei Shtylyov 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
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
---
Changes since the original posting:
- new patch in this version, split from
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.
Signed-off-by: Sergei
Hello.
On 04/09/2013 01:26 AM, 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
On 04/09/2013 01:51 AM, Sergei Shtylyov wrote:
Hello.
On 04/09/2013 01:26 AM, 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
On Tue, Apr 09, 2013 at 01:51:08AM +0400, Sergei Shtylyov wrote:
Hello.
On 04/09/2013 01:26 AM, 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
The following changes since commit 505bdbc79d20f8f2a56c02498f079bb23b0ef756:
USB: driver.c: processing failure, maching resume condition with suspend
condition (2013-04-01 12:32:43 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git
From: David Howells dhowe...@redhat.com
Use ilog2() rather than __ffs() for calculating SEGMENT_SHIFT as ilog2() can
be worked out at compile time, whereas __ffs() must be calculated at runtime.
Signed-off-by: David Howells dhowe...@redhat.com
cc: Sarah Sharp sarah.a.sh...@linux.intel.com
cc:
From: David Howells dhowe...@redhat.com
Rename SEGMENT_SIZE and SEGMENT_SHIFT as the former is used in a.out.h.
Signed-off-by: David Howells dhowe...@redhat.com
cc: Sarah Sharp sarah.a.sh...@linux.intel.com
cc: Greg Kroah-Hartman gre...@linuxfoundation.org
cc: linux-usb@vger.kernel.org
From: Tony Camuso tcam...@redhat.com
There are no functional changes in this patch. However, because the
compliance mode timer can be deleted in more than one function, it
seemed expedient to include the function name in the debug strings.
Also limited the use of capitals to the first word in
Hello.
On 04/09/2013 02:07 AM, 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
On Thu, Apr 04, 2013 at 08:31:26PM +0400, Vladimir Murzin wrote:
Commits
9574323 xHCI: test USB2 software LPM
b92cc66 xHCI: add aborting command ring function
introduce useful functions which involves lists manipulations.
If for whatever reason we fall into fail path in
The Linux xHCI driver relies on the USB core for setup. You really
don't want to attempt to to separate the two. You can't get just
interrupts for transfers either -- you need to do a lot of xHCI host
setup before you can even send a control transfer to the device (which
is necessary to find out
Hi Jean-Philippe,
On Monday 08 April 2013 14:08:09 jean-philippe francois wrote:
2013/4/8 Laurent Pinchart laurent.pinch...@ideasonboard.com:
On Wednesday 06 March 2013 14:21:14 jean-philippe francois wrote:
Hi,
The company I work for is doing USB cameras, for which I wrote the
On Mon, Apr 08, 2013 at 03:53:19PM -0700, Sarah Sharp wrote:
On Thu, Apr 04, 2013 at 08:31:26PM +0400, Vladimir Murzin wrote:
Commits
9574323 xHCI: test USB2 software LPM
b92cc66 xHCI: add aborting command ring function
introduce useful functions which involves lists
On Tue, Apr 09, 2013 at 02:04:56AM +0400, Sergei Shtylyov wrote:
On 04/09/2013 01:51 AM, Sergei Shtylyov wrote:
Hello.
On 04/09/2013 01:26 AM, Greg KH wrote:
Sometimes there is a need to initialize some non-standard
registers mapped to
the EHCI region before accessing the standard
On Mon, Apr 08, 2013 at 03:09:04PM -0700, Sarah Sharp wrote:
The following changes since commit 505bdbc79d20f8f2a56c02498f079bb23b0ef756:
USB: driver.c: processing failure, maching resume condition with suspend
condition (2013-04-01 12:32:43 -0700)
are available in the git repository
Hi Mylene,
On Mon, Apr 8, 2013 at 10:41 AM, Mylene Josserand
mylene.josser...@navocap.com wrote:
Hi everyone,
I need some help to understand how USB is configured.
I am updating an old kernel (2.6.32 !) to the version 3.8.2. I am
self-taught on Linux kernel so, sometimes, I need the help
When CONFIG_XHCI_HCD_DEBUGGING is activated, the XHCI driver can dump
device and input contexts to the console. The endpoint contexts in that
dump are labeled Endpoint N Context, where N is the XHCI endpoint
index (DCI - 1). This can be very confusing, especially for people who
are not that
On Tue, Apr 09, 2013 at 09:23:08AM +0800, li.ru...@zte.com.cn wrote:
Dear Greg,
No need, this information only let your know what kernel and source path
name i have used.
I do not need that, you should always send me a patch against the latest
development kernel version, I can't do
On Tue, Apr 09, 2013 at 10:22:17AM +0800, li.ru...@zte.com.cn wrote:
Hi，
I give your the patch is base on the kernel：
linux-next: next-20130405
when 2013-04-07
Now it up to next-20130408
Again, I do not need to know that at all. Do you see others sending
patches
Hi Felipe,
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
Unfortunately the very first part of the crash has scrolled off
Hello Sarah,
Thanks a lot for the information. For your information i am successfully
able to enumerate USB device(USB keyboard) over XHCI port by the help of
XHCI Stack patch provided in u-boot and also able to do BULK transfer
over Mass storage device.
After successfully able to do CONTROL and
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 kernel already, but no USB ones that
I know
Hi
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 arch/arm/mach-shmobile/ and drivers/usb/
84 matches
Mail list logo
