>From: Arnd Bergmann [mailto:a...@arndb.de]
>On Tuesday, October 25, 2016 4:26:27 PM CEST Sriram Dash wrote:
>> Do not require dma_set_coherent_mask for hcd
>>
>> Signed-off-by: Arnd Bergmann
>
>Aside from the comments I had for patch 3, you are doing two different things
>here:
>
>> diff --git a/
On Wed, Oct 26, 2016 at 11:00:07PM +0300, Muraru Mihaela wrote:
> On Tue, Oct 25, 2016 at 08:37:50AM +0200, Greg KH wrote:
> > On Mon, Oct 24, 2016 at 10:56:45PM +0300, Mihaela Muraru wrote:
> > > This is a parch to the emxx_udc.c file that remove the
> > > 'usb_device_descriptor' structure because
On 10/26/2016 10:03 AM, Alexandre Bailon wrote:
From: Petr Kulhavy
This adds the function musb_get_mode() to get the DT property "dr_mode"
Signed-off-by: Petr Kulhavy
Acked-by: Sergei Shtylyov
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/musb_core.c | 19 +++
driver
On 10/26/2016 10:03 AM, Alexandre Bailon wrote:
From: Petr Kulhavy
This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/da8xx.c | 47 +++
1 file chang
On 10/26/2016 04:08 PM, ahas...@baylibre.com wrote:
From: Manjunath Goudar
Separate the Davinci OHCI host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM
Signed-off-by: Manjunath Goudar
On 10/26/2016 04:08 PM, ahas...@baylibre.com wrote:
+module_exit(ohci_da8xx_exit);
+MODULE_DESCRIPTION(DRIVER_DESC);
+MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:ohci");
The "ohci" in MODULE_ALIAS() should also be replaced with hcd_name.
--
To unsubscribe from this list: send the line "un
On Wed, Oct 19, 2016 at 06:22:52PM -0700, John Youn wrote:
> Add the host-dma property to devicetree. This controls whether to use
> DMA in host mode.
>
> Signed-off-by: John Youn
> ---
> Documentation/devicetree/bindings/usb/dwc2.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Doc
From: Manjunath Goudar
Separate the Davinci OHCI host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM
Signed-off-by: Manjunath Goudar
[Axel: adapted and rebased, fixed minor comments]
Sign
On Wednesday 26 October 2016 02:17 AM, John Youn wrote:
> On 10/25/2016 7:15 AM, Randy Li wrote:
>> I forget to add a dummy function in case the CONFIG_GENERIC_PHY
>> is disabled.
>>
>> Signed-off-by: Randy Li
>
> Fixes: cac18ecb6f44 ("phy: Add reset callback")
> Tested-by: John Youn
>
> Hi K
On Tue, Oct 25, 2016 at 08:37:50AM +0200, Greg KH wrote:
> On Mon, Oct 24, 2016 at 10:56:45PM +0300, Mihaela Muraru wrote:
> > This is a parch to the emxx_udc.c file that remove the
> > 'usb_device_descriptor' structure because it is not used in the current
> > file or in other one.
> >
> > Signed
On Mon, Oct 24, 2016 at 4:24 PM, Johan Hovold wrote:
> On Sat, Oct 22, 2016 at 10:14:21PM +0100, Aidan Thornton wrote:
>> Sent, but please pay close attention to the new note in patch 2 about
>> higher baud rates. It turns out the timings for baud rates above 500kbaud
>> are out of spec. This isn'
Removing unnecessary duplicated actions that we've got while merging:
19915e623458 ("Merge 4.1-rc7 into usb-next")
Signed-off-by: Kirill Esipov
---
drivers/usb/musb/musb_core.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
ind
On 10/26/2016 05:40 PM, David Lechner wrote:
> On 10/26/2016 05:58 AM, Alexandre Bailon wrote:
>> If we configure the da8xx OTG phy in OTG mode, neither device or host
>> mode will work. That is because the PHY is not able to detect and notify
>> the driver that value of ID pin changed.
>> To work
On 10/26/2016 05:58 AM, Alexandre Bailon wrote:
If we configure the da8xx OTG phy in OTG mode, neither device or host
mode will work. That is because the PHY is not able to detect and notify
the driver that value of ID pin changed.
To work despite this hardware limitation, the da8xx glue implemen
Hi,
On Wed, Oct 26, 2016 at 05:24:27PM +0300, Kirill Esipov wrote:
> Removing unnecessary duplicated actions that we've got while merging:
> 19915e623458 ("Merge 4.1-rc7 into usb-next")
>
> Signed-off-by: Kirill Esipov
> ---
> drivers/usb/musb/musb_core.c | 6 --
> 1 file changed, 6 deletio
From: Petr Kulhavy
DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver.
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
---
.../devicetree/bindings/usb/da8xx-usb.txt | 43 ++
1 file changed, 43 insertions(+)
create mode 100644 Documentation
From: Petr Kulhavy
This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/da8xx.c | 47 +++
1 file changed, 47 insertions(+)
diff --git a/drivers/usb/mus
This adds the device tree node for the usb otg
controller present in the da850 family of SoC's.
This also enables the otg usb controller for the lcdk board.
Signed-off-by: Alexandre Bailon
---
arch/arm/boot/dts/da850-lcdk.dts | 8
arch/arm/boot/dts/da850.dtsi | 15 +++
From: Petr Kulhavy
This adds the function musb_get_mode() to get the DT property "dr_mode"
Signed-off-by: Petr Kulhavy
Acked-by: Sergei Shtylyov
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/musb_core.c | 19 +++
drivers/usb/musb/musb_core.h | 5 +
2 files changed
The purpose of this series is to add DT support to the da8xx USB OTG.
This series should apply and build without any issues but it has
some dependencies on "Add DT support for ohci-da8xx" series.
Without it, the phy init will fail and then the da8xx driver will also fail.
Changes in v2:
* Remove u
On Wed, 26 Oct 2016, Sriram Dash wrote:
> >From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com]
> >I don't think usb core tries to drive reset while port is still resuming
> >
>
> I am skeptical about it and hope somebody may help us on this.
You can see for yourself. In drivers/usb/core
* Johan Hovold [161026 07:21]:
> On Tue, Oct 25, 2016 at 08:11:10AM -0700, Tony Lindgren wrote:
> > * Johan Hovold [161025 01:33]:
> > > On Mon, Oct 24, 2016 at 10:35:38AM -0700, Tony Lindgren wrote:
> > >
> > > > From: Tony Lindgren
> > > > Date: Mon, 24 Oct 2016 09:18:02 -0700
> > > > Subject
Removing unnecessary duplicated actions that we've got while merging:
19915e623458 ("Merge 4.1-rc7 into usb-next")
Signed-off-by: Kirill Esipov
---
drivers/usb/musb/musb_core.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
in
On Tue, Oct 25, 2016 at 08:11:10AM -0700, Tony Lindgren wrote:
> * Johan Hovold [161025 01:33]:
> > On Mon, Oct 24, 2016 at 10:35:38AM -0700, Tony Lindgren wrote:
> >
> > > From: Tony Lindgren
> > > Date: Mon, 24 Oct 2016 09:18:02 -0700
> > > Subject: [PATCH] usb: musb: Fix sleeping function cal
On Wed, Oct 26, 2016 at 04:35:29PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Bin Liu writes:
> > On Wed, Oct 26, 2016 at 04:13:11PM +0300, Felipe Balbi wrote:
> >>
> >> Hi,
> >>
> >> Bin Liu writes:
> >> >> >> >> > There is no VBUS detection on this device and board. Is the VBUS
> >> >> >> >> >
Hi,
Bin Liu writes:
> On Wed, Oct 26, 2016 at 04:13:11PM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Bin Liu writes:
>> >> >> >> > There is no VBUS detection on this device and board. Is the VBUS
>> >> >> >> > detection needed for dwc3 to work in device mode?
>> >> >> >>
>> >> >> >> In the c
On Wed, Oct 26, 2016 at 04:13:11PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Bin Liu writes:
> >> >> >> > There is no VBUS detection on this device and board. Is the VBUS
> >> >> >> > detection needed for dwc3 to work in device mode?
> >> >> >>
> >> >> >> In the case of DRA7x, you don't *really*
On 10/26/2016 03:01 PM, Kirill Esipov wrote:
Removing unnecessary duplicated actions that we've got while merging:
"Merge 4.1-rc7 into usb-next" 19915e623458
See Documentation/SubmittingPatches, it should be: 19915e623458 ("Merge
4.1-rc7 into usb-next"). Perhaps the MUSB maintainer can fix
Hi,
Bin Liu writes:
>> >> >> > There is no VBUS detection on this device and board. Is the VBUS
>> >> >> > detection needed for dwc3 to work in device mode?
>> >> >>
>> >> >> In the case of DRA7x, you don't *really* need detection. All you need
>> >> >> to
>> >> >> do is correctly update UTMI
>From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com]
>On 25.10.2016 13:45, Sriram Dash wrote:
>> For the USB3.0 controller, USB 2.0 reset not driven while port is in
>> Resume state. So, do not program the USB 2.0 reset
>> (PORTSC[PR]=1) while in Resume state.
>>
>> Signed-off-by: Rajat Sriv
On Wed, Oct 26, 2016 at 10:20:11AM +0300, Roger Quadros wrote:
> Hi,
>
> On 25/10/16 23:55, Bin Liu wrote:
> > Felipe,
> >
> > On Tue, Oct 25, 2016 at 08:57:26AM -0500, Bin Liu wrote:
> >> On Tue, Oct 25, 2016 at 04:44:13PM +0300, Felipe Balbi wrote:
> >>
> >> [snip]
> >>
> Just reviewed thi
On Wed, Oct 26, 2016 at 01:50:14PM +0200, Linus Walleij wrote:
> On Wed, Oct 26, 2016 at 11:09 AM, Johan Hovold wrote:
> > On Tue, Oct 25, 2016 at 11:34:40AM +0200, Linus Walleij wrote:
>
> >> I was thinking on either reusing the .names field of the
> >> struct gpiochip to name the lines for the
On Wed, Oct 26, 2016 at 11:35:47AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Bin Liu writes:
> >> >> > There is no VBUS detection on this device and board. Is the VBUS
> >> >> > detection needed for dwc3 to work in device mode?
> >> >>
> >> >> In the case of DRA7x, you don't *really* need detecti
Removing unnecessary duplicated actions that we've got while merging:
"Merge 4.1-rc7 into usb-next" 19915e623458
Signed-off-by: Kirill Esipov
---
drivers/usb/musb/musb_core.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
inde
On Wed, Oct 26, 2016 at 11:09 AM, Johan Hovold wrote:
> On Tue, Oct 25, 2016 at 11:34:40AM +0200, Linus Walleij wrote:
>> I was thinking on either reusing the .names field of the
>> struct gpiochip to name the lines for the userspace
>> chardev. With the sideeffect of the names getting reflected
Hello.
On 10/26/2016 2:12 PM, Kirill Esipov wrote:
Remove unnecessary duplicate actions (that we've got here:
19915e623458004547c1c2490b09bb923fe69337)
You should also specify the commit's summary line in (""). And it's enough
to specify 12 digits of SHA1 ID.
Signed-off-by: Kirill Esip
Remove unnecessary duplicate actions (that we've got here:
19915e623458004547c1c2490b09bb923fe69337)
Signed-off-by: Kirill Esipov
---
drivers/usb/musb/musb_core.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
index 27dadc0..2
Currently, the USB OTG of the da8xx doesn't work.
This series intend to fix them.
Change in v2:
* Fix the error path da8xx_musb_init()
Alexandre Bailon (3):
usb: musb: da8xx: Call earlier clk_prepare_enable()
phy: da8xx-usb: Configure CFGCHIP2 to support OTG workaround
usb: musb: da8xx: Onl
When the phy is forced in host mode, only the first hot plug and
hot remove works. That is actually because the driver execute the
OTG workaround, whereas it is not applicable in host or device mode.
Indeed, to work correctly, the VBUS sense and session end comparator
must be enabled, what is only
The first attempt to read a register may fail because the clock may not
be enabled, and then the probe of musb driver will fail.
Call clk_prepare_enable() before the first register read.
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/da8xx.c | 17 -
1 file changed, 8 insert
If we configure the da8xx OTG phy in OTG mode, neither device or host
mode will work. That is because the PHY is not able to detect and notify
the driver that value of ID pin changed.
To work despite this hardware limitation, the da8xx glue implement a
workaround.
But to work, the workaround requir
On Tue, Oct 25, 2016 at 12:42:46PM -0700, John Youn wrote:
> Add interrupt moderation interval binding for dwc3.
>
> Signed-off-by: John Youn
> ---
> Documentation/devicetree/bindings/usb/dwc3.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/dwc
Hello.
On 10/25/2016 10:42 PM, John Youn wrote:
Add interrupt moderation interval binding for dwc3.
Signed-off-by: John Youn
---
Documentation/devicetree/bindings/usb/dwc3.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/usb/dwc3.txt
b/Documentation/
Hi,
Joseph Kogut writes:
> Hi David,
>
> I know this is a pretty old thread. I tried searching for the LKML
> etiquette on something like this and came up empty. If I should start
> a new thread, let me know.
>
> After what I learned from the last thread, I dropped the idea of using
> the device
On Tuesday 25 October 2016 09:35 PM, David Lechner wrote:
> On 10/25/2016 05:12 AM, Sekhar Nori wrote:
>> On Monday 24 October 2016 10:16 PM, ahas...@baylibre.com wrote:
>>> diff --git a/arch/arm/mach-davinci/usb-da8xx.c
>>> b/arch/arm/mach-davinci/usb-da8xx.c
>>> index 9e41a7f..982e105 100644
>>>
On 10/25/2016 07:38 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 10/25/2016 05:39 PM, Alexandre Bailon wrote:
>
>> From: Petr Kulhavy
>>
>> This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver
>>
>> Signed-off-by: Petr Kulhavy
>> Signed-off-by: Alexandre Bailon
>> ---
>> drivers
On 10/25/2016 09:16 PM, David Lechner wrote:
> On 10/25/2016 08:52 AM, Alexandre Bailon wrote:
>> If we configure the da8xx OTG phy in OTG mode, neither device or host
>> mode will work. That is because the PHY is not able to detect and notify
>> the driver that value of ID pin changed.
>> To work
On Tue, Oct 25, 2016 at 11:34:40AM +0200, Linus Walleij wrote:
> Good work on this patch, nice that it got merged.
>
> I was just thinking that as an add-on, you may want to name
> the gpio lines so they have meaningful names in userspace
> when you use this with the chardev (I have reasons to bel
The current error handling flow uses incorrect goto label, fix it
Cc:
Fixes: d12a8727171c ("usb: gadget: function: Remove
redundant usb_free_all_descriptors")
Signed-off-by: Peter Chen
---
drivers/usb/gadget/function/f_uac2.c | 20 +++-
1 file changed, 11 insertions(+),
On Tuesday 25 October 2016 09:23 PM, David Lechner wrote:
> Hi Sekhar,
>
> On 10/25/2016 05:17 AM, Sekhar Nori wrote:
>> On Tuesday 25 October 2016 03:07 PM, Axel Haslam wrote:
>>> Hi Sekar,
>>>
>>> On Tue, Oct 25, 2016 at 10:10 AM, Sekhar Nori wrote:
On Monday 24 October 2016 10:16 PM, ahas
Hi,
Bin Liu writes:
>> >> > There is no VBUS detection on this device and board. Is the VBUS
>> >> > detection needed for dwc3 to work in device mode?
>> >>
>> >> In the case of DRA7x, you don't *really* need detection. All you need to
>> >> do is correctly update UTMI mailbox.
>> >
>> > But t
Hi,
On 25/10/16 23:55, Bin Liu wrote:
> Felipe,
>
> On Tue, Oct 25, 2016 at 08:57:26AM -0500, Bin Liu wrote:
>> On Tue, Oct 25, 2016 at 04:44:13PM +0300, Felipe Balbi wrote:
>>
>> [snip]
>>
Just reviewed this patch, it seems to be the regression. But SS should
not generate ID pin event
On Wed, Oct 26, 2016 at 11:03:20AM +0800, Peter Chen wrote:
> The following changes since commit b76032396d7958f006bccf5fb2535beb5526837c:
>
> usb: renesas_usbhs: add wait after initialization for R-Car Gen3
> (2016-10-24 14:35:46 +0200)
>
> are available in the git repository at:
>
> git:/
53 matches
Mail list logo
