Hi Arnd,
2018-04-04 17:43 GMT+09:00 Arnd Bergmann :
> On Wed, Apr 4, 2018 at 10:00 AM, Felipe Balbi
> wrote:
>>
>> Hi,
>>
>> Masahiro Yamada writes:
> Each DWC3 instance is connected with
> multiple HS PHYs and multiple SS PHYs,
> depending on the number of ports.
in that c
On Wed, Apr 4, 2018 at 10:00 AM, Felipe Balbi
wrote:
>
> Hi,
>
> Masahiro Yamada writes:
Each DWC3 instance is connected with
multiple HS PHYs and multiple SS PHYs,
depending on the number of ports.
>>>
>>> in that case, you shouldn't need dwc3 at all. A Host-only dwc3 is xHCI
>>>
Hi,
Masahiro Yamada writes:
>>> Each DWC3 instance is connected with
>>> multiple HS PHYs and multiple SS PHYs,
>>> depending on the number of ports.
>>
>> in that case, you shouldn't need dwc3 at all. A Host-only dwc3 is xHCI
>> compliant. If you really don't have the gadget block, there's no n
2018-04-04 15:04 GMT+09:00 Felipe Balbi :
>
> Hi,
>
> Masahiro Yamada writes:
>> 2018-04-04 14:36 GMT+09:00 Felipe Balbi :
>>>
>>> Hi,
>>>
>>> Masahiro Yamada writes:
Currently, DWC3 core IP (drivers/usb/dwc3/core.c)
can take only one PHY phandle for each of SS, HS.
(phy-names DT p
Hi,
Masahiro Yamada writes:
> 2018-04-04 14:36 GMT+09:00 Felipe Balbi :
>>
>> Hi,
>>
>> Masahiro Yamada writes:
>>> Currently, DWC3 core IP (drivers/usb/dwc3/core.c)
>>> can take only one PHY phandle for each of SS, HS.
>>> (phy-names DT property is "usb2-phy" and "usb3-phy" for each)
>>
>> We
2018-04-04 14:36 GMT+09:00 Felipe Balbi :
>
> Hi,
>
> Masahiro Yamada writes:
>> Currently, DWC3 core IP (drivers/usb/dwc3/core.c)
>> can take only one PHY phandle for each of SS, HS.
>> (phy-names DT property is "usb2-phy" and "usb3-phy" for each)
>
> We never had any other requirements :-)
>
>>
Hi,
Masahiro Yamada writes:
> Currently, DWC3 core IP (drivers/usb/dwc3/core.c)
> can take only one PHY phandle for each of SS, HS.
> (phy-names DT property is "usb2-phy" and "usb3-phy" for each)
We never had any other requirements :-)
> The DWC3 core IP is provided by Synopsys,
> but some SoC
Hi.
Currently, DWC3 core IP (drivers/usb/dwc3/core.c)
can take only one PHY phandle for each of SS, HS.
(phy-names DT property is "usb2-phy" and "usb3-phy" for each)
The DWC3 core IP is provided by Synopsys,
but some SoC-dependent parts (a.k.a glue-layer)
are implemented by SoC venders.
The num
On 01/19/2017 07:15 AM, Shuah Khan wrote:
> On 01/19/2017 02:35 AM, Greg KH wrote:
>> On Fri, Jan 13, 2017 at 04:38:32PM -0700, Shuah Khan wrote:
>>> Update USB/IP driver location in README.
>>>
>>> Signed-off-by: Shuah Khan
>>> Reviewed-by: Krzysztof
On 01/19/2017 02:35 AM, Greg KH wrote:
> On Fri, Jan 13, 2017 at 04:38:32PM -0700, Shuah Khan wrote:
>> Update USB/IP driver location in README.
>>
>> Signed-off-by: Shuah Khan
>> Reviewed-by: Krzysztof Opasiak
>> ---
>> tools/usb/usbip/README | 2 +
On Fri, Jan 13, 2017 at 04:38:32PM -0700, Shuah Khan wrote:
> Update USB/IP driver location in README.
>
> Signed-off-by: Shuah Khan
> Reviewed-by: Krzysztof Opasiak
> ---
> tools/usb/usbip/README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --g
On 01/14/2017 12:38 AM, Shuah Khan wrote:
> Update USB/IP driver location in README.
>
> Signed-off-by: Shuah Khan
Reviewed-by: Krzysztof Opasiak
Best regards,
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
--
To unsubscribe from this list: send the line
Update USB/IP driver location in README.
Signed-off-by: Shuah Khan
---
tools/usb/usbip/README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/usb/usbip/README b/tools/usb/usbip/README
index 831f49f..f349ef4 100644
--- a/tools/usb/usbip/README
+++ b/tools/usb/usbip
This is a note to let you know that I've just added the patch titled
usb: ip: remove unnecessary & operation
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next relea
This is a note to let you know that I've just added the patch titled
usb: ip: remove unnecessary & operation
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-testing branch.
The patch will show up in the next r
Now that usb_endpoint_maxp() only returns the lowest
11 bits from wMaxPacketSize, we can remove the &
operation from this driver.
Cc: Valentina Manea
Cc: Shuah Khan
Cc:
Signed-off-by: Felipe Balbi
---
drivers/usb/usbip/vudc_dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
Now that usb_endpoint_maxp() only returns the lowest
11 bits from wMaxPacketSize, we can remove the &
operation from this driver.
Cc: Valentina Manea
Cc: Shuah Khan
Cc:
Signed-off-by: Felipe Balbi
---
drivers/usb/usbip/vudc_dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
On Tue, Mar 08, 2016 at 09:48:55PM +0100, Krzysztof Opasiak wrote:
> Hi,
>
> This series extends USB/IP support in Kernel by adding an emulated
> USB Device Controller. This allows to virtually connect USB gadget
> created on a server to some remote machine as if it would be a ful
From: Igor Kotrasinski
Add header with definitions needed by vudc driver.
This commit is a result of cooperation between Samsung R&D Institute
Poland and Open Operating Systems Student Society at University
of Warsaw (O2S3@UW) consisting of:
Igor Kotrasinski
Karol Kosik
Ewelina Ko
Hi,
This series extends USB/IP support in Kernel by adding an emulated
USB Device Controller. This allows to virtually connect USB gadget
created on a server to some remote machine as if it would be a fully
functional USB device.
--
Current design
Is there anyone who can help me with this deadlock?
Thanks,
Andrew
> -Original Message-
> From: Andrew Goodbody
> Sent: 14 December 2015 16:23
> To: linux-usb@vger.kernel.org
> Subject: Deadlock in USB/IP driver
>
> https://bugzilla.kernel.org/show_bug.cgi?id=109
so I
am simply attaching the file this time.
Andrew
Dec 10 15:03:20 cbrx-fw01 kernel: [ 220.497958] usbip_core: USB/IP Core v1.0.0
Dec 10 15:03:20 cbrx-fw01 kernel: [ 220.499707] vhci_hcd vhci_hcd: USB/IP
Virtual Host Controller
Dec 10 15:03:20 cbrx-fw01 kernel: [ 220.499713] vhci_hcd vhci_hcd
I have an application using the USB/IP drivers and I turned on the lock
debugging and checking options in the kernel.
I now get this deadlock report in syslog
Dec 11 15:03:20 cbrx-fw01 kernel: [ 220.497958] usbip_core: USB/IP Core v1.0.0
Dec 10 15:03:20 cbrx-fw01 kernel: [ 220.499707
Dear Valentina,
Thank you for reviewing.
> > For this, export function, connection is established from
device-side
> machine to application-side machine.
> >
> > Following use cases are supposed for the export function.
> > 1) Server application or cloud service serves distributed ubiquitous
> d
Hi,
On Fri, Apr 3, 2015 at 3:33 AM, Nobuo Iwata wrote:
>
> For this, export function, connection is established from device-side machine
> to application-side machine.
>
> Following use cases are supposed for the export function.
> 1) Server application or cloud service serves distributed ubiqui
ider your patches to
> be merged.
My pleasure.
> I don't think that question was really answered.
Sorry. I misread that your question ('this work') was about SSL.
> Why do you need / want websockets here?
WebSocket is needed for USB/IP in internet.
Linux is the most pop
to:g...@kroah.com]
> Sent: Friday, April 03, 2015 5:07 PM
> To: fx IWATA NOBUO
> Cc: valentina.mane...@gmail.com; shuah...@samsung.com;
> linux-usb@vger.kernel.org; fx MICHIMURA TADAO
> Subject: Re: [PATCH 04/13] USB/IP: kernel module for userspace URBs
> transmission
>
>
On Fri, Apr 03, 2015 at 09:33:32AM +0900, Nobuo Iwata wrote:
> 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 ne
package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
diff --git a/tools/usb/usbip/websocket/Makefile.am
b/too
0: at Full Speed(12Mbps)
diff --git a/tools/usb/usbip/doc/usbip.8 b/tools/usb/usbip/doc/usbip.8
index a6097be..dfaabba 100644
--- a/tools/usb/usbip/doc/usbip.8
+++ b/tools/usb/usbip/doc/usbip.8
@@ -6,9 +6,12 @@ usbip \- manage USB/IP devices
[\fIoptions\fR] <\fIcommand\fR> <\fIargs\fR>
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
ext);
+ }
+#endif
close(sock->fd);
free(sock);
}
diff --git a/tools/usb/usbip/src/usbip_network.h
b/tools/usb/usbip/src/usbip_network.h
index 1c304e0..3f7d0d3 100644
--- a/tools/usb/usbip/src/usbip_network.h
+++ b/tools/usb/usbip/src/usbip_network.h
@@ -17,6 +17,
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
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
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
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
and receive URBs in kernel space. The usbip_ux.ko kernel module
alternates the route to user space by forwarding USBs through USB/IP utilities
(ie. usbip, usbipd, usbipa). When userspace transmission enabled, usbip attach
and connect will continue executing until usbip detach or disconnect is
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
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
On Fri, Nov 21, 2014 at 5:36 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Fri, 21 Nov 2014 16:33:18 +0100
>
> The usb_put_dev() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected by us
From: Markus Elfring
Date: Fri, 21 Nov 2014 16:33:18 +0100
The usb_put_dev() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drive
On Wed, Aug 20, 2014 at 12:44:45PM +0530, sanjeev sharma wrote:
> Hello Valentina,
>
> I have started looking into USB IP Project and this look's very interesting
> and
> Do we have anything left in this Project apart from reviewing user-land
> protocol ?
What do you
This patch adds an entry in MAINTAINERS file for USB/IP
driver.
Signed-off-by: Valentina Manea
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index aefa948..76ac03d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9515,6 +9515,14 @@ S
On Tue, Feb 18, 2014 at 12:04:23AM +0700, konst...@ngs.ru wrote:
> Greetings.
>
> How can I build USB/IP kernel modules and userspace tools
> sparsely from linux kernel tree?
>
>
> I've tried
>
> make O=/home/build/directory/ drivers/staging/usbip/
>
>
Greetings.
How can I build USB/IP kernel modules and userspace tools
sparsely
from linux kernel tree?
I've tried
make O=/home/build/directory/ drivers/staging/usbip/
but this only compiles .c files to .o files, but doesn't
link them to kernel object .ko files.
And I nee
From: Greg KH
> > I found it much easier to build a non-initrd kernel (ie one that
> > has all the devices needed to boot builtin) than to work out
> > how to build one that contains an initrd image.
>
> Then you are using the wrong distro, as a simple 'make install' in the
> kernel directory shou
On Mon, Feb 10, 2014 at 09:52:52AM +, David Laight wrote:
> From: Peter Stuge
> > konst...@ngs.ru wrote:
> > > If so, which linux distro is worth being chosen for
> > > building and testing that custom kernel and, especially,
> > > usbip, in particular, and does distro really matter?
> >
> > I
From: Peter Stuge
> konst...@ngs.ru wrote:
> > If so, which linux distro is worth being chosen for
> > building and testing that custom kernel and, especially,
> > usbip, in particular, and does distro really matter?
>
> It depends on how much "value add" the distribution has around the
> kernel.
konst...@ngs.ru wrote:
> If so, which linux distro is worth being chosen for
> building and testing that custom kernel and, especially,
> usbip, in particular, and does distro really matter?
It depends on how much "value add" the distribution has around the
kernel.
The well-known distributions al
On Sun, Feb 09, 2014 at 01:52:50PM +0700, konst...@ngs.ru wrote:
> So, as far as I've concerned, I'd better build the whole
> custom linux kernel with the usbip debug-driver built-in
> to debug usbip, wouldn't I?
Yes, but build it as a module to make things easier than rebooting all
the time. Or
Greetings.
I've got an educational challenging task to develop
my own or to improve an existing one USB
device over IP network sharing system. And I've
made a decision to explore USB/IP project.
I've tried to explore it on my own, but I still have
questions which I haven't
> usb-storage
linux-166:# virsh attach-device suse usb.xml
Device attached successfully
linux-166:# cat usb.xml
Dmesg log :
[13603.742271] vhci_hcd vhci_hcd: USB/IP Virtual Host Controller
[13603.742278] vhci_hcd vhci_hcd: new USB bus registered, assigned bu
55 matches
Mail list logo
