[PATCH 0/5] dwc3: omap: adapt dwc3 to use extcon framework
The first three patches deals with cleanup of extcon inorder to get through compilation without any issues. It also adds an API to get extcon device from dt node which I felt was missing. The next two patches deals with adapt dwc3 to use extcon framework. The 4th patch (usb: dwc3: omap: improve error handling of dwc3_omap_probe) should have ideally been sent to Felipe, however since there will be merge conflicts with the 5th patch (usb: dwc3: use extcon fwrk to receive connect/disconnect) in this series, I've sent in the same series. Once this patch series get merged, dwc3 in omap would be functional in device mode. However there is still some discussion on modelling SMPS10 regulator. Once that gets finalized, dwc3 should be functional in host mode as well. Kishon Vijay Abraham I (5): extcon: Add an API to get extcon device from dt node extcon: Kconfig: Make extcon config type as bool extcon: add EXPORT_SYMBOL_GPL for exported functions usb: dwc3: omap: improve error handling of dwc3_omap_probe usb: dwc3: use extcon fwrk to receive connect/disconnect Documentation/devicetree/bindings/usb/omap-usb.txt |5 + drivers/extcon/Kconfig |2 +- drivers/extcon/extcon-class.c | 42 +++ drivers/usb/dwc3/dwc3-omap.c | 133 include/linux/extcon.h |8 ++ include/linux/usb/dwc3-omap.h | 30 - 6 files changed, 168 insertions(+), 52 deletions(-) delete mode 100644 include/linux/usb/dwc3-omap.h -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/5] dwc3: omap: adapt dwc3 to use extcon framework
Hi Kishon, Sorry for late reply. I applied patch1,2 on extcon-linus branch. - http://git.kernel.org/cgit/linux/kernel/git/chanwoo/extcon.git/log/?h=extcon-linus But, I have comment of patch 3 about dt API. I send comment on patch 3 mailing thread. Thanks, Chanwoo Choi On 06/04/2013 01:13 AM, Kishon Vijay Abraham I wrote: > The first three patches deals with cleanup of extcon inorder to get > through compilation without any issues. It also adds an API to get > extcon device from dt node which I felt was missing. > > The next two patches deals with adapt dwc3 to use extcon framework. > The 4th patch (usb: dwc3: omap: improve error handling of dwc3_omap_probe) > should have ideally been sent to Felipe, however since > there will be merge conflicts with the 5th patch > (usb: dwc3: use extcon fwrk to receive connect/disconnect) > in this series, I've sent in the same series. > > Once this patch series get merged, dwc3 in omap would be functional > in device mode. However there is still some discussion on modelling > SMPS10 regulator. Once that gets finalized, dwc3 should be functional > in host mode as well. > > Kishon Vijay Abraham I (5): > extcon: Add an API to get extcon device from dt node > extcon: Kconfig: Make extcon config type as bool > extcon: add EXPORT_SYMBOL_GPL for exported functions > usb: dwc3: omap: improve error handling of dwc3_omap_probe > usb: dwc3: use extcon fwrk to receive connect/disconnect > > Documentation/devicetree/bindings/usb/omap-usb.txt |5 + > drivers/extcon/Kconfig |2 +- > drivers/extcon/extcon-class.c | 42 +++ > drivers/usb/dwc3/dwc3-omap.c | 133 > > include/linux/extcon.h |8 ++ > include/linux/usb/dwc3-omap.h | 30 - > 6 files changed, 168 insertions(+), 52 deletions(-) > delete mode 100644 include/linux/usb/dwc3-omap.h > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/5] dwc3: omap: adapt dwc3 to use extcon framework
Hi Kishon, I confused patch number. I applied patch2,3 on extcon-linus branch. extcon: Kconfig: Make extcon config type as bool extcon: add EXPORT_SYMBOL_GPL for exported functions And I will reply comment about patch1 soon. extcon: Add an API to get extcon device from dt node Thanks, Chanwoo Choi On 06/04/2013 01:13 AM, Kishon Vijay Abraham I wrote: > The first three patches deals with cleanup of extcon inorder to get > through compilation without any issues. It also adds an API to get > extcon device from dt node which I felt was missing. > > The next two patches deals with adapt dwc3 to use extcon framework. > The 4th patch (usb: dwc3: omap: improve error handling of dwc3_omap_probe) > should have ideally been sent to Felipe, however since > there will be merge conflicts with the 5th patch > (usb: dwc3: use extcon fwrk to receive connect/disconnect) > in this series, I've sent in the same series. > > Once this patch series get merged, dwc3 in omap would be functional > in device mode. However there is still some discussion on modelling > SMPS10 regulator. Once that gets finalized, dwc3 should be functional > in host mode as well. > > Kishon Vijay Abraham I (5): > extcon: Add an API to get extcon device from dt node > extcon: Kconfig: Make extcon config type as bool > extcon: add EXPORT_SYMBOL_GPL for exported functions > usb: dwc3: omap: improve error handling of dwc3_omap_probe > usb: dwc3: use extcon fwrk to receive connect/disconnect > > Documentation/devicetree/bindings/usb/omap-usb.txt |5 + > drivers/extcon/Kconfig |2 +- > drivers/extcon/extcon-class.c | 42 +++ > drivers/usb/dwc3/dwc3-omap.c | 133 > > include/linux/extcon.h |8 ++ > include/linux/usb/dwc3-omap.h | 30 - > 6 files changed, 168 insertions(+), 52 deletions(-) > delete mode 100644 include/linux/usb/dwc3-omap.h > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/5] dwc3: omap: adapt dwc3 to use extcon framework
Kishon, What is the expectation when there is no palmas tied to dwc3/dwc3-omap ? Thank you Regards Ruchika On 06/03/2013 11:13 AM, Kishon Vijay Abraham I wrote: The first three patches deals with cleanup of extcon inorder to get through compilation without any issues. It also adds an API to get extcon device from dt node which I felt was missing. The next two patches deals with adapt dwc3 to use extcon framework. The 4th patch (usb: dwc3: omap: improve error handling of dwc3_omap_probe) should have ideally been sent to Felipe, however since there will be merge conflicts with the 5th patch (usb: dwc3: use extcon fwrk to receive connect/disconnect) in this series, I've sent in the same series. Once this patch series get merged, dwc3 in omap would be functional in device mode. However there is still some discussion on modelling SMPS10 regulator. Once that gets finalized, dwc3 should be functional in host mode as well. Kishon Vijay Abraham I (5): extcon: Add an API to get extcon device from dt node extcon: Kconfig: Make extcon config type as bool extcon: add EXPORT_SYMBOL_GPL for exported functions usb: dwc3: omap: improve error handling of dwc3_omap_probe usb: dwc3: use extcon fwrk to receive connect/disconnect Documentation/devicetree/bindings/usb/omap-usb.txt |5 + drivers/extcon/Kconfig |2 +- drivers/extcon/extcon-class.c | 42 +++ drivers/usb/dwc3/dwc3-omap.c | 133 include/linux/extcon.h |8 ++ include/linux/usb/dwc3-omap.h | 30 - 6 files changed, 168 insertions(+), 52 deletions(-) delete mode 100644 include/linux/usb/dwc3-omap.h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/5] dwc3: omap: adapt dwc3 to use extcon framework
Hi Ruchika, On Tuesday 04 June 2013 07:53 PM, Ruchika Kharwar wrote: Kishon, What is the expectation when there is no palmas tied to dwc3/dwc3-omap ? In the probe of dwc3-omap I have this check "if (of_property_read_bool(node, "extcon"))" So If dwc3 node does not have extcon property, it wont try to get extcon device at all. You can refer this patch to see how its handled usb: dwc3: use extcon fwrk to receive connect/disconnect. Thanks Kishon -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html