[PATCH v2 1/4] ARM: OMAP2+: omap_hwmod: provide space for more hwmod flags

From: Sekhar Nori 'flags' member of omap_hwmod structure is fast running out of space with 16 different flags already defined. Make flags a 32-bit entity so as to allow for more flags. This results is a ~2.3K data section size increase with omap2plus_defconfig on v4.11-rc2. before: text

Re: [PATCH 1/4] ARM: OMAP2+: omap_hwmod: provide space for more hwmod flags

On 13/03/17 15:35, Sekhar Nori wrote: > On Monday 13 March 2017 05:23 PM, Roger Quadros wrote: >> From: Sekhar Nori <nsek...@ti.com> >> >> 'flags' member of omap_hwmod structure is fast running >> out of space with 16 different flags already defined. >> >&

Re: [PATCH 1/4] ARM: OMAP2+: omap_hwmod: provide space for more hwmod flags

On 13/03/17 15:35, Sekhar Nori wrote: > On Monday 13 March 2017 05:23 PM, Roger Quadros wrote: >> From: Sekhar Nori >> >> 'flags' member of omap_hwmod structure is fast running >> out of space with 16 different flags already defined. >> >> Make flags a 32-b

[PATCH 0/2] ARM: am335x-icev2: Add ethernet support

Hi, This series adds ethernet support to am335x-icev2 board. The ethernet PHYs on the board need an explicit GPIO reset pulse to ensure they bootstrap to the correct mode. Without the GPIO reset they just don't work. cheers, -roger Roger Quadros (2): net: davinci_mdio: add GPIO reset logic

[PATCH 0/2] ARM: am335x-icev2: Add ethernet support

Hi, This series adds ethernet support to am335x-icev2 board. The ethernet PHYs on the board need an explicit GPIO reset pulse to ensure they bootstrap to the correct mode. Without the GPIO reset they just don't work. cheers, -roger Roger Quadros (2): net: davinci_mdio: add GPIO reset logic

[PATCH 2/2] ARM: dts: am335x-icev2: Add CPSW ethernet0 and ethernet1

Enable the 2 ethernet ports as CPSW ports in dual-mac mode Signed-off-by: Roger Quadros <rog...@ti.com> [nsek...@ti.com: use AM33XX_IOPAD()] Signed-off-by: Sekhar Nori <nsek...@ti.com> --- arch/arm/boot/dts/am335x-icev2.dts | 113 + 1 file

[PATCH 2/2] ARM: dts: am335x-icev2: Add CPSW ethernet0 and ethernet1

Enable the 2 ethernet ports as CPSW ports in dual-mac mode Signed-off-by: Roger Quadros [nsek...@ti.com: use AM33XX_IOPAD()] Signed-off-by: Sekhar Nori --- arch/arm/boot/dts/am335x-icev2.dts | 113 + 1 file changed, 113 insertions(+) diff --git a/arch/arm

[PATCH 1/2] net: davinci_mdio: add GPIO reset logic

for such cases. [1] - am572x-idk, am571x-idk, a437x-idk. Signed-off-by: Roger Quadros <rog...@ti.com> Signed-off-by: Sekhar Nori <nsek...@ti.com> --- .../devicetree/bindings/net/davinci-mdio.txt | 2 + drivers/net/ethernet/ti/davinci_mdio.c | 68 +++

[PATCH 1/2] net: davinci_mdio: add GPIO reset logic

for such cases. [1] - am572x-idk, am571x-idk, a437x-idk. Signed-off-by: Roger Quadros Signed-off-by: Sekhar Nori --- .../devicetree/bindings/net/davinci-mdio.txt | 2 + drivers/net/ethernet/ti/davinci_mdio.c | 68 +++--- 2 files changed, 62 insertions(+), 8

Re: [PATCH 0/4] ARM: DRA7: Fix DCAN1 stuck-in-transition

On 13/03/17 13:53, Roger Quadros wrote: > Hi, > > On DRA7 platform, DCAN1 module has an issue when it's clockdomain > (WKUPAON) is configured in HW_AUTO. After DCAN1 is enabled and disabled > the module remains stuck in transition. > > Suggested workaround by Silicon team

Re: [PATCH 0/4] ARM: DRA7: Fix DCAN1 stuck-in-transition

On 13/03/17 13:53, Roger Quadros wrote: > Hi, > > On DRA7 platform, DCAN1 module has an issue when it's clockdomain > (WKUPAON) is configured in HW_AUTO. After DCAN1 is enabled and disabled > the module remains stuck in transition. > > Suggested workaround by Silicon team

[PATCH 2/4] ARM: OMAP2+ hwmod: Allow modules to disable HW_AUTO

Introduce HWMOD_CLKDM_NOAUTO flag that allows the hwmod's clockdomain to be prevented from HW_AUTO while the hwmod is active. This is needed to workaround some modules which don't function correctly with HW_AUTO. e.g. DCAN on DRA7. Signed-off-by: Roger Quadros <rog...@ti.com> [nsek...@

[PATCH 2/4] ARM: OMAP2+ hwmod: Allow modules to disable HW_AUTO

Introduce HWMOD_CLKDM_NOAUTO flag that allows the hwmod's clockdomain to be prevented from HW_AUTO while the hwmod is active. This is needed to workaround some modules which don't function correctly with HW_AUTO. e.g. DCAN on DRA7. Signed-off-by: Roger Quadros [nsek...@ti.com: rebased to v4.9

[PATCH 3/4] ARM: DRA7: hwmod: Fix DCAN1 stuck in transition

rrata i893. Signed-off-by: Roger Quadros <rog...@ti.com> --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c b/arch/arm/mach-omap2/omap_hwmod_7xx_data.c index d058529..896f238 100644 --- a/arc

[PATCH 1/4] ARM: OMAP2+: omap_hwmod: provide space for more hwmod flags

From: Sekhar Nori 'flags' member of omap_hwmod structure is fast running out of space with 16 different flags already defined. Make flags a 32-bit entity so as to allow for more flags. This results is a ~2.3K data section size increase with TI config fragments. before: text

[PATCH 4/4] ARM: DRA7: hwmod_data: Prevent wait_target_disable error for usb_otg_ss

know yet if usb_otg_ss instances 3 and 4 are affected by this issue or not so don't add this flag for those instances. Cc: Tero Kristo <t-kri...@ti.com> Signed-off-by: Roger Quadros <rog...@ti.com> --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 ++ 1 file changed, 2 insertions(+)

[PATCH 3/4] ARM: DRA7: hwmod: Fix DCAN1 stuck in transition

rrata i893. Signed-off-by: Roger Quadros --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c b/arch/arm/mach-omap2/omap_hwmod_7xx_data.c index d058529..896f238 100644 --- a/arch/arm/mach-omap2/omap_hwmod_

[PATCH 1/4] ARM: OMAP2+: omap_hwmod: provide space for more hwmod flags

From: Sekhar Nori 'flags' member of omap_hwmod structure is fast running out of space with 16 different flags already defined. Make flags a 32-bit entity so as to allow for more flags. This results is a ~2.3K data section size increase with TI config fragments. before: textdata bss

[PATCH 4/4] ARM: DRA7: hwmod_data: Prevent wait_target_disable error for usb_otg_ss

know yet if usb_otg_ss instances 3 and 4 are affected by this issue or not so don't add this flag for those instances. Cc: Tero Kristo Signed-off-by: Roger Quadros --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2

[PATCH 0/4] ARM: DRA7: Fix DCAN1 stuck-in-transition

~# ifconfig can0 down [ 50.488786] omap_hwmod: dcan1: _wait_target_disable failed [ 50.502855] omap_hwmod: dcan1: _wait_target_disable failed cheers, -roger Roger Quadros (3): ARM: OMAP2+ hwmod: Allow modules to disable HW_AUTO ARM: DRA7: hwmod: Fix DCAN1 stuck in transition ARM: DRA7

[PATCH 0/4] ARM: DRA7: Fix DCAN1 stuck-in-transition

~# ifconfig can0 down [ 50.488786] omap_hwmod: dcan1: _wait_target_disable failed [ 50.502855] omap_hwmod: dcan1: _wait_target_disable failed cheers, -roger Roger Quadros (3): ARM: OMAP2+ hwmod: Allow modules to disable HW_AUTO ARM: DRA7: hwmod: Fix DCAN1 stuck in transition ARM: DRA7

Re: [PATCH v2 0/4] usb: dwc3: dual-role support

Felipe, On 16/02/17 15:06, Roger Quadros wrote: > 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 o

Re: [PATCH v2 0/4] usb: dwc3: dual-role support

Felipe, On 16/02/17 15:06, Roger Quadros wrote: > 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 o

[PATCH v2] usb: xhci: bInterval quirk for TI TUSB73x0

. Workaround this issue by limiting the bInterval to 7 (i.e. interval to 6) for High-speed or faster periodic endpoints. [1] - http://www.ti.com/lit/er/sllz076/sllz076.pdf Signed-off-by: Roger Quadros <rog...@ti.com> --- v2: -fixed typo in commit message drivers/usb/host/xhci-mem.c | 11 +

[PATCH v2] usb: xhci: bInterval quirk for TI TUSB73x0

. Workaround this issue by limiting the bInterval to 7 (i.e. interval to 6) for High-speed or faster periodic endpoints. [1] - http://www.ti.com/lit/er/sllz076/sllz076.pdf Signed-off-by: Roger Quadros --- v2: -fixed typo in commit message drivers/usb/host/xhci-mem.c | 11 +++ drivers/usb/ho

Re: [PATCH] usb: xhci: bInterval quirk for TI TUSB73x0

On 09/03/17 11:44, Sergei Shtylyov wrote: > Hello! > > On 3/9/2017 11:47 AM, Roger Quadros wrote: > >> As per [1] issue #4, >> "The periodic EP scheduler always tries to schedule the EPs >> that have large intervals (interval equal to or greater than

Re: [PATCH] usb: xhci: bInterval quirk for TI TUSB73x0

On 09/03/17 11:44, Sergei Shtylyov wrote: > Hello! > > On 3/9/2017 11:47 AM, Roger Quadros wrote: > >> As per [1] issue #4, >> "The periodic EP scheduler always tries to schedule the EPs >> that have large intervals (interval equal to or greater than

Re: [PATCH 1/2] usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval

Felipe, On 08/03/17 16:05, Roger Quadros wrote: > The streaming_maxburst module parameter is 0 offset (0..15) > so we must add 1 while using it for wBytesPerInterval > calculation for the SuperSpeed companion descriptor. > > Without this host uvcvideo driver will alway

Re: [PATCH 1/2] usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval

Felipe, On 08/03/17 16:05, Roger Quadros wrote: > The streaming_maxburst module parameter is 0 offset (0..15) > so we must add 1 while using it for wBytesPerInterval > calculation for the SuperSpeed companion descriptor. > > Without this host uvcvideo driver will alway

[PATCH] usb: xhci: bInterval quirk for TI TUSB73x0

. Workaround this issue by limiting the bInterval to 7 (i.e. interval to 6) for High-speed or faster periodic endpoints. [1] - http://www.ti.com/lit/er/sllz076/sllz076.pdf Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/usb/host/xhci-mem.c | 11 +++ drivers/usb/host/xhci-pci.c |

[PATCH] usb: xhci: bInterval quirk for TI TUSB73x0

. Workaround this issue by limiting the bInterval to 7 (i.e. interval to 6) for High-speed or faster periodic endpoints. [1] - http://www.ti.com/lit/er/sllz076/sllz076.pdf Signed-off-by: Roger Quadros --- drivers/usb/host/xhci-mem.c | 11 +++ drivers/usb/host/xhci-pci.c | 3 +++ drivers/us

Re: [PATCH 1/3] usb: dwc3-omap: Fix missing break in dwc3_omap_set_mailbox()

Felipe, On 15/02/17 13:38, Roger Quadros wrote: > We need to break from all cases if we want to treat > each one of them separately. > > Reported-by: Gustavo A. R. Silva <garsi...@embeddedor.com> > Fixes: d2728fb3e01f ("usb: dwc3: omap: Pass VBUS and ID events

Re: [PATCH 1/3] usb: dwc3-omap: Fix missing break in dwc3_omap_set_mailbox()

Felipe, On 15/02/17 13:38, Roger Quadros wrote: > We need to break from all cases if we want to treat > each one of them separately. > > Reported-by: Gustavo A. R. Silva > Fixes: d2728fb3e01f ("usb: dwc3: omap: Pass VBUS and ID events transparently") > Cc: #v4.8+ &g

[PATCH 1/2] usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval

a suitable video interface endpoint. e.g. for streaming_maxburst = 0 case it will always fail as wBytePerInterval was evaluating to 0. Cc: sta...@vger.kernel.org Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/usb/gadget/function/f_uvc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 1/2] usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval

a suitable video interface endpoint. e.g. for streaming_maxburst = 0 case it will always fail as wBytePerInterval was evaluating to 0. Cc: sta...@vger.kernel.org Signed-off-by: Roger Quadros --- drivers/usb/gadget/function/f_uvc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers

[PATCH 2/2] usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed

As per USB3.0 Specification "Table 9-20. Standard Endpoint Descriptor", for interrupt and isochronous endpoints, wMaxPacketSize must be set to 1024 if the endpoint defines bMaxBurst to be greater than zero. Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/usb/gadget/func

[PATCH 0/2] usb: gadget: f_uvc: SuperSpeed fixes

Hi Laurent & Felipe, These are some fixes for SuperSpeed case. -- cheers, -roger Roger Quadros (2): usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed drivers/usb/gadget/function/f_uvc.c

[PATCH 2/2] usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed

As per USB3.0 Specification "Table 9-20. Standard Endpoint Descriptor", for interrupt and isochronous endpoints, wMaxPacketSize must be set to 1024 if the endpoint defines bMaxBurst to be greater than zero. Signed-off-by: Roger Quadros --- drivers/usb/gadget/function/f_uvc.c | 8 +

[PATCH 0/2] usb: gadget: f_uvc: SuperSpeed fixes

Hi Laurent & Felipe, These are some fixes for SuperSpeed case. -- cheers, -roger Roger Quadros (2): usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed drivers/usb/gadget/function/f_uvc.c

Re: [PATCH] uvc-gadget: Fix Set Interface (alternate setting) response behaviour

Laurent, On 06/03/17 22:50, Laurent Pinchart wrote: > Hi Roger, > > Thank you for the patch. > > On Friday 03 Mar 2017 13:17:15 Roger Quadros wrote: >> On alternate setting change, webcam gadget sends us a UVC_EVENT_STREAMON >> or UVC_EVENT_STREAMOFF event. It expe

Re: [PATCH] uvc-gadget: Fix Set Interface (alternate setting) response behaviour

Laurent, On 06/03/17 22:50, Laurent Pinchart wrote: > Hi Roger, > > Thank you for the patch. > > On Friday 03 Mar 2017 13:17:15 Roger Quadros wrote: >> On alternate setting change, webcam gadget sends us a UVC_EVENT_STREAMON >> or UVC_EVENT_STREAMOFF event. It expe

[PATCH] uvc-gadget: Fix Set Interface (alternate setting) response behaviour

<<< No Message Collected >>>

[PATCH] uvc-gadget: Fix Set Interface (alternate setting) response behaviour

<<< No Message Collected >>>

[PATCH] Revert "usb: gadget: uvc: Add missing call for additional setup data"

. The bad commit was causing a duplicate response to be sent with incorrect response data thus causing UVC probe to fail at the host and broken control transfer endpoint at the gadget. [1] - git://git.ideasonboard.org/uvc-gadget.git Cc: <sta...@vger.kernel.org> # v4.9+ Signed-off-by: Roger Quadro

[PATCH] Revert "usb: gadget: uvc: Add missing call for additional setup data"

. The bad commit was causing a duplicate response to be sent with incorrect response data thus causing UVC probe to fail at the host and broken control transfer endpoint at the gadget. [1] - git://git.ideasonboard.org/uvc-gadget.git Cc: # v4.9+ Signed-off-by: Roger Quadros --- drivers/usb/gadget

Re: [PATCH v2 4/4] usb: dwc3: Workaround for super-speed host on dra7 in dual-role mode

On 25/02/17 05:35, Chanwoo Choi wrote: > Hi Roger, > > [snip] > >> /* dwc->lock must be held */ >> static void dwc3_otg_core_exit(struct dwc3 *dwc) >> { >> + if (dwc->edev) >> + return; >> + >> /* disable all otg irqs */ >> dwc3_otg_disable_events(dwc,

Re: [PATCH v2 4/4] usb: dwc3: Workaround for super-speed host on dra7 in dual-role mode

On 25/02/17 05:35, Chanwoo Choi wrote: > Hi Roger, > > [snip] > >> /* dwc->lock must be held */ >> static void dwc3_otg_core_exit(struct dwc3 *dwc) >> { >> + if (dwc->edev) >> + return; >> + >> /* disable all otg irqs */ >> dwc3_otg_disable_events(dwc,

Re: [PATCH v2 4/4] usb: dwc3: Workaround for super-speed host on dra7 in dual-role mode

+Chanwoo Hi Vivek, On 23/02/17 10:34, Vivek Gautam wrote: > > > On 02/16/2017 06:36 PM, Roger Quadros wrote: >> dra7 OTG core limits the host controller to USB2.0 (high-speed) mode >> when we're operating in dual-role. >> >> We work around that by b

Re: [PATCH v2 4/4] usb: dwc3: Workaround for super-speed host on dra7 in dual-role mode

+Chanwoo Hi Vivek, On 23/02/17 10:34, Vivek Gautam wrote: > > > On 02/16/2017 06:36 PM, Roger Quadros wrote: >> dra7 OTG core limits the host controller to USB2.0 (high-speed) mode >> when we're operating in dual-role. >> >> We work around that by b

[PATCH v2 0/4] usb: dwc3: dual-role support

if extcon phandle is present. - Fix bugs during system suspend/resume. cheers, -roger Roger Quadros (4): usb: dwc3: core.h: add some register definitions usb: dwc3: omap: don't miss events during suspend/resume usb: dwc3: add dual-role support usb: dwc3: Workaround for super-speed host

[PATCH v2 0/4] usb: dwc3: dual-role support

if extcon phandle is present. - Fix bugs during system suspend/resume. cheers, -roger Roger Quadros (4): usb: dwc3: core.h: add some register definitions usb: dwc3: omap: don't miss events during suspend/resume usb: dwc3: add dual-role support usb: dwc3: Workaround for super-speed host

[PATCH v2 1/4] usb: dwc3: core.h: add some register definitions

Add OTG and GHWPARAMS6 register definitions Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/usb/dwc3/core.h | 82 + 1 file changed, 82 insertions(+) diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h index d514dca..f

[PATCH v2 4/4] usb: dwc3: Workaround for super-speed host on dra7 in dual-role mode

dra7 OTG core limits the host controller to USB2.0 (high-speed) mode when we're operating in dual-role. We work around that by bypassing the OTG core and reading the extcon framework directly for ID/VBUS events. Signed-off-by: Roger Quadros <rog...@ti.com> --- Documentation/devicetree/bi

[PATCH v2 1/4] usb: dwc3: core.h: add some register definitions

Add OTG and GHWPARAMS6 register definitions Signed-off-by: Roger Quadros --- drivers/usb/dwc3/core.h | 82 + 1 file changed, 82 insertions(+) diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h index d514dca..fc82d2e 100644

[PATCH v2 4/4] usb: dwc3: Workaround for super-speed host on dra7 in dual-role mode

dra7 OTG core limits the host controller to USB2.0 (high-speed) mode when we're operating in dual-role. We work around that by bypassing the OTG core and reading the extcon framework directly for ID/VBUS events. Signed-off-by: Roger Quadros --- Documentation/devicetree/bindings/usb/dwc3.txt

[PATCH v2 2/4] usb: dwc3: omap: don't miss events during suspend/resume

The USB cable state can change during suspend/resume so be sure to check and update the extcon state. Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/usb/dwc3/dwc3-omap.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/usb/dwc3/dwc3-omap.c b/drive

[PATCH v2 3/4] usb: dwc3: add dual-role support

OST - Host controller active 1 0 B_IDLE - Both Host and Gadget controllers inactive 1 1 B_PERIPHERAL - Gadget controller active Calling dwc3_otg_fsm_sync() directly from dwc3_complete() can lock up the system at xHCI add/remove so we use a work queue for it. Signed-off-by: Rog

[PATCH v2 2/4] usb: dwc3: omap: don't miss events during suspend/resume

The USB cable state can change during suspend/resume so be sure to check and update the extcon state. Signed-off-by: Roger Quadros --- drivers/usb/dwc3/dwc3-omap.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/usb/dwc3/dwc3-omap.c b/drivers/usb/dwc3/dwc3-omap.c

[PATCH v2 3/4] usb: dwc3: add dual-role support

OST - Host controller active 1 0 B_IDLE - Both Host and Gadget controllers inactive 1 1 B_PERIPHERAL - Gadget controller active Calling dwc3_otg_fsm_sync() directly from dwc3_complete() can lock up the system at xHCI add/remove so we use a work queue for it. Signed-off-by: Rog

[PATCH v2 2/3] usb: dwc3: use BIT() macro where possible

To avoid checkpatch warnings with new patches let's start using the BIT() macro wherever possible. Signed-off-by: Roger Quadros <rog...@ti.com> --- v2: -include bitops.h drivers/usb/dwc3/core.h | 193 ++- drivers/usb/dwc3/dwc3-omap.c

[PATCH v2 2/3] usb: dwc3: use BIT() macro where possible

To avoid checkpatch warnings with new patches let's start using the BIT() macro wherever possible. Signed-off-by: Roger Quadros --- v2: -include bitops.h drivers/usb/dwc3/core.h | 193 ++- drivers/usb/dwc3/dwc3-omap.c | 48 +-- drivers/usb

Re: [PATCH 2/3] usb: dwc3: use BIT() macro where possible

On 16/02/17 10:54, Felipe Balbi wrote: > > Hi, > > Roger Quadros <rog...@ti.com> writes: >> On 15/02/17 13:44, Felipe Balbi wrote: >>> >>> Hi, >>> >>> Roger Quadros <rog...@ti.com> writes: >>>> To avoid checkpatch warn

Re: [PATCH 2/3] usb: dwc3: use BIT() macro where possible

On 16/02/17 10:54, Felipe Balbi wrote: > > Hi, > > Roger Quadros writes: >> On 15/02/17 13:44, Felipe Balbi wrote: >>> >>> Hi, >>> >>> Roger Quadros writes: >>>> To avoid checkpatch warnings with new patches let's >&g

Re: [PATCH 2/3] usb: dwc3: use BIT() macro where possible

On 15/02/17 13:44, Felipe Balbi wrote: > > Hi, > > Roger Quadros <rog...@ti.com> writes: >> To avoid checkpatch warnings with new patches let's >> start using the BIT() macro wherever possible. >> >> Signed-off-by: Roger Quadros <rog...@ti.com&g

Re: [PATCH 2/3] usb: dwc3: use BIT() macro where possible

On 15/02/17 13:44, Felipe Balbi wrote: > > Hi, > > Roger Quadros writes: >> To avoid checkpatch warnings with new patches let's >> start using the BIT() macro wherever possible. >> >> Signed-off-by: Roger Quadros >>

[PATCH 0/2] extcon: palmas/usb-gpio: Don't miss events during suspend/resume

Hi, This series ensures that we don't miss USB VBUS/ID event changes across system suspend/resume. cheers, -roger Roger Quadros (2): extcon: usb-gpio: Don't miss event during suspend/resume extcon: palmas: Don't miss GPIO events during suspend/resume drivers/extcon/extcon-palmas.c | 6

[PATCH 0/2] extcon: palmas/usb-gpio: Don't miss events during suspend/resume

Hi, This series ensures that we don't miss USB VBUS/ID event changes across system suspend/resume. cheers, -roger Roger Quadros (2): extcon: usb-gpio: Don't miss event during suspend/resume extcon: palmas: Don't miss GPIO events during suspend/resume drivers/extcon/extcon-palmas.c | 6

[PATCH 1/2] extcon: usb-gpio: Don't miss event during suspend/resume

We must check for ID/VBUS changes during resume irrespective of whether our device wakeup is enabled or not. Without this we seem to be missing ID/VBUS events after system suspend/resume. Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/extcon/extcon-usb-gpio.c | 5 ++--- 1 file c

[PATCH 1/2] extcon: usb-gpio: Don't miss event during suspend/resume

We must check for ID/VBUS changes during resume irrespective of whether our device wakeup is enabled or not. Without this we seem to be missing ID/VBUS events after system suspend/resume. Signed-off-by: Roger Quadros --- drivers/extcon/extcon-usb-gpio.c | 5 ++--- 1 file changed, 2 insertions

[PATCH 2/2] extcon: palmas: Don't miss GPIO events during suspend/resume

The USB cable state can change during suspend/resume so be sure to check and update the extcon state. Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/extcon/extcon-palmas.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/extcon/extcon-palmas.c b/drivers/extcon/

[PATCH 2/2] extcon: palmas: Don't miss GPIO events during suspend/resume

The USB cable state can change during suspend/resume so be sure to check and update the extcon state. Signed-off-by: Roger Quadros --- drivers/extcon/extcon-palmas.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/extcon/extcon-palmas.c b/drivers/extcon/extcon-palmas.c index

[PATCH] usb: dwc3: gadget: Fix system suspend/resume on TI platforms

) [ 141.998641] [] (kthread) from [] (ret_from_fork+0x14/0x24) [ 142.006213] ---[ end trace b4ecfe9f175b9a9c ]--- Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/usb/dwc3/gadget.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/usb/dwc3/gadget.c b/drivers/us

[PATCH] usb: dwc3: gadget: Fix system suspend/resume on TI platforms

) [ 141.998641] [] (kthread) from [] (ret_from_fork+0x14/0x24) [ 142.006213] ---[ end trace b4ecfe9f175b9a9c ]--- Signed-off-by: Roger Quadros --- drivers/usb/dwc3/gadget.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c index

[PATCH 3/3] usb: otg-fsm: Prevent build warning "VDBG" redefined

, from drivers/usb/dwc3/ep0.c:33: include/linux/usb/otg-fsm.h:30:1: warning: "VDBG" redefined In file included from drivers/usb/dwc3/ep0.c:31: include/linux/usb/composite.h:615:1: warning: this is the location of the previous definition Signed-off-by: Roger Quadros <rog...@ti.

[PATCH 3/3] usb: otg-fsm: Prevent build warning "VDBG" redefined

, from drivers/usb/dwc3/ep0.c:33: include/linux/usb/otg-fsm.h:30:1: warning: "VDBG" redefined In file included from drivers/usb/dwc3/ep0.c:31: include/linux/usb/composite.h:615:1: warning: this is the location of the previous definition Signed-off-by: Roger Quadros Reviewed-

[PATCH 0/3] usb: dwc3: trivial fixes.

Hi Felipe, These are some trivial fixes. First patch is tagged for stable. You might want to pick it up for v4.11. Thanks. cheers, -roger Roger Quadros (3): usb: dwc3-omap: Fix missing break in dwc3_omap_set_mailbox() usb: dwc3: use BIT() macro where possible usb: otg-fsm: Prevent build

[PATCH 0/3] usb: dwc3: trivial fixes.

Hi Felipe, These are some trivial fixes. First patch is tagged for stable. You might want to pick it up for v4.11. Thanks. cheers, -roger Roger Quadros (3): usb: dwc3-omap: Fix missing break in dwc3_omap_set_mailbox() usb: dwc3: use BIT() macro where possible usb: otg-fsm: Prevent build

[PATCH 2/3] usb: dwc3: use BIT() macro where possible

To avoid checkpatch warnings with new patches let's start using the BIT() macro wherever possible. Signed-off-by: Roger Quadros <rog...@ti.com> --- drivers/usb/dwc3/core.h | 192 +-- drivers/usb/dwc3/dwc3-omap.c | 48 +-- drivers/us

[PATCH 2/3] usb: dwc3: use BIT() macro where possible

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 | 192 +-- drivers/usb/dwc3/dwc3-omap.c | 48 +-- drivers/usb/dwc3/gadget.h| 20

[PATCH 1/3] usb: dwc3-omap: Fix missing break in dwc3_omap_set_mailbox()

We need to break from all cases if we want to treat each one of them separately. Reported-by: Gustavo A. R. Silva <garsi...@embeddedor.com> Fixes: d2728fb3e01f ("usb: dwc3: omap: Pass VBUS and ID events transparently") Cc: <sta...@vger.kernel.org> #v4.8+ Signed-off-

[PATCH 1/3] usb: dwc3-omap: Fix missing break in dwc3_omap_set_mailbox()

We need to break from all cases if we want to treat each one of them separately. Reported-by: Gustavo A. R. Silva Fixes: d2728fb3e01f ("usb: dwc3: omap: Pass VBUS and ID events transparently") Cc: #v4.8+ Signed-off-by: Roger Quadros --- drivers/usb/dwc3/dwc3-omap.c | 1 + 1 file

Re: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration

+Felipe, On 15/02/17 10:51, Peter Chen wrote: > On Wed, Feb 15, 2017 at 10:18:03AM +0200, Roger Quadros wrote: >> Peter, >> >> On 15/02/17 03:35, Peter Chen wrote: >>> On Tue, Feb 14, 2017 at 01:58:40PM +0100, Arnd Bergmann wrote: >>>> On Tue, Feb 14, 201

Re: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration

+Felipe, On 15/02/17 10:51, Peter Chen wrote: > On Wed, Feb 15, 2017 at 10:18:03AM +0200, Roger Quadros wrote: >> Peter, >> >> On 15/02/17 03:35, Peter Chen wrote: >>> On Tue, Feb 14, 2017 at 01:58:40PM +0100, Arnd Bergmann wrote: >>>> On Tue, Feb

Re: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration

Peter, On 15/02/17 03:35, Peter Chen wrote: > On Tue, Feb 14, 2017 at 01:58:40PM +0100, Arnd Bergmann wrote: >> On Tue, Feb 14, 2017 at 1:26 PM, Roger Quadros <rog...@ti.com> wrote: >>> On 14/02/17 13:44, Arnd Bergmann wrote: >>>> On Tue, Feb 14, 2017 at 11

Re: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration

Peter, On 15/02/17 03:35, Peter Chen wrote: > On Tue, Feb 14, 2017 at 01:58:40PM +0100, Arnd Bergmann wrote: >> On Tue, Feb 14, 2017 at 1:26 PM, Roger Quadros wrote: >>> On 14/02/17 13:44, Arnd Bergmann wrote: >>>> On Tue, Feb 14, 2017 at 11:36 AM, Roger Quadros wr

Re: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration

On 14/02/17 13:44, Arnd Bergmann wrote: > On Tue, Feb 14, 2017 at 11:36 AM, Roger Quadros <rog...@ti.com> wrote: >> On 11/02/17 03:27, Peter Chen wrote: >>> From: Arnd Bergmann <a...@arndb.de> >>> >>> For xhci-hcd platform device, all the DMA paramet

Re: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration

On 14/02/17 13:44, Arnd Bergmann wrote: > On Tue, Feb 14, 2017 at 11:36 AM, Roger Quadros wrote: >> On 11/02/17 03:27, Peter Chen wrote: >>> From: Arnd Bergmann >>> >>> For xhci-hcd platform device, all the DMA parameters are not >>> configured proper

Re: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration

Hi, On 11/02/17 03:27, Peter Chen wrote: > From: Arnd Bergmann > > For xhci-hcd platform device, all the DMA parameters are not > configured properly, notably dma ops for dwc3 devices. So, set > the dma for xhci from sysdev. sysdev is pointing to device that > is known to the

Re: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration

Hi, On 11/02/17 03:27, Peter Chen wrote: > From: Arnd Bergmann > > For xhci-hcd platform device, all the DMA parameters are not > configured properly, notably dma ops for dwc3 devices. So, set > the dma for xhci from sysdev. sysdev is pointing to device that > is known to the system firmware or

Re: [PATCH v13 00/12] power: add power sequence library

Peter, On 11/02/17 03:27, Peter Chen wrote: > Hi all, > > This is a follow-up for my last power sequence framework patch set [1]. > According to Rob Herring and Ulf Hansson's comments[2]. The kinds of > power sequence instances will be added at postcore_initcall, the match > criteria is

Re: [PATCH v13 00/12] power: add power sequence library

Peter, On 11/02/17 03:27, Peter Chen wrote: > Hi all, > > This is a follow-up for my last power sequence framework patch set [1]. > According to Rob Herring and Ulf Hansson's comments[2]. The kinds of > power sequence instances will be added at postcore_initcall, the match > criteria is

Re: [PATCH v12 6/9] usb: xhci: use bus->sysdev for DMA configuration

On 09/02/17 13:53, Roger Quadros wrote: > > > On 08/02/17 22:43, Jack Pham wrote: >> Hi Peter, Sriram, Arnd, >> >> On Mon, Feb 06, 2017 at 05:13:38PM +0800, Peter Chen wrote: >>> From: Arnd Bergmann <a...@arndb.de> >>> >&

Re: [PATCH v12 6/9] usb: xhci: use bus->sysdev for DMA configuration

On 09/02/17 13:53, Roger Quadros wrote: > > > On 08/02/17 22:43, Jack Pham wrote: >> Hi Peter, Sriram, Arnd, >> >> On Mon, Feb 06, 2017 at 05:13:38PM +0800, Peter Chen wrote: >>> From: Arnd Bergmann >>> >>> For xhci-hcd platform device,

Re: [PATCH v12 6/9] usb: xhci: use bus->sysdev for DMA configuration

On 08/02/17 22:43, Jack Pham wrote: > Hi Peter, Sriram, Arnd, > > On Mon, Feb 06, 2017 at 05:13:38PM +0800, Peter Chen wrote: >> From: Arnd Bergmann >> >> For xhci-hcd platform device, all the DMA parameters are not >> configured properly, notably dma ops for dwc3 devices. So,

Re: [PATCH v12 6/9] usb: xhci: use bus->sysdev for DMA configuration

On 08/02/17 22:43, Jack Pham wrote: > Hi Peter, Sriram, Arnd, > > On Mon, Feb 06, 2017 at 05:13:38PM +0800, Peter Chen wrote: >> From: Arnd Bergmann >> >> For xhci-hcd platform device, all the DMA parameters are not >> configured properly, notably dma ops for dwc3 devices. So, set >> the dma

Re: drivers: usb: dwc3: A question...

Hi, On 09/02/17 10:14, Gustavo A. R. Silva wrote: > Hello everybody, > > I ran into the following piece of code at drivers/usb/dwc3/dwc3-omap.c:218 > (linux-next) > > 218static void dwc3_omap_set_mailbox(struct dwc3_omap *omap, > 219enum omap_dwc3_vbus_id_status status) > 220{ > 221

Re: drivers: usb: dwc3: A question...

Hi, On 09/02/17 10:14, Gustavo A. R. Silva wrote: > Hello everybody, > > I ran into the following piece of code at drivers/usb/dwc3/dwc3-omap.c:218 > (linux-next) > > 218static void dwc3_omap_set_mailbox(struct dwc3_omap *omap, > 219enum omap_dwc3_vbus_id_status status) > 220{ > 221

Re: [PATCH 0/8] usb: dwc3: add dual-role support

Vivek, On 09/02/17 08:42, Vivek Gautam wrote: > Hi Roger, > > On Mon, Jan 23, 2017 at 4:49 PM, Roger Quadros <rog...@ti.com> wrote: >> Hi, >> >> We rely on the OTG controller block to provide us with >> VBUS and ID line status via an interrupt. >>

Re: [PATCH 0/8] usb: dwc3: add dual-role support

Vivek, On 09/02/17 08:42, Vivek Gautam wrote: > Hi Roger, > > On Mon, Jan 23, 2017 at 4:49 PM, Roger Quadros wrote: >> Hi, >> >> We rely on the OTG controller block to provide us with >> VBUS and ID line status via an interrupt. >> >> This is th

Re: [PATCH 6/8] ARM: dts: dra7x-evm: Enable dual-role mode for USB1

On 26/01/17 17:56, Tony Lindgren wrote: > * Roger Quadros <rog...@ti.com> [170123 03:21]: >> USB1 port is micro-AB type and can function as peripheral >> as well as host. Enable dual-role mode for USB1. > > Good to see this happening :) Can you please send the dts

<    4   5   6   7   8   9   10   11   12   13   >