Re: [PATCH 2/6] usb: core: TPL should apply for both OTG and EH

Hi Peter, On Thu, Aug 07, 2014 at 02:45:15PM +0800, Peter Chen wrote: > According to On-The-Go and Embedded Host Supplement to the USB Revision > 2.0 Specification, the targeted hosts (non-PC hosts) include both > embedded hosts and otg, and each targeted host product defines the > set of supporte

Re: [PATCH] USB: pch_udc: USB gadget device support for Intel Quark X1000

On Mon, Aug 11, 2014 at 05:21:50AM +, Chen, Alvin wrote: > Hi Felipe, > > Any update for this patch? Just want to follow-up. It's the middle of the merge window, we can't do anything until 3.17-rc1 is out, please relax... greg k-h -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH] USB: pch_udc: USB gadget device support for Intel Quark X1000

Hi Felipe, Any update for this patch? Just want to follow-up. > -Original Message- > From: Chen, Alvin > Sent: Tuesday, August 05, 2014 1:23 AM > To: Felipe Balbi > Cc: linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org; Ong, Boon > Leong > Subject: [PATCH] USB: pch_udc: USB gadget

[PATCH v2 6/6] doc: dt-binding: ci-hdrc-imx: add TPL support

TPL (Targeted Peripheral List) is needed for targets host (OTG and Embedded Hosts) for usb certification and other vendor specific requirements. Signed-off-by: Peter Chen --- .../devicetree/bindings/usb/ci-hdrc-imx.txt|2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation

[PATCH v2 0/6] usb: host: change TPL support behaviour

Changes for v2: - Move TPL support judgement out of is_target, the user can be easy to know if it needs to do TPL judgement. [patch 1/6] - Keep the unsupport device message unchange [patch 1/6] According to On-The-Go and Embedded Host Supplement to the USB Revision 2.0 Specification, a Targeted Ho

[PATCH v2 5/6] usb: chipidea: add TPL support for targeted hosts

For OTG and Embedded hosts, they may need TPL (Targeted Peripheral List) for usb certification and other vender specific requirements, the platform can tell chipidea core driver if it supports tpl through DT or platform data. Signed-off-by: Peter Chen --- drivers/usb/chipidea/core.c |4

[PATCH v2 2/6] usb: core: TPL should apply for both OTG and EH

According to On-The-Go and Embedded Host Supplement to the USB Revision 2.0 Specification, the targeted hosts (non-PC hosts) include both embedded hosts and otg, and each targeted host product defines the set of supported peripherals on a TPL (Targeted Peripheral List). So, TPL should apply for bot

[PATCH v2 3/6] usb: core: Kconfig: TPL should apply for both OTG and EH

Update configuration for USB_OTG_WHITELIST, any targeted hosts (non PC-hosts) can have TPL (Targered Peripheral List). Signed-off-by: Peter Chen --- drivers/usb/core/Kconfig | 12 +++- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/drivers/usb/core/Kconfig b/drivers/usb/

[PATCH v2 4/6] usb: common: add API to get if the platform supports TPL

The TPL (Targeted Peripheral List) is used for targeted hosts (non-PC hosts), and it can be used at USB OTG & EH certification and some specific products which need white list. Signed-off-by: Peter Chen --- drivers/usb/common/usb-common.c | 15 +++ include/linux/usb/of.h |

[PATCH v2 1/6] usb: hcd: add TPL support flag

The targeted hosts (non-PC hosts) need to have TPL (Targeted Peripheral List) for USB OTG & EH certification and other vendor specific requirements. The platform who needs TPL feature should set this flag at usb host controller driver. Signed-off-by: Peter Chen --- include/linux/usb/hcd.h |

Re: [PATCH] usb: phy: drop kfree of devm_kzalloc's data

On Monday, August 11, 2014 5:00 AM, Himangi Saraogi wrote: > > Using kfree to free data allocated with devm_kzalloc causes double frees. > > The Coccinelle semantic patch that fixes this problem is as follows: > > // > @@ > expression x; > @@ > > x = devm_kzalloc(...) > ... > ?-kfree(x); > //

RE: [RFC PATCH] Revert "usb: chipidea: udc: .pullup is valid only when vbus is there"

> > Hello Peter, > > I have seen this call is still returning EOPNOTSUPP which is also > returned by usb_gadget_connect and usb_gadget_disconnect if the pullup > function is not available. Should it not handle that case somehow special? > > > Is it still a valid condition to bailout if vbus

[PATCH] usb: phy: drop kfree of devm_kzalloc's data

Using kfree to free data allocated with devm_kzalloc causes double frees. The Coccinelle semantic patch that fixes this problem is as follows: // @@ expression x; @@ x = devm_kzalloc(...) ... ?-kfree(x); // Signed-off-by: Himangi Saraogi Acked-by: Julia Lawall --- drivers/usb/phy/phy-gpio-

[PATCH] USB: dbgp gadget: fix use after free in dbgp_unbind()

After dbgp_bind()-dbgp_unbind() cycle happens, static variable dbgp contains pointers to already deallocated memory (dbgp.serial and dbgp.req). If the next dbgp_bind() fails, for example in usb_ep_alloc_request(), dbgp_bind() calls dbgp_unbind() on failure path, and dbgp_unbind() frees dbgp.serial