On Wed, Mar 29, 2017 at 08:50:23AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> > According to xHCI ch4.20 Scratchpad Buffers
> > A Scratchpad Buffer is a PAGESIZE block of system memory
> > located on a PAGESIZE boundary
> > ...
> > Software clears the Scr
Hi,
> -Original Message-
> From: Felipe Balbi, Sent: Wednesday, March 29, 2017 2:52 PM
>
> Hi,
>
> Yoshihiro Shimoda writes:
> > Hi Felipe-san,
> >
> >> From: Felipe Balbi, Sent: Tuesday, March 28, 2017 9:06 PM
> >>
> >> Hi,
> >>
> >> Yoshihiro Shimoda writes:
> >> > Sadly, to change t
Sometimes, the user needs to adjust some properties for controllers, eg
the role for controller, we add sysfs group for them.
The attribute 'role' is used to switch host/gadget role dynamically, the
uewr can read the current role, and write the other role compare to
current one to finish the switc
Hi,
Peter Chen writes:
>> > According to xHCI ch4.20 Scratchpad Buffers
>> >A Scratchpad Buffer is a PAGESIZE block of system memory
>> >located on a PAGESIZE boundary
>> >...
>> >Software clears the Scratchpad Buffer to ‘0’
>> >
>> > So, we need to use dma pool for PAGES
Yoshihiro-san
Yoshihiro Shimoda writes:
>> >> Yoshihiro Shimoda writes:
>> >> > Sadly, to change the role ("host" and "peripheral") of USB3.0 DRD
>> >> > controller on R-Car Gen3, software has to set the DRD_CON register
>> >> > which is included in a usb3.0 peripheral controler's register.
>>
Hi Felipe-san,
> From: Felipe Balbi, Sent: Wednesday, March 29, 2017 5:03 PM
>
> Yoshihiro-san
>
> Yoshihiro Shimoda writes:
> >> >> Yoshihiro Shimoda writes:
> >> >> > Sadly, to change the role ("host" and "peripheral") of USB3.0 DRD
> >> >> > controller on R-Car Gen3, software has to set the
Le 28/03/2017 à 18:07, cristian.bir...@microchip.com a écrit :
> From: Cristian Birsan
>
> This patch series provides fixes, based on the feedback received on the
> mailing list, for
> the following:
> - fifo table parameters validation against device tree values
> - coding style
>
Hi,
On 28/03/17 13:27, Felipe Balbi wrote:
> Roger Quadros writes:
>
>> Hi,
>>
>> We rely on the OTG controller block or Extcon to provide us with
>> VBUS and ID line status via an interrupt.
>>
>> This is then used to switch the controller between host, peripheral
>> and idle roles based on the
Hi,
On Tue, 2017-03-28 at 10:30 +0300, Mathias Nyman wrote:
> Hi
>
> On 28.03.2017 05:35, Olivier Langlois wrote:
> > Hardware:
> > HP Spectre 13
> > http://h10032.www1.hp.com/ctg/Manual/c05228576.pdf
> >
> > Kernel version:
> > 4.10.6 SMP PREEMPT x86_64
>
> Is this a new issue? was it working
On Tue, Mar 28, 2017 at 12:13:50PM +0200, Johan Hovold wrote:
> Drop some unnecessary termios-flag debugging that have been faithfully
> reproduced in a few old drivers, including the "clfag" typo and all.
>
> This also addresses a compiler warning on sparc where tcflag_t is
> unsigned long and wo
On Tue, Mar 28, 2017 at 06:48:02AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 17 Mar 2017 10:24:15 +0900
> Greg Kroah-Hartman escreveu:
>
> > On Thu, Mar 16, 2017 at 09:08:40PM -0300, Mauro Carvalho Chehab wrote:
> > > The dwc2 hardware doesn't like to do DMA transfers without
> > > aligning d
On Tue, Mar 28, 2017 at 08:09:32AM -0400, Ajay Kaher wrote:
> Greg, sending patch again using git send-email, please apply.
> Let me know if still any issue.
Note, please put comments like this below the --- line so I don't have
to manually edit the file by hand.
I've now queued this up, thanks.
On 28/03/17 14:10, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>> dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
>> when we're operating in dual-role.
>
> yeah, that's not a quirk. DRA7 supports OTGv2, not OTGv3. There was no
> USB3 when OTGv2 was written.
>
> D
Hi,
Roger Quadros writes:
>> Roger Quadros writes:
>>> dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
>>> when we're operating in dual-role.
>>
>> yeah, that's not a quirk. DRA7 supports OTGv2, not OTGv3. There was no
>> USB3 when OTGv2 was written.
>>
>> DRA7 just shoul
Hi Krzysztof,
On 07/01/17 09:51, Krzysztof Kozlowski wrote:
> Hi,
>
> Thanks to Markus Reichl, I got an Odroid U3 to work with. Thanks to Peter
> Chen, we got a power sequence generic library which solves my long
> standing Odroid U3 problem - no LAN9730 if it was enabled by bootloader.
>
> My p
Hi,
On 28/03/17 14:07, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>> If dr_mode is "otg" then support dual role mode of operation.
>>
>> Get ID and VBUS information from the OTG controller
>> and put the controller in the appropriate state.
>>
>> This is our dual-role state table.
>>
This patch set is based on the latest Felipe's usb.bit / testing/next branch
(commit id = 29986993f67341493988b6c5d68e0653061975b2).
The USB3.0 DRD controller on R-Car Gen3 can change the role via DRD_CON
register in the periperal side sadly, so this patch adds support
for usb role swap feature in
This patch adds extcon support to see VBUS/ID signal states.
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/gadget/udc/Kconfig| 1 +
drivers/usb/gadget/udc/renesas_usb3.c | 43 +--
2 files changed, 42 insertions(+), 2 deletions(-)
diff --git a/drivers/
This usb 3.0 peripheral controller has a register (USB_OTG_STA) to monitor
the USB ID signal. So, this patch adds the ID signal monitoring to change
the mode to host (A-Device) or peripheral (B-Device).
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/gadget/udc/renesas_usb3.c | 53 +
This patch adds support for usb role swap via sysfs "role".
For example:
1) Connect a usb cable using 2 Salvator-X boards.
- For A-Device, the cable is connected to CN11 (USB3.0 ch0).
- For B-Device, the cable is connected to CN9 (USB2.0 ch0).
2) On A-Device, you input the following command:
On 29/03/17 13:32, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>>> Roger Quadros writes:
dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
when we're operating in dual-role.
>>>
>>> yeah, that's not a quirk. DRA7 supports OTGv2, not OTGv3. There was no
>>>
Hi Shimoda-san,
On Wed, Mar 29, 2017 at 1:42 PM, Yoshihiro Shimoda
wrote:
> --- a/drivers/usb/gadget/udc/renesas_usb3.c
> +++ b/drivers/usb/gadget/udc/renesas_usb3.c
> @@ -568,12 +573,29 @@ static void usb3_mode_a_host(struct renesas_usb3 *usb3)
> usb3_set_bit(usb3, DRD_CON_VBOUT, USB3_DR
commit bc1e2154542071e3cfe1734b143af9b8bdacf8bd upstream.
The DSPS glue calls del_timer_sync() in its musb_platform_disable()
implementation, which requires the caller to not hold a lock. But
musb_remove() calls musb_platform_disable() will musb->lock held. This
could causes spinlock deadlock.
So
Hi,
Roger Quadros writes:
>>> @@ -839,6 +841,505 @@ static int dwc3_core_get_phy(struct dwc3 *dwc)
>>> return 0;
>>> }
>>>
>>> +static int dwc3_drd_start_host(struct dwc3 *dwc, int on, bool skip);
>>> +static int dwc3_drd_start_gadget(struct dwc3 *dwc, int on);
>>> +
>>> +/* dwc->lock mus
Hi,
Roger Quadros writes:
>> Roger Quadros writes:
Roger Quadros writes:
> dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
> when we're operating in dual-role.
yeah, that's not a quirk. DRA7 supports OTGv2, not OTGv3. There was no
USB3 when OTGv
On 28.03.2017 16:25, Stephan Müller wrote:
Am Dienstag, 28. März 2017, 03:12:44 CEST schrieb Peter Chen:
What kernel version was this on again?
Has it been working before?
does reloading xhci driver work?
The device is question is at port 2-3.
usb core dyndbg:
[ 72.546341] Restarting
On 29/03/17 16:21, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>>> Roger Quadros writes:
> Roger Quadros writes:
>> dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
>> when we're operating in dual-role.
>
> yeah, that's not a quirk. DRA7 supp
On Wed, Mar 29, 2017 at 11:56:24AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Mar 28, 2017 at 12:13:50PM +0200, Johan Hovold wrote:
> > Drop some unnecessary termios-flag debugging that have been faithfully
> > reproduced in a few old drivers, including the "clfag" typo and all.
> >
> > This also
Am Mittwoch, 29. März 2017, 15:52:13 CEST schrieb Mathias Nyman:
Hi Mathias,
> On 28.03.2017 16:25, Stephan Müller wrote:
> > Am Dienstag, 28. März 2017, 03:12:44 CEST schrieb Peter Chen:
> What kernel version was this on again?
> Has it been working before?
It is 4.10 vanilla. It never worked.
The CPPI 4.1 DMA is sharing its clock with the USB OTG,
and most of the time, the clock will be enabled by USB.
But during the init of the DMA, USB is not enabled (waiting for DMA),
and then we must enable the clock before to do anything.
Add the clock for the CPPI 4.1 DMA engine.
Note:
This patch
Hello!
On 03/29/2017 07:09 PM, Alexandre Bailon wrote:
The CPPI 4.1 DMA is sharing its clock with the USB OTG,
and most of the time, the clock will be enabled by USB.
But during the init of the DMA, USB is not enabled (waiting for DMA),
and then we must enable the clock before to do anything.
This series update MUSB driver to add DMA support to DA8xx.
It should be applied on top of:
"[PATCH v4 0/3] dmaengine: cppi41: Add dma support to da8xx" and
"[PATCH] ARM: davinci: Add the clock for the CPPI 4.1 DMA engine"
Changes in v7:
- Remove the patch that was adding runtime PM.
It was brea
Hello Serge,
On 03/29/2017 06:16 PM, Sergei Shtylyov wrote:
Hello!
On 03/29/2017 07:09 PM, Alexandre Bailon wrote:
The CPPI 4.1 DMA is sharing its clock with the USB OTG,
and most of the time, the clock will be enabled by USB.
But during the init of the DMA, USB is not enabled (waiting for D
Currently, only the PIO mode is supported.
This add support of CPPI 4.1 to DA8xx.
As the In DA8xx the CPPI 4.1 DMA is a part of the USB.
Create the CPPI 4.1 device as a child of USB.
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/Kconfig | 4 ++--
drivers/usb/musb/da8xx.c | 43 +++
In the DA8xx, USB and CPPI 4.1 are sharing the same interrupt line.
Update the driver to request a shared irq.
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/musb_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb
The DMA may hang up if a teardown is initiated while an endpoint is still
active (Advisory 2.3.27 of DA8xx errata).
To workaround this issue, add a delay before to initiate the teardown.
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/da8xx.c | 2 +-
drivers/usb/musb/musb_core.h | 1
On Wed, Mar 29, 2017 at 06:24:31PM +0200, Alexandre Bailon wrote:
> Currently, only the PIO mode is supported.
> This add support of CPPI 4.1 to DA8xx.
> As the In DA8xx the CPPI 4.1 DMA is a part of the USB.
> Create the CPPI 4.1 device as a child of USB.
As in DA8xx the CPPI 4.1 DMA is a part of
Em Wed, 29 Mar 2017 11:57:22 +0200
Greg Kroah-Hartman escreveu:
> On Tue, Mar 28, 2017 at 06:48:02AM -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 17 Mar 2017 10:24:15 +0900
> > Greg Kroah-Hartman escreveu:
> >
> > > On Thu, Mar 16, 2017 at 09:08:40PM -0300, Mauro Carvalho Chehab wrote:
>
This document describe some USB core features. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/index.rst | 1 +
.../persist.txt => driver-api/usb/persist.rst} | 22 +-
2 files changed, 14 insertions(+), 9 d
This document describe some USB core functions. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../anchors.txt => driver-api/usb/anchors.rst} | 36 --
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 21 insertions(+), 16
The structs there at device table are used by other documentation
at the Kernel. So, add it to the driver API.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/basics.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/driver-api/basics.rst
b/Documentati
Several host controllers, commonly found on ARM, like dwc2,
require buffers that are CPU-word aligned for they to work.
Failing to do that will cause random troubles at the caller
drivers, causing them to fail.
Document it.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/
There's one value that use spaces instead of tabs to ident.
That causes the following warning:
./include/linux/usb/gadget.h:193: ERROR: Unexpected indentation.
Signed-off-by: Mauro Carvalho Chehab
---
include/linux/usb/gadget.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
This document describe some USB core features. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/error-codes.rst | 205 +++
Documentation/driver-api/usb/index.rst | 1 +
Documentation/usb/error-codes.txt
This file is actually quite complex, and required several
manual handwork:
- add a title for the document;
- use the right tags for monospaced fonts;
- use c references where needed;
- adjust cross-reference to writing_usb_driver.rst
- hightlight cross-referenced lines.
With regards to C code sni
- use the proper warning and note markups;
- add references for parts of the document that will be
cross-referenced on other USB docs;
- some minor adjustments to make it better to read in
text mode and in html.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/usb.rst |
The pandoc conversion is not perfect. Do handwork in order to:
- add a title to this chapter;
- use the proper warning and note markups;
- use kernel-doc to include Kernel header and c files;
- remove legacy notes with regards to DocBook;
- some other minor adjustments to make it better to read in
We need an space before a numbered list to avoid those warnings:
./drivers/usb/core/message.c:478: ERROR: Unexpected indentation.
./drivers/usb/core/message.c:479: WARNING: Block quote ends without a blank
line; unexpected unindent.
./include/linux/usb/composite.h:455: ERROR: Unexpected indentati
The URB doc describes the Kernel mechanism that do USB transfers.
While the functions are already described at urb.h, there are a
number of concepts and theory that are important for USB driver
developers.
Convert it to ReST and use C ref links to point to the places
at usb.h where each function a
By definition, we use /* private: */ tag when we won't be documenting
a parameter. However, those two parameters are documented:
./include/linux/usb/composite.h:510: warning: Excess struct/union/enum/typedef
member 'setup_pending' description in 'usb_composite_dev'
./include/linux/usb/composite.h
This document describe some USB core features. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../{usb/dma.txt => driver-api/usb/dma.rst}| 51 --
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 28 insertions(+), 24
The pandoc conversion is not perfect. Do handwork in order to:
- add a title to this chapter;
- adjust function and struct references;
- use monospaced fonts for C code names;
- some other minor adjustments to make it better to read in
text mode and in html.
Signed-off-by: Mauro Carvalho Chehab
Get rid of those warnings:
Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name:
"usb_type".
Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name:
"usb_dir".
Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name:
"usb_recip".
Docume
The DocBook file used to have "!E" include tags for usb gadget functions.
However, there's nothing there to be documented:
./drivers/usb/gadget/function/f_acm.c:1: warning: no structured
comments found
./drivers/usb/gadget/function/f_ecm.c:1: warning: no structured
comments found
This document describe some USB core functions. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/index.rst | 1 +
.../usb/power-management.rst} | 403 +++--
2 files changed, 214 insertions(+),
This document describe some USB core features. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../hotplug.txt => driver-api/usb/hotplug.rst} | 66 --
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 37 insertions(+), 30
This document describe some USB core functions. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../bulk-streams.txt => driver-api/usb/bulk-streams.rst}| 13 +
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 10 insertio
As some USB documentation files got moved, adjust their
cross-references to their new place.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/ABI/stable/sysfs-bus-usb| 2 +-
Documentation/driver-api/usb/URB.rst | 2 ++
Documentation/driver-api/usb/callbacks.rst
This document describe some USB core functions. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../callbacks.txt => driver-api/usb/callbacks.rst} | 61 +++---
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 43 insertions(+), 19
According to file
https://www.kernel.org/doc/Documentation/hid/hiddev.txt, hiddev devices
are always named /dev/usb/hiddevN (where n = 0..15).
However, searching the web I see statements that the hiddev device files
might be located in any of several distribution dependent directories,
and code th
Hi Mauro,
Thank you for the patch.
On Wednesday 29 Mar 2017 15:54:21 Mauro Carvalho Chehab wrote:
> Several host controllers, commonly found on ARM, like dwc2,
> require buffers that are CPU-word aligned for they to work.
>
> Failing to do that will cause random troubles at the caller
> drivers,
On Tue, Feb 21, 2017 at 3:43 PM, Rob Herring wrote:
> On Fri, Feb 17, 2017 at 4:07 AM, Hans Ulli Kroll
> wrote:
>> Hi Rob,
>>
>> On Wed, 15 Feb 2017, Rob Herring wrote:
>>
>>> On Wed, Feb 08, 2017 at 09:00:09PM +0100, Hans Ulli Kroll wrote:
>>> > This adds DT bindings for the Faraday FOTG2 host c
Em Thu, 30 Mar 2017 01:15:27 +0300
Laurent Pinchart escreveu:
> Hi Mauro,
>
> Thank you for the patch.
>
> On Wednesday 29 Mar 2017 15:54:21 Mauro Carvalho Chehab wrote:
> > Several host controllers, commonly found on ARM, like dwc2,
> > require buffers that are CPU-word aligned for they to wor
Hi Geert-san,
> From: Geert Uytterhoeven, Sent: Wednesday, March 29, 2017 9:23 PM
>
> Hi Shimoda-san,
>
> On Wed, Mar 29, 2017 at 1:42 PM, Yoshihiro Shimoda
> wrote:
> > --- a/drivers/usb/gadget/udc/renesas_usb3.c
> > +++ b/drivers/usb/gadget/udc/renesas_usb3.c
> > @@ -568,12 +573,29 @@ static
On Wed, Mar 29, 2017 at 11:06:53AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> >> > According to xHCI ch4.20 Scratchpad Buffers
> >> > A Scratchpad Buffer is a PAGESIZE block of system memory
> >> > located on a PAGESIZE boundary
> >> > ...
> >> > Software clears the
Am Mittwoch, 29. März 2017, 04:17:33 CEST schrieb Peter Chen:
Hi Peter,
> Add Mathias
>
> Would you tries to apply below Mathias's patches [1] and [2]?
>
> [1] http://www.spinics.net/lists/linux-usb/msg155351.html
> [2] http://www.spinics.net/lists/linux-usb/msg155353.html
Applying these patch
This usb 3.0 peripheral controller has a register (USB_OTG_STA) to monitor
the USB ID signal. So, this patch adds the ID signal monitoring to change
the mode to host (A-Host) or peripheral (B-Peripheral).
This patch also removes hardcoded setting as B-Peripheral mode.
Signed-off-by: Yoshihiro Shim
This patch adds extcon support to see VBUS/ID signal states.
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/gadget/udc/Kconfig| 1 +
drivers/usb/gadget/udc/renesas_usb3.c | 43 +--
2 files changed, 42 insertions(+), 2 deletions(-)
diff --git a/drivers/
This patch set is based on the latest Felipe's usb.bit / testing/next branch
(commit id = 29986993f67341493988b6c5d68e0653061975b2).
The USB3.0 DRD controller on R-Car Gen3 can change the role via DRD_CON
register in the periperal side sadly, so this patch adds support
for usb role swap feature in
This patch adds support for usb role swap via sysfs "role".
For example:
1) Connect a usb cable using 2 Salvator-X boards.
- For A-Device, the cable is connected to CN11 (USB3.0 ch0).
- For B-Device, the cable is connected to CN9 (USB2.0 ch0).
2) On A-Device, you input the following command:
Am Mittwoch, 29. März 2017, 15:52:13 CEST schrieb Mathias Nyman:
Hi Mathias,
> you could try a kernel without that patch and see if it works:
>
> commit 37be66767e3cae4fd16e064d8bb7f9f72bf5c045
> usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices
After hand-reverting this pat
Hi,
On 28 March 2017 at 21:40, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> Usually usb phy need register one extcon device to get the connection
>> notifications. It will remove some duplicate code if the extcon device
>> is registered using common code instead of each phy driver havi
Hi,
On 29 March 2017 at 06:56, NeilBrown wrote:
> On Thu, Mar 23 2017, Baolin Wang wrote:
>
>> Usually usb phy need register one extcon device to get the connection
>> notifications. It will remove some duplicate code if the extcon device
>> is registered using common code instead of each phy dri
Hi,
On 29 March 2017 at 07:04, NeilBrown wrote:
> On Tue, Mar 07 2017, Baolin Wang wrote:
>
>> On 3 March 2017 at 10:23, NeilBrown wrote:
>>
>>>
>>> I understand your reluctance to change drivers that you cannot test.
>>> An alternative it do change all the
>>> atomic_notifier_call_chain(.*not
I had seen some odd behavior with HiKey's usb-gadget interface
that I finally seemed to have chased down. Basically every other
time I plugged in the OTG port, the gadget interface would
properly initialize. The other times, I'd get a big WARN_ON
in dwc2_hsotg_init_fifo() about the fifo_map not bei
Hi,
On 28 March 2017 at 21:42, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> Since usb phy core has added common code to register or unregister
>> extcon device, then phy-qcom-8x16-usb driver does not need its own
>> code to register/unregister extcon device, then remove them.
>>
>> Sig
Enable the xHCI plat runtime PM for parent device to suspend/resume
xHCI. Also call pm_runtime_forbid() in probe() function to force users
to explicitly enable runtime pm using power/control in sysfs, in case
some parent devices didn't implement runtime PM callbacks.
Signed-off-by: Baolin Wang
--
Hi,
On 29/03/17 16:15, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
@@ -839,6 +841,505 @@ static int dwc3_core_get_phy(struct dwc3 *dwc)
return 0;
}
+static int dwc3_drd_start_host(struct dwc3 *dwc, int on, bool skip);
+static int dwc3_drd_start_gadg
To avoid checkpatch warnings with new patches let's
start using the BIT() macro wherever possible.
Signed-off-by: Roger Quadros
---
drivers/usb/dwc3/core.h | 193 ++-
drivers/usb/dwc3/dwc3-omap.c | 48 +--
drivers/usb/dwc3/gadget.h| 20 +
If usb/otg-fsm.h and usb/composite.h are included together
then it results in the build warning [1].
Prevent that by defining VDBG locally.
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,
fr
Hi Felipe,
Resending this series rebased on v4.11-rc4.
Changelog:
v3:
-rebased on v4.11-rc4
v2:
-include bitops.h header
cheers,
-roger
Roger Quadros (2):
usb: dwc3: use BIT() macro where possible
usb: otg-fsm: Prevent build warning "VDBG" redefined
drivers/usb/common/usb-otg-fsm.c | 7
81 matches
Mail list logo
