Re: [PATCH v2] can: kvaser_usb: Add support for Kvaser CAN/USB devices

On Monday 06 August 2012 07:21:29 Olivier Sobrie wrote: > This driver provides support for several Kvaser CAN/USB devices. > Such kind of devices supports up to three can network interfaces. > > It has been tested with a Kvaser USB Leaf Light (one network interface) > connected to a pch_can interf

Re: [PATCH 1/5] usb: phy: samsung: Introducing usb phy driver for hsotg

Hi Heiko, On Mon, Aug 6, 2012 at 3:24 AM, Heiko Stübner wrote: > Hi Praveen, > > Am Mittwoch, 1. August 2012, 15:05:47 schrieb Praveen Paneri: >> This driver uses usb_phy interface to interact with s3c-hsotg. Supports >> phy_init and phy_shutdown functions to enable/disable phy. Tested with >> sm

Re: [PATCH 1/5] usb: phy: samsung: Introducing usb phy driver for hsotg

Hi Praveen, On 8/6/12, Praveen Paneri wrote: > Hi Heiko, > > On Mon, Aug 6, 2012 at 3:24 AM, Heiko Stübner wrote: >> Hi Praveen, >> >> Am Mittwoch, 1. August 2012, 15:05:47 schrieb Praveen Paneri: >>> This driver uses usb_phy interface to interact with s3c-hsotg. Supports >>> phy_init and phy_sh

Re: [RFC][PATCH 1/4 v3] usb: host: ehci-platform: BUG_ON() to WARN_ON() on probe

On Sun, Aug 05, 2012 at 06:51:34PM -0700, kuninori.morimoto...@renesas.com wrote: > We should avoid using BUG_ON() in drivers. > This patch switch to use WARN_ON() from BUG_ON(), > and avoid NULL pointer access by new macro. > > Signed-off-by: Kuninori Morimoto > --- > v2 -> v3 > > - BUG_ON ->

Re: [RFC][PATCH 1/4 v3] usb: host: ehci-platform: BUG_ON() to WARN_ON() on probe

Hi Simon Thank you for checking patch > > +#define ehci_pdata_get(pdata, x) ((pdata) ? (pdata)->x : 0) > > + > > FWIW, I think that an inline function would be a slight improvement over > a macro here. Likewise for the 2nd patch of this series. All these patches have this kind of macros. I ne

Re: [PATCH v6 01/11] drivers: usb: otg: add a new driver for omap usb2 phy

Hi, On Fri, Aug 03, 2012 at 08:01:44PM +0530, ABRAHAM, KISHON VIJAY wrote: > >> + return 0; > >> +} > >> + > >> +#ifdef CONFIG_PM_RUNTIME > >> + > >> +static int omap_usb2_runtime_suspend(struct device *dev) > >> +{ > >> + struct platform_device *pdev = to_platform_device(dev); > >> +

Re: [PATCH v6 00/11] omap: musb: Add device tree support

Hi, On Mon, Jul 30, 2012 at 02:39:49PM +0530, Kishon Vijay Abraham I wrote: > This patch series adds device tree support for MUSB and device > tree support for all the related modules to get MUSB working in > OMAP platform. > > A new omap-usb2 phy driver has been added (with only dt suppport) > t

Re: [PATCH v6 00/11] omap: musb: Add device tree support

On Mon, Aug 6, 2012 at 2:22 PM, Felipe Balbi wrote: > Hi, > > On Mon, Jul 30, 2012 at 02:39:49PM +0530, Kishon Vijay Abraham I wrote: >> This patch series adds device tree support for MUSB and device >> tree support for all the related modules to get MUSB working in >> OMAP platform. >> >> A new o

Re: [PATCH 1/5] usb: phy: samsung: Introducing usb phy driver for hsotg

Am Montag, 6. August 2012, 10:23:52 schrieb Kyungmin Park: > Hi Praveen, > > On 8/6/12, Praveen Paneri wrote: > > Hi Heiko, > > > > On Mon, Aug 6, 2012 at 3:24 AM, Heiko Stübner wrote: > >> Hi Praveen, > >> > >> Am Mittwoch, 1. August 2012, 15:05:47 schrieb Praveen Paneri: > >>> This driver us

Re: [PATCH v6 01/11] drivers: usb: otg: add a new driver for omap usb2 phy

Hi Felipe, On Mon, Aug 6, 2012 at 2:19 PM, Felipe Balbi wrote: > Hi, > > On Fri, Aug 03, 2012 at 08:01:44PM +0530, ABRAHAM, KISHON VIJAY wrote: >> >> + return 0; >> >> +} >> >> + >> >> +#ifdef CONFIG_PM_RUNTIME >> >> + >> >> +static int omap_usb2_runtime_suspend(struct device *dev) >> >> +{ >

[PATCH] USB: ftdi_sio: Quiet sparse noise about using plain integer was NULL pointer

Pointers should not be compared to plain integers. Quiets the sparse warning: warning: Using plain integer as NULL pointer Signed-off-by: Ying Xue --- drivers/usb/serial/ftdi_sio.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/u

Re: [PATCH v6 01/11] drivers: usb: otg: add a new driver for omap usb2 phy

On Mon, Aug 06, 2012 at 03:14:42PM +0530, ABRAHAM, KISHON VIJAY wrote: > >> >> +static int omap_usb2_runtime_resume(struct device *dev) > >> >> +{ > >> >> + u32 ret = 0; > >> >> + struct platform_device *pdev = to_platform_device(dev); > >> >> + struct omap_usb *phy = platform_get_drvd

Re: [PATCH 1/5] usb: phy: samsung: Introducing usb phy driver for hsotg

Hi, On Mon, Aug 6, 2012 at 2:53 PM, Heiko Stübner wrote: > Am Montag, 6. August 2012, 10:23:52 schrieb Kyungmin Park: >> Hi Praveen, >> >> On 8/6/12, Praveen Paneri wrote: >> > Hi Heiko, >> > >> > On Mon, Aug 6, 2012 at 3:24 AM, Heiko Stübner wrote: >> >> Hi Praveen, >> >> >> >> Am Mittwoch, 1.

[PATCH] usb/dwc3: Correct DEPCFG for Config Action "Modify"

From: Pratyush ANAND We need to issue DEPCFG (with Config Action Set to "Modify") as per specification. Even if we do not respect this , it works in normal cases. But, I have observed one failure in very peculiar situation. If cpu clock is very slow and execution of connection done ISR takes lo

[BUG] Kernel panic when try s3c-hsotg.c with kernel 3.5

I got a kernel panic when try hsotg of ok6410 which is based on s3c6410: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Unable to handle kernel NULL pointer dereference at virtual address 0100 pgd = c0004000 [0100] *pgd= Internal error: Oops: 5 [#1] AR

Re: [BUG] Kernel panic when try s3c-hsotg.c with kernel 3.5

Hi, On Mon, Aug 06, 2012 at 06:12:05PM +0800, Peiyong Feng wrote: > I got a kernel panic when try hsotg of ok6410 which is based on s3c6410: > > > cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters > Unable to handle kernel NULL pointer dereference at virtual address 000

[PATCH v3 2/2] arm/dts: omap4: Add ocp2scp data

Add ocp2scp data node in omap4 device tree file. Acked-by: Felipe Balbi Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/omap4.dtsi |8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi index 04cbbcb..8a780b2 100644

[PATCH v3 0/2] omap: add ocp2scp as a bus driver

This patch series is done as a preparatory step for adding phy drivers for dwc3 and musb. This series adds a new driver for ocp2scp (only dt) to which phy drivers are connected. Since currently there is no generic way to create a child device along with doing a pm_runtime_enable (the exact requir

[PATCH v3 1/2] drivers: bus: add a new driver for omap-ocp2scp

Adds a new driver *omap-ocp2scp*. This driver takes the responsibility of creating all the devices that is connected to OCP2SCP. In the case of OMAP4, USB2PHY is connected to ocp2scp. This also includes device tree support for ocp2scp driver and the documentation with device tree binding informati

Re: [PATCH v3 1/2] drivers: bus: add a new driver for omap-ocp2scp

On Mon, Aug 06, 2012 at 04:55:30PM +0530, Kishon Vijay Abraham I wrote: > Adds a new driver *omap-ocp2scp*. This driver takes the responsibility of > creating all the devices that is connected to OCP2SCP. In the case of OMAP4, > USB2PHY is connected to ocp2scp. > > This also includes device tree s

Re: [PATCH] usb/dwc3: Correct DEPCFG for Config Action "Modify"

Hi, On Mon, Aug 06, 2012 at 03:33:16PM +0530, Pratyush Anand wrote: > From: Pratyush ANAND > > We need to issue DEPCFG (with Config Action Set to "Modify") as per > specification. Even if we do not respect this , it works in normal > cases. But, I have observed one failure in very peculiar situ

[RFC/PATCH v4] usb: dwc3: Introduce OTG driver for dwc3

This is first release of otg driver for the dwc3 Synopsys USB3 core. The otg driver implements the otg final state machine and control the activation of the device controller or host controller. In this first implementation, only simple DRD mode is implemented, determine if A or B device according

[PATCH v7 6/7] drivers: usb: musb: Add device tree support for omap musb glue

Added device tree support for omap musb driver and updated the Documentation with device tree binding information. Signed-off-by: Kishon Vijay Abraham I --- Documentation/devicetree/bindings/usb/omap-usb.txt | 34 +++- drivers/usb/musb/omap2430.c| 54 +

[PATCH v7 2/7] arm: omap: hwmod: add a new addr space in otg for writing to control module

The mailbox register for usb otg in omap is present in control module. On detection of any events VBUS or ID, this register should be written to send the notification to musb core. Till we have a separate control module driver to write to control module, omap2430 will handle the register writes to

[PATCH v7 0/7] omap: musb: Add device tree support

This patch series adds device tree support for MUSB and device tree support for all the related modules to get MUSB working in OMAP platform. A new omap-usb2 phy driver has been added (with only dt suppport) to perform phy configurations. Previously this configuration was performed by twl6030, usi

[PATCH v7 4/7] drivers: usb: twl6030: Add dt support for twl6030 usb

Add device tree support for twl6030 usb driver. Update the Documentation with device tree binding information. Signed-off-by: Kishon Vijay Abraham I --- .../devicetree/bindings/usb/twl-usb.txt| 21 +++ drivers/usb/otg/twl6030-usb.c | 39 +-

[PATCH v7 7/7] arm: omap: phy: remove unused functions from omap-phy-internal.c

All the unnessary functions in omap-phy-internal is removed. These functionality are now handled by omap-usb2 phy driver. Cc: Felipe Balbi Signed-off-by: Kishon Vijay Abraham I Acked-by: Tony Lindgren --- arch/arm/mach-omap2/omap_phy_internal.c | 138 --- arch/arm/

[PATCH v7 1/7] drivers: usb: phy: add a new driver for omap usb2 phy

All phy related programming like enabling/disabling the clocks, powering on/off the phy is taken care of by this driver. It is also used for OTG related functionality like srp. This also includes device tree support for usb2 phy driver and the documentation with device tree binding information is

[PATCH v7 5/7] drivers: usb: twl4030: Add device tree support for twl4030 usb

Add device tree support for twl4030 usb driver. Update the Documentation with device tree binding information. Signed-off-by: Kishon Vijay Abraham I --- .../devicetree/bindings/usb/twl-usb.txt| 19 ++ drivers/usb/otg/twl4030-usb.c | 26 +++

[PATCH v7 3/7] drivers: usb: otg: make twl6030_usb as a comparator driver to omap_usb2

All the PHY configuration other than VBUS, ID GND and OTG SRP are removed from twl6030. The phy configurations are taken care by the dedicated usb2 phy driver. So twl6030 is made as comparator driver for VBUS and ID detection. Writing to control module which is now handled in omap2430.c should be

Re: [BUG] Kernel panic when try s3c-hsotg.c with kernel 3.5

Hi, > Hi, > > On Mon, Aug 06, 2012 at 06:12:05PM +0800, Peiyong Feng wrote: > > I got a kernel panic when try hsotg of ok6410 which is based on > > s3c6410: As you said, you are using the ok6410. And it is "based" on the s3c6410 CPU. S3C6410 is a single core CPU. I assume that ok6410 is also sing

Re: Linux 3.2: USB mouse not recognized after resuming from suspend to RAM

Am Mittwoch, den 20.06.2012, 17:34 +0200 schrieb Paul Menzel: > Am Mittwoch, den 20.06.2012, 11:11 -0400 schrieb Alan Stern: > > On Wed, 20 Jun 2012, Paul Menzel wrote: > > > > > [This message is more a less the same as sent to the Debian BTS > > >

Re: Do we need asynchronous pm_runtime_get()? (was: Re: bisected regression ...)

On Sun, Aug 5, 2012 at 11:26 PM, Rafael J. Wysocki wrote: > --- > drivers/base/power/runtime.c | 82 > +++ > include/linux/pm.h |1 > include/linux/pm_runtime.h | 14 +++ > 3 files changed, 90 insertions(+), 7 deletions(-) > > Inde

[PATCH v4 2/2] arm/dts: omap4: Add ocp2scp data

Add ocp2scp data node in omap4 device tree file. Acked-by: Felipe Balbi Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/omap4.dtsi |8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi index 04cbbcb..8a780b2 100644

[PATCH v4 1/2] drivers: bus: add a new driver for omap-ocp2scp

Adds a new driver *omap-ocp2scp*. This driver takes the responsibility of creating all the devices that is connected to OCP2SCP. In the case of OMAP4, USB2PHY is connected to ocp2scp. This also includes device tree support for ocp2scp driver and the documentation with device tree binding informati

[PATCH v4 0/2] omap: add ocp2scp as a bus driver

This patch series is done as a preparatory step for adding phy drivers for dwc3 and musb. This series adds a new driver for ocp2scp (only dt) to which phy drivers are connected. Since currently there is no generic way to create a child device along with doing a pm_runtime_enable (the exact requir

Re: [PATCH] usb/dwc3: Correct DEPCFG for Config Action "Modify"

On 8/6/2012 5:28 PM, Felipe Balbi wrote: Hi, On Mon, Aug 06, 2012 at 03:33:16PM +0530, Pratyush Anand wrote: From: Pratyush ANAND We need to issue DEPCFG (with Config Action Set to "Modify") as per specification. Even if we do not respect this , it works in normal cases. But, I have observed

[PATCH] ARM: EXYNOS: Add USB HSIC device

This patch support to control USB HSIC of EXYNOS4, edited based on Samsung's GT-i9100 ICS Opensource Update7. Change-Id: Ifba33c6a5166abf3644794eee6abe528bd71f521 Signed-off-by: Dongjin Kim --- arch/arm/mach-exynos/common.c|5 + arch/arm/mach-exynos/include/mach/regs-pmu.

Re: [RFC][PATCH 1/4 v3] usb: host: ehci-platform: BUG_ON() to WARN_ON() on probe

On Mon, 6 Aug 2012, Simon Horman wrote: > On Sun, Aug 05, 2012 at 06:51:34PM -0700, kuninori.morimoto...@renesas.com > wrote: > > We should avoid using BUG_ON() in drivers. > > This patch switch to use WARN_ON() from BUG_ON(), > > and avoid NULL pointer access by new macro. > > > > Signed-off-by

Re: [RFC][PATCH 3/4 v3] usb: host: ehci-platform: add platform specific power callback

On Sun, 5 Aug 2012 kuninori.morimoto...@renesas.com wrote: > This patch enables to call platform specific power callback function. > > Signed-off-by: Kuninori Morimoto > --- > v2 -> v3 > > - add power multi functions > - call it by macro > > drivers/usb/host/ehci-platform.c | 40 +

Re: Do we need asynchronous pm_runtime_get()? (was: Re: bisected regression ...)

On Mon, 6 Aug 2012, Ming Lei wrote: > Maybe the return value should be passed to caller. Also the race between > 'func' and its .runtime_resume callback should be stated in comment. > > In fact, maybe it is better to call 'func' always first, then call > ' rpm_resume(dev, RPM_ASYNC);', otherwise

[PATCH v2]staging "usbip" Fix typos.

From: "Justin P. Mattock" Signed-off-by: Justin P. Mattock --- NOTE:I see *rc1 in the git web log, so hopefully its ok to send out. The below patch fixes typos found while reading through staging usbip. drivers/staging/usbip/stub_rx.c |2 +- drivers/staging/usbip/vhci_hcd.c |4 ++--

Re: [PATCH] usb/dwc3: Correct DEPCFG for Config Action "Modify"

Hi, On Mon, Aug 06, 2012 at 07:22:52PM +0530, Pratyush Anand wrote: > >commit 4b345c9a3c7452340fb477868d8db475f05978b1 > >Author: Felipe Balbi > >Date: Mon Jul 16 14:08:16 2012 +0300 > > > > usb: dwc3: gadget: set Ignore Sequence Number bit from ConnectDone Event > > > > Databook says w

Re: Do we need asynchronous pm_runtime_get()? (was: Re: bisected regression ...)

On Sun, 5 Aug 2012, Rafael J. Wysocki wrote: > I don't really think we'll need to store func_sync in dev->power. At least > I don't see a reason to do that at the moment. You're right; I wasn't thinking straight. > I also think that func_sync() would have to be called if runtime PM is > disable

Re: Continuous stream of small bulk transfers hangs on OHCI-based system

On Sun, 5 Aug 2012, Tomas Sokorai wrote: > Here's after plugging in, but before the hang: > - > bus pci, device :00:04.0 > OHCI Host Controller > ohci_hcd > OHCI 1.0, NO legacy support registers, rh state running > control 0x68f RWE RWC HCFS=

Re: Continuous stream of small bulk transfers hangs on OHCI-based system

On Mon, Aug 6, 2012 at 12:24 PM, Alan Stern wrote: > any lines in the dmesg log from boot-up about "enabled Compaq ZFMicro > chipset quirks"? Nope, no quirks message at all in the boot log. > > Are you comfortable writing your own debugging patches, or would you Quite comfortable, I'll gather m

Runtime PM defaults for USB hosts

Hi Alan and Rafael, Is there a reason why runtime PM is disabled by default for PCI USB host controllers? It would really be nice to have this turned on by default at boot, rather than running udev scripts or powertop. Are there PCI USB hosts that can't handle D3? Or something else preventing u

usb/host/ohci-tmio.c:105: bad switch statement

Hello there, I just ran the static analyser cppcheck over the source code of the linux kernel version 3.6-rc1. It said linux-3.6-rc1/drivers/usb/host/ohci-tmio.c:105]: (warning) Redundant bitwise operation on "pm" in switch The source code is switch (ohci->num_ports) { default:

Re: usb/host/ohci-tmio.c:105: bad switch statement

On Mon, 6 Aug 2012, David Binderman wrote: > > Hello there, > > I just ran the static analyser cppcheck over the source code of the > linux kernel version 3.6-rc1. > > It said > > linux-3.6-rc1/drivers/usb/host/ohci-tmio.c:105]: (warning) Redundant bitwise > operation on "pm" in switch > > Th

Re: Runtime PM defaults for USB hosts

On Mon, 6 Aug 2012, Sarah Sharp wrote: > Hi Alan and Rafael, > > Is there a reason why runtime PM is disabled by default for PCI USB host > controllers? It would really be nice to have this turned on by default > at boot, rather than running udev scripts or powertop. As far as I know, the only

Re: Do we need asynchronous pm_runtime_get()? (was: Re: bisected regression ...)

On Monday, August 06, 2012, Alan Stern wrote: > On Sun, 5 Aug 2012, Rafael J. Wysocki wrote: [...] > > > What about the appended experimental patch? > > For now, I think it would be best to start with a single func argument. > If it turns out that anyone really needs to have two separate > argu

Re: Runtime PM defaults for USB hosts

Hi, On Monday, August 06, 2012, Sarah Sharp wrote: > Hi Alan and Rafael, > > Is there a reason why runtime PM is disabled by default for PCI USB host > controllers? It would really be nice to have this turned on by default > at boot, rather than running udev scripts or powertop. > > Are there P

[RFC ebeam PATCH v3 1/2] hid: Blacklist new eBeam classic device

Signed-off-by: Yann Cantin --- drivers/hid/hid-core.c |3 +++ drivers/hid/hid-ids.h |3 +++ 2 files changed, 6 insertions(+) diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c index 60ea284..b1ed8ee 100644 --- a/drivers/hid/hid-core.c +++ b/drivers/hid/hid-core.c @@ -1908,6 +

[RFC ebeam PATCH v3 0/2]

Hi, New USB input driver for eBeam devices. Currently, only the Luidia eBeam classic projection model is supported. Edge model and a NEC interactive video-projector support planned for the end of the mounth. Patch 1 to blacklist the device for hid generic-usb. Patch 2 is the actual driver. Ch

[RFC ebeam PATCH v3 2/2] input: misc: New USB eBeam input driver.

Signed-off-by: Yann Cantin --- drivers/input/misc/ebeam.c | 764 1 file changed, 764 insertions(+) create mode 100644 drivers/input/misc/ebeam.c diff --git a/drivers/input/misc/ebeam.c b/drivers/input/misc/ebeam.c new file mode 100644 index 000

Re: [RFC ebeam PATCH v3 1/2] hid: Blacklist new eBeam classic device

On Mon, Aug 06, 2012 at 11:21:43PM +0200, Yann Cantin wrote: > > Signed-off-by: Yann Cantin > --- > drivers/hid/hid-core.c |3 +++ > drivers/hid/hid-ids.h |3 +++ > 2 files changed, 6 insertions(+) > > diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c > index 60ea284..b1ed8e

Re: [RFC ebeam PATCH v3 2/2] input: misc: New USB eBeam input driver.

On Mon, Aug 06, 2012 at 11:21:44PM +0200, Yann Cantin wrote: > > Signed-off-by: Yann Cantin > --- > drivers/input/misc/ebeam.c | 764 > > 1 file changed, 764 insertions(+) > create mode 100644 drivers/input/misc/ebeam.c What adds this file to the

Re: [RFC ebeam PATCH v3 0/2]

On Mon, Aug 06, 2012 at 11:21:42PM +0200, Yann Cantin wrote: > Hi, > > New USB input driver for eBeam devices. > > Currently, only the Luidia eBeam classic projection model is supported. > Edge model and a NEC interactive video-projector support planned for the > end of the mounth. > > Patch 1

Re: [RFC ebeam PATCH v3 1/2] hid: Blacklist new eBeam classic device

On Monday, August 06, 2012 02:43:40 PM Greg KH wrote: > On Mon, Aug 06, 2012 at 11:21:43PM +0200, Yann Cantin wrote: > > Signed-off-by: Yann Cantin > > --- > > > > drivers/hid/hid-core.c |3 +++ > > drivers/hid/hid-ids.h |3 +++ > > 2 files changed, 6 insertions(+) > > > > diff --git a

Re: [RFC ebeam PATCH v3 0/2]

On Monday, August 06, 2012 02:44:23 PM Greg KH wrote: > On Mon, Aug 06, 2012 at 11:21:42PM +0200, Yann Cantin wrote: > > Hi, > > > > New USB input driver for eBeam devices. > > > > Currently, only the Luidia eBeam classic projection model is supported. > > Edge model and a NEC interactive video-p

[PATCH] usb: host: mips: sead3: Update for EHCI register structure.

From: "Steven J. Hill" One line fix after 'struct ehci_regs' definition was changed in commit a46af4ebf9ffec35eea0390e89935197b833dc61. Signed-off-by: Steven J. Hill --- drivers/usb/host/ehci-sead3.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/host/ehci-sead

Re: Continuous stream of small bulk transfers hangs on OHCI-based system

On Mon, Aug 6, 2012 at 12:24 PM, Alan Stern wrote: > any lines in the dmesg log from boot-up about "enabled Compaq ZFMicro > chipset quirks"? BTW, I printk'ed the ohci->flags just to be sure what quirks were enabled, and only the "do not trust power" was enabled. > My guess is that ed_rm_list is

Re: [RFC ebeam PATCH v3 2/2] input: misc: New USB eBeam input driver.

Hi, Le 06/08/2012 23:43, Greg KH a écrit : > On Mon, Aug 06, 2012 at 11:21:44PM +0200, Yann Cantin wrote: >> >> Signed-off-by: Yann Cantin >> --- >> drivers/input/misc/ebeam.c | 764 >> >> 1 file changed, 764 insertions(+) >> create mode 100644 dri

Re: [RFC][PATCH 0/4 v4] usb: host: ehci-platform: add platform specific .power callback

Hi Alan, Felipe, Greg These are v4 of ehci/ohci-platform patches Kuninori Morimoto (4): usb: host: ehci-platform: BUG_ON() to WARN_ON() on probe usb: host: ohci-platform: BUG_ON() to WARN_ON() on probe usb: host: ehci-platform: add platform specific power callback usb: ho

[RFC][PATCH 1/4 v4] usb: host: ehci-platform: BUG_ON() to WARN_ON() on probe

usb_ehci_pdata is certainly required in ehci-platform driver. This patch avoids using BUG_ON() from driver, and return from probe with WARN_ON() if pdata was NULL. Signed-off-by: Kuninori Morimoto --- v3 -> v4 - remove macro - return probe if pdata was NULL drivers/usb/host/ehci-platform.c |

[RFC][PATCH 2/4 v4] usb: host: ohci-platform: BUG_ON() to WARN_ON() on probe

usb_ohci_pdata is certainly required in ohci-platform driver. This patch avoids using BUG_ON() from driver, and return from probe with WARN_ON() if pdata was NULL. Signed-off-by: Kuninori Morimoto --- v3 -> v4 - remove macro - return probe if pdata was NULL drivers/usb/host/ohci-platform.c |

[RFC][PATCH 3/4] usb: host: ehci-platform: add platform specific power callback

This patch enables to call platform specific power callback function. Signed-off-by: Kuninori Morimoto --- v3 -> v4 - remove macro - remove .power_suspend - check return value on resume drivers/usb/host/ehci-platform.c | 40 +++-- include/linux/usb/ehci_pdr

[RFC][PATCH 4/4] usb: host: ohci-platform: add platform specific power callback

This patch enables to call platform specific power callback function. Signed-off-by: Kuninori Morimoto --- v3 -> v4 - remove macro - remove .power_suspen - check return value on resume drivers/usb/host/ohci-platform.c | 36 ++-- include/linux/usb/ohci_pdriv

Re: [RFC ebeam PATCH v3 1/2] hid: Blacklist new eBeam classic device

Le 07/08/2012 00:07, Dmitry Torokhov a écrit : > On Monday, August 06, 2012 02:43:40 PM Greg KH wrote: >> On Mon, Aug 06, 2012 at 11:21:43PM +0200, Yann Cantin wrote: >>> Signed-off-by: Yann Cantin >>> --- >>> >>> drivers/hid/hid-core.c |3 +++ >>> drivers/hid/hid-ids.h |3 +++ >>> 2 fil

Re: Do we need asynchronous pm_runtime_get()? (was: Re: bisected regression ...)

On Mon, Aug 6, 2012 at 10:47 PM, Alan Stern wrote: > No, no, you have completely misunderstood the whole point of this > change. Sorry, you are right. And the callback should be renamed as '.runtime_post_resume', which should do something I/O related in theory just after device becomes active. >

Re: [RFC ebeam PATCH v3 2/2] input: misc: New USB eBeam input driver.

On Tue, Aug 07, 2012 at 02:56:40AM +0200, Yann Cantin wrote: > Hi, > > Le 06/08/2012 23:43, Greg KH a écrit : > > On Mon, Aug 06, 2012 at 11:21:44PM +0200, Yann Cantin wrote: > >> > >> Signed-off-by: Yann Cantin > >> --- > >> drivers/input/misc/ebeam.c | 764 > >> ++

Re: [RFC ebeam PATCH v3 0/2]

Le 07/08/2012 00:09, Dmitry Torokhov a écrit : > On Monday, August 06, 2012 02:44:23 PM Greg KH wrote: >> On Mon, Aug 06, 2012 at 11:21:42PM +0200, Yann Cantin wrote: >>> Hi, >>> >>> New USB input driver for eBeam devices. >>> >>> Currently, only the Luidia eBeam classic projection model is support

Re: [RFC ebeam PATCH v3 1/2] hid: Blacklist new eBeam classic device

On Tue, Aug 07, 2012 at 03:21:45AM +0200, Yann Cantin wrote: > Le 07/08/2012 00:07, Dmitry Torokhov a écrit : > > On Monday, August 06, 2012 02:43:40 PM Greg KH wrote: > >> On Mon, Aug 06, 2012 at 11:21:43PM +0200, Yann Cantin wrote: > >>> Signed-off-by: Yann Cantin > >>> --- > >>> > >>> drivers/

Re: [BUG] Kernel panic when try s3c-hsotg.c with kernel 3.5

2012/8/6 Lukasz Majewski : > Hi, > >> Hi, >> >> On Mon, Aug 06, 2012 at 06:12:05PM +0800, Peiyong Feng wrote: >> > I got a kernel panic when try hsotg of ok6410 which is based on >> > s3c6410: > As you said, you are using the ok6410. And it is "based" on the s3c6410 > CPU. S3C6410 is a single core

Re: [PATCH 1/5] usb: phy: samsung: Introducing usb phy driver for hsotg

Hi, On Mon, Aug 6, 2012 at 3:21 PM, Praveen Paneri wrote: > Hi, > > On Mon, Aug 6, 2012 at 2:53 PM, Heiko Stübner wrote: >> Am Montag, 6. August 2012, 10:23:52 schrieb Kyungmin Park: >>> Hi Praveen, >>> >>> On 8/6/12, Praveen Paneri wrote: >>> > Hi Heiko, >>> > >>> > On Mon, Aug 6, 2012 at 3:24

[PATCH V2] usb/dwc3: Send DEPCFG with "Config Action: Modify" after conndone

From: Pratyush ANAND For core 1.94A and latter, specification says to issue DEPCFG with "Config Action: Modify" for physical endpoint 0/1. Signed-off-by: Pratyush Anand --- drivers/usb/dwc3/gadget.c |8 ++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/usb/dwc

Re: [PATCH 1/5] usb: phy: samsung: Introducing usb phy driver for hsotg

On 8/7/12, Praveen Paneri wrote: > Hi, > > On Mon, Aug 6, 2012 at 3:21 PM, Praveen Paneri > wrote: >> Hi, >> >> On Mon, Aug 6, 2012 at 2:53 PM, Heiko Stübner wrote: >>> Am Montag, 6. August 2012, 10:23:52 schrieb Kyungmin Park: Hi Praveen, On 8/6/12, Praveen Paneri wrote: >

Re: [PATCH] ARM: EXYNOS: Add USB HSIC device

Hi, Now another person try to use drivers/usb/phy for it. "usb: phy: samsung: Introducing usb phy driver for hsotg" Can you use it instead of previous one? Thank you, Kyungmin Park On 8/6/12, Dongjin Kim wrote: > This patch support to control USB HSIC of EXYNOS4, > edited based on Samsung's GT-

[PATCH] usb: dwc3: gadget: Fix sparse warnings

From: Moiz Sonasath This patch fixes the following sparse warnings: drivers/usb/dwc3/gadget.c:1096:7: warning: symbol 'ret' shadows an earlier one drivers/usb/dwc3/gadget.c:1058:8: originally declared here drivers/usb/dwc3/gadget.c:1100:16: warning: symbol 'dwc' shadows an earlier one drivers/us

Re: [PATCH V2] usb/dwc3: Send DEPCFG with "Config Action: Modify" after conndone

Hi, On Tue, Aug 07, 2012 at 09:33:42AM +0530, Pratyush Anand wrote: > From: Pratyush ANAND > > For core 1.94A and latter, specification says to issue DEPCFG with > "Config Action: Modify" for physical endpoint 0/1. > > Signed-off-by: Pratyush Anand > --- > drivers/usb/dwc3/gadget.c |8 +++

Re: [PATCH v2] can: kvaser_usb: Add support for Kvaser CAN/USB devices

On 08/06/2012 07:21 AM, Olivier Sobrie wrote: > This driver provides support for several Kvaser CAN/USB devices. > Such kind of devices supports up to three can network interfaces. s/can/CAN/ > It has been tested with a Kvaser USB Leaf Light (one network interface) > connected to a pch_can interf