Introduce option -P / --pid to request that usbipd save its PID to
a file while running.
Signed-Off-By: Anthony Foiani anthony.foi...@gmail.com
---
drivers/staging/usbip/userspace/src/usbipd.c | 38 +++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git
A few whitespace changes allows the file to pass checkpatch --strict
(other than ignoring the CamelCase derived from the USB standard.)
Signed-Off-By: Anthony Foiani anthony.foi...@gmail.com
---
drivers/staging/usbip/userspace/src/usbipd.c | 31 ++--
1 file changed, 16
In the course of adapting the USBIP tools to our project, I added a
few features:
* Configure TCP/IP port number
* Save process id of 'usbipd'
I did some minor cleaning along the way: some checkpatch, later to
repair alignments broken while adding new options.
Finally, the log option was not
Give useful error messages when we can't create server sockets.
Signed-Off-By: Anthony Foiani anthony.foi...@gmail.com
---
drivers/staging/usbip/userspace/src/usbipd.c | 28 ++--
1 file changed, 22 insertions(+), 6 deletions(-)
diff --git
Add an option -p / --port to specify the TCP port to listen on.
Signed-Off-By: Anthony Foiani anthony.foi...@gmail.com
---
drivers/staging/usbip/userspace/src/usbip.c| 9 +--
.../staging/usbip/userspace/src/usbip_network.c| 30 ++
This option is checked for, and is in the long options list, but the
optstring didn't include it.
Signed-Off-By: Anthony Foiani anthony.foi...@gmail.com
---
drivers/staging/usbip/userspace/src/usbip.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Re-align the option lists.
Signed-Off-By: Anthony Foiani anthony.foi...@gmail.com
---
drivers/staging/usbip/userspace/src/usbip.c | 6 +++---
drivers/staging/usbip/userspace/src/usbipd.c | 10 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git
Using a simple integer makes the code easier to read and removes the
need to blank out array elements in case of errors.
Signed-Off-By: Anthony Foiani anthony.foi...@gmail.com
---
drivers/staging/usbip/userspace/src/usbipd.c | 27 ---
1 file changed, 12 insertions(+), 15
Using below configs, the compile will have error:
ERROR: ehci_init_driver undefined!
.config:
CONFIG_USB_CHIPIDEA=m
CONFIG_USB_CHIPIDEA_HOST=y
CONFIG_USB_CHIPIDEA_DEBUG=y
The reason is chipidea host uses symbol from ehci, but ehci
is not compiled. Let the chipidea host depend on
ehci even it is
Hi,
On Tue, Jun 18, 2013 at 08:07:01PM +0300, Aaro Koskinen wrote:
+static ssize_t vbus_state_show(struct device *device,
+struct device_attribute *attr, char *buf)
+{
+ struct tahvo_usb *tu = dev_get_drvdata(device);
+ return sprintf(buf, %d\n,
On Fri, Jun 21, 2013 at 10:46:10AM -0500, Ruchika Kharwar wrote:
Addition of the M and N recommended values for the USB3 PHY DPLL.
Sysclk for DRA7xx is 20MHz.
This yields:
Clk = 20MHz * M/(N+1) = 20MHz * 1000 /(7+1) = 2.5 Ghz
Signed-off-by: Nikhil Devshatwar nikhil...@ti.com
Signed-off-by:
Hi,
On Tue, Jun 25, 2013 at 05:38:23PM +0200, Tomasz Figa wrote:
This patch adds OF match table to the driver to allow instantiating it
using device tree.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
I will take this one only, the
Now, chipidea host has already depended on USB_EHCI_HCD
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/host/Kconfig |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
index 7d0aa5f..79b4503 100644
Chipidea controller is an EHCI compatible controller, with current
kconfig, even CONIFG_USB_EHCI_HCD is not chosen, but CONFIG_USB
is there, the chipidea code still will be compiled, in fact, it
is useless.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/Kconfig |
On 07/06/2013 11:39 PM, Ezequiel Garcia wrote:
Hi Sebastian,
Hello Ezequiel,
On Fri, Jul 5, 2013 at 10:32 AM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
This enables the two musb instances on am335x to work.
I like a lot the idea of splitting the DT representation of the two
On 07/07/2013 04:55 PM, Sergei Shtylyov wrote:
Hello.
Hello Sergei,
On 05-07-2013 20:12, Sebastian Andrzej Siewior wrote:
This is a first shot of the cppi41 DMA driver.
Where have you been when I submitted my drivers back in 2009? :-)
Not here it seems :) There is a driver I got
Hello Greg,
The USB_CONFIGFS_RNDIS depends on USB_U_RNDIS but does not select it.
The patch fixes it.
It was detected by Fengguag Wu's kbuild test robot. Thank you,
Fengguang Wu!
Sorry about the problem,
Regards,
Andrzej
Andrzej Pietrasiewicz (1):
usb/gadget: Kconfig: Fix configfs-based
USB_CONFIGFS_RNDIS depends on USB_U_RNDIS. Select it.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
Remove usb phy control module access from platform glue.
The same is now done using am phy driver and phy-omap-control.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/musb/musb_dsps.c | 105 +++
1 file changed, 36 insertions(+), 69
This patch series adds phy support for AM335X platform.
This patch series is based on Generic PHY framework [1].
This series has
- adds dual musb instances support for am335x platform (just for
testing)
- adds phy-am-usb driver used in AM platforms
- adds dt
From: Ravi Babu ravib...@ti.com
The dsps am33xx platform has two instances of musb controller,
enable the support for dual musb instances
Signed-off-by: Ravi Babu ravib...@ti.com
---
drivers/usb/musb/musb_dsps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Add DT bindings of phy nodes for AM33XX platform.
Signed-off-by: George Cherian george.cher...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 8e1248f..4f3cca0
Add API to power on/off USB PHY for AM335X. This API will be called
from phy-am-usb driver.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/phy/phy-omap-control.c | 32
include/linux/usb/omap_control_usb.h | 11 +++
2 files
Adds phy driver support for am33xx platform, the host/device
peripheral controller shall get this phy object to control the phy
operations.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/phy/Kconfig | 12 +++
drivers/phy/Makefile | 1 +
commit 09fc7d (usb: musb: fix incorrect usage of resource pointer)
assumes musb core will always have only 2 resources. But for OMAP
platforms there can be 3 resources (2 irq resource and 1 iomem
resource). Fixed it here.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So
added a new API to get the PHY reference by PHY label (PHY label
should be filled which creating the PHY).
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So used the
new API devm_usb_get_phy_by_name to get the PHY reference.
Signed-off-by: Kishon Vijay Abraham I
Now that MUSB for OMAP started using devm_usb_get_phy_by_name
which does not require PHY library to already have the binding
information, removed usb_bind_phy calls that binds the MUSB controller
with the PHY from the board files.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by:
This series fixes the USB enumeration issue caused because of the controller
not able to get a reference to the PHY because of incorrect binding in the
board file.
In the case of non-dt boot, the platform specific initialization file
(board file) will do usb_bind_phy that binds the usb controller
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy label) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Tested-by: Tomi Valkeinen tomi.valkei...@ti.com
---
Hi,
On Monday 08 July 2013 04:13 PM, George Cherian wrote:
Add API to power on/off USB PHY for AM335X. This API will be called
from phy-am-usb driver.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/phy/phy-omap-control.c | 32
Hi,
On Monday 08 July 2013 04:13 PM, George Cherian wrote:
Adds phy driver support for am33xx platform, the host/device
peripheral controller shall get this phy object to control the phy
operations.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/phy/Kconfig | 12
Hi,
On Monday 08 July 2013 04:13 PM, George Cherian wrote:
Add DT bindings of phy nodes for AM33XX platform.
Signed-off-by: George Cherian george.cher...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git
Hi,
On Monday 08 July 2013 04:13 PM, George Cherian wrote:
Remove usb phy control module access from platform glue.
The same is now done using am phy driver and phy-omap-control.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/musb/musb_dsps.c | 105
Hello.
On 08-07-2013 14:55, Kishon Vijay Abraham I wrote:
commit 09fc7d (usb: musb: fix incorrect usage of resource pointer)
assumes musb core will always have only 2 resources. But for OMAP
platforms there can be 3 resources (2 irq resource and 1 iomem
resource). Fixed it here.
hi,
I'm reading latest usb_skeleton.c sample and compared with that with ldd3 book.
Looks like the skel_read changed a lot against previous version. Why we now not
use usb_bulk_msg, just due to we want to get chance to cancel the urb if any
unexpected exit?
Also in current skel_read function, I
On Sat, Jul 6, 2013 at 9:39 PM, James Stone jamesmst...@gmail.com wrote:
On Sat, Jul 6, 2013 at 9:36 PM, James Stone jamesmst...@gmail.com wrote:
On Sat, Jul 6, 2013 at 3:41 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sat, 6 Jul 2013, James Stone wrote:
The output when I try to start
On Monday 08 July 2013 13:09:05 汪辰 wrote:
hi,
I'm reading latest usb_skeleton.c sample and compared with that with ldd3
book.
Looks like the skel_read changed a lot against previous version. Why we now
not use usb_bulk_msg, just due to we want to get chance to cancel the urb if
any
On 07/08/2013 02:28 AM, Felipe Balbi wrote:
On Fri, Jun 21, 2013 at 10:46:10AM -0500, Ruchika Kharwar wrote:
Addition of the M and N recommended values for the USB3 PHY DPLL.
Sysclk for DRA7xx is 20MHz.
This yields:
Clk = 20MHz * M/(N+1) = 20MHz * 1000 /(7+1) = 2.5 Ghz
Signed-off-by: Nikhil
On Mon, Jul 08, 2013 at 11:18:16AM +0200, Andrzej Pietrasiewicz wrote:
USB_CONFIGFS_RNDIS depends on USB_U_RNDIS. Select it.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
1 files
On Sat, Jul 06, 2013 at 11:13:15AM +0200, Oleksij Rempel wrote:
Hi Sarah,
thanks you or who ever fixed this issue. With latest wireless-testing
i can't reproduce my crash any more. Instead i get this messages:
What kernel is your wireless-testing branch based on?
It would be nice to know
On Mon, 8 Jul 2013, Manjunath Goudar wrote:
@@ -79,7 +93,10 @@ static int usb_hcd_ep93xx_probe(const struct
hc_driver *driver,
ep93xx_start_hc(pdev-dev);
- ohci_hcd_init(hcd_to_ohci(hcd));
+ ohci = hcd_to_ohci(hcd);
+ ohci-next_statechange = jiffies;
+
From: Sami Rahman sami.rah...@mmbresearch.com
Kernel Version: 3.5.0-34-generic
Added support for MMB Networks and Planet Innovation Ingeni ZigBee USB devices
using customized Silicon Labs' CP210x.c USB to UART bridge drivers with PIDs:
88A4, 88A5.
Signed-off-by: Sami Rahman
On Mon, 8 Jul 2013, Manjunath Goudar wrote:
Several aspects of this are strange. For example, consider how you
used the private part of the ohci_hcd structure and how the variable
names are inconsistent with the other OHCI glue drivers.
Here we are considering private date like clk
Hi,
On Mon, Jul 08, 2013 at 10:21:09AM +0300, Felipe Balbi wrote:
On Tue, Jun 18, 2013 at 08:07:01PM +0300, Aaro Koskinen wrote:
+static ssize_t vbus_state_show(struct device *device,
+ struct device_attribute *attr, char *buf)
+{
+ struct tahvo_usb *tu =
On 07/08/2013 12:43 PM, George Cherian wrote:
This patch series adds phy support for AM335X platform.
This patch series is based on Generic PHY framework [1].
This series has
- adds dual musb instances support for am335x platform (just for
testing)
- adds phy-am-usb
Hi,
On Mon, Jul 08, 2013 at 09:44:33PM +0200, Sebastian Andrzej Siewior wrote:
We need two nodes each one with a glue layer and a musb child node. The
instances crap in kernel has to vanish. Also that means your phy nodes
are wrong. This is not musb with two ports but two musb instances each
Hi Peter,
-Original Message-
From: Marek Vasut [mailto:ma...@denx.de]
Sent: Sunday, July 07, 2013 9:10 AM
To: Chen Peter-B29397
Cc: shawn@linaro.org; Michael Grzeschik; maxime.ripard@free-
electrons.com; Hector Palacios; linux-usb@vger.kernel.org;
s.ha...@pengutronix.de;
From: Stephen Warren [mailto:swar...@wwwdotorg.org]
Sent: Tuesday, July 02, 2013 7:41 PM
On 07/02/2013 07:47 PM, Stephen Warren wrote:
On 06/26/2013 02:20 PM, Paul Zimmerman wrote:
...
I hope whoever is supporting the Pi in the mainline kernel will try adding
dwc2 support now that it
-Original Message-
From: Marek Vasut [mailto:ma...@denx.de]
Sent: Sunday, July 07, 2013 9:10 AM
To: Chen Peter-B29397
Cc: shawn@linaro.org; Michael Grzeschik; maxime.ripard@free-
electrons.com; Hector Palacios; linux-usb@vger.kernel.org;
s.ha...@pengutronix.de;
Anthony Foiani anthony.foi...@gmail.com writes:
Introduce option -P / --pid to request that usbipd save its PID to
a file while running.
I've already spotted one problem with this patch:
+ write_pid_file(pid_file);
rc = do_standalone_mode(daemonize);
+
Anthony Foiani anthony.foi...@gmail.com writes:
Add an option -p / --port to specify the TCP port to listen on.
This is unfortunate, as port is also used to indicate which usbip
port is in use by a particular connection.
So I might change this to -t / --tcp-port in v2.
It's not a fatal flaw,
On Mon, Jul 8, 2013 at 9:39 AM, Devin Heitmueller
dheitmuel...@kernellabs.com wrote:
Hi Alan,
Thanks for taking the time to provide feedback. I'm just noticing now
that I left off the subject line, which all the more reason makes me
thankful that you bothered to read an email with as
Felipe, Andy, and Seb, I have a couple questions below.
On Fri, Jul 05, 2013 at 08:24:56PM +0300, Xenia Ragiadakou wrote:
The function dma_set_mask() tests internally whether the dma_mask pointer
for the device is initialized and fails if the dma_mask pointer is NULL.
On pci platforms, the
On 7/9/2013 1:14 AM, Sebastian Andrzej Siewior wrote:
On 07/08/2013 12:43 PM, George Cherian wrote:
This patch series adds phy support for AM335X platform.
This patch series is based on Generic PHY framework [1].
This series has
- adds dual musb instances support for am335x platform
usb_gadget_ops :: udc_stop might be called with driver = NULL since
511f3c5326eabe1ece35202a404c24c0aeacc246
(usb: gadget: udc-core: fix a regression during gadget driver unbinding)
Because of that, 2nd times insmod goes fail.
This patch fixes it up.
Reported-by: Yusuke Goda
56 matches
Mail list logo
