On Tue, Oct 22, 2013 at 01:58:36PM +0800, Peter Chen wrote:
The mxs-phy has three versions until now, each versions have
some differences among PHY operations. the 1st version is
for mx23/mx28 SoC, The 2nd version is for mx6q and mx6dl, the
3rd version is for mx6sl and later mx6 platform.
On Tue, Oct 22, 2013 at 01:58:44PM +0800, Peter Chen wrote:
This property is used to disconnect line between USB PHY and
USB controller.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
Documentation/devicetree/bindings/usb/mxs-phy.txt |4
1 files changed, 4 insertions(+),
On Wed, Oct 23, 2013 at 01:56:00PM +0800, Shawn Guo wrote:
On Tue, Oct 22, 2013 at 01:58:35PM +0800, Peter Chen wrote:
Since there are three mxs PHY versions, using three compatible
strings for them.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
On Tue, Oct 22, 2013 at 01:58:47PM +0800, Peter Chen wrote:
When we need the PHY can be waken up by external signals,
we can call this API. Besides, we call mxs_phy_disconnect_line
at this API to close the connection between USB PHY and
controller, after that, the line state from controller is
On Wed, Oct 23, 2013 at 02:13:24PM +0800, Shawn Guo wrote:
+
+enum imx_phy_type {
+ IMX6Q_USB_PHY,
+ IMX6SL_USB_PHY,
+ IMX23_USB_PHY,
+};
+
struct mxs_phy {
struct usb_phy phy;
struct clk *clk;
+ enum imx_phy_type devtype;
};
-#define to_mxs_phy(p)
On Wed, Oct 23, 2013 at 02:31:56PM +0800, Shawn Guo wrote:
On Tue, Oct 22, 2013 at 01:58:44PM +0800, Peter Chen wrote:
This property is used to disconnect line between USB PHY and
USB controller.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
On Wed, Oct 23, 2013 at 02:35:23PM +0800, Shawn Guo wrote:
+static void mxs_phy_disconnect_line(struct mxs_phy *mxs_phy, bool on)
+{
+ void __iomem *base = mxs_phy-phy.io_priv;
+ bool vbus_is_on = false;
+ static bool line_is_disconnected;
+ unsigned int vbus_value = 0;
+
Hi Sarah,
On Fri, Oct 11, 2013 at 05:43:49AM +0800, Sarah Sharp wrote:
Hi Sipter and Marcus,
Xenia has a potential fix for a long-standing bug in the xHCI driver,
and I need your help testing it. You ran into that bug back in Feb
2013:
On Wed, Oct 23, 2013 at 02:31:56PM +0800, Shawn Guo wrote:
On Tue, Oct 22, 2013 at 01:58:44PM +0800, Peter Chen wrote:
This property is used to disconnect line between USB PHY and
USB controller.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
On 22 October 2013 11:44, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Oct 21, 2013 at 07:23:11AM -0500, Felipe Balbi wrote:
Hi,
On Sat, Oct 19, 2013 at 02:17:52PM -0700, Greg KH wrote:
On Thu, Oct 17, 2013 at 01:55:02PM +0530, Sachin Kamat wrote:
'of_match_ptr' is defined in
On Wed, Oct 23, 2013 at 03:08:25PM +0800, Peter Chen wrote:
One more thing: it is a SoC feature, so I can delete it from DT, and
using compatible string (or of_device_id.data) to judge if it is needed
at driver, do you think so?
That's exactly my point - it's not a thing belonging to device
According to Freescale imx28 Errata, ENGR119653 USB: ARM to USB
register error issue, All USB register write operations must
use the ARM SWP instruction. So, we implement special hw_write
and hw_test_and_clear for imx28.
Discussion for it at below:
According to Freescale imx28 Errata, ENGR119653 USB: ARM to USB
register error issue, All USB register write operations must
use the ARM SWP instruction. So, we implement a special ehci_write
for imx28.
Discussion for it at below:
http://marc.info/?l=linux-usbm=137996395529294w=2
Signed-off-by:
Due to imx28 needs ARM swp instruction for writing, we set
CI_HDRC_IMX28_WRITE_FIX for imx28.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/ci_hdrc_imx.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c
On Wed, Oct 23, 2013 at 02:46:04PM +0800, Peter Chen wrote:
How about compare compatible string directly at probe?
if (of_device_is_compatible(np, fsl,imx6q-usbphy))
mxs_phy-devtype = IMX6Q_USB_PHY;
else if ((of_device_is_compatible(np, fsl,imx6sl-usbphy))
When CONFIG_NOP_USB_XCEIV is as 'm', usb_nop_xceiv_register() will be
exported when the related module is loaded. So for built-in source
code, still need use the empty one.
Or it will can not pass compiling, the related error (for arm, with
allmodconfig):
arch/arm/mach-omap2/built-in.o: In
Hi,
in USB gadget menu (that is Device Drivers --- USB support --- USB
Gadget Support --- USB Gadget Drivers) I can create a configuration
which is lost. Here is how to reproduce it:
- first config two gadgets as M:
M USB Gadget Drivers
M Audio Gadget
M Ethernet Gadget
M MIDI
Sebastian, All,
On 2013-10-23 12:51 +0200, Sebastian Andrzej Siewior spake thusly:
Hi,
in USB gadget menu (that is Device Drivers --- USB support --- USB
Gadget Support --- USB Gadget Drivers) I can create a configuration
which is lost. Here is how to reproduce it:
- first config two
On 10/23/2013 01:23 PM, Yann E. MORIN wrote:
Sebastian, All,
Hi Yann,
So, I've tried your tests here, and indeed it does not behave as
expected. Yet, I can observe a slight deviation from your observations:
the third time I enter the USB Gadget Support sub-menu, the USB
Gadget Drivers
Hi Peter,
On Wed, Oct 23, 2013 at 6:35 AM, Peter Chen peter.c...@freescale.com wrote:
According to Freescale imx28 Errata, ENGR119653 USB: ARM to USB
register error issue, All USB register write operations must
use the ARM SWP instruction. So, we implement a special ehci_write
for imx28.
USB function's configfs config group is created in a generic way in
usb/gadget/configfs.c:function_make(), which in turn delegates actual
allocation and setup of the USB function instance to a particular
implementation, e.g. in f_acm.c. The said implementation does its job
in a parameter-less
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmim Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_ecm.c | 73 +-
A header file to be used by f_fs.c and g_ffs.c will be required when
f_fs.c is converted into a module.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_fs.c |1 +
drivers/usb/gadget/g_ffs.c | 19
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_subset.c | 60 +
Since d6a0143985489e470a118605352f4b18df0ce142
usb: gadget: move the global the_dev variable to their users
the_dev variable can be used as a setup done flag; non-NULL
meaning setup done, NULL meaning setup not done. Moreover,
gether_cleanup() can be safely called with a NULL argument.
Corrected
There is a new function interface of f_subset and g_ffs is the last to use
the old one.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 69
The rndis function's users use only the new interface, so the two modules
can be merged.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |7 ---
drivers/usb/gadget/Makefile |4 +---
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_rndis.c | 72 +-
This will be required in order to use the new function interface
(usb_get_function_instance/usb_put_function_instance)
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyunmgin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_fs.c | 41
From: Mark Charlebois charl...@gmail.com
The use of variable length arrays in structs (VLAIS) in the Linux Kernel code
precludes the use of compilers which don't implement VLAIS (for instance the
Clang compiler). This alternate patch calculates offsets into the kmalloc-ed
memory buffer using
There is a new funtion interface and g_ffs is the last gadget to use the old.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 94
There is a new interface of f_rndis and g_ffs is the last to use the old one.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 105
Prepare for configfs integration. Use the new interface so that f_fs can be
made a module.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 138
There are no old function interface users left, so the old interface can
be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_fs.c | 148 +---
Add support for using FunctionFS in configfs-based USB gadgets.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
Documentation/ABI/testing/configfs-usb-gadget-ffs |9 ++
drivers/usb/gadget/f_fs.c |
This is required in order to integrate configfs support.
f_fs needs to be a separately compiled module and so it needs to use the new
interface.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |
On Wed, Oct 23, 2013 at 02:06:31PM +0530, Sachin Kamat wrote:
On 22 October 2013 11:44, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Oct 21, 2013 at 07:23:11AM -0500, Felipe Balbi wrote:
Hi,
On Sat, Oct 19, 2013 at 02:17:52PM -0700, Greg KH wrote:
On Thu, Oct 17, 2013 at
Add a driver which supports the following Moxa USB to serial converters:
* 2 ports : UPort 1250, UPort 1250I
* 4 ports : UPort 1410, UPort 1450, UPort 1450I
* 8 ports : UPort 1610-8, UPort 1650-8
* 16 ports : UPort 1610-16, UPort 1650-16
The UPORT devices don't directy fit
Su contraseña caducará en 3 días formulario llenar y enviar de inmediato para
validar su dirección de e-mail.
Nombre de Usuario: .
Contraseña anterior: .
Nueva Contraseña:
gracias
administrador del sistema
--
To unsubscribe from this list: send the
On Tue, 22 Oct 2013, Jack Pham wrote:
From: Hemant Kumar hema...@codeaurora.org
USB control transfers can contain an optional IN data stage, in which
case the xHCI driver would queue an additional TRB. The interrupt on
short packet (ISP) bit is set so that the host controller driver can
On Tue, 22 Oct 2013, Prasad Koya wrote:
Hi
I have a USB subsystem question. If there is a specific mailing list for
USB queries I could post it there.
The specific mailing list for USB queries is
linux-usb@vger.kernel.org. It's listed in the kernel's MAINTAINERS
file.
I'm seeing this
On Wed, 23 Oct 2013, Peter Chen wrote:
According to Freescale imx28 Errata, ENGR119653 USB: ARM to USB
register error issue, All USB register write operations must
use the ARM SWP instruction. So, we implement a special ehci_write
for imx28.
Discussion for it at below:
On Tue, Oct 22, 2013 at 04:38:52PM -0500, Rob Herring wrote:
On 10/22/2013 06:25 AM, Matt Porter wrote:
On Tue, Oct 22, 2013 at 12:48:29PM +0200, Matthijs Kooijman wrote:
Hi Kishon,
On Mon, Oct 21, 2013 at 02:57:26PM +0530, Kishon Vijay Abraham I wrote:
I think it makes sense to keep
On Tue, 22 Oct 2013, Peter Chen wrote:
For chipidea controller, it does not follow ehci spec strictly.
Taking resume signal as an example, it will stop resume signal about
20-21ms later automatically, but standard ehci spec says, the resume
signal is controlled by software (clear
On Tue, 22 Oct 2013, Peter Chen wrote:
When the port goes to suspend or finishes resme, it needs to
notify PHY, it is not a standard EHCI operation, so we add a
quirk for it.
Actually, this _should_ be a standard EHCI operation. But we have to
figure out a way to do it that will work on all
On Tue, 22 Oct 2013, Peter Chen wrote:
Hi Alan,
Currently, the controller's wakeup setting is enabled by default,
is it ok let it be disabled by default, and let the user control it.
Enable usb wakeup will cause more power consumption(some phy logic
need to be on to detect wakeup) and
Hi,
On Wed, Oct 23, 2013 at 10:46:09AM -0400, Alan Stern wrote:
On Tue, 22 Oct 2013, Peter Chen wrote:
When the port goes to suspend or finishes resme, it needs to
notify PHY, it is not a standard EHCI operation, so we add a
quirk for it.
Actually, this _should_ be a standard EHCI
Hi,
On Wed, Oct 23, 2013 at 10:42:42AM -0400, Matt Porter wrote:
On Tue, Oct 22, 2013 at 04:38:52PM -0500, Rob Herring wrote:
On 10/22/2013 06:25 AM, Matt Porter wrote:
On Tue, Oct 22, 2013 at 12:48:29PM +0200, Matthijs Kooijman wrote:
Hi Kishon,
On Mon, Oct 21, 2013 at 02:57:26PM
On Wed, 23 Oct 2013, Felipe Balbi wrote:
Hi,
On Wed, Oct 23, 2013 at 10:46:09AM -0400, Alan Stern wrote:
On Tue, 22 Oct 2013, Peter Chen wrote:
When the port goes to suspend or finishes resme, it needs to
notify PHY, it is not a standard EHCI operation, so we add a
quirk for it.
This patch set contains a few enhancements to isochronous support in
the HWA which improve audio quality for wireless USB audio devices.
These have been sitting in my testing branch for a few weeks and look
to be solid.
Thomas Pugliese (4):
usb: wusbcore: set the RPIPE wMaxPacketSize value
Combine multiple isoc frames in a single transfer request. This allows
the HWA to take advantage of bursting to deliver data to endpoints
whose logical service interval is less than the minimum wireless USB
service interval of 4ms. Wireless audio quality is much improved after
this update.
change WA_SEGS_MAX to a number that is legal according to the WUSB
spec.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/usb/wusbcore/wa-xfer.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/wusbcore/wa-xfer.c
Add a quirk for Alereon HWA devices to concatenate the frames of isoc
transfer requests.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/usb/host/hwa-hc.c | 13 ---
drivers/usb/wusbcore/wa-hc.c |4 +++-
drivers/usb/wusbcore/wa-hc.h | 13 ++-
For isochronous endpoints, set the RPIPE wMaxPacketSize value using
wOverTheAirPacketSize from the endpoint companion descriptor instead of
wMaxPacketSize from the normal endpoint descriptor.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/usb/wusbcore/wa-rpipe.c |5
On Wed, Oct 23, 2013 at 01:11:15PM -0500, Felipe Balbi wrote:
Hi,
On Wed, Oct 23, 2013 at 10:42:42AM -0400, Matt Porter wrote:
On Tue, Oct 22, 2013 at 04:38:52PM -0500, Rob Herring wrote:
On 10/22/2013 06:25 AM, Matt Porter wrote:
On Tue, Oct 22, 2013 at 12:48:29PM +0200, Matthijs
Hi,
I have some news about this device. Under Windows 8.1 (6.3)(testversion)
with these IDs:
USB\VID_12D1PID_1F16REV_0102MI_00
USB\VID_12D1PID_1F16MI_00
USB\Class_02SubClass_0eProt_00
USB\Class_02SubClass_0e
USB\Class_02
the device works as mobile broadband device with IPv6.
So I think the
Hello.
On 10/23/2013 11:44 PM, Thomas Pugliese wrote:
For isochronous endpoints, set the RPIPE wMaxPacketSize value using
wOverTheAirPacketSize from the endpoint companion descriptor instead of
wMaxPacketSize from the normal endpoint descriptor.
Signed-off-by: Thomas Pugliese
From: Matt Porter [mailto:matt.por...@linaro.org]
Sent: Wednesday, October 23, 2013 7:43 AM
On Tue, Oct 22, 2013 at 04:38:52PM -0500, Rob Herring wrote:
On 10/22/2013 06:25 AM, Matt Porter wrote:
On Tue, Oct 22, 2013 at 12:48:29PM +0200, Matthijs Kooijman wrote:
Hi Kishon,
On
On Wed, 2013-10-23 at 22:56 +0200, Thomas Schäfer wrote:
Hi,
I have some news about this device. Under Windows 8.1 (6.3)(testversion)
with these IDs:
USB\VID_12D1PID_1F16REV_0102MI_00
USB\VID_12D1PID_1F16MI_00
USB\Class_02SubClass_0eProt_00
USB\Class_02SubClass_0e
USB\Class_02
On Wed, Oct 23, 2013 at 10:09:39AM -0200, Fabio Estevam wrote:
Hi Peter,
On Wed, Oct 23, 2013 at 6:35 AM, Peter Chen peter.c...@freescale.com wrote:
According to Freescale imx28 Errata, ENGR119653 USB: ARM to USB
register error issue, All USB register write operations must
use the ARM
On Wed, Oct 23, 2013 at 10:42:58AM -0400, Alan Stern wrote:
On Tue, 22 Oct 2013, Peter Chen wrote:
For chipidea controller, it does not follow ehci spec strictly.
Taking resume signal as an example, it will stop resume signal about
20-21ms later automatically, but standard ehci spec says,
On Wed, Oct 23, 2013 at 02:45:39PM -0400, Alan Stern wrote:
On Wed, 23 Oct 2013, Felipe Balbi wrote:
Hi,
On Wed, Oct 23, 2013 at 10:46:09AM -0400, Alan Stern wrote:
On Tue, 22 Oct 2013, Peter Chen wrote:
When the port goes to suspend or finishes resme, it needs to
notify
This patch removes limitation when only one PHY of specific type
could be used.
Signed-off-by: Anton Tikhomirov av.tikhomi...@samsung.com
---
drivers/usb/phy/phy-samsung-usb2.c |3 ++-
drivers/usb/phy/phy-samsung-usb3.c |3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git
Hi,
On Wednesday 23 October 2013 08:12 PM, Matt Porter wrote:
On Tue, Oct 22, 2013 at 04:38:52PM -0500, Rob Herring wrote:
On 10/22/2013 06:25 AM, Matt Porter wrote:
On Tue, Oct 22, 2013 at 12:48:29PM +0200, Matthijs Kooijman wrote:
Hi Kishon,
On Mon, Oct 21, 2013 at 02:57:26PM +0530,
On Wed, Oct 23, 2013 at 10:55:08AM -0400, Alan Stern wrote:
On Tue, 22 Oct 2013, Peter Chen wrote:
Hi Alan,
Currently, the controller's wakeup setting is enabled by default,
is it ok let it be disabled by default, and let the user control it.
Enable usb wakeup will cause more power
Hi,
Peter Chen wrote:
For chipidea controller, it does not follow ehci spec strictly.
Taking resume signal as an example, it will stop resume signal about
20-21ms later automatically, but standard ehci spec says, the resume
signal is controlled by software (clear portsc.PORT_RESUME).
This
66 matches
Mail list logo
