On Wed, Mar 30, 2016 at 01:29:34PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> > [ text/plain ]
> > On Wed, Mar 23, 2016 at 02:17:27PM -0400, Jaret Cantu wrote:
> >> On 03/23/2016 01:37 PM, Jaret Cantu wrote:
> >> >On 03/23/2016 12:36 AM, Peter Chen wrote:
> >> >>On Mon, Mar 21,
Baolin Wang writes:
>>> diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kconfig
>>> index af5d922..82a5b3c 100644
>>> --- a/drivers/usb/gadget/Kconfig
>>> +++ b/drivers/usb/gadget/Kconfig
>>> @@ -133,6 +133,13 @@ config U_SERIAL_CONSOLE
>>> help
>>> It supports the seri
On 31 March 2016 at 14:12, Jun Li wrote:
> Hi
>
>> -Original Message-
>> From: Baolin Wang [mailto:baolin.w...@linaro.org]
>> Sent: Thursday, March 31, 2016 1:23 PM
>> To: Jun Li
>> Cc: Peter Chen ; Felipe Balbi ;
>> Greg KH ; Sebastian Reichel ;
>> Dmitry Eremin-Solenikov ; David Woodhou
On 31 March 2016 at 14:18, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> [ text/plain ]
>> On 30 March 2016 at 19:24, Felipe Balbi wrote:
> >> >> >
> >> >> > Seems you don't want to guarantee charger type detection is done
> >> >> > before gadget connection(pullup DP), right
On 30 March 2016 at 18:09, Felipe Balbi wrote:
>> ---
>> drivers/usb/gadget/Kconfig |7 +
>> drivers/usb/gadget/Makefile |1 +
>> drivers/usb/gadget/charger.c| 669
>> +++
>
> It seems to me this should be part of udc-core's functionality.
Mark Brown writes:
> [ text/plain ]
> On Wed, Mar 30, 2016 at 01:09:00PM +0300, Felipe Balbi wrote:
>> Baolin Wang writes:
>
>> > +#include
>> > +#include
>> > +#include
>> > +#include
>
>> not very nice to depend on either of or platform_device here. What about
>> PCI-based devices ?
>
> The
Hi,
Baolin Wang writes:
> [ text/plain ]
> On 30 March 2016 at 19:24, Felipe Balbi wrote:
>> >> >
>> >> > Seems you don't want to guarantee charger type detection is done
>> >> > before gadget connection(pullup DP), right?
>> >> > I see you call usb_charger_detect_type() in
Hi,
Bin Liu writes:
> [ text/plain ]
> Hi,
>
> On Wed, Mar 30, 2016 at 09:14:18AM +0300, Felipe Balbi wrote:
>>
>> Hi again,
>>
>> Felipe Balbi writes:
>> > Bin Liu writes:
>> >> On Fri, Mar 18, 2016 at 08:59:48AM +0200, Felipe Balbi wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> Bin Liu writes:
Hi
> -Original Message-
> From: Baolin Wang [mailto:baolin.w...@linaro.org]
> Sent: Thursday, March 31, 2016 1:23 PM
> To: Jun Li
> Cc: Peter Chen ; Felipe Balbi ;
> Greg KH ; Sebastian Reichel ;
> Dmitry Eremin-Solenikov ; David Woodhouse
> ; Peter Chen ; Alan Stern
> ; r.bald...@samsung
On 30 March 2016 at 19:24, Felipe Balbi wrote:
>>> >> >> >
>>> >> >> > Seems you don't want to guarantee charger type detection is done
>>> >> >> > before gadget connection(pullup DP), right?
>>> >> >> > I see you call usb_charger_detect_type() in each gadget usb
>>> >> >> > state
>>> >> >> change
Hello Greg,
3.18.x is missing this patch [1] in order to perform a successful
build. The reason: following patch [2] in 3.18.x uses a macro name
introduced in the missing patch [1].
Could you queue it for 3.18.30?
[1] http://marc.info/?l=git-commits-head&m=142403040503570&w=2
[2]
https://git.ke
On 30 March 2016 at 18:58, Jun Li wrote:
>> >> >> > Seems you don't want to guarantee charger type detection is done
>> >> >> > before gadget connection(pullup DP), right?
>> >> >> > I see you call usb_charger_detect_type() in each gadget usb
>> >> >> > state
>> >> >> changes.
>> >> >>
>> >> >> I
On Wed, Mar 30, 2016 at 01:48:28PM +0300, Felipe Balbi wrote:
>
> Hi Greg,
>
> here's the first set of fixes for v4.6-rc cycle. Let me know if you want
> anything to be changed ;-)
>
> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
>
> Linux 4.6-rc1 (2016-03-26 1
> -Original Message-
> From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com]
> Sent: Tuesday, March 29, 2016 10:51 PM
> To: Rajesh Bhagat
> Cc: gre...@linuxfoundation.org; linux-usb@vger.kernel.org; linux-
> ker...@vger.kernel.org; Sriram Dash
> Subject: Re: [PATCH] usb: xhci: Fix
On 3/30/2016 8:08 AM, Przemek Rudy wrote:
> On 03/30/2016 12:15 PM, Felipe Balbi wrote:
>> John Youn writes:
>>> [ text/plain ]
>>> On 3/16/2016 3:10 PM, Przemek Rudy wrote:
The host/device mode set with dr_mode should be kept all the time,
not being changed to OTG in gadget setup (by ov
On 3/30/2016 6:22 AM, Felipe Balbi wrote:
>
> Hi,
>
> John Keeping writes:
>> Setting up a gadget with the uac2 function results in:
>>
>> Unable to handle kernel NULL pointer dereference at virtual address
>> 0058
>> ...
>> PC is at dwc2_hsotg_irq+0x7f0/0x908
>> LR is at dwc2_hsotg
Hi,
On Thu, Mar 31, 2016 at 1:08 AM, Bin Liu wrote:
> Hi,
>
> On Fri, Aug 15, 2014 at 2:37 AM, Dirk Gouders wrote:
>> Bin Liu writes:
>>
>>> Dirk,
>>>
>>> On Thu, Aug 14, 2014 at 1:52 AM, Dirk Gouders wrote:
Bin Liu writes:
> All,
>
> On Mon, Nov 18, 2013 at 12:08 PM, Ya
Hi,
On Fri, Aug 15, 2014 at 2:37 AM, Dirk Gouders wrote:
> Bin Liu writes:
>
>> Dirk,
>>
>> On Thu, Aug 14, 2014 at 1:52 AM, Dirk Gouders wrote:
>>> Bin Liu writes:
>>>
All,
On Mon, Nov 18, 2013 at 12:08 PM, Yann E. MORIN
wrote:
> Dirk, All,
>
> On 2013-11-07
* Alan Stern [160330 12:26]:
> On Wed, 30 Mar 2016, Ivaylo Dimitrov wrote:
>
> > >>> seems to be created twice :). Maybe the problem is that the first time
> > >>> musb-hdrc is probed it fails with -EPROBE_DEFER, however that failure is
> > >>> after gadget drivers got loaded and noone unloads th
On Wed, 30 Mar 2016, Ivaylo Dimitrov wrote:
> >>> seems to be created twice :). Maybe the problem is that the first time
> >>> musb-hdrc is probed it fails with -EPROBE_DEFER, however that failure is
> >>> after gadget drivers got loaded and noone unloads them.
> >>
> >> gadget drivers will get ad
On 30.03.2016 21:50, Ivaylo Dimitrov wrote:
On 30.03.2016 17:01, Ivaylo Dimitrov wrote:
On 30.03.2016 16:38, Felipe Balbi wrote:
Hi,
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 30.03.2016 17:01, Ivaylo Dimitrov wrote:
On 30.03.2016 16:38, Felipe Balbi wrote:
Hi,
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
Hi a
On 3/23/2016 11:52 PM, Felipe Balbi wrote:
>
> Hi,
>
> John Youn writes:
>> [ text/plain ]
>> On 3/21/2016 11:40 PM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> John Youn writes:
[ text/plain ]
On 3/18/2016 12:17 PM, John Youn wrote:
> On 3/16/2016 6:56 AM, Felipe Balbi wrote:
>>
On Wed, Mar 30, 2016 at 01:09:00PM +0300, Felipe Balbi wrote:
> Baolin Wang writes:
> > +#include
> > +#include
> > +#include
> > +#include
> not very nice to depend on either of or platform_device here. What about
> PCI-based devices ?
The header inclusion shouldn't be conditional though.
Hi,
On Wed, Mar 30, 2016 at 10:23:31AM -0500, Bin Liu wrote:
> Hi,
>
>
> On Wed, Mar 30, 2016 at 06:56:28AM +0800, Antonio Victor Hilario wrote:
> > I'd been using kernel 3.18.10-29 on a set of Beaglebone Black boards, and
> > had found and corrected this on my local build tree.
> >
> > Kernel
Hi,
On Wed, Mar 30, 2016 at 06:56:28AM +0800, Antonio Victor Hilario wrote:
> I'd been using kernel 3.18.10-29 on a set of Beaglebone Black boards, and had
> found and corrected this on my local build tree.
>
> Kernel build fails when the source file drivers/usb/musb/musb_cppi41.c is
> built,
On 03/30/2016 12:15 PM, Felipe Balbi wrote:
> John Youn writes:
>> [ text/plain ]
>> On 3/16/2016 3:10 PM, Przemek Rudy wrote:
>>> The host/device mode set with dr_mode should be kept all the time,
>>> not being changed to OTG in gadget setup (by overriding CFGUSB_FORCEDEVMODE
>>> and CFGUSB_FORCE
On Wed, 30 Mar 2016, Lipengcheng wrote:
> Hi,
> > The ohci-platform and ehci-platform drivers already perform their own
> root-hub and bus resets.
> I don't understand the sentence clearly.
>
> Synopsis control VERSION： DesignWare Cores USB2.0 Host-AHB Controller,
> Version 2.98a
> The syno
On Wednesday 30 March 2016 16:01:53 Ivaylo Dimitrov wrote:
> On 30.03.2016 16:38, Felipe Balbi wrote:
> > Hi,
> >
> > Ivaylo Dimitrov writes:
> >>> Ivaylo Dimitrov writes:
> > Ivaylo Dimitrov writes:
> >>> Ivaylo Dimitrov writes:
> On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
>
Hi,
On Wed, Mar 30, 2016 at 09:14:18AM +0300, Felipe Balbi wrote:
>
> Hi again,
>
> Felipe Balbi writes:
> > Bin Liu writes:
> >> On Fri, Mar 18, 2016 at 08:59:48AM +0200, Felipe Balbi wrote:
> >>>
> >>> Hi,
> >>>
> >>> Bin Liu writes:
> >>> > [ text/plain ]
> >>> > Hi,
> >>> >
> >>> > On F
On 30.03.2016 16:38, Felipe Balbi wrote:
Hi,
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
Hi all,
Looks like there's some issue with the USB
On Wed, Mar 30, 2016 at 3:03 PM, Pavel Machek wrote:
> Hi!
>
>> >Ok, so:
>> >
>> >a) Do we want RGB leds to be handled by existing subsystem, or do we
>> >need separate layer on top of that?
>> >
>> >b) Does RGB make sense, or HSV? RGB is quite widely used in graphics,
>> >and it is what hardware
Arnd Bergmann writes:
> [ text/plain ]
> On Wednesday 30 March 2016 13:31:01 Felipe Balbi wrote:
>> Arnd Bergmann writes:
>> > [ text/plain ]
>> > The phy-am335x driver selects 'USB_COMMON', but all other drivers
>> > use 'depends on' for that symbol, and it depends on USB || USB_GADGET
>> > its
Grygorii Strashko writes:
> [ text/plain ]
> On 03/30/2016 04:10 PM, Felipe Balbi wrote:
>> "Thang Q. Nguyen" writes:
>>
>>> [ text/plain ]
>>> From: "Thang Q. Nguyen"
>>>
>>> The xhci-hcd child node needs to inherit archdata attribute to use
>>> dma_ops functions and attributes. This patch en
On Wednesday 30 March 2016 13:31:01 Felipe Balbi wrote:
> Arnd Bergmann writes:
> > [ text/plain ]
> > The phy-am335x driver selects 'USB_COMMON', but all other drivers
> > use 'depends on' for that symbol, and it depends on USB || USB_GADGET
> > itself, which causes a Kconfig warning:
> >
> > war
On 03/30/2016 04:10 PM, Felipe Balbi wrote:
> "Thang Q. Nguyen" writes:
>
>> [ text/plain ]
>> From: "Thang Q. Nguyen"
>>
>> The xhci-hcd child node needs to inherit archdata attribute to use
>> dma_ops functions and attributes. This patch enables the USB DWC3
>> driver to pass archdata attribut
Hi,
Ivaylo Dimitrov writes:
>> Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
>> Ivaylo Dimitrov writes:
>>> On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
> Hi all,
>
> Looks like ther
Hi,
On 30.03.2016 13:22, Felipe Balbi wrote:
Hi,
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
Hi all,
Looks like there's some issue with the USB gadgets and configfs.
Hi,
John Keeping writes:
> Setting up a gadget with the uac2 function results in:
>
> Unable to handle kernel NULL pointer dereference at virtual address 0058
> ...
> PC is at dwc2_hsotg_irq+0x7f0/0x908
> LR is at dwc2_hsotg_irq+0x4c/0x908
> Backtrace:
> [] (dwc2_hsotg_irq) from
"Thang Q. Nguyen" writes:
> [ text/plain ]
> From: "Thang Q. Nguyen"
>
> The xhci-hcd child node needs to inherit archdata attribute to use
> dma_ops functions and attributes. This patch enables the USB DWC3
> driver to pass archdata attributes to its xhci-hcd child node.
>
> Changes from v2:
>
Hi,
"Thang Q. Nguyen" writes:
> From: "Thang Q. Nguyen"
>
> Add 64-bit DMA operation support to the USB DWC3 driver.
> First attempt to set the coherent DMA mask for 64-bit DMA.
> If that failed, attempt again with 32-bit DMA.
>
> Changes from v2:
> - None.
>
> Changes from v1:
> -
Hi Gil,
Gil Weber writes:
>>> To make sure, I have also performed some additional tests. The problem
>>> seems unrelated to the gadget being used: I have tried various
>>> combinations (zero, ethernet, etc.), even setting up an ACM device
>>> using configfs, and the result is the same: a host de
Hi,
>> To make sure, I have also performed some additional tests. The problem
>> seems unrelated to the gadget being used: I have tried various
>> combinations (zero, ethernet, etc.), even setting up an ACM device
>> using configfs, and the result is the same: a host detects the device
>> for a br
Hi!
> >Ok, so:
> >
> >a) Do we want RGB leds to be handled by existing subsystem, or do we
> >need separate layer on top of that?
> >
> >b) Does RGB make sense, or HSV? RGB is quite widely used in graphics,
> >and it is what hardware implements. (But we'd need to do gamma
> >correction).
> >
> >c)
Hi,
JB writes:
>>> To make sure, I have also performed some additional tests. The problem
>>> seems unrelated to the gadget being used: I have tried various
>>> combinations (zero, ethernet, etc.), even setting up an ACM device
>>> using configfs, and the result is the same: a host detects the d
On Wed, Mar 30 2016, Felipe Balbi wrote:
> a USB packet, right. that's correct. But a struct usb_request can
> point to whatever size buffer it wants and UDC is required to split
> that into wMaxPacketSize transfers.
D’oh. Of course. Disregard all my comments on the patch (except for
Ack).
--
In the current implementation functionfs generates a EFAULT for async read
operations if the read buffer size is larger than the URB data size. Since
a application does not necessarily know how much data the host side is
going to send it typically supplies a buffer larger than the actual data,
whic
Hi, Sergei,
You are correct. I had only thought to submit the least number of changes to
eliminate the problem.
A better fix is to make the leading part of the names EP_MODE_AUTOREQ
consistent for the [mode] parameter to cppi41_set_autoreq_mode( struct
cppi41_dma_channel *cppi41_channel, unsi
Hello,
>> To make sure, I have also performed some additional tests. The problem
>> seems unrelated to the gadget being used: I have tried various
>> combinations (zero, ethernet, etc.), even setting up an ACM device
>> using configfs, and the result is the same: a host detects the device
>> for a
Hi,
JB writes:
>> did you check that getty is still running ? That "deactivated" message
>> means that whatever had /dev/ttyGS0 opened, decided to close it. This
>> could mean that getty got a SIGHUP and just decided to close that fd.
>
> I have only briefly experimented with getty (I also tried
Hello,
> did you check that getty is still running ? That "deactivated" message
> means that whatever had /dev/ttyGS0 opened, decided to close it. This
> could mean that getty got a SIGHUP and just decided to close that fd.
I have only briefly experimented with getty (I also tried opening the
por
Hello.
On 3/30/2016 1:56 AM, Antonio Victor Hilario wrote:
I'd been using kernel 3.18.10-29 on a set of Beaglebone Black boards, and had
found and corrected this on my local build tree.
Kernel build fails when the source file drivers/usb/musb/musb_cppi41.c is
built, with these kernel options
Hi,
Jun Li writes:
>> -Original Message-
>> From: Baolin Wang [mailto:baolin.w...@linaro.org]
>> Sent: Wednesday, March 30, 2016 5:31 PM
>> To: Jun Li
>> Cc: Peter Chen ; Felipe Balbi ;
>> Greg KH ; Sebastian Reichel ;
>> Dmitry Eremin-Solenikov ; David Woodhouse
>> ; Peter Chen ; Alan
> > @@ -1873,7 +1873,7 @@ static void dwc3_gadget_free_endpoints(struct
> dwc3 *dwc)
> >
> > /*
> > --
> > */
> >
> > -static int __dwc3_cleanup_done_trbs(struct dwc3 *dwc, struct dwc3_ep
> *dep,
> > +static int __dwc3_clean
Hi,
changbin...@intel.com writes:
> [ text/plain ]
> From: "Du, Changbin"
>
> Actually, the function only clean one trb. So rename the function.
>
> Signed-off-by: Du, Changbin
okay :-)
> ---
> drivers/usb/dwc3/gadget.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --g
> -Original Message-
> From: Baolin Wang [mailto:baolin.w...@linaro.org]
> Sent: Wednesday, March 30, 2016 5:31 PM
> To: Jun Li
> Cc: Peter Chen ; Felipe Balbi ;
> Greg KH ; Sebastian Reichel ;
> Dmitry Eremin-Solenikov ; David Woodhouse
> ; Peter Chen ; Alan Stern
> ; r.bald...@samsung.
Rafał Miłecki writes:
> [ text/plain ]
> On 30 March 2016 at 12:13, Felipe Balbi wrote:
>> Rafał Miłecki writes:
>>> Northstar is a family of SoCs used in home routers. They have USB 2.0
>>> and 3.0 controllers with PHYs that need to be properly initialized.
>>> This driver provides PHY init sup
Michal Nazarewicz writes:
> [ text/plain ]
> On Wed, Mar 09 2016, Felipe F. Tonello wrote:
>> buflen by default (256) is smaller than wMaxPacketSize (512) in high-speed
>> devices.
>>
>> That caused the OUT endpoint to freeze if the host send any data packet of
>> length greater than 256 bytes.
>>
On Tue, 2016-03-29 at 19:08 +0200, Thierry Reding wrote:
> On Tue, Mar 29, 2016 at 05:24:59PM +0200, Marcel Ziswiler wrote:
> >
> > Hi Thierry
> >
> > On Fri, 2016-03-04 at 17:19 +0100, Thierry Reding wrote:
> > >
> > > From: Thierry Reding > > .org
> > > >
> > > >
> > > The NVIDIA Tegra XUSB
Hi Greg,
here's the first set of fixes for v4.6-rc cycle. Let me know if you want
anything to be changed ;-)
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are available in the git repository at:
git://git.kernel.org/
Arnd Bergmann writes:
> [ text/plain ]
> The phy-am335x driver selects 'USB_COMMON', but all other drivers
> use 'depends on' for that symbol, and it depends on USB || USB_GADGET
> itself, which causes a Kconfig warning:
>
> warning: (AM335X_PHY_USB) selects USB_COMMON which has unmet direct
> de
Hi,
Peter Chen writes:
> [ text/plain ]
> On Wed, Mar 23, 2016 at 02:17:27PM -0400, Jaret Cantu wrote:
>> On 03/23/2016 01:37 PM, Jaret Cantu wrote:
>> >On 03/23/2016 12:36 AM, Peter Chen wrote:
>> >>On Mon, Mar 21, 2016 at 12:32:27PM -0400, Jaret Cantu wrote:
>> >>>The TX settings can be calibr
From: "Du, Changbin"
Actually, the function only clean one trb. So rename the function.
Signed-off-by: Du, Changbin
---
drivers/usb/dwc3/gadget.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index 3ac170f..f84be3d
Hi,
Ivaylo Dimitrov writes:
>> Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
> On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
>> Hi,
>>
>> On 16.01.2016 00:48, Tony Lindgren wrote:
>>> Hi all,
>>>
>>> Looks like there's some issue with the USB gadgets and config
On 30 March 2016 at 12:13, Felipe Balbi wrote:
> Rafał Miłecki writes:
>> Northstar is a family of SoCs used in home routers. They have USB 2.0
>> and 3.0 controllers with PHYs that need to be properly initialized.
>> This driver provides PHY init support in a generic way and can be bound
>> with
John Youn writes:
> [ text/plain ]
> On 3/16/2016 3:10 PM, Przemek Rudy wrote:
>> The host/device mode set with dr_mode should be kept all the time,
>> not being changed to OTG in gadget setup (by overriding CFGUSB_FORCEDEVMODE
>> and CFGUSB_FORCEHOSTMODE bits).
>>
>> Signed-off-by: Przemek Rudy
Rafał Miłecki writes:
> Northstar is a family of SoCs used in home routers. They have USB 2.0
> and 3.0 controllers with PHYs that need to be properly initialized.
> This driver provides PHY init support in a generic way and can be bound
> with XHCI controller driver.
>
> Signed-off-by: Rafał Miłe
Hi,
Baolin Wang writes:
> This patch introduces the usb charger driver based on usb gadget that
> makes an enhancement to a power driver. It works well in practice but
> that requires a system with suitable hardware.
>
> The basic conception of the usb charger is that, when one usb charger
> is
Hi,
Add documentation for struct otg_fsm with some trivial cleanups.
All patches have been Acked by otg-fsm maintainer (Peter Chen).
cheers,
-roger
Roger Quadros (3):
usb: otg-fsm: Add documentation for struct otg_fsm
usb: otg-fsm: support multiple instances
usb: otg-fsm: Prevent build war
If usb/otg-fsm.h and usb/composite.h are included together
then it results in the build warning [1].
Prevent that by using dev_vdbg() instead.
Also get rid of MPC_LOC which doesn't seem to be used
by anyone.
[1] - warning fixed by this patch:
In file included from drivers/usb/dwc3/core.h:33,
struct otg_fsm is the interface to the OTG state machine.
Document the input, output and internal state variables.
Definations are taken from Table 7-2 and Table 7-4 of
the USB OTG & EH Specification Rev.2.0
Re-arrange some of the members as per use case for more
clarity.
Signed-off-by: Roger Qu
Move the state_changed variable into struct otg_fsm
so that we can support multiple instances.
Signed-off-by: Roger Quadros
Acked-by: Peter Chen
---
drivers/usb/common/usb-otg-fsm.c | 10 --
include/linux/usb/otg-fsm.h | 1 +
2 files changed, 5 insertions(+), 6 deletions(-)
diff
On 30 March 2016 at 17:19, Peter Chen wrote:
> On Wed, Mar 30, 2016 at 04:40:31PM +0800, Baolin Wang wrote:
>> >> > - Third, since composite driver covers 500mA (and more for CDP) after
>> >> > set
>> >> > configuration and 2mA after suspend, and vbus handler covers connect
>> >> > and disconnect
On 30 March 2016 at 16:07, Jun Li wrote:
> Hi
>> On 30 March 2016 at 10:54, Jun Li wrote:
>> >> >> It is not for udc driver but for power users who want to negotiate
>> >> >> with USB subsystem.
>> >> >>
>> >> >
>> >> > Seems you don't want to guarantee charger type detection is done
>> >> > bef
Hi,
JB writes:
> [ text/plain ]
>> IIRC ACM will only do anything after you open /dev/ttyGS0 on the
>> peripheral side. Are you running getty on ttyGS0 ?
>
> I did try that, that would explain why it appears only once.
did you check that getty is still running ? That "deactivated" message
means
On Wed, Mar 30, 2016 at 04:40:31PM +0800, Baolin Wang wrote:
> >> > - Third, since composite driver covers 500mA (and more for CDP) after set
> >> > configuration and 2mA after suspend, and vbus handler covers connect
> >> > and disconnect. I can't see any reasons we need to notify gadget state
> >
Out-of-bounds access was triggered on a Thinkpad Yoga during suspend or
by rmmod'ing the xhci-pci module, sometimes leading to a general
protection fault.
This is a defensive symptom fix; the error proper must occur somewhere
else, eg. when the udev with its portnum is left lingering around even
a
Kernel build for an ARM target (Beaglebone Black) fails when the source file
drivers/usb/musb/musb_cppi41.c is built, with these kernel options enabled:
CONFIG_USB_MUSB_HDRC=y
CONFIG_USB_TI_CPPI41_DMA=y
The build fails with these errors, due to a misspelled constant name
EP_MODE_AUTOREQ_NONE:
> IIRC ACM will only do anything after you open /dev/ttyGS0 on the
> peripheral side. Are you running getty on ttyGS0 ?
I did try that, that would explain why it appears only once.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.ke
Hi
> -Original Message-
> From: Baolin Wang [mailto:baolin.w...@linaro.org]
> Sent: Wednesday, March 30, 2016 2:15 PM
> To: Jun Li
> Cc: Peter Chen ; Felipe Balbi ;
> Greg KH ; Sebastian Reichel ;
> Dmitry Eremin-Solenikov ; David Woodhouse
> ; Peter Chen ; Alan Stern
> ; r.bald...@samsun
On 30 March 2016 at 15:42, Peter Chen wrote:
> On Wed, Mar 30, 2016 at 03:07:49PM +0800, Baolin Wang wrote:
>> On 30 March 2016 at 10:05, Peter Chen wrote:
>> > On Tue, Mar 29, 2016 at 10:23:14AM -0700, Mark Brown wrote:
>> >> On Mon, Mar 28, 2016 at 03:13:51PM +0800, Peter Chen wrote:
>> >> > On
>
> On 16-03-29 00:24:46, Peter Chen wrote:
> >
> > >
> > > On 2016-03-25 00:40, Peter Chen wrote:
> > > > On Tue, Mar 15, 2016 at 02:08:26PM +0530, Sanchayan Maity wrote:
> > > >> Hello Peter,
> > > >>
> > > >> The existing usage of extcon in Chipidea driver relies on OTG
> > > >> registers. In
On 03/29/2016 11:43 PM, Pavel Machek wrote:
Hi!
First, please Cc me on RGB color support.
Add generic support for RGB Color LED's.
Basic idea is to use enum led_brightness also for the hue and saturation
color components.This allows to implement the color extension w/o
changes to struct led_
On 03/29/2016 10:42 PM, Heiner Kallweit wrote:
Am 29.03.2016 um 12:05 schrieb Pavel Machek:
On Tue 2016-03-01 22:36:12, Heiner Kallweit wrote:
Export a function to convert HSV color values to RGB.
It's intended to be called by drivers for RGB LEDs.
Signed-off-by: Heiner Kallweit
---
v2:
- mov
Hi Heiner and Pavel,
On 03/29/2016 10:38 PM, Heiner Kallweit wrote:
Am 29.03.2016 um 12:02 schrieb Pavel Machek:
Hi!
First, please Cc me on RGB color support.
Add generic support for RGB Color LED's.
Basic idea is to use enum led_brightness also for the hue and saturation
color components.T
Hi Alexey,
On 26.03.2016 21:42, Alexey Khoroshilov wrote:
> Fixing checks for dma mapping error in qset_fill_page_list(),
> I have missed two similar problems in qset_add_urb_sg() and
> in qset_add_urb_sg_linearize().
>
> v2: check validity of dma_addr with dma_mapping_error()
> in qset_free_std(
On Wed, Mar 30, 2016 at 03:07:49PM +0800, Baolin Wang wrote:
> On 30 March 2016 at 10:05, Peter Chen wrote:
> > On Tue, Mar 29, 2016 at 10:23:14AM -0700, Mark Brown wrote:
> >> On Mon, Mar 28, 2016 at 03:13:51PM +0800, Peter Chen wrote:
> >> > On Mon, Mar 28, 2016 at 02:51:40PM +0800, Baolin Wang
On Tue, 2016-03-29 at 17:58 -0700, Greg KH wrote:
> On Tue, Mar 29, 2016 at 05:42:50PM +0100, reggie macdonald wrote:
> > Hi I made a bug report on bugzilla and was told to forward it to this email.
> >
> > Please see this thread: https://bbs.archlinux.org/viewtopic.php?id=210446
> >
> > for curr
We never, ever route any of the other event buffers
so we might as well drop support for them.
Until someone has a real, proper benefit for
multiple event buffers, we will rely on a single
one. This also helps reduce memory footprint of
dwc3.ko which won't allocate memory for the extra
event buffe
we will be using a single event buffer and that
renders ev_buffs array unnecessary. Let's remove it
in favor of a single pointer to a single event
buffer.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 13 -
drivers/usb/dwc3/core.h | 2 +-
drivers/usb/dwc3/gadget.c |
we don't plan on using multiple event buffers, but
if we find a good use case for it, this little trick
will help us avoid a loop in hardirq handler looping
for each and every event buffer.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 28 +---
1 file change
Hi,
Yoshihiro Shimoda writes:
> Hi,
>
>> Sent: Wednesday, March 30, 2016 2:59 PM
>>
>> Yoshihiro Shimoda writes:
>> > [ text/plain ]
>> > Hi Felipe,
>> >
>> > Thank you for the patch!
>>
>> hey, no problem :-)
>>
>> >> Sent: Tuesday, March 29, 2016 7:11 PM
>> > < snip >
>> >> static const s
Hi,
> Sent: Wednesday, March 30, 2016 2:59 PM
>
> Yoshihiro Shimoda writes:
> > [ text/plain ]
> > Hi Felipe,
> >
> > Thank you for the patch!
>
> hey, no problem :-)
>
> >> Sent: Tuesday, March 29, 2016 7:11 PM
> > < snip >
> >> static const struct xhci_plat_priv xhci_plat_renesas_rcar_gen2
On 30 March 2016 at 10:05, Peter Chen wrote:
> On Tue, Mar 29, 2016 at 10:23:14AM -0700, Mark Brown wrote:
>> On Mon, Mar 28, 2016 at 03:13:51PM +0800, Peter Chen wrote:
>> > On Mon, Mar 28, 2016 at 02:51:40PM +0800, Baolin Wang wrote:
>>
>> > > > I am afraid I still not find the user (udc driver)
94 matches
Mail list logo
