Peter Chen (3):
usb: dwc2: gadget: fix below build warning
usb: core: fix below build warning
usb: wusbcore: fix below build warning
drivers/usb/core/hub.c |7 ---
drivers/usb/dwc2/gadget.c |2 +-
drivers/usb/wusbcore/wa-xfer.c |4 ++--
3 files changed, 7 insert
linux-2.6/drivers/usb/dwc2/gadget.c: In function 's3c_hsotg_irq_enumdone':
linux-2.6/drivers/usb/dwc2/gadget.c:1904: warning: 'ep_mps' may be used
uninitialized in this function
Signed-off-by: Peter Chen
---
drivers/usb/dwc2/gadget.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
linux-2.6/drivers/usb/wusbcore/wa-xfer.c: In function 'wa_buf_in_cb':
linux-2.6/drivers/usb/wusbcore/wa-xfer.c:2590: warning: 'rpipe' may be used
uninitialized in this function
Signed-off-by: Peter Chen
---
drivers/usb/wusbcore/wa-xfer.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions
linux-2.6/drivers/usb/core/hub.c: In function 'usb_disconnect':
linux-2.6/drivers/usb/core/hub.c:2110: warning: 'hub' may be used uninitialized
in this function
linux-2.6/drivers/usb/core/hub.c:2111: warning: 'port1' may be used
uninitialized in this function
Signed-off-by: Peter Chen
---
driv
On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
> Hi all,
>
> i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and usb_div)
> but the current chipidea driver implementation, and devicetree, provides
> only ipg and ahb. Consequently, if the bootloader don't enable the la
On Monday, August 18, 2014 5:32 PM, Peter Chen wrote:
>
> linux-2.6/drivers/usb/dwc2/gadget.c: In function 's3c_hsotg_irq_enumdone':
> linux-2.6/drivers/usb/dwc2/gadget.c:1904: warning: 'ep_mps' may be used
> uninitialized in this function
(+cc Dinh Nguyen)
I think that this warning is false.
On Wed, Aug 06, 2014 at 08:46:44AM -0700, Brennan Ashton wrote:
> This VIA Telecom baseband processor is used is used by by u-blox in both the
> FW2770 and FW2760 products and may be used in others as well.
>
> This patch has been tested on both of these modem versions.
>
> Signed-off-by: Brennan
On Fri, Aug 15, 2014 at 03:22:21PM +0800, Greg Kroah-Hartman wrote:
> This adds a new device id to the pl2303 driver for the ZTEK device.
>
> Reported-by: Mike Chu
> Cc: stable
> Signed-off-by: Greg Kroah-Hartman
Applied, thanks.
Johan
> diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb
On Mon, Aug 18, 2014 at 05:00:59PM +0800, Peter Chen wrote:
> On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
> > Hi all,
> >
> > i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and usb_div)
> > but the current chipidea driver implementation, and devicetree, provides
>
On Sat, Aug 16, 2014 at 12:44:27PM +0200, Jaša Bartelj wrote:
> Added support to the ftdi_sio driver for ekey Converter USB which
> uses an FT232BM chip.
>
> Signed-off-by: Jaša Bartelj
Applied, thanks.
Johan
> ---
> drivers/usb/serial/ftdi_sio.c | 2 ++
> drivers/usb/serial/ftdi_sio_ids.
On Mon, Aug 18, 2014 at 04:54:44AM +0200, Jaša Bartelj wrote:
> Changes two simple if statements to switch statements.
> Fixes some issues reported by checkpatch.pl like whitespace.
> Bracing changes so all arms of a statement have consistent bracing.
Please, only use checkpatch.pl on your own pat
On Sun, Aug 17, 2014 at 09:04:32AM +0800, Wang YanQing wrote:
> On Tue, Aug 12, 2014 at 04:46:25PM +0200, Johan Hovold wrote:
> > On Sat, Aug 09, 2014 at 01:28:28PM +0800, Wang YanQing wrote:
> > > PL2303 USB Serial devices always has GPIOs,
> >
> > Always? Are you sure? It's probably better to wr
On Sun, Aug 17, 2014 at 10:05:36AM +0800, Wang YanQing wrote:
> Hi Johan Hovold.
>
> Another two questions.
>
> On Tue, Aug 12, 2014 at 04:46:25PM +0200, Johan Hovold wrote:
> >
> > > + int (*gpio_startup)(struct usb_serial *serial);
> > > + void (*gpio_release)(struct usb_serial *serial);
> On Mon, Aug 18, 2014 at 05:00:59PM +0800, Peter Chen wrote:
> > On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
> > > Hi all,
> > >
> > > i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and
> > > usb_div) but the current chipidea driver implementation, and
> > > dev
Hi,
On Thursday, August 14, 2014 08:07:40 PM Vivek Gautam wrote:
> Hi Bartlomiej Zolnierkiewicz,
>
>
> On Thursday, August 14, 2014 7:55 PM, Bartlomiej Zolnierkiewicz
> wrote
>
> Subject: [PATCH 3/5] usb: phy: samsung: remove old USB 2.0 PHY driver
>
> I would say it co-incidence that both
On 18.08.2014 13:02, Bartlomiej Zolnierkiewicz wrote:
> On Thursday, August 14, 2014 08:07:40 PM Vivek Gautam wrote:
>> On Thursday, August 14, 2014 7:55 PM, Bartlomiej Zolnierkiewicz
>> wrote
>
>> There's one thing that I would want to comment here, since we don't have any
>> new usb-phy drive
Andrzej Pietrasiewicz writes:
> This series aims at integrating configfs into the audio gadget, the way
> it has been done for acm, ncm, ecm, eem, ecm subset, rndis, obex, phonet,
> mass_storage, FunctionFS, loopback, sourcesink; rfc for uvc has also been
> sent. It contains everything that is req
On Mon, Aug 18, 2014 at 06:35:53PM +0800, Chen Peter-B29397 wrote:
>
> > On Mon, Aug 18, 2014 at 05:00:59PM +0800, Peter Chen wrote:
> > > On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
> > > > Hi all,
> > > >
> > > > i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate a
> On Fri, 15 Aug 2014, Du, ChangbinX wrote:
> > If my analysis is correct, could you share your ideas for this issue?
>
> Hasn't this already been fixed? See commit d6236f6d1d88 (xhci: Fix runtime
> suspended xhci from blocking system suspend).
>
> Alan Stern
Hi, Stern,
These are two different
On Mon, 18 Aug 2014 10:35:53 +
Peter Chen wrote:
>
> > On Mon, Aug 18, 2014 at 05:00:59PM +0800, Peter Chen wrote:
> > > On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
> > > > Hi all,
> > > >
> > > > i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and
> > > > u
On Mon, 18 Aug 2014, Peter Chen wrote:
> linux-2.6/drivers/usb/core/hub.c: In function 'usb_disconnect':
> linux-2.6/drivers/usb/core/hub.c:2110: warning: 'hub' may be used
> uninitialized in this function
> linux-2.6/drivers/usb/core/hub.c:2111: warning: 'port1' may be used
> uninitialized in t
On Mon, 18 Aug 2014, Du, ChangbinX wrote:
> > On Fri, 15 Aug 2014, Du, ChangbinX wrote:
> > > If my analysis is correct, could you share your ideas for this issue?
> >
> > Hasn't this already been fixed? See commit d6236f6d1d88 (xhci: Fix runtime
> > suspended xhci from blocking system suspend).
On Mon, 18 Aug 2014, Peter Chen wrote:
> We introduce the connect API at usb_gadget_driver, the udc driver
> uses it to tell gadget driver that it is ready to CONNECT, and the
> dp can be pulled up from now on.
>
> Meanwhile, we introduce an API usb_udc_ready_to_connect to encapsulate
> above ope
On Mon, 18 Aug 2014, Peter Chen wrote:
> linux-2.6/drivers/usb/wusbcore/wa-xfer.c: In function 'wa_buf_in_cb':
> linux-2.6/drivers/usb/wusbcore/wa-xfer.c:2590: warning: 'rpipe' may be used
> uninitialized in this function
>
> Signed-off-by: Peter Chen
> ---
> drivers/usb/wusbcore/wa-xfer.c |
Hello,
I already opened a bug report for my problem here:
https://bugzilla.kernel.org/show_bug.cgi?id=82731#c1
Starting with Kernel 3.16 I get kernel Oops from time to time when
booting my desktop system.
A reset helps to bring the system up without problems.
I've attached a dmesg dump to m
Instead of building all of the xHCI code into a single module, separate
it out into the core (xhci-hcd), PCI (xhci-pci, now selected by the new
config option CONFIG_USB_XHCI_PCI), and platform (xhci-plat) drivers.
Also update the PCI/platform drivers with module descriptions/licenses
and have them
It was suggested in the review of the Tegra xHCI driver [1] that we
allow xHCI drivers to be built as individual modules (like EHCI) instead
of building them all into the single xhci-hcd module as they are today.
Patches 1-3 prepare for making the xHCI PCI and platform drivers able
to be built as
Since the struct hc_driver is mostly the same across the xhci-pci,
xhci-plat, and the upcoming xhci-tegra driver, introduce the function
xhci_init_driver() which will populate the hc_driver with the default
xHCI operations. The caller must supply a setup function which will
be used as the hc_drive
> > Do you know what the three interfaces are used for by the way? And do you
> > have any idea about whether the other products using the same PID also
> > have six bulk endpoints (three tty interfaces)?
>
> Yes. There are three [mostly] independent terminals. The older
> devices were normally
Add support for multi-port simple drivers.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/usb-serial-simple.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/serial/usb-serial-simple.c
b/drivers/usb/serial/usb-serial-simple.c
index fb79775447b0..02cb77a1
Add simple driver for Novatel Wireless GPS receivers.
Reported-by: Kirk Madsen
Signed-off-by: Johan Hovold
---
drivers/usb/serial/Kconfig | 1 +
drivers/usb/serial/usb-serial-simple.c | 7 +++
2 files changed, 8 insertions(+)
diff --git a/drivers/usb/serial/Kconfig b/drivers/us
Instead of calling xhci_compliance_mode_recovery_timer_quirk_check() again
in the PCI suspend path, just check for XHCI_COMP_MODE_QUIRK which will
have been set based on xhci_compliance_mode_recovery_timer_quirk_check()
in xhci_init().
Signed-off-by: Andrew Bresticker
---
No change from v1.
---
In preparation for allowing the xHCI host controller drivers to be built
as separate modules, export symbols from the xHCI core that may be used
by the host controller drivers.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- exported xhci_run()
---
drivers/usb/host/xhci-dbg.c | 1 +
dri
> > > Do you know what the three interfaces are used for by the way? And do you
> > > have any idea about whether the other products using the same PID also
> > > have six bulk endpoints (three tty interfaces)?
Interestingly I've a modern Asmedia motherboard for the haswell cpu that
has 5 RS232 po
Add simple driver for Medtronic CareLink USB devices.
Reported-by: Benjamin West
Tested-by: Benjamin West
Signed-off-by: Johan Hovold
---
Not sure if the enumeration issues with the xhci driver have been
solved by now, but let's add this driver anyway.
Johan
drivers/usb/serial/Kconfig
On Mon, Aug 18, 2014 at 04:21:10PM +, David Laight wrote:
> > > > Do you know what the three interfaces are used for by the way? And do
> > > > you
> > > > have any idea about whether the other products using the same PID also
> > > > have six bulk endpoints (three tty interfaces)?
>
> Intere
Add device id for NOVITUS Bono E thermal printer.
Reported-by: Emanuel Koczwara
Cc: stable
Signed-off-by: Johan Hovold
---
drivers/usb/serial/ftdi_sio.c | 1 +
drivers/usb/serial/ftdi_sio_ids.h | 6 ++
2 files changed, 7 insertions(+)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drive
Simplify ioctl handling by using video_ioctl2.
Signed-off-by: Laurent Pinchart
---
drivers/usb/gadget/function/f_uvc.c| 1 +
drivers/usb/gadget/function/uvc_v4l2.c | 298 +
2 files changed, 158 insertions(+), 141 deletions(-)
diff --git a/drivers/usb/gadget
Hello,
This small patch series replaces manual handling of V4L2 ioctls in the UVC
gadget function driver with the video_ioctl2 infrastructure. This simplifies
the driver and brings support for V4L2 tracing features.
The series is based on top of Michael Grzeschik's "usb: gadget/uvc: remove
DRIVER
To handle class requests received on ep0, the driver needs to access the
length and direction of the request after the setup stage. It currently
stores them in a v4l2 event during the setup stage, and then copies them
from the event structure to the driver internal state structure when the
event is
In addition to the PCIe and SATA PHYs, the XUSB pad controller also
supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a single
PCIe or SATA lane and is mapped to one of the three UTMI ports.
The xHCI controller will also send messages intended for the PHY driver,
so request and listen
Add device-tree binding documentation for the xHCI controller present
on Tegra124 and later SoCs.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- Updated to use common mailbox bindings.
- Added remaining XUSB-related clocks and resets.
- Updated list of power supplies to be more accura
Assign ports previously owned by the EHCI controllers to the xHCI
controller. There are two external USB ports (UTMI ports 0/2 and
USB3 ports 0/1) and an internal USB port (UTMI port 1). PCIe lanes
0 and 1 are used by the USB3 ports.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- Upda
The Tegra xHCI controller's firmware communicates requests to the host
processor through a mailbox interface. While there is only a single
communication channel, messages sent by the controller can be divided
into two groups: those intended for the PHY driver and those intended
for the host-contro
Add new bindings used for USB support by the Tegra XUSB pad controller.
This includes additional PHY types, USB-specific pinconfig properties, etc.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- Updated to use common mailbox bindings.
- Made USB3 port-to-lane mappins a top-level bindin
Add device-tree bindings for the Tegra XUSB mailbox which will be used
for communication between the Tegra xHCI controller's firmware and the
host processor.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- Updated to use common mailbox bindings.
---
.../bindings/mailbox/nvidia,tegra124-
Add support for the on-chip xHCI host controller present on Tegra SoCs.
The driver is currently very basic: it loads the controller with its
firmware, starts the controller, and is able to service messages sent
by the controller's firmware. The hardware supports device mode as
well as lower-power
On 08/15/2014 05:49 AM, Xuebing Wang wrote:
> Jassi, thanks for your help.
>
> Without knowing what is the best way to implement UAC2 at the device
> side, I managed to simply pipe is as below:
>
> Note: When I am playing music from Ubuntu host, I can hear light noise
> from the device (via UAC
This series adds support for xHCI on NVIDIA Tegra SoCs. This includes:
- adding a driver for the mailbox used to communicate with the xHCI
controller's firmware,
- extending the XUSB pad controller driver to support the USB PHY
types (UTMI, HSIC, and USB3), and
- adding a xHCI host-contro
Add nodes for the Tegra XUSB mailbox and Tegra xHCI controller and
add the PHY mailbox channel to the XUSB padctl node.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- Updated to use common mailbox bindings.
- Added remaining clocks/resets.
---
arch/arm/boot/dts/tegra124.dtsi | 40
Assign USB ports previously owned by the EHCI controllers to the xHCI
controller. There is a mini-PCIe USB port (UTMI port 1) and a USB A
connector (UTMI port 2, USB3 port 0). PCIe lane 0 is used for USB3
port 0.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- Updated USB power supplie
On 08/18/2014 11:08 AM, Andrew Bresticker wrote:
This series adds support for xHCI on NVIDIA Tegra SoCs. This includes:
- adding a driver for the mailbox used to communicate with the xHCI
controller's firmware,
- extending the XUSB pad controller driver to support the USB PHY
types (
Hi. was told to forward my bug-report here.
The issue in short:
When connecting the mouse in USB 3.0 the mouse wont have higher
polling rate than 125Hz and will behave erratic in Witcher 2.
More details is on the kernel Bugzilla.
https://bugzilla.kernel.org/show_bug.cgi?id=82571
Best Regards
Art
> From: Jingoo Han [mailto:jg1@samsung.com]
> Sent: Monday, August 18, 2014 2:17 AM
>
> On Monday, August 18, 2014 5:32 PM, Peter Chen wrote:
> >
> > linux-2.6/drivers/usb/dwc2/gadget.c: In function 's3c_hsotg_irq_enumdone':
> > linux-2.6/drivers/usb/dwc2/gadget.c:1904: warning: 'ep_mps' may b
On Mon, 18 Aug 2014, Commander wrote:
> Hi. was told to forward my bug-report here.
>
> The issue in short:
> When connecting the mouse in USB 3.0 the mouse wont have higher
> polling rate than 125Hz and will behave erratic in Witcher 2.
>
> More details is on the kernel Bugzilla.
> https://bugz
On 08/18/2014 05:06 PM, Laurent Pinchart wrote:
> Simplify ioctl handling by using video_ioctl2.
Are you able to test this on actual hardware? And if so, can you run
v4l2-compliance?
Regards,
Hans
>
> Signed-off-by: Laurent Pinchart
> ---
> drivers/usb/gadget/function/f_uvc.c|
Hi Andrzej,
Thank you for the patch.
On Wednesday 16 July 2014 16:54:12 Andrzej Pietrasiewicz wrote:
> Prepare for separate compilation of uvc function's components.
> Some symbols will have to be exported, so rename to avoid
> conflicts with functions of the same name in host uvc.
>
> Signed-of
Hi Andrzej,
Thank you for the patch.
On Wednesday 16 July 2014 16:54:11 Andrzej Pietrasiewicz wrote:
> When configfs support is integrated the future uvc function
> module must not take any parameters. Move parameters to
> webcam.
>
> Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Laurent Pinc
Hi Andrzej,
Thank you for the patch.
On Wednesday 16 July 2014 16:54:13 Andrzej Pietrasiewicz wrote:
> Compile uvc_queue, uvc_v4l2, uvc_video separately so that later they can
> be all combined in a separately compiled f_uvc.
>
> Signed-off-by: Andrzej Pietrasiewicz
> ---
> drivers/usb/gadget/
Hi Andrzej,
Thank you for the patch.
On Wednesday 16 July 2014 16:54:14 Andrzej Pietrasiewicz wrote:
> Use the new function registration interface. It is required
> in order to integrate configfs support.
>
> Signed-off-by: Andrzej Pietrasiewicz
> ---
> drivers/usb/gadget/Kconfig |
On Mon, Aug 18, 2014 at 10:30 AM, Stephen Warren wrote:
> On 08/18/2014 11:08 AM, Andrew Bresticker wrote:
>>
>> This series adds support for xHCI on NVIDIA Tegra SoCs. This includes:
>> - adding a driver for the mailbox used to communicate with the xHCI
>> controller's firmware,
>> - ext
Hi Andrzej,
Thank you for the patch.
On Wednesday 16 July 2014 16:54:17 Andrzej Pietrasiewicz wrote:
> Attach strings to gadget with usb_strings_attach.
> It is required for correct instantiation of functions more than once:
> instead of modifying the local uvc_en_us_strings a function instance
>
Hi Andrzej,
Thank you for the patches. The series looks good, I only had a few comments.
I have rebased the patches on top of my UVC gadget branch, addressed my
comments (the modified patches are marked as such in the commit message) and
pushed the result to
git://linuxtv.org/pinchartl
This adds Vybrid VF610 SoC support. The IP is very similar to i.MX6,
however, the non-core registers are spread in two different register
areas. Hence we support multiple instances of the USB misc driver
and add the driver instance to the imx_usbmisc_data structure.
Signed-off-by: Stefan Agner
--
Add USB support for Freescale Vybrid tower. The USB hosts over-current
protection signal is not connected is not connected to the PHY's over-
current protection, hence we need to disable it.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vf610-twr.dts | 10 ++
1 file changed, 10 inser
This adds support for the USB PHY in Vybrid VF610. We assume that
the disconnection without VBUS is also needed for Vybrid.
Tests showed, without MXS_PHY_NEED_IP_FIX, enumeration of devices
behind a USB Hub fails with errors:
[ 215.163507] usb usb1-port1: cannot reset (err = -32)
[ 215.170498]
This patchset adds USB support for Vybrid VF610 SoC. It extends the
clock framework to support the USB PHY cocks, extends the device
tree files and adds support for the non-core registers in the
usbmisc_imx driver.
This patchset needs the eSDHC registers length fix available in
Shawn's for-next br
This commit adds PLL7 which is required for USBPHY1. It also adds
the USB PHY and USB Controller clocks and the gates to enable them.
Acked-by: Jingchang Lu
Signed-off-by: Stefan Agner
---
arch/arm/mach-imx/clk-vf610.c | 12 ++--
include/dt-bindings/clock/vf610-clock.h | 5 ++
Add device tree node for usbmisc which controls the non-core USB
registers. This is required to use the property to disable the over-
current detection.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vf610.dtsi | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git
This adds USB PHY and USB controller nodes. Vybrid SoCs have two
independent USB cores which each supports DR (dual role). However,
real OTG is not supported since the OTG ID pin is not available.
The PHYs are located within the anadig register range, hence we need
to change the length of the anad
Add USB support for Colibri VF61 modules. The Colibri standard pinout
defines a pin for USB over-current. However, due to lack of pinmux
options, the USB hosts over-current protection signal of the Colibri
standard could not be connected to the PHY's over-current protection.
Hence we need to disabl
Hello.
On 08/19/2014 12:07 AM, Stefan Agner wrote:
Add USB support for Freescale Vybrid tower. The USB hosts over-current
protection signal is not connected is not connected to the PHY's over-
Yes, we all understood that it's not connected, no need to repeat. ;-)
current protection, henc
Hi Hans,
On Monday 18 August 2014 18:24:26 Hans Verkuil wrote:
> On 08/18/2014 05:06 PM, Laurent Pinchart wrote:
> > Simplify ioctl handling by using video_ioctl2.
>
> Are you able to test this on actual hardware? And if so, can you run
> v4l2-compliance?
I'm afraid not. I don't have a platform
> Currently there is no way to change the polling rate, unless you use a
> USB-2 port.
I see.
Any ideas why the USB 3.0 port should affect the game Witcher 2 like
in the video if that is an hardware/driver issue or SDL or maybe
combination?
Thanks for the fast reply, Best Regards
Artur O.
On Mon
> From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
> Sent: Monday, August 04, 2014 12:58 PM
>
> On Mon, Aug 04, 2014 at 07:53:35PM +, Paul Zimmerman wrote:
> > > From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
> > > Sent: Monday, August 04, 2014 12:11 P
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Paul Zimmerman
> Sent: Monday, August 18, 2014 3:00 PM
...
> It looks like your v3 patch series doesn't apply cleanly to Greg's
> linux-next branch any more. Can you please rediff it and send an
> upd
Hello.
On 07/22/2014 11:27 PM, Sergei Shtylyov wrote:
This PHY, though formally being a part of Renesas USBHS controller, contains the
UGCTRL2 register that controls multiplexing of the USB ports (Renesas calls them
channels) to the different USB controllers: channel 0 can be connected to eithe
Hello.
On 07/23/2014 02:17 AM, Sergei Shtylyov wrote:
Add the generic PHY support, analogous to the USB PHY support. Intended it to be
used with the PCI EHCI/OHCI drivers and the xHCI platform driver.
Signed-off-by: Sergei Shtylyov
Signed-off-by: Yoshihiro Shimoda
---
This patch is agai
Signed-off-by: Arjun Sreedharan
---
drivers/usb/misc/yurex.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/misc/yurex.c b/drivers/usb/misc/yurex.c
index 1472805..c3a45da 100644
--- a/drivers/usb/misc/yurex.c
+++ b/drivers/usb/misc/yurex.c
@@ -358,7 +358,7
> From: Paul Zimmerman
> Sent: Monday, August 18, 2014 11:03 AM
>
> > From: Jingoo Han [mailto:jg1@samsung.com]
> > Sent: Monday, August 18, 2014 2:17 AM
> >
> > On Monday, August 18, 2014 5:32 PM, Peter Chen wrote:
> > >
> > > linux-2.6/drivers/usb/dwc2/gadget.c: In function 's3c_hsotg_irq_en
On 08/19/2014 01:11 AM, Daniel Mack wrote:
On 08/15/2014 05:49 AM, Xuebing Wang wrote:
Jassi, thanks for your help.
Without knowing what is the best way to implement UAC2 at the device
side, I managed to simply pipe is as below:
Note: When I am playing music from Ubuntu host, I can hear light
On Mon, Aug 18, 2014 at 10:27:36PM +0800, Alan Stern wrote:
> On Mon, 18 Aug 2014, Peter Chen wrote:
>
> > We introduce the connect API at usb_gadget_driver, the udc driver
> > uses it to tell gadget driver that it is ready to CONNECT, and the
> > dp can be pulled up from now on.
> >
> > Meanwhil
On Mon, Aug 18, 2014 at 10:07:10PM +0200, Stefan Agner wrote:
> This patchset adds USB support for Vybrid VF610 SoC. It extends the
> clock framework to support the USB PHY cocks, extends the device
> tree files and adds support for the non-core registers in the
> usbmisc_imx driver.
>
> This patc
linux-2.6/drivers/usb/wusbcore/wa-xfer.c: In function 'wa_buf_in_cb':
linux-2.6/drivers/usb/wusbcore/wa-xfer.c:2590: warning: 'rpipe' may be used
uninitialized in this function
Signed-off-by: Peter Chen
Suggested-by: Thomas Pugliese
---
Changes for v2:
- Move rpipe initialization out of condit
linux-2.6/drivers/usb/core/hub.c: In function 'usb_disconnect':
linux-2.6/drivers/usb/core/hub.c:2110: warning: 'hub' may be used uninitialized
in this function
linux-2.6/drivers/usb/core/hub.c:2111: warning: 'port1' may be used
uninitialized in this function
Signed-off-by: Peter Chen
---
Chang
linux-2.6/drivers/usb/dwc2/gadget.c: In function 's3c_hsotg_irq_enumdone':
linux-2.6/drivers/usb/dwc2/gadget.c:1904: warning: 'ep_mps' may be used
uninitialized in this function
Acked-by: Paul Zimmerman
Signed-off-by: Peter Chen
---
Changes for v2:
- Add Paul's suggestion and ack
drivers/usb/
Peter Chen (3):
usb: dwc2: gadget: fix below build warning
usb: core: fix below build warning
usb: wusbcore: fix below build warning
drivers/usb/core/hub.c |4 ++--
drivers/usb/dwc2/gadget.c |2 +-
drivers/usb/wusbcore/wa-xfer.c |3 +--
3 files changed, 4 insertion
Changes for v3:
- Add possible role switch for unsupported HNP capable OTG B-peripheral,
see USB OTG & EH 2.0 spec page 38, this feature was deleted wrongly
at previous revision patches.
Changes for v2:
- Move TPL support judgement out of is_target, the user can be easy to
know if it needs to do T
The targeted hosts (non-PC hosts) need to have TPL (Targeted Peripheral List)
for USB OTG & EH certification and other vendor specific requirements.
The platform who needs TPL feature should set this flag at usb host
controller driver.
Signed-off-by: Peter Chen
---
include/linux/usb/hcd.h |
Update configuration for USB_OTG_WHITELIST, any targeted hosts
(non PC-hosts) can have TPL (Targered Peripheral List).
Signed-off-by: Peter Chen
---
drivers/usb/core/Kconfig | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/core/Kconfig b/drivers/usb/
According to On-The-Go and Embedded Host Supplement to the USB Revision
2.0 Specification, the targeted hosts (non-PC hosts) include both
embedded hosts and otg, and each targeted host product defines the
set of supported peripherals on a TPL (Targeted Peripheral List). So,
TPL should apply for bot
The TPL (Targeted Peripheral List) is used for targeted hosts
(non-PC hosts), and it can be used at USB OTG & EH certification
and some specific products which need white list.
Signed-off-by: Peter Chen
---
drivers/usb/common/usb-common.c | 15 +++
include/linux/usb/of.h |
For OTG and Embedded hosts, they may need TPL (Targeted Peripheral List)
for usb certification and other vender specific requirements, the
platform can tell chipidea core driver if it supports tpl through DT
or platform data.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/core.c |4
TPL (Targeted Peripheral List) is needed for targets host
(OTG and Embedded Hosts) for usb certification and other
vendor specific requirements.
Signed-off-by: Peter Chen
---
.../devicetree/bindings/usb/ci-hdrc-imx.txt|2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation
> From: Peter Chen [mailto:peter.c...@freescale.com]
> Sent: Sunday, August 17, 2014 9:14 PM
>
> Except for chipidea driver, all other udc drivers will tell the
> gadget driver that they are ready to pullup dp at udc_start, it
> is the default behaviour.
>
> The chipidea driver is ready to pullup
Hi Community,
My environment is Freescale i.MX6SL EVK board (as USB peripheral
device), which is based on kernel 3.10.17. i.MX6SL uses ChipIdea
dual-role controller.
My problem is that gadget drivers g_ether and g_audio (UAC1 enabled) can
NOT be detected by Windows 7 natively, while g_mass_s
>
> My environment is Freescale i.MX6SL EVK board (as USB peripheral device),
> which is based on kernel 3.10.17. i.MX6SL uses ChipIdea dual-role
> controller.
>
> My problem is that gadget drivers g_ether and g_audio (UAC1 enabled) can
> NOT be detected by Windows 7 natively, while g_mass_stor
Hi,
On Tue, Jul 22, 2014 at 3:32 PM, Varka Bhadram wrote:
> On 07/22/2014 02:38 PM, Subbaraya Sundeep Bhatta wrote:
>>
>> +#include
>> +#include
>> +#include
>> +#include "gadget_chips.h"
>> +#include
>> +#include
>> +#include
>> +#include
>> +#include
>> +#include
>> +#include
>> +#inc
Hi,
(2014/08/19 1:12), Andrew Bresticker wrote:
> Since the struct hc_driver is mostly the same across the xhci-pci,
> xhci-plat, and the upcoming xhci-tegra driver, introduce the function
> xhci_init_driver() which will populate the hc_driver with the default
> xHCI operations. The caller must s
Hi Greg,
Any feedback on this patch ?
Regards
Sanjeev Sharma
-Original Message-
From: Sharma, Sanjeev
Sent: Tuesday, August 12, 2014 12:07 PM
To: 'Hans de Goede'
Cc: gre...@linuxfoundation.org; kra...@redhat.com;
mdharm-...@one-eyed-alien.net; linux-usb@vger.kernel.org;
linux-ker...@v
1 - 100 of 101 matches
Mail list logo
