On 08/05/14 20:15, Paul Zimmerman wrote:
From: Nick Hudson [mailto:sk...@netbsd.org]
Sent: Tuesday, August 05, 2014 1:57 AM
On 07/22/14 22:22, Nick Hudson wrote:
On 07/22/14 18:46, Paul Zimmerman wrote:
The nak_frame handling would have added some benefit, but wouldn't
handle all
cases.
I'm s
On 2014-08-05 23:56, Johan Hovold wrote:
On Tue, Aug 05, 2014 at 02:30:31PM +1000, ress...@ausics.net wrote:
On 2014-08-05 00:10, Johan Hovold wrote:
> I'll queue this up for v3.17-rc.
>
Awesome, any chance of it finding its way into 3.14.x since it's a LT
release?
Yes, it's marked for sta
Hi everyone,
On Tue, Mar 18, 2014 at 01:33:24PM -0700, Greg KH wrote:
> On Tue, Mar 18, 2014 at 10:11:20PM +0200, Valentina Manea wrote:
> > After migrating userspace code to libudev, converting usbip-host
> > to a device driver and various bug fixes and enhancements, USB/IP
> > is fully functiona
Hi,
we need a kernel with patch on [1] to usb works on guests machine of
VirtualBox without spam dmesg.
I tested patch [1] devio: fix issue with log flooding of message and it
works, I wonder if this patch will be applied to kernel or not ? and if
can go to stables or not ?
The problem of this
On Wed, Aug 06, 2014 at 02:42:31PM +0100, Sérgio Basto wrote:
> Hi,
>
> we need a kernel with patch on [1] to usb works on guests machine of
> VirtualBox without spam dmesg.
Then build such a kernel, what is preventing that?
> I tested patch [1] devio: fix issue with log flooding of message and
On Wed, Aug 06, 2014 at 02:22:10PM +0200, Max Vozeler wrote:
> Hi everyone,
>
> On Tue, Mar 18, 2014 at 01:33:24PM -0700, Greg KH wrote:
> > On Tue, Mar 18, 2014 at 10:11:20PM +0200, Valentina Manea wrote:
> > > After migrating userspace code to libudev, converting usbip-host
> > > to a device dri
On Qua, 2014-08-06 at 07:43 -0700, Greg KH wrote:
> On Wed, Aug 06, 2014 at 02:42:31PM +0100, Sérgio Basto wrote:
> > Hi,
> >
> > we need a kernel with patch on [1] to usb works on guests machine of
> > VirtualBox without spam dmesg.
>
> Then build such a kernel, what is preventing that?
I did
On Wed, Aug 06, 2014 at 04:12:20PM +0100, Sérgio Basto wrote:
> On Qua, 2014-08-06 at 07:43 -0700, Greg KH wrote:
> > On Wed, Aug 06, 2014 at 02:42:31PM +0100, Sérgio Basto wrote:
> > > Hi,
> > >
> > > we need a kernel with patch on [1] to usb works on guests machine of
> > > VirtualBox without
This VIA Telecom baseband processor is used is used by by u-blox in both the
FW2770 and FW2760 products and may be used in others as well.
This patch has been tested on both of these modem versions.
Signed-off-by: Brennan Ashton
---
drivers/usb/serial/option.c | 5 +
1 file changed, 5 inser
On Qua, 2014-08-06 at 08:25 -0700, Greg KH wrote:
> On Wed, Aug 06, 2014 at 04:12:20PM +0100, Sérgio Basto wrote:
> > On Qua, 2014-08-06 at 07:43 -0700, Greg KH wrote:
> > > On Wed, Aug 06, 2014 at 02:42:31PM +0100, Sérgio Basto wrote:
> > > > Hi,
> > > >
> > > > we need a kernel with patch on [
Signed-off-by: Peter Griffin
---
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 359a64e..847572d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1325,7 +1325,8 @@ F:drivers/pinctrl/pinctrl-st.c
F: drivers/media/rc/st_r
This patch documents the device tree bindings required for
the ohci on-chip controller found in ST consumer electronics SoC's.
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/usb/ohci-st.txt | 40 +++
1 file changed, 40 insertions(+)
create mode 100644 Doc
This patch documents the device tree bindings required for the
ehci on-chip controller found in ST consumer electronics SoC's.
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/usb/ehci-st.txt | 41 +++
1 file changed, 41 insertions(+)
create mode 100644 Doc
This patch adds the glue code required to ensure the on-chip OHCI
controller works on STi consumer electronics SoC's from STMicroelectronics.
It mainly manages the setting and enabling of the relevant clocks and manages
the reset / power signals to the IP block.
Signed-off-by: Peter Griffin
---
This patch adds the glue code required to ensure the on-chip EHCI
controller works on STi consumer electronics SoC's from STMicroelectronics.
It mainly manages the setting and enabling of the relevant clocks and manages
the reset / power signals to the IP block.
Signed-off-by: Peter Griffin
---
This series adds support for the OHCI and EHCI on-chip controllers
found in STi consumer electronics SoC's from STMicroelectronics.
The series has been re-worked from v2 to split out the ehci and ohci parts
into their own drivers / devices like most other ARM platforms based on
feedback from Arnd
This patch abstracts out some common code required by both the ehci-st
and ohci-st drivers.
Signed-off-by: Peter Griffin
---
drivers/usb/host/usb-st-common.c | 99
drivers/usb/host/usb-st-common.h | 34 ++
2 files changed, 133 insertions(+)
c
V2 - Restart polling (which will restart the timer) for the shared
HCD in xhci_resume().
xhci_suspend() will stop the primary HCD's root hub timer, but leaves
the shared HCD's timer running. This change adds stopping of the
shared HCD timer.
Signed-off-by: Al Cooper
---
drivers/usb/host/xhci.c
On Wed, Aug 06, 2014 at 03:29:47PM +0200, Douglas Gilbert wrote:
> If not and since I'm told black lists and the like won't
> work, my advice for the record is to use FreeBSD or Windows
> for tools that need this capability.
I doubt either of them forces users to hack up flags for these cases.
At
On Wed, 6 Aug 2014, Christoph Hellwig wrote:
> On Wed, Aug 06, 2014 at 03:29:47PM +0200, Douglas Gilbert wrote:
> > If not and since I'm told black lists and the like won't
> > work, my advice for the record is to use FreeBSD or Windows
> > for tools that need this capability.
>
> I doubt either
Please don't remove names from the CC: list; use Reply-To-All. I had
to go back and add all the names back in.
On Wed, 6 Aug 2014, Tiziano Bacocco wrote:
> Test with alcor based USB flash drives, linux 3.16 will remove the 3 msb of
> the CDB byte when using SG raw
Sure, but isn't that what you
On Wednesday 06 August 2014, Peter Griffin wrote:
> +int st_usb_platform_power_on(struct st_platform_priv *priv)
> +{
> + int clk, ret;
> +
> + if (priv->pwr) {
> + ret = reset_control_deassert(priv->pwr);
> + if (ret)
> + return ret;
> + }
>
On Wednesday 06 August 2014, Peter Griffin wrote:
> +static int st_ehci_platform_reset(struct usb_hcd *hcd)
> +{
> + struct platform_device *pdev = to_platform_device(hcd->self.controller);
> + struct usb_ehci_pdata *pdata = dev_get_platdata(&pdev->dev);
> + struct ehci_hcd *ehci = hcd
On Wednesday 06 August 2014, Peter Griffin wrote:
> This series adds support for the OHCI and EHCI on-chip controllers
> found in STi consumer electronics SoC's from STMicroelectronics.
>
> The series has been re-worked from v2 to split out the ehci and ohci parts
> into their own drivers / device
Hi,
Hope this is the right place to mention/post this; I'm new to this. As a
point of reference, I'm running uClinux on a bf609-ezkit that is based on
3.10, but from what I can tell this hasn't been changed/fixed since 3.10 yet
and applies in general.
As per section 4.3.2 of Universal Serial Bus
Hi,
On Wed, Aug 06, 2014 at 09:14:55PM +, Ken Helberg wrote:
> Hope this is the right place to mention/post this; I'm new to this. As a
> point of reference, I'm running uClinux on a bf609-ezkit that is based on
> 3.10, but from what I can tell this hasn't been changed/fixed since 3.10 yet
> a
Paul,
On Tue, Aug 5, 2014 at 1:08 PM, Paul Zimmerman
wrote:
>> Maybe dwc2 is refer to the Kconfig in dwc3 for there is a choice from
>> one of "Host only mode", "Gadget only mode" and "Dual Role mode",
>> which means the role is decided by the Kconfig.
>>
>> In my opinion, there maybe more than o
Kever,
On Tue, Aug 5, 2014 at 6:01 PM, Kever Yang wrote:
> According to the "dr_mode", the otg controller can work as
> device role and host role. Some boards always want to use host mode
> and some other boards want to use gadget mode. We use the dts setting
> to set dwc2's mode, rather than fix
From: Francois Romieu
It must be tristate to avoid broken dependencies with kernel built-in
usb network drivers when usb support is module only.
When net config option is set, least surprize default should match usb.
Wireless RNDIS USB driver used to select USB_USBNET. USB_USBNET now
depends on
On Wed, Aug 6, 2014 at 5:24 PM, Doug Anderson wrote:
> Kever,
>
> On Tue, Aug 5, 2014 at 6:01 PM, Kever Yang wrote:
>> According to the "dr_mode", the otg controller can work as
>> device role and host role. Some boards always want to use host mode
>> and some other boards want to use gadget mode
> From: diand...@google.com [mailto:diand...@google.com] On Behalf Of Doug
> Anderson
> Sent: Wednesday, August 06, 2014 3:25 PM
>
> On Tue, Aug 5, 2014 at 6:01 PM, Kever Yang wrote:
> > According to the "dr_mode", the otg controller can work as
> > device role and host role. Some boards always
From: Francois Romieu
Date: Thu, 7 Aug 2014 00:36:40 +0200
> From: Francois Romieu
>
> It must be tristate to avoid broken dependencies with kernel built-in
> usb network drivers when usb support is module only.
>
> When net config option is set, least surprize default should match usb.
>
> W
On 8/6/14, 5:57 PM, Paul Zimmerman wrote:
>> From: diand...@google.com [mailto:diand...@google.com] On Behalf Of Doug
>> Anderson
>> Sent: Wednesday, August 06, 2014 3:25 PM
>>
>> On Tue, Aug 5, 2014 at 6:01 PM, Kever Yang wrote:
>>> According to the "dr_mode", the otg controller can work as
>>>
Kever,
On Tue, Aug 5, 2014 at 6:01 PM, Kever Yang wrote:
> According to the "dr_mode", the otg controller can work as
> device role and host role. Some boards always want to use host mode
> and some other boards want to use gadget mode. We use the dts setting
> to set dwc2's mode, rather than fix
As, the interrupt for DMA is counted from 1, so need to checked
the USBA_NR_DMAS, in old way, it only check (USBA_NR_DMAS - 1),
so fix it.
Reported-by: Max Liao
Signed-off-by: Bo Shen
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This was used back when usbip-host was an interface device driver;
after the conversion to device driver, the table remained unused.
Remove it in order to stop receiving a warning about it.
Signed-off-by: Valentina Manea
---
drivers/usb/usbip/stub_dev.c | 27 ---
1 file c
At this point, USB/IP userspace code is fully functional
and can be moved out of staging.
Signed-off-by: Valentina Manea
---
{drivers/staging/usbip/userspace => tools/usb/usbip}/.gitignore | 0
{drivers/staging/usbip/userspace => tools/usb/usbip}/AUTHORS | 0
{drivers/stag
After migrating userspace code to libudev, converting usbip-host
to a device driver and various bug fixes and enhancements, USB/IP
is fully functional and can be moved out of staging.
This patch series moves it as following:
* userspace code to tools/usb/usbip
* kernel code to drivers/usb/usbip
B
At this point, USB/IP kernel code is fully functional
and can be moved out of staging.
Signed-off-by: Valentina Manea
---
drivers/staging/Kconfig| 2 --
drivers/staging/Makefile | 1 -
drivers/{staging => usb}/usbip/Kconfig
This is a resend of the patch series from March.
After migrating userspace code to libudev, converting usbip-host
to a device driver and various bug fixes and enhancements, USB/IP
is fully functional and can be moved out of staging.
This patch series moves it as following:
* userspace code to too
I am getting the following warn
drivers/net/usb/rtl8150.c:30:0: warning: "RSR" redefined
arch/xtensa/include/asm/processor.h:189:0: note: this is the location of the
previous definition
I wanted to remove RSR as it is not being used but it is not clear if being used
for documenting purpose. unde
On Thu, Aug 07, 2014 at 08:10:25AM +0300, Valentina Manea wrote:
> This is a resend of the patch series from March.
>
> After migrating userspace code to libudev, converting usbip-host
> to a device driver and various bug fixes and enhancements, USB/IP
> is fully functional and can be moved out of
From: Nick Krause
Date: Thu, 7 Aug 2014 07:24:54 +0200
> I am getting the following warn
>
> drivers/net/usb/rtl8150.c:30:0: warning: "RSR" redefined
> arch/xtensa/include/asm/processor.h:189:0: note: this is the location of the
> previous definition
>
> I wanted to remove RSR as it is not be
Replace a single-value sscanf() call with a call to kstrtou32(), as
recommended by checkpatch.pl.
Signed-off-by: Lars R. Damerow
---
drivers/staging/usbip/vhci_sysfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/usbip/vhci_sysfs.c
b/drivers/staging/usbip/
On Wed, Aug 06, 2014 at 04:02:22PM -0400, Alan Stern wrote:
> > I doubt either of them forces users to hack up flags for these cases.
>
> Why was this change needed in the first place? There's no explanation
> in the patch itself.
Which chance? The one to not support SG_FLAG_LUN_INHIBIT?
>
>
According to On-The-Go and Embedded Host Supplement to the USB Revision
2.0 Specification, a Targeted Host (non-PC host, OTG or Embedded host)
is not required to support operation with all types of USB peripherals.
It is up to the manufacturer of each Targeted Host to declare which peripherals
the
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
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 |
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 |
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
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/
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
52 matches
Mail list logo
