Hi
Thank you very much for the attention and support.
Unfortunately I made a mistake, when I send data to the device, I
expected that the device will send an answer for me, while I should
read the response from the device.
Thanks a lot
M.Razavi
2013/6/11 Greg KH gre...@linuxfoundation.org:
On
Hi Mike,
On Tuesday 11 of June 2013 19:54:51 Mike Turquette wrote:
Quoting Tomasz Figa (2013-06-05 16:57:26)
This patch adds new, Common Clock Framework-based clock driver for
Samsung S3C64xx SoCs. The driver is just added, without actually
letting the platforms use it yet, since this
On Wed, Jun 12, 2013 at 10:43 AM, Ming Lei ming@canonical.com wrote:
On Wed, Jun 12, 2013 at 3:10 AM, Alan Stern st...@rowland.harvard.edu wrote:
I don't follow your reasoning. Consider the following situation, where
the same spinlock is used in both a URB completion handler and an
Hi Chanwoo Choi,
On Wednesday 12 June 2013 07:09 AM, Chanwoo Choi wrote:
From: Kishon Vijay Abraham I kis...@ti.com
Added an API of_extcon_get_extcon_dev() to be used by drivers to get
extcon device in the case of dt boot (this can be used instead of
extcon_get_extcon_dev()).
Signed-off-by:
+
+ res = platform_get_resource_byname(pdev, IORESOURCE_MEM, phy_wkup);
+ phy-phy_wkup = ioremap(res-start, resource_size(res));
devm_ioremap?
The phy_wakeup register is common across two instances of phy,
devm_ioremap_resource() will fail to map for twice for same register space.
Typo.. corrected
The /proc/iomem does not show this common register
-Original Message-
From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-ow...@vger.kernel.org]
On Behalf Of B, Ravi
Sent: Wednesday, June 12, 2013 12:51 PM
To: Sergei Shtylyov
Cc: ABRAHAM, KISHON VIJAY;
On Wed, 12 Jun 2013, Ming Lei wrote:
On Wed, Jun 12, 2013 at 3:10 AM, Alan Stern st...@rowland.harvard.edu wrote:
Also the tasklet running in CPU0 can handle the work which should
have been done by the same tasket scheduled in CPU1, so we can
avoid busy-waitting in CPU1 which may be
On Tuesday 11 June 2013 15:10:03 Alan Stern wrote:
In order to prevent this from happening, you would have to change the
spin_lock() call in the completion handler to spin_lock_irqsave().
Furthermore, you will have to audit every USB driver to make sure that
all the completion handlers get
This patch Initializes the register offset values depending
on the X_MAJOR of USBOTGSS_REVISION register. Also adds register
offset defines and new debug register defines.
X_MAJOR is 2 for both OMAP5 and AM437x. But both have different glue register
layout. Differentiate AM437x using dt
This patch adds wrappers to dwc3_omap_readl/writel calls to accomodate
both OMAP5 and AM437x reg maps (It uses the cached register offsets).
Also renames OMAP5 IRQ1 as IRQMISC and IRQ1 bits as IRQMISC bits.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c |
AM437x and OMAP5 dwc3 subsytem have different register map.
Major differences are as follows.
OMAP5 has one main interrupt and one misc interrupt
Aegis has four main interrupts and one misc interrupt.
Miscellanous Interrupt offsets are changed.
UTMI OTG Control and Status Registers offsets are
Initial patch set to add support for dwc3 in am437x platform.
This patch series addresses the regiter map differences between
OMAP5 and AM437x, to re-use the same driver.
AM437x and OMAP5 dwc3 subsytem have different register map.
Major differences are as follows.
OMAP5 has one main interrupt
On Wed, Jun 12, 2013 at 5:11 PM, Oliver Neukum oli...@neukum.org wrote:
On Tuesday 11 June 2013 15:10:03 Alan Stern wrote:
In order to prevent this from happening, you would have to change the
spin_lock() call in the completion handler to spin_lock_irqsave().
Furthermore, you will have to
On Wednesday 12 June 2013 18:11:34 Ming Lei wrote:
On Wed, Jun 12, 2013 at 5:11 PM, Oliver Neukum oli...@neukum.org wrote:
On Tuesday 11 June 2013 15:10:03 Alan Stern wrote:
In order to prevent this from happening, you would have to change the
spin_lock() call in the completion handler to
On Thu, May 30, 2013 at 11:19:33PM +0200, Linus Walleij wrote:
On Thu, May 30, 2013 at 10:31 PM, Tony Lindgren t...@atomide.com wrote:
There are many devices where the device FIFO is memory mapped to the
GPMC bus on omaps, like TUSB, OneNAND, smc911x etc. I believe the
only reason why
a37025b USB: ftdi_sio: fix chars_in_buffer overhead
c413364 USB: ftdi_sio: clean up get_modem_status
dcf0105 USB: serial: add generic wait_until_sent implementation
These three are also needed in 3.9 (and also 3.8).
I have these three. 3.8-stable is dead as far as I'm concerned,
On Wed, Jun 12, 2013 at 6:19 PM, Oliver Neukum oli...@neukum.org wrote:
On Wednesday 12 June 2013 18:11:34 Ming Lei wrote:
On Wed, Jun 12, 2013 at 5:11 PM, Oliver Neukum oli...@neukum.org wrote:
On Tuesday 11 June 2013 15:10:03 Alan Stern wrote:
In order to prevent this from happening, you
Hi,
The usbmon trace shows lots of errors. All those -75 (EOVERFLOW)
status codes mean that the gadget sent a packet that was too large,
i.e., more than 512 bytes. This happened in all the READ(10) commands
except the last one -- none of them succeeded in transferring any data.
After the
On 12 June 2013 15:35, Vinod Koul vinod.k...@intel.com wrote:
On Thu, May 30, 2013 at 11:19:33PM +0200, Linus Walleij wrote:
On Thu, May 30, 2013 at 10:31 PM, Tony Lindgren t...@atomide.com wrote:
There are many devices where the device FIFO is memory mapped to the
GPMC bus on omaps, like
On Sun, Jun 9, 2013 at 6:25 AM, Barry Song 21cn...@gmail.com wrote:
CSR SiRF SoCs licensed chipidea ci13xxx USB IP, this patch
makes the chipidea drivers support CSR SiRF SoCS.
It also changes the Kconfig, only compile MSM and IMX if related
drivers are enabled. Otherwise, we always need to
On Wed, 12 Jun 2013, Ming Lei wrote:
If not, I am wondering why one USB driver need register another hard
interrupt handler? Could you share such examples? I understand the
case only exists with timer handler as discussed with Oliver, don't I?
Here's another possibility. A USB driver has a
On 23:04 Thu 07 Feb , manjunath.gou...@linaro.org wrote:
From: Manjunath Goudar manjunath.gou...@linaro.org
Separate the Atmel host controller driver from ehci-hcd host code
into its own driver module.
Signed-off-by: Manjunath Goudar manjunath.gou...@linaro.org
Cc: Alan Stern
On Wed, Jun 05, 2013 at 02:03:04PM -0600, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
When this file is built as a module, it needs a MODULE_LICENSE in order
to access many exported symbols.
Signed-off-by: Stephen Warren swar...@nvidia.com
Acked-by: Arnd Bergmann
On Wed, Jun 05, 2013 at 02:03:03PM -0600, Stephen Warren wrote:
From: Manjunath Goudar manjunath.gou...@linaro.org
In order to build a ULPI PHY driver as a module, this symbol needs to
be exported.
Signed-off-by: Manjunath Goudar manjunath.gou...@linaro.org
[swarren, reworked Manjunath's
On Fri, Jun 07, 2013 at 08:08:18PM +0200, Boris BREZILLON wrote:
Replace clk_enable/disable with clk_prepare_enable/disable_unprepare to
avoid common clk framework warnings.
Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com
Acked-by: Felipe Balbi ba...@ti.com
--
balbi
signature.asc
On Wednesday 12 June 2013 10:35:44 Alan Stern wrote:
On Wed, 12 Jun 2013, Ming Lei wrote:
If not, I am wondering why one USB driver need register another hard
interrupt handler? Could you share such examples? I understand the
case only exists with timer handler as discussed with Oliver,
On Mon, Apr 29, 2013 at 12:39:56PM +0200, Andrzej Pietrasiewicz wrote:
A USB gadget can be set up entirely through configfs.
This patch adds options to build the USB functions' modules
without building old gadget modules, e.g. build
usb_f_acm.ko or usb_f_ecm.ko, but not g_cdc.ko.
Please
On Wed, 12 Jun 2013, victor yeo wrote:
I did another usbmon capture from the moment usb cable is plugged into
the Ubuntu x100e laptop. This time the usbmon does not have -75 error.
When the SCSI_READ_10 command request for 4096 bytes of data, and the
data is returned by the gadget, usbmon
Suspend scenario in case of ohci-ep93xx glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_hcd_ep93xx_drv_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci-exynos glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in exynos_ohci_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci-s3c2410 glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_hcd_s3c2410_drv_suspend() will ensure
proper handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci-da8xx glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_da8xx_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci bus glue was not properly handled as
it was not suspending generic part of ohci controller. Calling
explicitly the ohci_suspend()routine will ensure proper handling
of suspend scenario.
Manjunath Goudar (10):
USB: OHCI: Properly handle ohci-at91 suspend
Suspend scenario in case of ohci-at91 glue was not properly
handled as it was not suspending generic part of ohci controller.
Calling explicitly the ohci_suspend()routine in ohci_hcd_at91_drv_suspend()
will ensure proper handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci-omap glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_omap_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci-pxa27x glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_hcd_pxa27x_drv_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci-spear glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in spear_ohci_hcd_drv_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci-platform glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_platform_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Suspend scenario in case of ohci-sm501 glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_sm501_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Change intervall into interval.
Signed-off-by: Huang Rui ray.hu...@amd.com
---
drivers/usb/dwc3/core.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index b69d322..0fc54cc 100644
--- a/drivers/usb/dwc3/core.h
+++
Hello.
On 12-06-2013 19:28, Manjunath Goudar wrote:
Suspend scenario in case of ohci-da8xx glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_da8xx_suspend() will ensure proper
handling of suspend
These patches are for separating the SOC On-Chip ohci host controller
from ohci-hcd host code into its own driver module.
This work is part of enabling multi-platform kernels on ARM.
V2:
In patch 5/6 and 6/6:
-Set non-standard fields in hc_driver manually, rather than
relying on an
Separate the TI OHCI OMAP3 host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
it would be nice to have in 3.11.
V2:
-ohci_setup() removed because it is called in .reset member
of the
Separate the TI OHCI OMAP1/2 host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
it would be nice to have in 3.11.
V2:
-omap_ohci_clock_power(0) called in usb_hcd_omap_remove().
Separate the Samsung OHCI S3C host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
it would be nice to have in 3.11.
V2:
-Set non-standard fields in ohci_s3c2410_hc_driver manually,
Separate the TI OHCI Atmel host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
it would be nice to have in 3.11.
V2:
-Set non-standard fields in ohci_at91_hc_driver manually, rather than
Separate the Samsung OHCI EXYNOS host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
it would be nice to have in 3.11.
V2:
-exynos_ohci_hcd structure assignment error fixed.
-Removed
Hello.
On 12-06-2013 19:28, Manjunath Goudar wrote:
Suspend scenario in case of ohci-s3c2410 glue was not
properly handled as it was not suspending generic part
of ohci controller.Calling explicitly the ohci_suspend()
routine in ohci_hcd_s3c2410_drv_suspend() will ensure
proper handling of
On Wed, 12 Jun 2013, Manjunath Goudar wrote:
Suspend scenario in case of ohci-at91 glue was not properly
handled as it was not suspending generic part of ohci controller.
Calling explicitly the ohci_suspend()routine in ohci_hcd_at91_drv_suspend()
will ensure proper handling of suspend
On 06/12/2013 09:06 AM, Felipe Balbi wrote:
On Wed, Jun 05, 2013 at 02:03:03PM -0600, Stephen Warren wrote:
From: Manjunath Goudar manjunath.gou...@linaro.org
In order to build a ULPI PHY driver as a module, this symbol
needs to be exported.
Signed-off-by: Manjunath Goudar
Make the Linux xHCI driver automatically try to switchover the EHCI ports to
xHCI when an Intel xHCI host is detected, and it also finds an Intel EHCI host.
This means we will no longer have to add Intel xHCI hosts to a quirks list when
the PCI device IDs change. Simply continuing to add new
Hi Greg,
Here's my pull request for v3.11 merge window. It's rather
large. Let me know if you want any changes.
cheers
The following changes since commit e4aa937ec75df0eea0bee03bffa3303ad36c986b:
Linux 3.10-rc3 (2013-05-26 16:00:47 -0700)
are available in the git repository at:
On Wed, 12 Jun 2013, Alan Stern wrote:
On Wed, 12 Jun 2013, Manjunath Goudar wrote:
Suspend scenario in case of ohci-at91 glue was not properly
handled as it was not suspending generic part of ohci controller.
Calling explicitly the ohci_suspend()routine in ohci_hcd_at91_drv_suspend()
On Wed, Jun 12, 2013 at 07:11:23PM +0300, Mathias Nyman wrote:
Make the Linux xHCI driver automatically try to switchover the EHCI ports to
xHCI when an Intel xHCI host is detected, and it also finds an Intel EHCI
host.
This means we will no longer have to add Intel xHCI hosts to a quirks
On Wed, Jun 12, 2013 at 10:11:27AM -0600, Stephen Warren wrote:
On 06/12/2013 09:06 AM, Felipe Balbi wrote:
On Wed, Jun 05, 2013 at 02:03:03PM -0600, Stephen Warren wrote:
From: Manjunath Goudar manjunath.gou...@linaro.org
In order to build a ULPI PHY driver as a module, this symbol
Hi,
On Wed, Jun 12, 2013 at 10:51:05AM -0600, Stephen Warren wrote:
On 06/12/2013 10:38 AM, Felipe Balbi wrote:
On Wed, Jun 12, 2013 at 10:11:27AM -0600, Stephen Warren wrote:
On 06/12/2013 09:06 AM, Felipe Balbi wrote:
On Wed, Jun 05, 2013 at 02:03:03PM -0600, Stephen Warren
wrote:
Hi,
On Fri, Jun 07, 2013 at 03:50:17PM +0800, Huang Rui wrote:
Hi Felipe,
I was reading dwc3 codes and found that during the process of
configuring event buffer (dwc3_event_buffers_setup), it only write the
size of the buffer and doesn't write interrupt mask bit into GEVNTSIZ
register like
We are running the 2.6.28-15 kernel under Ubuntu 9.04 (I know... we are
migrating now). We see the USB communication between the kernel driver and the
USB device stop after what appears to be 0x7 microseconds, and suspect
it is a logic problem with an unsigned long rolling over. We
Am 11.06.2013 19:34, schrieb Sarah Sharp:
On Mon, Jun 10, 2013 at 08:55:56AM +0200, Oleksij Rempel wrote:
Hello all,
i'm working on usb_autosuspend for ath9k_htc and triggered this
oops. Currently i do not know if real bug is in ath9k_htc or in
xhci. Same adapter with same kernel and my
Hi,
On Wed, Jun 12, 2013 at 01:17:42PM -0700, Greg KH wrote:
On Wed, Jun 12, 2013 at 07:12:23PM +0300, Felipe Balbi wrote:
Hi Greg,
Here's my pull request for v3.11 merge window. It's rather
large. Let me know if you want any changes.
cheers
The following changes since commit
Hi,
On Wed, Jun 12, 2013 at 11:56:19PM +0300, Felipe Balbi wrote:
But, I get a build error with your tree pulled in, at the link point in
time:
ERROR: usb_add_phy [drivers/usb/phy/phy-samsung-usb3.ko] undefined!
ERROR: usb_remove_phy [drivers/usb/phy/phy-samsung-usb3.ko] undefined!
On Thu, Jun 13, 2013 at 12:19:02AM +0300, Felipe Balbi wrote:
Hi,
On Wed, Jun 12, 2013 at 11:56:19PM +0300, Felipe Balbi wrote:
But, I get a build error with your tree pulled in, at the link point in
time:
ERROR: usb_add_phy [drivers/usb/phy/phy-samsung-usb3.ko] undefined!
On Wed, Jun 12, 2013 at 06:51:00PM +, Kerry Calvert wrote:
We are running the 2.6.28-15 kernel under Ubuntu 9.04 (I know... we
are migrating now).
Then you really need to get support from Ubuntu, there's nothing we can
do here about such an old and obsolete, and really unknown kernel
On Fri, Jun 07, 2013 at 11:37:53PM +0300, Felipe Balbi wrote:
Hi,
On Fri, Jun 07, 2013 at 10:19:23AM -0700, Sarah Sharp wrote:
Adding Felipe.
Xenia, Felipe is the USB gadget maintainer, and also added code for
non-PCI xHCI hosts. Felipe, Xenia is my summer intern through the FOSS
On Wed, Jun 12, 2013 at 03:01:50PM -0700, Sarah Sharp wrote:
On Wed, Jun 12, 2013 at 09:32:58AM -0700, Greg KH wrote:
On Wed, Jun 12, 2013 at 07:11:23PM +0300, Mathias Nyman wrote:
Make the Linux xHCI driver automatically try to switchover the EHCI ports
to
xHCI when an Intel xHCI
On Wed, Jun 12, 2013 at 08:47:30PM -0400, Jérôme Poulin wrote:
In reference to this email:
http://www.spinics.net/lists/linux-usb/msg78711.html
I have exactly the same stack dump with different words, null pointer
dereference.
Plugging a USB3 external disk and using ddrescue will cause
Hi,
On Wed, Jun 12, 2013 at 03:37:00PM -0700, Greg KH wrote:
On Wed, Jun 12, 2013 at 02:31:17PM -0700, Greg KH wrote:
On Thu, Jun 13, 2013 at 12:19:02AM +0300, Felipe Balbi wrote:
Hi,
On Wed, Jun 12, 2013 at 11:56:19PM +0300, Felipe Balbi wrote:
But, I get a build error with
On Fri, May 31, 2013 at 02:29:01PM +0300, Roger Quadros wrote:
Hi,
Improve Kconfig so that the relevant PHY driver can be explicitely
selected by the controller driver instead of relying on the user
to do so.
Detailed description in patch 1.
v2:
- Merge patches 3-5 into the first
On Wed, Jun 12, 2013 at 3:45 PM, Thomas Gleixner t...@linutronix.de wrote:
On Wed, 12 Jun 2013, Ming Lei wrote:
Yes, please. I read through the thread and I really recommend that you
get rid of the tasklet. tasklets are a complete disaster by design and
we really should make efforts to get
On Fri, 2013-06-07 at 15:14 +0200, Lotfi Manseur wrote:
Handle null termios in ftdi_set_termios(), introduced in
commit 552f6bf1bb0eda0011c0525dd587aa9e7ba5b846
This has been corrected in the mainline by
commits c515598e0f5769916c31c00392cc2bfe6af74e55 and
On Wed, Jun 12, 2013 at 10:35 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 12 Jun 2013, Ming Lei wrote:
If not, I am wondering why one USB driver need register another hard
interrupt handler? Could you share such examples? I understand the
case only exists with timer handler as
Good day, I Am Chi Pui;Do not be surprised! I got your email contact via the
World Email On-line Directory I am crediting officer at Sino Pac Bank Plc
in Hong Kong and i have a deal of $17.3M to discuss with you urgently.
Regards,
Mr.Chi Pui
--
To unsubscribe from this list: send the line
72 matches
Mail list logo
