On Thu, Aug 08, 2013 at 11:00:20PM +0200, Ben Hutchings wrote:
> On Thu, 2013-08-08 at 12:20 +0200, Andrew Lunn wrote:
> > Hi Ben, David
> >
> > Here is a pull request for firmware for Moxa USB-Serial hub devices.
> >
> > Thanks
> > Andrew
> >
> > The following changes since commit 931e4469d
On Thursday, August 08, 2013 6:02 PM Sebastian Andrzej Siewior wrote:
> On 08/08/2013 09:43 AM, Andrzej Pietrasiewicz wrote:
> > diff --git a/drivers/usb/gadget/configfs.c
> > b/drivers/usb/gadget/configfs.c index c5d8f81..8cb5006 100644
> > --- a/drivers/usb/gadget/configfs.c
> > +++ b/drivers/usb
Add the volume control quirk for avoiding the kernel warning
for the Logitech HD Webcam C525
as in the similar commit 36691e1be6ec551eef4a5225f126a281f8c051c2
for the Logitech HD Webcam C310.
Reported-by: Maksim Boyko
Tested-by: Maksim Boyko
Cc: # 3.10.5+
Signed-off-by: Maksim Boyko
--
sound/
On Fri, 2013-08-09 at 09:10 +0200, Andrew Lunn wrote:
> On Thu, Aug 08, 2013 at 11:00:20PM +0200, Ben Hutchings wrote:
> > On Thu, 2013-08-08 at 12:20 +0200, Andrew Lunn wrote:
> > > Hi Ben, David
> > >
> > > Here is a pull request for firmware for Moxa USB-Serial hub devices.
> > >
> > > Thanks
Add the volume control quirk for avoiding the kernel warning
for the Logitech HD Webcam C525
as in the similar commit 36691e1be6ec551eef4a5225f126a281f8c051c2
for the Logitech HD Webcam C310.
Reported-by: Maksim Boyko
Tested-by: Maksim Boyko
Cc: # 3.10.5+
Signed-off-by: Maksim Boyko
--
soun
Add the volume control quirk for avoiding the kernel warning
for the Logitech HD Webcam C525
as in the similar commit 36691e1be6ec551eef4a5225f126a281f8c051c2
for the Logitech HD Webcam C310.
Reported-by: Maksim Boyko
Tested-by: Maksim Boyko
Cc: # 3.10.5+
Signed-off-by: Maksim Boyko
--
soun
On Thu, Jul 25, 2013 at 06:20:34PM -0300, Fabio Estevam wrote:
> Currently hw_phymode_configure() is located inside hw_device_reset(), which is
> only called by chipidea udc driver.
>
> When operating in host mode, we also need to call hw_phymode_configure() in
> order to properly configure the P
Hi Fabio,
On Thu, Jul 25, 2013 at 06:20:34PM -0300, Fabio Estevam wrote:
> Currently hw_phymode_configure() is located inside hw_device_reset(), which is
> only called by chipidea udc driver.
>
> When operating in host mode, we also need to call hw_phymode_configure() in
> order to properly conf
From: "Ivan T. Ivanov"
DWC3 glue layer is hardware layer around Synopsys DesignWare
USB3 core. Its purpose is to supply Synopsys IP with required
clocks, voltages and interface it with the rest of the SoC.
Signed-off-by: Ivan T. Ivanov
---
drivers/usb/dwc3/Kconfig|8 ++
drivers/usb/dwc
From: "Ivan T. Ivanov"
Hi,
These patches add basic support for USB3.0 controllers found
on MSM platforms. USB3.0 core is based on Synopsys DesignWare
SuperSpeed IP.
Changes since first version:
* Split devicetree bindings description file to separate patch
* Address comments for device bindin
From: "Ivan T. Ivanov"
MSM USB3.0 core wrapper consist of USB3.0 IP (SNPS)
and HS, SS PHY's controll and configuration registers.
It could operate in device mode (SS, HS, FS) and host
mode (SS, HS, FS, LS).
Signed-off-by: Ivan T. Ivanov
---
.../devicetree/bindings/usb/msm-ssusb.txt |
From: "Ivan T. Ivanov"
These drivers handles control and configuration of the HS
and SS USB PHY transceivers. They are part of the driver
which manage Synopsys DesignWare USB3 controller stack
inside Qualcomm SoC's.
Signed-off-by: Ivan T. Ivanov
---
drivers/usb/phy/Kconfig | 11 ++
On Fri, Aug 09, 2013 at 02:26:40AM +0100, Ming Lei wrote:
> In isp1760-hcd driver, flush_dcache_page() is introduced in commit
> db8516f61b4(USB: isp1760: Flush the D-cache for the pipe-in transfer buffers)
> to fix cache incoherency problem when PIO reading from USB mass storage
> device to mapped
Fabio Estevam writes:
> Currently hw_phymode_configure() is located inside hw_device_reset(), which is
> only called by chipidea udc driver.
>
> When operating in host mode, we also need to call hw_phymode_configure() in
> order to properly configure the PHY mode, so move this function into prob
Peter Chen writes:
> Signed-off-by: Peter Chen
Added a commit message and applied. Thanks!
--
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
From: Mark Brown
Since there is no runtime interface for changing modes this is probably
the most sensible default.
Signed-off-by: Mark Brown
---
drivers/usb/misc/usb3503.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/misc/usb3503.c b/drivers/usb/misc/usb3503
From: Mark Brown
If the connect signal is pulled high then the device will start up meaning
that if we just pull it high on probe then the device will start running
prior to the configuration being written out. Fix this by pulling the GPIO
low when we reset and only pulling it high when configura
From: Mark Brown
There are no software visible differences that I am aware of but in case
any are discovered allow the DTS to specify exactly which device is
present.
Signed-off-by: Mark Brown
---
Documentation/devicetree/bindings/usb/usb3503.txt | 2 +-
drivers/usb/misc/usb3503.c
From: Mark Brown
The /RESET GPIO is not manipulated from atomic context so support GPIOs
that can't be written from atomic context by using _cansleep().
---
drivers/usb/misc/usb3503.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/misc/usb3503.c b/drivers/usb/mis
From: Mark Brown
The intn and connect GPIO properties are swapped in the code which will
cause failures at runtime if these are connected, fix the code.
There are currently no in-tree users of this device to check or update.
Signed-off-by: Mark Brown
---
drivers/usb/misc/usb3503.c | 4 ++--
1
From: Mark Brown
In preparation for supporting operation without an I2C control interface
factor out the I2C-specific parts of the probe routine from those that
don't do any register I/O.
Signed-off-by: Mark Brown
---
drivers/usb/misc/usb3503.c | 77 ++--
From: Mark Brown
Signed-off-by: Mark Brown
---
drivers/usb/misc/usb3503.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/misc/usb3503.c b/drivers/usb/misc/usb3503.c
index ca0f789..777102e 100644
--- a/drivers/usb/misc/usb3503.c
+++ b/drivers/usb/misc/usb3503
From: Mark Brown
Refactor so that register writes for configuration are only performed if
the device has a regmap provided and also register as a platform driver.
This allows the driver to be used to manage GPIO based control of the
device.
Signed-off-by: Mark Brown
Cc: devicet...@vger.kernel.o
From: Mark Brown
The binding document says that all properties are required but in fact
almost all are optional (and should be) - update the document to reflect
this.
Signed-off-by: Mark Brown
Cc: devicet...@vger.kernel.org
---
Documentation/devicetree/bindings/usb/usb3503.txt | 2 ++
1 file c
From: Mark Brown
This will give access to the diagnostic infrastructure regmap has but
the main point is to support future refactoring.
Signed-off-by: Mark Brown
---
drivers/usb/misc/Kconfig | 1 +
drivers/usb/misc/usb3503.c | 93 ++
2 files chang
From: Mark Brown
Saves us a bit of code.
Signed-off-by: Mark Brown
---
drivers/usb/misc/usb3503.c | 42 +++---
1 file changed, 7 insertions(+), 35 deletions(-)
diff --git a/drivers/usb/misc/usb3503.c b/drivers/usb/misc/usb3503.c
index 8c06eb2..2e9e100 10064
Peter Chen writes:
> Now, chipidea host has already depended on USB_EHCI_HCD
>
> Signed-off-by: Peter Chen
Alan, what do you think?
> ---
> drivers/usb/host/Kconfig |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kco
Lothar Waßmann writes:
> This patch provides a cleaner solution to the problem described in
> commit 20a677fd.
>
> The goal to be achieved is to force USB_CHIPIDEA=m if either
> USB_EHCI_HCD=m or USB_GADGET=m.
> If both are 'y' USB_CHIPIDEA may be selected to be 'm' or 'y'.
>
> The old patch had
Fabio Estevam writes:
> From: Fabio Estevam
>
> After the rename to ci_hdrc we ended up with two MODULE_ALIAS entries, so
> remove the old one.
>
> Signed-off-by: Fabio Estevam
Applied and pushed, thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of
On Fri, Aug 09, 2013 at 08:20:45AM +0200, Sascha Hauer wrote:
> On Thu, Aug 08, 2013 at 06:19:43PM +0800, Peter Chen wrote:
> > > > - compatible = "fsl,imx25-usbmisc";
> > > > - clocks = <&clks 9>, <&clks 70>, <&clks
> > > > 8>;
> > > > -
On Fri, Aug 09, 2013 at 08:56:56AM +0200, Sascha Hauer wrote:
> The chipidea i.MX driver is split into two drivers. The ci_hdrc_imx driver
> handles the chipidea cores and the usbmisc_imx driver handles the noncore
> registers common to all chipidea cores (but SoC specific). Current flow is:
>
> -
On Fri, Aug 09, 2013 at 06:25:29PM +0800, Peter Chen wrote:
> > -void usbmisc_unset_ops(const struct usbmisc_ops *ops)
> > -{
> > - usbmisc_ops = NULL;
> > -}
> > -EXPORT_SYMBOL_GPL(usbmisc_unset_ops);
> > -
> > -int usbmisc_get_init_data(struct device *dev, struct usbmisc_usb_device
> > *usbdev
Peter Chen writes:
> Since we need otgsc to know vbus's status at some chipidea
> controllers even it is peripheral-only mode. Besides, some
> SoCs (eg, AR9331 SoC) don't have otgsc register even
> the DCCPARAMS_DC and DCCPARAMS_HC are both 1 at CAP_DCCPARAMS.
>
> We inroduce flag CI_HDRC_DUAL_RO
Peter Chen writes:
> This file is mainly used to access otgsc currently, it may
> add otg related things in the future.
>
> Tested-by: Marek Vasut
> Signed-off-by: Peter Chen
> ---
> drivers/usb/chipidea/Makefile |2 +-
> drivers/usb/chipidea/bits.h | 10
> drivers/usb/chipide
On Fri, Aug 09, 2013 at 03:55:56PM +0300, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > Since we need otgsc to know vbus's status at some chipidea
> > controllers even it is peripheral-only mode. Besides, some
> > SoCs (eg, AR9331 SoC) don't have otgsc register even
> > the DCCPARAMS_DC an
Peter Chen writes:
A few typos:
> Move otg relate things to otg file.
"related"
>
> Tested-by: Marek Vasut
> Signed-off-by: Peter Chen
> ---
> drivers/usb/chipidea/core.c | 63
> +--
> drivers/usb/chipidea/otg.c | 57
On Fri, Aug 09, 2013 at 04:00:13PM +0300, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > This file is mainly used to access otgsc currently, it may
> > add otg related things in the future.
> >
> > Tested-by: Marek Vasut
> > Signed-off-by: Peter Chen
> > ---
> > drivers/usb/chipidea/Make
On Sun, Aug 04, 2013 at 08:45:24PM +0400, Sergei Shtylyov wrote:
> Hello.
>
>I have basically two questions on this change:
>
> 1) why it wasn't published before committing?
look deeper
> 2) why you omitted am35x.c from this commit?
mistake
--
balbi
signature.asc
Description: Digital s
On Mon, Aug 05, 2013 at 03:08:43PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Fix (randconfig) build problem with DEBUG_FS on
>
> Cc: ba...@ti.com
> Cc: linux-usb@vger.kernel.org
> Signed-off-by: Andi Kleen
care to show me the defconfig which makes the build fail ?
--
balbi
signature.
Peter Chen writes:
> On Fri, Aug 09, 2013 at 03:55:56PM +0300, Alexander Shishkin wrote:
>> > + } else {
>> > + /*
>> > + * If the controller is not OTG capable, but support
>> > + * role switch, the defalt role is gadget, and the
>> >
Peter Chen writes:
> CI_HDRC_REGS_SHARED stands for the controller registers is shared
> with other USB drivers, if all USB drivers are at chipidea/, it doesn't
> needed to set.
We still have the msm driver that uses REGS_SHARED.
> CI_HDRC_PULLUP_ON_VBUS stands for pullup dp when the vbus is on
Hi,
On Tue, Aug 06, 2013 at 02:53:11PM +0300, Ivan T. Ivanov wrote:
> diff --git a/drivers/usb/dwc3/dwc3-msm.c b/drivers/usb/dwc3/dwc3-msm.c
> new file mode 100644
> index 000..e509abc
> --- /dev/null
> +++ b/drivers/usb/dwc3/dwc3-msm.c
> @@ -0,0 +1,175 @@
> +#undef CONFIG_REGULATOR
why ?
Hi,
On Tue, Aug 06, 2013 at 01:21:38PM +0100, Pawel Moll wrote:
> > @@ -47,3 +64,25 @@ Example device nodes:
> > vddcx-supply = <&supply>;
> > v1p8-supply = <&supply>;
> > };
> > +
> > + usb@fd4ab000 {
> > + compatible = "qcom,dwc-usb3-msm";
> > +
On Wed, Aug 07, 2013 at 06:01:00PM +0800, Andy Green wrote:
> On 7 August 2013 17:34, Mark Brown wrote:
> > On Tue, Aug 06, 2013 at 10:35:52PM -0300, Fabio Estevam wrote:
> >> On Tue, Aug 6, 2013 at 12:49 PM, Mark Brown wrote:
> >> > From: Andy Green
> >> >
> >> > You might have CONFIG_PM, but y
On Thu, Aug 08, 2013 at 10:25:36AM -0700, Sarah Sharp wrote:
> Hi Yu,
>
> Please test this patch, and make sure that interrupts aren't registered
> twice. I think this approach is better, since it creates a new quirk
> specifically for xhci platform devices, so we can tell them apart from
> PCI d
On Wed, Aug 07, 2013 at 12:03:34PM +, Wang, Yu Y wrote:
> Hi Balbi,
>
> Because dwc3 driver request_threaded_irq with flags
> IRQF_ONESHOT and IRQF_SHARED.
> But xHCI driver will not set IRQF_ONESHOT. Then will met
> IRQ request failed if use same IRQ number.
>
>
> <4>[1.019248] Call Tra
Hi,
On Wed, Aug 07, 2013 at 12:12:59PM +, Wang, Yu Y wrote:
>
> Hi Balbi,
>
> Because dwc3 driver request_threaded_irq with flags
> IRQF_ONESHOT and IRQF_SHARED.
> But xHCI driver will not set IRQF_ONESHOT. Then will met
> IRQ request failed if use same IRQ number.
can you please fix your e
On Thu, Aug 08, 2013 at 07:25:47AM -0700, Sarah Sharp wrote:
> I've heard there's little to do at the software level, but I haven't
you've heard ? IIRC your name is in the spec :-)
--
balbi
signature.asc
Description: Digital signature
On Fri, Aug 09, 2013 at 12:53:47PM +0300, Ivan T. Ivanov wrote:
> From: "Ivan T. Ivanov"
>
> DWC3 glue layer is hardware layer around Synopsys DesignWare
> USB3 core. Its purpose is to supply Synopsys IP with required
> clocks, voltages and interface it with the rest of the SoC.
>
> Signed-off-b
> On Wed, Aug 07, 2013 at 12:03:34PM +, Wang, Yu Y wrote:
> > Hi Balbi,
> >
> > Because dwc3 driver request_threaded_irq with flags IRQF_ONESHOT and
> > IRQF_SHARED.
> > But xHCI driver will not set IRQF_ONESHOT. Then will met IRQ request
> > failed if use same IRQ number.
> >
> >
> > <4>[1
On Tue, Aug 06, 2013 at 11:27:11PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 08/06/2013 11:16 PM, Tuomas Tynkkynen wrote:
>
> >[...]
>
> >>>+ match = of_match_device(tegra_ehci_of_match, &pdev->dev);
> >>>+ if (!match) {
> >>>+ dev_err(&pdev->dev, "Error: No device match found\n")
On Fri, Aug 09, 2013 at 04:23:11PM +0300, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > CI_HDRC_REGS_SHARED stands for the controller registers is shared
> > with other USB drivers, if all USB drivers are at chipidea/, it doesn't
> > needed to set.
>
> We still have the msm driver that us
Hi,
On Thu, Jul 25, 2013 at 05:33:48PM -0400, Alan Stern wrote:
> > On Thu, Jul 25, 2013 at 03:44:20PM -0400, Alan Stern wrote:
> > > On Thu, 25 Jul 2013, Greg KH wrote:
> > >
> > > > On Tue, Jul 02, 2013 at 08:13:52PM -0700, Jack Pham wrote:
> > > > > From: Manu Gautam
> > > > >
> > > > > The
On Fri, Aug 09, 2013 at 01:34:09PM +, Wang, Yu Y wrote:
> > On Wed, Aug 07, 2013 at 12:03:34PM +, Wang, Yu Y wrote:
> > > Hi Balbi,
> > >
> > > Because dwc3 driver request_threaded_irq with flags IRQF_ONESHOT and
> > > IRQF_SHARED.
> > > But xHCI driver will not set IRQF_ONESHOT. Then will
Hi Felipe,
Here's a small fix for the UVC gadget driver, could you please take it in your
tree for v3.12 ?
The following changes since commit 941ea3616c747545d0278fc432fb7919b6d0d8f0:
usb: dwc3: use dev_get_platdata() (2013-07-31 16:52:02 +0300)
are available in the git repository at:
git
On Fri, Aug 09, 2013 at 07:46:00PM +0800, Peter Chen wrote:
> On Fri, Aug 09, 2013 at 04:23:11PM +0300, Alexander Shishkin wrote:
> > Peter Chen writes:
> >
> > > CI_HDRC_REGS_SHARED stands for the controller registers is shared
> > > with other USB drivers, if all USB drivers are at chipidea/, i
On Fri, 9 Aug 2013, Christian Lamparter wrote:
> > After loading firmware, a reset generally is necessary. Some devices
> > will do it themselves; others require you to call usb_reset_device().
>
> This makes things complicated. Because, as far as I remember,
> usb_reset_device() will cause the
On Thu, 8 Aug 2013, Sean O. Stalley wrote:
> rh_call_control() contains a buffer, tbuf, which it uses to hold
> USB descriptors. These discriptors are eventually copied into the
> transfer_buffer in the URB. The buffer in the URB is dynamically
> defined and is always large enough to hold the amou
Hi Tony,
here's a pull request of one patch to avoid conflicts during the merge
window.
Please consider applying to your tree and I'll take this same patch
upstream.
The following changes since commit 5ae90d8e467e625e447000cb4335c4db973b1095:
Linux 3.11-rc3 (2013-07-28 20:53:33 -0700)
are av
On Fri, Aug 02, 2013 at 09:24:10PM +0200, Sebastian Andrzej Siewior wrote:
> This driver is currently used by musb' cppi41 couter part. I may merge
> both dma engine user of musb at some point but not just yet.
>
> The driver seems to work in RX/TX mode in host mode, tested on mass
> storage. I in
This patch fixes a kernel panic that can occur when unplugging the HWA
dongle while a downstream device is in the process of disconnecting.
This involved 2 changes. First, call usb_lock_device_for_reset before
usb_reset_device to synchronize the HWA's post_rest and disconnect
routines. Secon
On Fri, 9 Aug 2013, Sujith Manoharan wrote:
> Christian Lamparter wrote:
> > So, if we call usb_reset_device there and the driver is unbound
> > and later rebound. the next ath9k_htc .probe will start again and
> > again and again not knowing that it is already initialized
> > (and we have a loop
On Fri, 9 Aug 2013, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > Now, chipidea host has already depended on USB_EHCI_HCD
> >
> > Signed-off-by: Peter Chen
>
> Alan, what do you think?
>
> > ---
> > drivers/usb/host/Kconfig |4 ++--
> > 1 files changed, 2 insertions(+), 2 deletion
Am 09.08.2013 16:13, schrieb Alan Stern:
On Fri, 9 Aug 2013, Christian Lamparter wrote:
After loading firmware, a reset generally is necessary. Some devices
will do it themselves; others require you to call usb_reset_device().
This makes things complicated. Because, as far as I remember,
usb
On Fri, 9 Aug 2013, Felipe Balbi wrote:
> > > Wait a minute, didn't we discuss a while back that these test features
> > > should be built into usbcore so that we could have a usbcv clone for
> > > linux ?
> >
> > There's no way this can be built into the core. This test requires the
> > behavio
On Thu, Aug 08, 2013 at 12:35:04PM +0100, Mark Brown wrote:
> From: Mark Brown
>
> Systems with the common clock API need clk_prepare() as well as the enable
> step.
>
> Signed-off-by: Mark Brown
clk_prepare() is done on probe()... -ECONFUSED
--
balbi
signature.asc
Description: Digital sig
Alan Stern writes:
> On Fri, 9 Aug 2013, Alexander Shishkin wrote:
>
>> Peter Chen writes:
>>
>> > Now, chipidea host has already depended on USB_EHCI_HCD
>> >
>> > Signed-off-by: Peter Chen
>>
>> Alan, what do you think?
>>
>> > ---
>> > drivers/usb/host/Kconfig |4 ++--
>> > 1 files c
On Fri, Aug 09, 2013 at 03:50:10PM +0200, Laurent Pinchart wrote:
> Hi Felipe,
>
> Here's a small fix for the UVC gadget driver, could you please take it in
> your
> tree for v3.12 ?
>
> The following changes since commit 941ea3616c747545d0278fc432fb7919b6d0d8f0:
>
> usb: dwc3: use dev_get_p
Hi,
On Fri, Aug 09, 2013 at 10:37:50AM -0400, Alan Stern wrote:
> > > > Wait a minute, didn't we discuss a while back that these test features
> > > > should be built into usbcore so that we could have a usbcv clone for
> > > > linux ?
> > >
> > > There's no way this can be built into the core.
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
> > What about a "get firmware version" sort of thing? There really should
> > be a way for the driver to tell whether the firmware has already been
> > updated.
>
> I was not able to find good direct way to check firmware version. If i
> would add some
This patch fixes a kernel panic that can occur when disconnecting a
wireless USB->serial device. When the serial device disconnects, the
device cleanup procedure ends up calling usb_hcd_disable_endpoint on the
serial device's endpoints. The wusbcore uses the ABORT_RPIPE command to
abort all t
On Fri, 9 Aug 2013, Alexander Shishkin wrote:
> Alan Stern writes:
>
> > On Fri, 9 Aug 2013, Alexander Shishkin wrote:
> >
> >> Peter Chen writes:
> >>
> >> > Now, chipidea host has already depended on USB_EHCI_HCD
> >> >
> >> > Signed-off-by: Peter Chen
> >>
> >> Alan, what do you think?
>
On Fri, Aug 09, 2013 at 05:38:57PM +0300, Felipe Balbi wrote:
> On Thu, Aug 08, 2013 at 12:35:04PM +0100, Mark Brown wrote:
> > Systems with the common clock API need clk_prepare() as well as the enable
> > step.
> clk_prepare() is done on probe()... -ECONFUSED
Ah, so it is, missed that - though
On Fri, Aug 9, 2013 at 10:26 AM, Felipe Balbi wrote:
> looks good to me too, please send it as a real patch (if you already
> have, sorry about that, catching up with my inbox now).
Yes, I have already sent it as a formal patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-
On Fri, 9 Aug 2013, Felipe Balbi wrote:
> > > heh, it doesn't need to be entirely in the core. Core could have the
> > > generic calls and HCDs could implement some callbacks, but I think quite
> > > a bit of the code will be similar if we implement the same thing on all
> > > HCDs.
> >
> > What
> On Fri, Aug 09, 2013 at 01:34:09PM +, Wang, Yu Y wrote:
> > > On Wed, Aug 07, 2013 at 12:03:34PM +, Wang, Yu Y wrote:
> > > > Hi Balbi,
> > > >
> > > > Because dwc3 driver request_threaded_irq with flags IRQF_ONESHOT
> > > > and IRQF_SHARED.
> > > > But xHCI driver will not set IRQF_ONESH
Hi,
On Fri, 2013-08-09 at 16:32 +0300, Felipe Balbi wrote:
> On Fri, Aug 09, 2013 at 12:53:47PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > DWC3 glue layer is hardware layer around Synopsys DesignWare
> > USB3 core. Its purpose is to supply Synopsys IP with required
> > clo
The binding spec wasn't clear that the order of the phandles in the
usb-phy array has meaning. Clarify this point in the binding that
it should be .
Signed-off-by: Kumar Gala
---
Documentation/devicetree/bindings/usb/dwc3.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Am 09.08.2013 16:52, schrieb Alan Stern:
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
What about a "get firmware version" sort of thing? There really should
be a way for the driver to tell whether the firmware has already been
updated.
I was not able to find good direct way to check firmware ve
On Thu, Aug 08, 2013 at 04:11:46PM -0700, Greg KH wrote:
> Note, I don't apply "RFC" patches, and rarely review them. Why are you
> claiming that is what this is, when it is in the 3rd version already?
This is a new approach from the last patch (dynamic allocation vs.
making the static tbuf bigge
Alan,
Just wondering why we don't require the HCDs to validate the length instead of
blindly copying the descriptor to the buffer passed in. In the pseudo host
controller we are developing we only copy the number of bytes requested to the
buffer passed in.
Thx!
Rahman
-Original Message---
This is what I observe:
On the first connect, the musb starts with DEVCTL.Session set. On
disconnect, musb_core calls try_idle. That functions removes the Session
bit signalize that the session is over (something that only in OTG is
required). A new device, that is plugged, is no longer recognized.
Hi,
On Fri, 2013-08-09 at 16:23 +0300, Felipe Balbi wrote:
> Hi,
>
> On Tue, Aug 06, 2013 at 02:53:11PM +0300, Ivan T. Ivanov wrote:
> > diff --git a/drivers/usb/dwc3/dwc3-msm.c b/drivers/usb/dwc3/dwc3-msm.c
> > new file mode 100644
> > index 000..e509abc
> > --- /dev/null
> > +++ b/drivers/
On Fri, Aug 09, 2013 at 04:40:32PM +0100, Kumar Gala wrote:
> The binding spec wasn't clear that the order of the phandles in the
> usb-phy array has meaning. Clarify this point in the binding that
> it should be .
>
> Signed-off-by: Kumar Gala
> ---
> Documentation/devicetree/bindings/usb/dwc3
You are right that comment should read USB2.0! Will resend.
Thank you.
From: linux-usb-ow...@vger.kernel.org [linux-usb-ow...@vger.kernel.org] on
behalf of Greg KH [gre...@linuxfoundation.org]
Sent: Thursday, August 08, 2013 5:36 PM
To: Alexandra Yates
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
> Am 09.08.2013 16:52, schrieb Alan Stern:
> > On Fri, 9 Aug 2013, Oleksij Rempel wrote:
> >
> >>> What about a "get firmware version" sort of thing? There really should
> >>> be a way for the driver to tell whether the firmware has already been
> >>> upd
On Fri, 9 Aug 2013, Ismail, Abdul R wrote:
> Alan,
>
> Just wondering why we don't require the HCDs to validate the length
> instead of blindly copying the descriptor to the buffer passed in. In
> the pseudo host controller we are developing we only copy the number
> of bytes requested to the buf
Hi Shawn,
I noticed that the ChromeOS kernel tree is still using this particular
patch, and thought it was probably time to revisit it.
On Sat, May 25, 2013 at 09:57:57AM -0700, Shawn Nematbakhsh wrote:
> Hi Sarah and Alan,
>
> Thanks for the comments. I will make the following revisions:
>
> 1
From: Mark Brown
Ensure that the definition of ax88172a_info matches the declaration seen
by users and silence sparse warnings about symbols without declarations
in the global namespace by moving the declaration into the shared header
asix.h.
Signed-off-by: Mark Brown
---
drivers/net/usb/asix.
From: Mark Brown
Make functions that are only referenced from ops structures static, they
do not need to be in the global namespace and sparse complains about this.
Signed-off-by: Mark Brown
---
drivers/net/usb/ax88172a.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --gi
On Fri, Aug 9, 2013 at 2:31 PM, Mark Brown wrote:
> From: Mark Brown
>
> Ensure that the definition of ax88172a_info matches the declaration seen
> by users and silence sparse warnings about symbols without declarations
> in the global namespace by moving the declaration into the shared header
>
On Fri, 9 Aug 2013 14:39:06 -0300
Fabio Estevam wrote:
> On Fri, Aug 9, 2013 at 2:31 PM, Mark Brown wrote:
> > From: Mark Brown
> >
> > Ensure that the definition of ax88172a_info matches the declaration seen
> > by users and silence sparse warnings about symbols without declarations
> > in the
On Fri, 2013-08-09 at 10:40 -0700, Stephen Hemminger wrote:
> On Fri, 9 Aug 2013 14:39:06 -0300
> Fabio Estevam wrote:
>
> > On Fri, Aug 9, 2013 at 2:31 PM, Mark Brown wrote:
> > > From: Mark Brown
> > >
> > > Ensure that the definition of ax88172a_info matches the declaration seen
> > > by use
On Fri, Aug 9, 2013 at 2:40 PM, Stephen Hemminger
wrote:
>> > +extern const struct driver_info ax88172a_info;
>>
>> You could drop the 'extern' here.
>>
>> All other function prototypes in this header file do not use 'extern'.
>
> That is data, not function prototype, so yes extern is needed.
Yo
From: Eric Dumazet
Date: Fri, 09 Aug 2013 10:50:36 -0700
> Some compiler folk decided 'extern' were not mandatory for code, but its
> really adding confusion and endless discussions.
I certainly stopped talking about it, you could too :-)
--
To unsubscribe from this list: send the line "unsubscr
On Wednesday 31 July 2013 14:38:34 Alan Stern wrote:
> On Wed, 31 Jul 2013, Alberto Gonzalez wrote:
> >
> > There seems to be a regression in Kernel 3.10.3 (from 3.10.2) that
> > prevents me being able to mount my external USB hard drive.
>
> See
>
> http://marc.info/?l=linux-usb&m=137523
On Fri, 9 Aug 2013, Lionel Landwerlin wrote:
> Hi there,
>
> I'm playing with 2 small usb webcams, showing up the stream of the
> camera with it's plugged in and hiding it when it's unplugged. I'm
> basically using 2 external camera + the integrated one.
>
> I've noticed the usb port just beco
On Fri, Aug 09, 2013 at 08:51:30AM -0700, Sarah Sharp wrote:
> On Thu, Aug 08, 2013 at 04:11:46PM -0700, Greg KH wrote:
> > Note, I don't apply "RFC" patches, and rarely review them. Why are you
> > claiming that is what this is, when it is in the 3rd version already?
>
> This is a new approach f
Some bad gadget drivers do not check the return status of usb_add_config.
Thus they get a not correctly initialized config and when this gadget gets
deactivated the whole kernel crashes. Since on initialization failure cdev
is set to NULL it can be used to detect this problem situation. It can be
a
On Aug 9, 2013, at 11:28 AM, Mark Rutland wrote:
> On Fri, Aug 09, 2013 at 04:40:32PM +0100, Kumar Gala wrote:
>> The binding spec wasn't clear that the order of the phandles in the
>> usb-phy array has meaning. Clarify this point in the binding that
>> it should be .
>>
>> Signed-off-by: Kumar
1 - 100 of 127 matches
Mail list logo
