From: Rafal Redzimski
Broxton B0 also requires XHCI_PME_STUCK_QUIRK.
Adding PCI device ID for Broxton B and adding to quirk.
Signed-off-by: Rafal Redzimski
Signed-off-by: Robert Dobrowolski
---
drivers/usb/host/xhci-pci.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/
Thanks to switching to devm_gpiod_get:
1) We don't have to pass fwnode pointer
2) We can request initial GPIO value at getting call
This was successfully tested on Netgear R6250 (BCM4708).
Signed-off-by: Rafał Miłecki
---
drivers/usb/host/bcma-hcd.c | 6 ++
1 file changed, 2 insertions(+), 4
Since commit 7fe3976e0f3ab26f8ffd9430d3d2a19a70f2c8d2 ("gadget: switch
ep_io_operations to ->read_iter/->write_iter") io submissions fail with
ENODEV.
Signed-off-by: Mathieu Laurendeau
---
drivers/usb/gadget/legacy/inode.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dr
On Wed, Mar 23, 2016 at 04:41:02AM -0700, Robert Dobrowolski wrote:
> From: Rafal Redzimski
>
> Broxton B0 also requires XHCI_PME_STUCK_QUIRK.
> Adding PCI device ID for Broxton B and adding to quirk.
>
> Signed-off-by: Rafal Redzimski
> Signed-off-by: Robert Dobrowolski
> ---
> drivers/usb/h
Hi,
On 03/23/2016 07:37 PM, Rafał Miłecki wrote:
> Thanks to switching to devm_gpiod_get:
> 1) We don't have to pass fwnode pointer
> 2) We can request initial GPIO value at getting call
> This was successfully tested on Netgear R6250 (BCM4708).
>
> Signed-off-by: Rafał Miłecki
> ---
> drivers/u
On 23.03.2016 05:53, Rajesh Bhagat wrote:
IMO, The assumption that "xhci_abort_cmd_ring would always generate an
event and handle_cmd_completion would be called" will not be always be true if
HW
is in bad state.
Please share your opinion.
writing the CA (command abort) bit in CRCR (comman
It seems like this is because the uas driver queues the UNMAP commands.
After some test I am no longer sure that it has nothing to do with my
hardware at all. Still I have doubt on the uas driver. Like, is
queuing UNMAP commands the right thing to do? Or is the uas driver
wrongly queuing too many
On Mon, Mar 21, 2016 at 12:32:27PM -0400, Jaret Cantu wrote:
> The TX settings can be calibrated for particular hardware. The
> phy is reset by Linux, so this cannot be handled by the bootloader.
>
> The TRM mentions that the maximum resistance should be used for the
> DN/DP calibration in order
> On Wed, Mar 23, 2016 at 04:41:02AM -0700, Robert Dobrowolski wrote:
>> From: Rafal Redzimski
>>
>> Broxton B0 also requires XHCI_PME_STUCK_QUIRK.
>> Adding PCI device ID for Broxton B and adding to quirk.
>>
>> Signed-off-by: Rafal Redzimski
>> Signed-off-by: Robert Dobrowolski
>> ---
>> driv
On 23 March 2016 at 14:52, Lu Baolu wrote:
> On 03/23/2016 07:37 PM, Rafał Miłecki wrote:
>> Thanks to switching to devm_gpiod_get:
>> 1) We don't have to pass fwnode pointer
>> 2) We can request initial GPIO value at getting call
>> This was successfully tested on Netgear R6250 (BCM4708).
>>
>> S
hi Alan:
2016-03-04 23:25 GMT+08:00 Alan Stern :
> On Fri, 4 Mar 2016, yoma sophian wrote:
>
>> BTW, when I disable BH support in hcd driver.
>> I get below recursion of spin lock sometimes.
>> Did I missing anything once disable BH?
>
> Yes, you missed a very important fact: ehci-hcd _requires_ BH
On Wed, Mar 23, 2016 at 08:56:49AM -0700, Robert Dobrowolski wrote:
> > On Wed, Mar 23, 2016 at 04:41:02AM -0700, Robert Dobrowolski wrote:
> >> From: Rafal Redzimski
> >>
> >> Broxton B0 also requires XHCI_PME_STUCK_QUIRK.
> >> Adding PCI device ID for Broxton B and adding to quirk.
> >>
> >> Sig
The ati_remote2 driver expects at least two interfaces with one
endpoint each. If given malicious descriptor that specify one
interface or no endpoints, it will crash in the probe function.
Ensure there is at least two interfaces and one endpoint for each
interface before using it.
The full disclo
On Wed, 23 Mar 2016, yoma sophian wrote:
> hi Alan:
> 2016-03-04 23:25 GMT+08:00 Alan Stern :
> > On Fri, 4 Mar 2016, yoma sophian wrote:
> >
> >> BTW, when I disable BH support in hcd driver.
> >> I get below recursion of spin lock sometimes.
> >> Did I missing anything once disable BH?
> >
> > Y
On Thursday 17 March 2016 07:56 AM, David Lechner wrote:
> The da850 family of processors has an async3 clock domain that can be
> muxed to either pll0_sysclk2 or pll1_sysclk2. Now that the davinci clocks
> have a set_parent callback, we can use this to control the async3 mux
> instead of a stand-a
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Valentin Yakovenkov
> Sent: Tuesday, March 22, 2016 11:12
> To: linux-usb@vger.kernel.org
> Subject: [PATCH] Add DCD line support to CP210x driver
You'll have to re-generat
The usbhid driver has inconsistently duplicated code in its post-reset,
resume, and reset-resume pathways.
reset-resume doesn't check HID_STARTED before trying to
restart the I/O queues.
resume fails to clear the HID_SUSPENDED flag if HID_STARTED
isn't set.
gcc warns about the use of regulators in phy_8x16_probe:
drivers/usb/phy/phy-qcom-8x16-usb.c: In function 'phy_8x16_probe':
drivers/usb/phy/phy-qcom-8x16-usb.c:284:13: error: 'regs[0].consumer' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
drivers/usb/phy/ph
> -Original Message-
> From: Konstantin Shkolnyy
> Sent: Wednesday, March 23, 2016 11:26
> To: 'Valentin Yakovenkov'; linux-usb@vger.kernel.org
> Subject: RE: [PATCH] Add DCD line support to CP210x driver
>
> > -Original Message-
> > From: linux-usb-ow...@vger.kernel.org [mailto:li
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Valentin Yakovenkov
> Sent: Tuesday, March 22, 2016 11:12
> To: linux-usb@vger.kernel.org
> Subject: [PATCH] Add DCD line support to CP210x driver
[...]
> static struct us
The phy-am335x driver selects 'USB_COMMON', but all other drivers
use 'depends on' for that symbol, and it depends on USB || USB_GADGET
itself, which causes a Kconfig warning:
warning: (AM335X_PHY_USB) selects USB_COMMON which has unmet direct
dependencies (USB_SUPPORT && (USB || USB_GADGET))
As
This behavior is expected to be enabled by default, i think.
I'm using CP210x converter with GPS connected to it and DCD line is used
as PPS discipline to NTP daemon (this is standard behavior).
Moreover, it should be nice to add CTS/DSR handling same way.
Here is the patch against latest usb-ser
Here's regenerated patch against latest usb-serial tree.
This patch adds DCD line support to CP210x USB serial driver.
First it enables CP210x events embedding to incoming URB's by calling:
cp210x_set_config_single(port, CP210X_EMBED_EVENTS, CP210X_ESCCHAR);
Then it parses incoming URB's via cus
On Thursday 17 March 2016 07:56 AM, David Lechner wrote:
> Up to this point, the USB phy clock configuration was handled manually in
> the board files and in the usb drivers. This adds proper clocks so that
> the usb drivers can use clk_get and clk_enable and not have to worry about
> the details.
buflen by default (256) is smaller than wMaxPacketSize (512) in high-speed
devices.
That caused the OUT endpoint to freeze if the host send any data packet of
length greater than 256 bytes.
This is an example dump of what happended on that enpoint:
HOST: [DATA][Length=260][...]
DEVICE: [NAK]
HO
On Thursday 17 March 2016 07:56 AM, David Lechner wrote:
> Device tree binding for new phy-da8xx-usb driver.
>
> Signed-off-by: David Lechner
> ---
>
> v2 changes: This is new patch in v2.
>
>
> .../devicetree/bindings/phy/phy-da8xx-usb.txt | 34
> ++
> 1 file change
On 03/23/2016 10:56 AM, Sekhar Nori wrote:
On Thursday 17 March 2016 07:56 AM, David Lechner wrote:
The da850 family of processors has an async3 clock domain that can be
muxed to either pll0_sysclk2 or pll1_sysclk2. Now that the davinci clocks
have a set_parent callback, we can use this to contr
On Thursday 17 March 2016 07:56 AM, David Lechner wrote:
> This is a new phy driver for the SoC USB controllers on the TI DA8XX
> family of microcontrollers. The USB 1.1 PHY is just a simple on/off.
> The USB 2.0 PHY also allows overriding the VBUS and ID pins.
>
> Signed-off-by: David Lechner
>
Hi David,
On Thursday 17 March 2016 07:09 PM, Sergei Shtylyov wrote:
> On 3/17/2016 5:26 AM, David Lechner wrote:
>
>> OK, ready for round two.
>
>You're quick... :-)
>
>> I've added a new callback in the davinci clocks so that they can properly
>> handle clock muxing. The clock functions a
On Wednesday 23 March 2016 10:50 PM, David Lechner wrote:
> On 03/23/2016 10:56 AM, Sekhar Nori wrote:
>> On Thursday 17 March 2016 07:56 AM, David Lechner wrote:
>>> The da850 family of processors has an async3 clock domain that can be
>>> muxed to either pll0_sysclk2 or pll1_sysclk2. Now that the
On 03/23/2016 12:36 AM, Peter Chen wrote:
On Mon, Mar 21, 2016 at 12:32:27PM -0400, Jaret Cantu wrote:
The TX settings can be calibrated for particular hardware. The
phy is reset by Linux, so this cannot be handled by the bootloader.
The TRM mentions that the maximum resistance should be used
On 03/23/2016 11:56 AM, Sekhar Nori wrote:
+static struct clk usb_ref_clk = {
+ .name = "usb_ref_clk",
+ .rate = 4800,
+ .set_rate = davinci_simple_set_rate,
+};
can we call this usb_refclkin so it matches the TRM name? Also, should
this node be
On Wednesday 23 March 2016 11:15 PM, David Lechner wrote:
> On 03/23/2016 11:56 AM, Sekhar Nori wrote:
>>>
>>> +static struct clk usb_ref_clk = {
>>> +.name= "usb_ref_clk",
>>> +.rate= 4800,
>>> +.set_rate= davinci_simple_set_rate,
>>> +};
>>
>> can we call this
On 03/23/2016 12:06 PM, Sekhar Nori wrote:
On Thursday 17 March 2016 07:56 AM, David Lechner wrote:
Device tree binding for new phy-da8xx-usb driver.
Signed-off-by: David Lechner
---
v2 changes: This is new patch in v2.
.../devicetree/bindings/phy/phy-da8xx-usb.txt | 34 +
> -Original Message-
> From: Valentin Yakovenkov [mailto:yakoven...@niistt.ru]
> Sent: Wednesday, March 23, 2016 11:52
> To: Konstantin Shkolnyy; linux-usb@vger.kernel.org
> Subject: Re: [PATCH] Add DCD line support to CP210x driver
>
> Here's regenerated patch against latest usb-serial tr
On 03/23/2016 12:21 PM, Sekhar Nori wrote:
+/* DA8xx CFGCHIP2 (USB PHY Control) register bits */
+#define PHYCLKGD (1 << 17)
+#define VBUSSENSE (1 << 16)
+#define RESET (1 << 15)
+#define OTGMODE_MASK (3 << 13)
+#define NO_OVERRIDE
On 03/23/2016 01:37 PM, Jaret Cantu wrote:
On 03/23/2016 12:36 AM, Peter Chen wrote:
On Mon, Mar 21, 2016 at 12:32:27PM -0400, Jaret Cantu wrote:
The TX settings can be calibrated for particular hardware. The
phy is reset by Linux, so this cannot be handled by the bootloader.
The TRM mentions
Hi
On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
Hi all,
Looks like there's some issue with the USB gadgets and configfs.
I'm seeing rmmod of the UDC driver cause a warning and then reboot
hangs the system. This happens at least with v4.4, and I've
On 03/23/2016 12:29 PM, Sekhar Nori wrote:
Alright, I guess 'can be called' in the comment should have used
stronger language :) How about late registration of USB clocks as I
suggested. It should also help consolidate code across da830 and da850.
What about the new async3 clock? It will requ
Hello again.
On lun, 2016-03-21 at 09:36 -0400, Greg KH wrote:
> On Sun, Mar 20, 2016 at 06:57:30PM +0100, Guido Trentalancia wrote:
> >
> > Hello Greg !
> >
> > On dom, 2016-03-20 at 10:34 -0700, Greg KH wrote:
> > >
> > > On Sun, Mar 20, 2016 at 06:09:57PM +0100, Guido Trentalancia
> > > wrot
Hi,
On 03/23/2016 11:18 PM, Rafał Miłecki wrote:
> On 23 March 2016 at 14:52, Lu Baolu wrote:
>> On 03/23/2016 07:37 PM, Rafał Miłecki wrote:
>>> Thanks to switching to devm_gpiod_get:
>>> 1) We don't have to pass fwnode pointer
>>> 2) We can request initial GPIO value at getting call
>>> This wa
On 3/21/2016 11:40 PM, Felipe Balbi wrote:
>
> Hi,
>
> John Youn writes:
>> [ text/plain ]
>> On 3/18/2016 12:17 PM, John Youn wrote:
>>> On 3/16/2016 6:56 AM, Felipe Balbi wrote:
heh, +john
Felipe Balbi writes:
> [ text/plain ]
>
> Hi,
>
> Roger Quadros
Hello my dear how are you today I hope that everything is OK with you
please contact me at my email ok. giftbikom...@gmail.com
--
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.o
Dear all,
1. Overview
In current USB/IP implementation, event kernel threads are created for
each port. The functions of the threads are closing connection and
error handling so they don't have not so many events to handle. There's
no need to have thread for each port.
BEFORE) vhci side - VHC
On Wed, Mar 23, 2016 at 02:17:27PM -0400, Jaret Cantu wrote:
> On 03/23/2016 01:37 PM, Jaret Cantu wrote:
> >On 03/23/2016 12:36 AM, Peter Chen wrote:
> >>On Mon, Mar 21, 2016 at 12:32:27PM -0400, Jaret Cantu wrote:
> >>>The TX settings can be calibrated for particular hardware. The
> >>>phy is re
Hi,
On 03/23/2016 11:38 AM, Lipengcheng wrote:
>> It looks like a wild pointer exists after xhci_mem_cleanup() is called.
>> >Let me try to reproduce it and seek for a fix.
>
> Hi,
>Thanks very much.
>The kernel is 3.10 and is inevitable emergence. The kernel 3.18 is
> accidental, but
Hi,
Our Stock list.
Brand NEW
96 x Cisco 7900 IP Phone
87 x Unified IP Phone 6900
12 x Unified IP Phone 8900
76 x Unified IP Phone 9900
55 x Unified IP Phone 8800
67 x Cisco 1921
67 x Cisco 1941
56 x Cisco CP-7961G 7961G
34 x Cisco CP-7971G-GE 7971G
19 x Cisco Unified IP Conference Station 7937G
On 24 March 2016 at 01:02, Lu Baolu wrote:
> On 03/23/2016 11:18 PM, Rafał Miłecki wrote:
>> On 23 March 2016 at 14:52, Lu Baolu wrote:
>>> On 03/23/2016 07:37 PM, Rafał Miłecki wrote:
Thanks to switching to devm_gpiod_get:
1) We don't have to pass fwnode pointer
2) We can request
On 3/22/2016 12:44 PM, Doug Anderson wrote:
> John,
>
> On Tue, Mar 22, 2016 at 12:26 PM, John Youn wrote:
>> Thanks for the debug logs and everyones help.
>>
>> After reviewing with our hardware engineers, it seems this is likely
>> to do with the IDDIG debounce filtering when switching between
Hi,
Ivaylo Dimitrov writes:
> On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
>> Hi,
>>
>> On 16.01.2016 00:48, Tony Lindgren wrote:
>>> Hi all,
>>>
>>> Looks like there's some issue with the USB gadgets and configfs.
>>>
>>> I'm seeing rmmod of the UDC driver cause a warning and then reboot
>>> han
Hi,
John Youn writes:
> [ text/plain ]
> On 3/21/2016 11:40 PM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> John Youn writes:
>>> [ text/plain ]
>>> On 3/18/2016 12:17 PM, John Youn wrote:
On 3/16/2016 6:56 AM, Felipe Balbi wrote:
>
> heh, +john
>
> Felipe Balbi writes:
>> [
51 matches
Mail list logo
