From: Arnd Bergmann
This takes the MAC address for smsc75xx/smsc95xx USB network devices
from a the device tree. This is required to get a usable persistent
address on the popular beagleboard, whose hardware designers
accidentally forgot that an ethernet device really requires an a
MAC address to
Hi Greg,
Here are some new device ids for rc6. These have been in next for a few
days now without any issues.
Thanks,
Johan
The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9:
Linux 4.6-rc4 (2016-04-17 19:13:32 -0700)
are available in the git repository at:
git://
Hi,
On 04/28/2016 02:42 PM, Arnd Bergmann wrote:
> With the addition of VUDC, the USBIP stack can now be used on
> configurations without USB host support, but trying to build
Not exactly. This is the goal but unfortunately for now this will not
work... Most of USB_IP common functions operates o
If choices consist of choice_values of type tristate that depend on
symbols set to 'm', those choice_values are not set to 'n' if the
choice is changed from 'm' to 'y' (in which case only one active
choice_value is allowed). Those values are also written to the config
file causing modules to be bui
On 04/28/2016 09:21 PM, Dan Carpenter wrote:
> Hello Igor Kotrasinski,
>
> The patch 80fd9cd52de6: "usbip: vudc: Add VUDC main file" from Mar 8,
> 2016, leads to the following static checker warning:
>
> drivers/usb/usbip/vudc_main.c:88 init()
> warn: perhaps platform_device_put() w
Added support for Gemalto's Cinterion PH8 and AHxx products
with 2 RmNet Interfaces and products with 1 RmNet + 1 USB Audio interface.
In addition some minor renaming and formatting.
Signed-off-by: Hans-Christoph Schemmel
---
Changes in v2:
- using USB_DEVICE_INTERFACE_CLASS instead of USB_DEV
Ahh.. Too bad.
Thanks for looking at this.
regards,
dan carpenter
--
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
Hello Igor Kotrasinski,
The patch ea6873a45a22: "usbip: vudc: Add SysFS infrastructure for
VUDC" from Mar 8, 2016, leads to the following static checker warning:
drivers/usb/usbip/vudc_sysfs.c:201 usbip_status_show()
error: we previously assumed 'udc' could be null (see line 200)
On Tue, Apr 26, 2016 at 03:24:53PM +0300, Maksim Salau wrote:
> Hi Johan,
>
> On Sun, 24 Apr 2016 15:36:35 +0200
> Johan Hovold wrote:
>
> > On Mon, Feb 29, 2016 at 04:11:20PM +0300, Maksim Salau wrote:
> > > The adaptor can be found on development boards for 78k, RL78 and V850
> > > microcontro
On 04/29/2016 11:02 AM, Dan Carpenter wrote:
> Hello Igor Kotrasinski,
>
> The patch ea6873a45a22: "usbip: vudc: Add SysFS infrastructure for
> VUDC" from Mar 8, 2016, leads to the following static checker warning:
>
> drivers/usb/usbip/vudc_sysfs.c:201 usbip_status_show()
> error:
On Thursday 14 April 2016 03:07 PM, Rafał Miłecki wrote:
> Northstar is a family of SoCs used in home routers. They have USB 2.0
> and 3.0 controllers with PHYs that need to be properly initialized.
> This driver provides PHY init support in a generic way and can be bound
> with an EHCI controlle
On Thursday 14 April 2016 03:07 PM, Rafał Miłecki wrote:
> Northstar is a family of SoCs used in home routers. They have USB 2.0
> and 3.0 controllers with PHYs that need to be properly initialized.
> This driver provides PHY init support in a generic way and can be bound
> with an EHCI controlle
On Thu, Mar 24, 2016 at 10:53:27AM +0300, Valentin Yakovenkov wrote:
> Sorry, I missed the branch.
>
> Here it is.
Thanks for the patch. Please resubmit it on a format that can be applied
(i.e. without quoted text, etc). Remember to include a patch
revision in the Subject when resubmitting patche
Hi Felipe,
I am trying to bring up a USB 3.0 Host Controller with an ARM64 platform (Juno)
and I was also getting the dma issue discussed in this thread:
https://www.mail-archive.com/linux-usb@vger.kernel.org/msg73137.html
I then applied Grygorii Strashko' patch and managed to have a bus instant
Hi João,
Joao Pinto writes:
> I am trying to bring up a USB 3.0 Host Controller with an ARM64 platform
> (Juno)
> and I was also getting the dma issue discussed in this thread:
>
> https://www.mail-archive.com/linux-usb@vger.kernel.org/msg73137.html
>
> I then applied Grygorii Strashko' patch a
Hi Felipe,
I confirmed that no interrupts are received. My hw colleague is going to check
the design!
On 4/29/2016 11:25 AM, Felipe Balbi wrote:
>
> Hi João,
>
> Joao Pinto writes:
>> I am trying to bring up a USB 3.0 Host Controller with an ARM64 platform
>> (Juno)
>> and I was also getting t
One line above we have checked that udc is NULL so we shouldn't
dereference it while printing error message.
Reported-by: Dan Carpenter
Signed-off-by: Krzysztof Opasiak
---
drivers/usb/usbip/vudc_sysfs.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/usbip/vu
Hi,
Patches are independent, please pick up as you wish.
However all of them are needed to solve the issue, so I am sending
everything together for easier testng.
Problem
===
When Odroid U3 (usb3503 + smsc95xx + max77686) boots from network (TFTP),
the usb3503 does not show up in "lsusb". H
The enable time for buck regulators was not configured but actually is
essential: consumers, like usb3503, doing hard reset (regulator off/on)
should wait for the regulator to settle.
Configure the enable time according to datasheet.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/max7
On Odroid U3 (Exynos4412-based) board if USB was initialized by
bootloader (in U-Boot "usb start" before tftpboot), the HUB after after
successful probing was not visible in the system ("lsusb"). Connected
devices were not visible neither.
In such case the USB3503 has to be fully reset before conf
On Odroid U3 (Exynos4412-based) board if USB was initialized by
bootloader (in U-Boot "usb start" before tftpboot), the HUB after
successful probing was not visible in the system ("lsusb"). Connected
devices were not visible neither.
The USB3503 takes optional regulator so provide one - buck8 on O
On 2016年04月28日 20:21, Felipe Balbi wrote:
I also attach git log of system/core/adb/usb_linux_client.cpp of Android
N for your reference.
"
Author: Badhri Jagan Sridharan
Date: Mon Oct 5 13:04:03 2015 -0700
adbd: Add os descriptor support for adb.
Eventhough windows does not rely
On Fri, Apr 29, 2016 at 12:59:49PM +0200, Krzysztof Kozlowski wrote:
> +++ b/Documentation/devicetree/bindings/usb/usb3503.txt
> @@ -24,6 +24,7 @@ Optional properties:
> pins (optional, if not provided, driver will not set rate of the
> REFCLK signal and assume that a value from the pr
The patch
regulator: max77686: Configure enable time to properly handle regulator
enable
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually s
From: Igor Kotrasinski
We read a struct usb_device_descriptor from it, so make it an actual
binary attribute.
Signed-off-by: Igor Kotrasinski
Signed-off-by: Krzysztof Opasiak
Tested-by: Krzysztof Opasiak
---
drivers/usb/usbip/vudc_sysfs.c | 20 ++--
1 file changed, 14 inser
On 04/29/2016 01:30 PM, Mark Brown wrote:
> On Fri, Apr 29, 2016 at 12:59:49PM +0200, Krzysztof Kozlowski wrote:
>
>> +++ b/Documentation/devicetree/bindings/usb/usb3503.txt
>> @@ -24,6 +24,7 @@ Optional properties:
>> pins (optional, if not provided, driver will not set rate of the
>> R
Hi,
Jim Lin writes:
> On 2016年04月28日 20:21, Felipe Balbi wrote:
>>>
>>> I also attach git log of system/core/adb/usb_linux_client.cpp of Android
>>> N for your reference.
>>> "
>>> Author: Badhri Jagan Sridharan
>>> Date: Mon Oct 5 13:04:03 2015 -0700
>>>
>>> adbd: Add os descriptor sup
Hi,
Joao Pinto writes:
> Hi Felipe,
> I confirmed that no interrupts are received. My hw colleague is going to check
> the design!
>
> On 4/29/2016 11:25 AM, Felipe Balbi wrote:
>>
>> Hi João,
>>
>> Joao Pinto writes:
>>> I am trying to bring up a USB 3.0 Host Controller with an ARM64 platfor
On Fri, Apr 15, 2016 at 11:14:04PM +0200, Grigori Goronzy wrote:
> This may fail, do not assume it always works.
>
> Signed-off-by: Grigori Goronzy
> ---
> drivers/usb/serial/ch341.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/usb/serial/ch341.c b/drivers
On Fri, Apr 15, 2016 at 11:14:05PM +0200, Grigori Goronzy wrote:
> BREAK2 seems to be a misnomer, the register configures various aspects
> of the UART configuration.
>
> Signed-off-by: Grigori Goronzy
Finally. Thanks for fixing this. :)
Johan
--
To unsubscribe from this list: send the line "un
On Fri, Apr 15, 2016 at 11:14:06PM +0200, Grigori Goronzy wrote:
No commit message?
> Signed-off-by: Grigori Goronzy
> ---
> drivers/usb/serial/ch341.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
> index 1ab
Hello Peter,
On 16-04-27 13:41:35, Peter Chen wrote:
> On Wed, Apr 27, 2016 at 10:20:53AM +0530, maitysancha...@gmail.com wrote:
> > >
> > > Do you know the connect/disconnect by using USB Cable (not ID cable), I
> > > just want to know if the software can know connection,
> >
> > I did not und
On Fri, Apr 15, 2016 at 11:14:07PM +0200, Grigori Goronzy wrote:
> Use the correct types and sizes.
>
> v2: use u8 shorthand for unsigned char.
Pleas place commit logs below the cut-off line (---).
> Signed-off-by: Grigori Goronzy
> ---
> drivers/usb/serial/ch341.c | 10 +-
> 1 file ch
On Thu, Apr 28, 2016 at 06:53:14PM +0100, Salah Triki wrote:
> The call of eprom_read may fail, therefore its return value must be
> checked.
>
> Signed-off-by: Salah Triki
> ---
> drivers/staging/rtl8192u/r8192U_core.c | 147
> +++--
> 1 file changed, 104 insertions
On Fri, Apr 15, 2016 at 11:14:08PM +0200, Grigori Goronzy wrote:
> Changing the LCR register after initialization does not seem to be
> reliable on all chips (particularly not on CH341A). Restructure
> initialization and configuration to always reinit the chip on
> configuration changes instead an
On Fri, Apr 15, 2016 at 11:14:09PM +0200, Grigori Goronzy wrote:
> With the new reinitialization method, configuring parity, different
> frame lengths and different stop bit settings work as expected on
> both CH340G and CH341A. This has been extensively tested with a
> logic analyzer.
>
> v2: on
On Fri, Apr 15, 2016 at 11:14:10PM +0200, Grigori Goronzy wrote:
> There are at least two hardware revisions, this may be helpful in
> case compatibility issues need to be debugged.
>
> Signed-off-by: Grigori Goronzy
> ---
> drivers/usb/serial/ch341.c | 1 +
> 1 file changed, 1 insertion(+)
>
>
On Fri, Apr 15, 2016 at 11:14:11PM +0200, Grigori Goronzy wrote:
No commit message?
> v2: use correct flag variable.
> v3: fix compilation
>
> Signed-off-by: Grigori Goronzy
> ---
> drivers/usb/serial/ch341.c | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/usb/se
On Fri, Apr 15, 2016 at 11:14:12PM +0200, Grigori Goronzy wrote:
> No functional change. The following adjustments were made to be more in
> line with official coding style and to be more consistent.
>
> Stop mixing tabs and spaces for alignment. Stop putting labels and
> statements into the sam
Hi Greg,
On Thu, Apr 28, 2016 at 12:53:24PM -0700, Greg Kroah-Hartman wrote:
> On Thu, Apr 21, 2016 at 03:43:40PM +0300, Heikki Krogerus wrote:
> > USB Type-C Connector System Software Interface (UCSI) is
> > specification that defines the registers and data structures
> > that can be used to cont
On Fri, Apr 15, 2016 at 11:14:13PM +0200, Grigori Goronzy wrote:
> No functional change. Remove explicit function name printing, it's
> easy to use dynamic debug to print it every time, if required.
While that is true, we currently use __func__ in a lot of debug messages
as a compact form for a s
On Fri, Apr 15, 2016 at 11:14:14PM +0200, Grigori Goronzy wrote:
> Check for B0 in a more idiomatic way and make sure to not enable
> RTS/CTS hardware flow control in B0 as it may override the control
> lines. Also make sure to only enable RTS/DTR if there's a transition
> from B0.
Ah, here it is
On Fri, Apr 15, 2016 at 11:14:16PM +0200, Grigori Goronzy wrote:
> The status bit was found with USB captures of the Windows driver and
> some luck. Tested on CH340G and CH341A.
>
> v2: unify general status definitions
>
> Signed-off-by: Grigori Goronzy
Looks good too.
Thanks for doing all th
On Fri, Apr 15, 2016 at 11:14:15PM +0200, Grigori Goronzy wrote:
> If the serial port hasn't been opened yet, no baud rate should be
> set and RTS/DTR need to be deasserted.
But what about reset_resume?
Thanks,
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the b
On 2016-04-29 14:16, Johan Hovold wrote:
On Fri, Apr 15, 2016 at 11:14:04PM +0200, Grigori Goronzy wrote:
This may fail, do not assume it always works.
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/
On 2016-04-29 14:52, Johan Hovold wrote:
@@ -168,9 +168,9 @@ static int ch341_set_handshake(struct usb_device
*dev, u8 control)
static int ch341_get_status(struct usb_device *dev, struct
ch341_private *priv)
{
- char *buffer;
+ unsigned char *buffer;
int r;
- const
On 28.04.2016 15:21, Felipe Balbi wrote:
Hi,
dmesg from PC host side (after adding your change without my patch):
[17907.984647] usb 6-2: new SuperSpeed USB device number 54 using xhci_hcd
[17908.012036] usb 6-2: No SuperSpeed endpoint companion for config 1
interface 1 altsetting 0 ep 2: usi
Hi everyone,
This is a fairly complicated series of pull requests because of the
dependencies involved. The goal is to take all of the patches through
the ARM-SoC tree but I'm sending out these individual pull requests
to document this. Also, if these branches were starting to cause
conflicts they
The following changes since commit 87d66f280672800c9c2ad1ce3b7a993ce1e04769:
phy: tegra: Add Tegra210 support (2016-04-29 16:44:48 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git
tags/tegra-for-4.7-pci
for you to fetch changes up
The following changes since commit 3358d2d9f47af86bdd71edb24b361f72a54ec04e:
clk: tegra: Add interface to enable hardware control of SATA/XUSB PLLs
(2016-04-28 12:41:44 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git
tags/tegra-f
* Tony Lindgren [160428 11:09]:
> * Sergei Shtylyov [160428 10:55]:
> > >+ cable_connected = ((glue->status & MUSB_ID_GROUND) ||
> > >+ (glue->status & MUSB_VBUS_VALID));
> >
> > cable_connected = glue->status & (MUSB_ID_GROUND |
> > M
The following changes since commit 87d66f280672800c9c2ad1ce3b7a993ce1e04769:
phy: tegra: Add Tegra210 support (2016-04-29 16:44:48 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git
tags/tegra-for-4.7-xhci
for you to fetch changes u
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git
tags/tegra-for-4.7-xusb
for you to fetch changes up to 7bdf9d2308192b
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git
tags/tegra-for-4.7-xusb-no-defconfig
for you to fetch changes up to 1
On Fri, Apr 29, 2016 at 01:55:14PM +0200, Krzysztof Kozlowski wrote:
> On 04/29/2016 01:30 PM, Mark Brown wrote:
> > Supplies are only optional if they may be physically absent. In this
> > case it's possible that on device regulators may be used instead, a
> > pattern more like that used for ari
> -Original Message-
> From: Johan Hovold [mailto:jhov...@gmail.com] On Behalf Of Johan Hovold
> Sent: Friday, April 29, 2016 05:09
> To: Valentin Yakovenkov
> Cc: Konstantin Shkolnyy; linux-usb@vger.kernel.org
> Subject: [EXT] Re: [PATCH] Add DCD line support to CP210x driver
>
> On Thu,
Good morning Alan,
I just finished testing your latest patch on Ubuntu 14.04.4 LTS (4.2.x
kernel) and Ubuntu 16.04 LTS (4.4.x kernel) on x86/x64, and it resolves
the issues I've encountered. May we please have this patch submitted for
review?
Thank you and the linux-usb developers for your time
On Thu, 28 Apr 2016, Greg KH wrote:
> On Fri, Apr 15, 2016 at 12:12:26PM -0400, Alan Stern wrote:
> > The debugging facilities in ehci-dbg.c follow an uneven pattern. Some
> > of them are protected by "#ifdef CONFIG_DYNAMIC_DEBUG" and some
> > aren't, presumably in the hope of having some of the
The debugging facilities in ehci-dbg.c follow an uneven pattern. Some
of them are protected by "#ifdef CONFIG_DYNAMIC_DEBUG" and some
aren't, presumably in the hope of having some of the debugging output
available in any configuration.
This leads to build problems when dynamic debugging isn't con
When a USB driver is bound to an interface (either through probing or
by claiming it) or is unbound from an interface, the USB core always
disables Link Power Management during the transition and then
re-enables it afterward. The reason is because the driver might want
to prevent hub-initiated lin
On 04/28/2016 04:30 AM, Roger Quadros wrote:
> Hi Joe,
>
> On 27/04/16 23:41, Joe Lawrence wrote:
>> Hello Mathias, Roger, Gabriel
>>
>> [ ... snip ... ]
>> In the meantime I was browsing recent linux-scsi archives and noticed
>> Gabriel's [PATCH v2] xhci: Cleanup only when releasing primary hcd
On Fri, Apr 29, 2016 at 10:23:28AM +0200, Johan Hovold wrote:
> Hi Greg,
>
> Here are some new device ids for rc6. These have been in next for a few
> days now without any issues.
>
> Thanks,
> Johan
>
> The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9:
>
> Linux 4.
On Fri, Apr 29, 2016 at 04:32:22PM +0300, Heikki Krogerus wrote:
> Hi Greg,
>
> On Thu, Apr 28, 2016 at 12:53:24PM -0700, Greg Kroah-Hartman wrote:
> > On Thu, Apr 21, 2016 at 03:43:40PM +0300, Heikki Krogerus wrote:
> > > USB Type-C Connector System Software Interface (UCSI) is
> > > specificatio
Replaced magic numbers used in the CRTSCTS flag code with symbolic names
from the chip specification.
Signed-off-by: Konstantin Shkolnyy
---
Changes in v2:
Improved CRTSCTS fix based on feedback. Dropped get_termios error handling.
drivers/usb/serial/cp210x.c | 93 ++
The CRTSCTS flag code cleared (and inconsistently) bits unrelated to
CRTSCTS functionality. It was also harder than necessary to read.
Signed-off-by: Konstantin Shkolnyy
---
Changes in v2:
Improved CRTSCTS fix based on feedback. Dropped get_termios error handling.
drivers/usb/serial/cp210x.c |
A bug in the CRTSCTS handling caused RTS to alternate between
CRTSCTS=0 => "RTS transmits active signal" and
CRTSCTS=1 => "RTS receives flow control"
instead of
CRTSCTS=0 => "RTS is statically active" and
CRTSCTS=1 => "RTS receives flow control"
This only happened after first having enabled CRTSCTS
66 matches
Mail list logo
