Hi Michal,
On 04/01/2015 05:17 PM, Michal Nazarewicz wrote:
> On Wed, Apr 01 2015, Robert Baldyga wrote:
>> FunctionFS can't support O_NONBLOCK because read/write operatons are
>> directly translated into USB requests which are asynchoronous, so we
>> can't know how long we will have to wait for
Hi Morimoto-san,
> From: Kuninori Morimoto
>
> Current usbhs_for_each_dfifo macro will read out-of-array's
> memory after last loop operation.
> It was not good C language operation, and the kernel which was
> compiled by (at least) gcc 4.8.1 will be broken.
>
> This patch is based on
> 925403f
This patch adds utilities transmit packets via WebSocket protocol.
WebSocket version of utilities as following.
usbws : command
usbwsa : application-side daemon
usbwsd : device-side daemon
The command supports all sub-command (ie. list, connect, disconnect, port,
bind, unbind, attach and de
This patch adds function and usage of export to README and manuals.
The wording, 'server' and 'client', is changed also.
For existing attach command, the daemon runs device side machine and attach
command is executed in application side machine. Then 'server' is used for
device side and 'client
Originally, USB/IP transmits requests and response PDUs for preparation to
transfer URBs in user space, after completion of the preparation, URBs are
transmitted in kernel space.
To make easy to introduce application network protocols like SSL, WebSocket,
the driver, usbip_ux.ko, forwards URBs
This patch allows to transfer both request/response between utilities and
userspace URBs transfer over SSL. OpenSSL is used for the implementation.
Options --with-ssl=yes at ./configure and --ssl to command and daemon enable
SSL. Default of --with-ssl is depends on existence of OpenSSL package.
Addition to README and manuals regarding USB/IP with SSL.
Signed-off-by: Nobuo Iwata
---
tools/usb/usbip/README | 13 -
tools/usb/usbip/doc/usbip.8 | 38 +++---
tools/usb/usbip/doc/usbipa.8 | 34 ++
tools/usb/usbi
This patch allows to substitute send, receive and shutdown routines for both a)
request/response PDUs among utilities and b) user space URBs transmission.
usbip_sock_t is introduced instead of sockfd. it includes function pointers of
send/receive/shutdown routines, an argument for the routines,
This patch adds 'const' qualifier to 'char*' arguments of library interfaces to
make acceptable std::string.c_str(). Essentially, these qualifiers are better
to be used even if not to use C++. Although, I just added to functions related
to previous patch.
Also, it changes C++ reserved words (ie
Originally, USB/IP transmits requests and response PDUs for preparation to
transfer URBs in user space, after the preparation, URBs are transmitted in
kernel space.
To make easy to introduce application network protocols like SSL, WebSocket and
so on, the driver, usbip_ux.ko, forwards URBs to U
USB/IP supports a function to import USB devices from application-side machine
by attach command.
The usage is as following.
dev:# (Physically attach your USB device.)
dev:# insmod usbip-core.ko and usbip-host.ko
dev:# usbipd -D // Start usbip daemon.
dev:# usbip list -l // List local USB devices
From: Kuninori Morimoto
Current usbhs_for_each_dfifo macro will read out-of-array's
memory after last loop operation.
It was not good C language operation, and the kernel which was
compiled by (at least) gcc 4.8.1 will be broken.
This patch is based on
925403f425a4a9c503f2fc295652647b1eb10d82
(u
stub_shutdown_connection() : drivers/usb/usbip/stub_dev.c
stub_device_cleanup_urbs() : drivers/usb/usbip/stub_main.c requests to
kill pending URBs and clears priv lists.
stub_complete() : drivers/usb/usbip/stub_tx.c might be called with URBs to have
been requested to kill.
To avoid kernel
Addition to README regarding user space URBs transmission.
Signed-off-by: Nobuo Iwata
---
tools/usb/usbip/README | 22 ++
1 file changed, 22 insertions(+)
diff --git a/tools/usb/usbip/README b/tools/usb/usbip/README
index 74f4afb..6b61da5 100644
--- a/tools/usb/usbip/README
To introduce some application protocols like WebSocket, this patch allows to
substitute connection establishment and termination. In combination with
previous patch, both connection and transmission can be replaced.
usbip_connection_operations_t includes open and close operation. Open method
re
Dear all,
This series of patches introduces WebSocket to USB/IP.
It also includes some independent features effective in themselves.
1) Exporting devices
Export request and response PDU had been defined in a header but not been used.
Now it works!
Also, it supports senarios, for example, co
To utilize core parts of USB/IP to application protocol implementations, this
patch derives libraries by exposing some functions of utilities and removing
some unnecessary portions.
Following functions are exposed.
For command:
- usbip_attach_device()
- usbip_detach_port()
- usbip_bind_device()
ed reference to `hwrng_register'
Signed-off-by: Randy Dunlap
---
drivers/usb/misc/Kconfig |1 +
1 file changed, 1 insertion(+)
--- linux-next-20150402.orig/drivers/usb/misc/Kconfig
+++ linux-next-20150402/drivers/usb/misc/Kconfig
@@ -258,6 +258,7 @@ config USB_LINK_LAYER_TEST
Hi Robert,
On 04/02/2015 10:13 PM, Robert Baldyga wrote:
> IRQ handler touches info->edev, so if interrupt occurs before extcon
> device initialization it can cause NULL pointer dereference. Doing extcon
> initialization before IRQ handler registration fixes this problem.
>
> Signed-off-by: Rober
Alan,
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Thursday, April 02, 2015 3:28 PM
> To: Liu, Bin
> Cc: Balbi, Felipe; linux-usb@vger.kernel.org
> Subject: RE: [PATCH v2] usb: musb: only set test mode once
>
> On Thu, 2 Apr 2015, Liu, Bin wrote:
>
>
On Thu, 2 Apr 2015, Liu, Bin wrote:
> > > This is to reset the bus, not the controller right? For the MUSB case,
> > > the controller itself needs reset, no device/hub is connected on the
> > > bus.
> >
> > IIRC, device-reset -D 1d6b:0002 -c 1 should work, but needs testing.
>
> I thought about
Felipe,
> -Original Message-
> From: Balbi, Felipe
> Sent: Thursday, April 02, 2015 2:53 PM
> To: Liu, Bin
> Cc: Balbi, Felipe; linux-usb@vger.kernel.org
> Subject: Re: [PATCH v2] usb: musb: only set test mode once
>
> Hi,
>
> On Thu, Apr 02, 2015 at 02:50:05PM -0500, Liu, Bin wrote:
> >
Hi,
On Thu, Apr 02, 2015 at 02:50:05PM -0500, Liu, Bin wrote:
> > > I really don't care about reset or not, it is just about board reboot,
> > > not a big deal. The only thing I want to do is prevent the *** user
> > > using the current driver loading test packets to FIFO multiple times
> > > whic
Felipe,
> -Original Message-
> From: Balbi, Felipe
> Sent: Thursday, April 02, 2015 2:44 PM
> To: Liu, Bin
> Cc: Balbi, Felipe; linux-usb@vger.kernel.org
> Subject: Re: [PATCH v2] usb: musb: only set test mode once
>
> On Thu, Apr 02, 2015 at 01:48:35PM -0500, Liu, Bin wrote:
> > Felipe,
On Thu, Apr 02, 2015 at 01:48:35PM -0500, Liu, Bin wrote:
> Felipe,
>
> > -Original Message-
> > From: Balbi, Felipe
> > Sent: Thursday, April 02, 2015 1:22 PM
> > To: Liu, Bin
> > Cc: linux-usb@vger.kernel.org; Balbi, Felipe
> > Subject: Re: [PATCH v2] usb: musb: only set test mode once
>
Felipe,
> -Original Message-
> From: Liu, Bin
> Sent: Thursday, April 02, 2015 11:45 AM
> To: linux-usb@vger.kernel.org
> Cc: Balbi, Felipe
> Subject: RE: [PATCH v2] usb: musb: only set test mode once
>
> Felipe,
>
> > -Original Message-
> > From: Liu, Bin
> > Sent: Tuesday, Marc
Felipe,
> -Original Message-
> From: Balbi, Felipe
> Sent: Thursday, April 02, 2015 1:22 PM
> To: Liu, Bin
> Cc: linux-usb@vger.kernel.org; Balbi, Felipe
> Subject: Re: [PATCH v2] usb: musb: only set test mode once
>
> On Thu, Apr 02, 2015 at 11:44:30AM -0500, Liu, Bin wrote:
> > Felipe,
On Thu, Apr 02, 2015 at 11:44:30AM -0500, Liu, Bin wrote:
> Felipe,
>
> > -Original Message-
> > From: Liu, Bin
> > Sent: Tuesday, March 24, 2015 3:09 PM
> > To: linux-usb@vger.kernel.org
> > Cc: Balbi, Felipe; Liu, Bin
> > Subject: [PATCH v2] usb: musb: only set test mode once
> >
> > Th
Felipe,
> -Original Message-
> From: Liu, Bin
> Sent: Tuesday, March 24, 2015 3:09 PM
> To: linux-usb@vger.kernel.org
> Cc: Balbi, Felipe; Liu, Bin
> Subject: [PATCH v2] usb: musb: only set test mode once
>
> The MUSB test mode register can only be set once, otherwise the result is
> unde
On Thu, 2 Apr 2015, Pieter Roodnat wrote:
> Hi Alan,
Hello.
> Sorry for bothering you like this, but i am getting pretty desperate and on
> what i see here
> http://www.spinics.net/lists/linux-usb/msg60916.html
> you are a real expert on this topic.
> So i boldly ask you the following, hoping y
On Thu, Apr 02, 2015 at 04:25:50PM +0200, Dr. H. Nikolaus Schaller wrote:
> But it is outdated. The parameters vendor= and product= are no longer
> available since ca. 3.12 which means that documentation is lagging behind
> quite some time.
> >>>
> >>> This is simply not true. The
Hi,
Am 30.03.2015 um 12:08 schrieb Johan Hovold :
> On Mon, Mar 30, 2015 at 11:32:39AM +0200, Dr. H. Nikolaus Schaller wrote:
>> Hi Johan,
>>
>> Am 30.03.2015 um 09:45 schrieb Johan Hovold :
>>
>>> On Sat, Mar 28, 2015 at 02:37:57PM +0100, Marek Belisko wrote:
From: "H. Nikolaus Schaller"
On Wed, 1 Apr 2015, Arun Ramamurthy wrote:
> Getting phys by index instead of phy names so that we do
> not have to create a naming scheme when multiple phys
> are present
>
> Signed-off-by: Arun Ramamurthy
> Reviewed-by: Ray Jui
> Reviewed-by: Scott Branden
> @@ -204,36 +197,23 @@ static in
On 02/04/15 16:13, Robert Baldyga wrote:
> This patch adds VBUS pin detection support to extcon-usb-gpio driver.
> It allows to use this driver with boards which have both VBUS and ID
> pins, or only one of them.
>
> Following table of states presents relationship between this signals
> and detect
On Thu, 2 Apr 2015, Peter Chen wrote:
> On Wed, Apr 01, 2015 at 10:35:16AM -0400, Alan Stern wrote:
> > On Wed, 1 Apr 2015, Peter Chen wrote:
> >
> > > > This is bad. All the endpoints have maxpacket = 1023, and that's much
> > > > too big for this test. We need a maxpacket size of 64 (maybe a
IRQ handler touches info->edev, so if interrupt occurs before extcon
device initialization it can cause NULL pointer dereference. Doing extcon
initialization before IRQ handler registration fixes this problem.
Signed-off-by: Robert Baldyga
Acked-by: Roger Quadros
---
drivers/extcon/extcon-usb-g
Hello,
This patch set modifies extcon-usb-gpio driver fixing bugs, and adds
new features - VBUS pin detection support and 'debounce' property in
devicetree node. It also updates documentation with information about
new features.
More detailed description of changes can be found in commit messages
This patch adds VBUS pin detection support to extcon-usb-gpio driver.
It allows to use this driver with boards which have both VBUS and ID
pins, or only one of them.
Following table of states presents relationship between this signals
and detected cable type:
State |ID | VBU
This patch adds devicetree property for setting debounce value. It allows
to set debounce time shorter or longer depending on the needs of given
platform.
Signed-off-by: Robert Baldyga
Acked-by: Roger Quadros
---
drivers/extcon/extcon-usb-gpio.c | 14 +-
1 file changed, 9 insertions
Add information about VBUS pin detection support, 'debounce' property
and some other details.
Signed-off-by: Robert Baldyga
Acked-by: Roger Quadros
---
.../devicetree/bindings/extcon/extcon-usb-gpio.txt | 28 --
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/
Hi,
While testing for OTG/DRD [1], I encountered a couple of
problems with the XHCI driver.
The first 2 patches clean up the HCD allocation logic as we want
both primary and shared HCDs to be allocated before the
primary HCD registers for OTG use. That's the only way the OTG
core will know that i
Don't set xhci->shared_hcd to NULL in xhci_stop() as we have
still not de-allocated it. It was resulting in a NULL pointer
de-reference if usb_add/remove_hcd() is called repeatedly.
We want repeated add/remove to work for the OTG use case.
Signed-off-by: Roger Quadros
---
drivers/usb/host/xhci.
HCD core allocates memory for HCD private data in
usb_create_[shared_]hcd() so make use of that
mechanism to allocate the struct xhci_hcd.
Introduce struct xhci_driver_overrides to provide
the size of HCD private data and hc_driver operation
overrides. As of now we only need to override the
reset
The problem seems to be that if a new device is detected
while we have already removed the shared HCD, then many of the
xhci operations (e.g. xhci_alloc_dev(), xhci_setup_device())
hang as command never completes.
I don't think XHCI can operate without the shared HCD as we've
already called xhci_
In the OTG case, the controller might not yet have been
added or is removed before the system suspends.
Assign xhci->main_hcd during probe to prevent NULL
pointer de-reference in xhci_suspend/resume().
Use the hcd->state flag to check if HCD is halted
and if that is so do nothing for xhci_suspend
As xhci_hcd is now allocated by usb_create_hcd(), we don't
need to add the primary HCD before creating the shared HCD.
Creating the shared HCD before adding the primary HCD is particularly
useful for the OTG use case so that we know at the OTG core if
the HCD is in single configuration or dual (pr
Robert,
On 01/04/15 14:49, Robert Baldyga wrote:
> Hi Roger,
>
> On 04/01/2015 01:28 PM, Roger Quadros wrote:
>> Robert,
>>
>> On 01/04/15 10:23, Robert Baldyga wrote:
>>> This patch adds VBUS pin detection support to extcon-usb-gpio driver.
>>> It allows to use this driver with boards which have
On Wed, 1 Apr 2015, Oliver Neukum wrote:
> > I am postponing all these before it is clarified that this is indeed a
> > case reporter is able to reproduce on different system as well to rule out
> > the possibility of hub being the actual root cause.
>
> The test has been redone on a different
On Thu, 2 Apr 2015 12:35:09 +0200
Johan Hovold wrote:
> This patch was incorrect and needed to be updated as discussed in the
> thread. Can you drop it or is your tree immutable?
Sigh...and I thought I was on top of that. Dropped, sorry for the
confusion.
jon
--
To unsubscribe from this list:
According to the technical update (No. TN-RCS-B011A/E), the UGSTS LOCK
bit location is bit 8, not bits 9 and 8. So, this patch fixes the
USBHS_UGSTS_LOCK value.
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/phy/phy-rcar-gen2-usb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
This reverts commit <1dc6120ef7f003305d99ef12f598a6b05eacc38c>.
if we are doing allyesconfig on x86_64, build fails with error:
drivers/built-in.o: In function `sl811_cs_probe':
sl811_cs.c:(.text+0x1d4612e): undefined reference to `sl811h_driver'
this commit has declared sl811h_driver as static b
Am 02.04.2015 um 12:35 schrieb Johan Hovold :
> On Thu, Apr 02, 2015 at 12:12:37PM +0200, Jonathan Corbet wrote:
>> On Sat, 28 Mar 2015 14:37:57 +0100
>> Marek Belisko wrote:
>>
>>> This patch changes the documentation file as needed.
>>
>> Applied to the docs tree (with the changelog typo fix
On Thu, Apr 02, 2015 at 12:12:37PM +0200, Jonathan Corbet wrote:
> On Sat, 28 Mar 2015 14:37:57 +0100
> Marek Belisko wrote:
>
> > This patch changes the documentation file as needed.
>
> Applied to the docs tree (with the changelog typo fixed).
This patch was incorrect and needed to be updated
On Sat, 28 Mar 2015 14:37:57 +0100
Marek Belisko wrote:
> This patch changes the documentation file as needed.
Applied to the docs tree (with the changelog typo fixed).
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vge
54 matches
Mail list logo
