Hi Rob,
Sorry to bother you again.
Can I describe usb-connector in usb node like this?
usb2: usb@1120 {
compatible = "mediatek,mt2701-musb";
"mediatek,mtk-musb";
reg = <0 0x1120 0 0x1000>;
...
usb_connector: musb_connector {
compatible = "usb-b-connector
Hello!
On 13.02.2019 19:36, Heikki Krogerus wrote:
To prevent loading of the driver when the PD controller is
still in some operational mode that the driver does not
support, checking the mode in driver probe callback
function.
TI PD controllers may be in undefined mode of operation
for exampl
On Thu, Feb 14, 2019 at 10:58:13AM +0530, Nagarjuna Kristam wrote:
>
>
> On 13-02-2019 18:46, Thierry Reding wrote:
> > On Wed, Feb 13, 2019 at 01:56:24PM +0100, Thierry Reding wrote:
> >> On Wed, Feb 13, 2019 at 04:08:15PM +0530, Nagarjuna Kristam wrote:
> >>>
> >>>
> >>> On 04-02-2019 17:18, Th
On Thu, Feb 14, 2019 at 07:49:57AM +0100, Stefan Wahren wrote:
> Hi Stanislaw,
>
> > Stanislaw Gruszka hat am 12. Februar 2019 um 10:30
> > geschrieben:
> >
> >
> >
> > In usb_sg_init() urb->num_sgs is set 0 for sg_tablesize = 0 controllers.
> > In mt76 we set urb->num_sgs to 1. I thought it
Hi Stanislaw,
Am 14.02.19 um 10:25 schrieb Stanislaw Gruszka:
> On Thu, Feb 14, 2019 at 07:49:57AM +0100, Stefan Wahren wrote:
>> Hi Stanislaw,
>>
>>> Stanislaw Gruszka hat am 12. Februar 2019 um 10:30
>>> geschrieben:
>>>
>>>
>>>
>>> In usb_sg_init() urb->num_sgs is set 0 for sg_tablesize = 0 c
On Thu, Feb 14, 2019 at 10:48:15AM +0100, Stefan Wahren wrote:
> Hi Stanislaw,
>
> Am 14.02.19 um 10:25 schrieb Stanislaw Gruszka:
> > On Thu, Feb 14, 2019 at 07:49:57AM +0100, Stefan Wahren wrote:
> >> Hi Stanislaw,
> >>
> >>> Stanislaw Gruszka hat am 12. Februar 2019 um 10:30
> >>> geschrieben
This patch is referred to Robert's patch
commit cf54772b913b ("usb: dwc2: call dwc2_is_controller_alive() under
spinlock")
During running sdb with otg mode, the usb is hung sometime.
The one of SDB hang issues should be fixed with this patch.
After hang, it doesn't never trigger the usb interrup
On Wed, Feb 13, 2019 at 10:45:48AM +0300, Heikki Krogerus wrote:
> Hi,
>
> This is the third version of my proposal to add device graph parsing
> to the device connection API. There was only one problem reported in
> v2 by Jun - kernel-doc entry was missing for the new fwnode member in
> struct us
Hi Jaehoon Chung,
On 2/14/2019 2:04 PM, Jaehoon Chung wrote:
> This patch is referred to Robert's patch
> commit cf54772b913b ("usb: dwc2: call dwc2_is_controller_alive() under
> spinlock")
>
> During running sdb with otg mode, the usb is hung sometime.
>
> The one of SDB hang issues should be
Hi Sergei,
On Thu, Feb 14, 2019 at 11:52:23AM +0300, Sergei Shtylyov wrote:
> > +static int tps6598x_check_mode(struct tps6598x *tps)
> > +{
> > + char mode[5] = { };
> > + int ret;
> > +
> > + ret = tps6598x_read32(tps, TPS_REG_MODE, (void *)mode);
>
>Casting pointers to 'void *' happe
On Thu, Feb 14, 2019 at 12:08 AM Pawel Laszczak wrote:
>
> Hi Rob,
> >On Thu, Jan 31, 2019 at 11:52:28AM +, Pawel Laszczak wrote:
> >> This patch aim at documenting USB related dt-bindings for the
> >> Cadence USBSS-DRD controller.
> >>
> >> Signed-off-by: Pawel Laszczak
> >> ---
> >> .../de
On 12 February 2019 16:20, Guenter Roeck wrote:
> On 2/12/19 2:54 AM, Greg KH wrote:
> > On Tue, Feb 12, 2019 at 06:29:39PM +0800, Kyle Tso wrote:
> >> On Thu, Jan 31, 2019 at 3:02 PM Greg KH
> wrote:
> >>
> >>> On Thu, Jan 31, 2019 at 11:54:11AM +0800, Kyle Tso wrote:
> Provide a function t
On Thu, Feb 14, 2019 at 02:17:14PM +, Adam Thomson wrote:
> On 12 February 2019 16:20, Guenter Roeck wrote:
>
> > On 2/12/19 2:54 AM, Greg KH wrote:
> > > On Tue, Feb 12, 2019 at 06:29:39PM +0800, Kyle Tso wrote:
> > >> On Thu, Jan 31, 2019 at 3:02 PM Greg KH
> > wrote:
> > >>
> > >>> On Thu,
On 2/14/19 6:17 AM, Adam Thomson wrote:
On 12 February 2019 16:20, Guenter Roeck wrote:
On 2/12/19 2:54 AM, Greg KH wrote:
On Tue, Feb 12, 2019 at 06:29:39PM +0800, Kyle Tso wrote:
On Thu, Jan 31, 2019 at 3:02 PM Greg KH
wrote:
On Thu, Jan 31, 2019 at 11:54:11AM +0800, Kyle Tso wrote:
P
On 04-02-2019 19:26, Thierry Reding wrote:
> On Thu, Jan 03, 2019 at 03:34:58PM +0530, Nagarjuna Kristam wrote:
>> This patch adds UDC driver for tegra XUSB 3.0 device mode controller.
>> XUSB device mode controller support SS, HS and FS modes
>>
>> Based on work by:
>> Mark Kuo
>> Andrew B
On 12.2.2019 20.55, Eric Blau wrote:
On Tue, Feb 12, 2019 at 1:06 PM Alan Stern wrote:
On Tue, 12 Feb 2019, Mathias Nyman wrote:
This logs shows a USB3 Apple card reader successfully suspending to U3 state
once, but fails to resume back to U0. It is logically disconnected as a result
of
fa
>> +reg = <0x0 0x700d 0x0 0x8000>,
>> +<0x0 0x700d8000 0x0 0x1000>,
>> +<0x0 0x700d9000 0x0 0x1000>;
>> +interrupts = <0 44 0x4>;
>> +clocks = <&tegra_car TEGRA210_CLK_XUSB_DEV>,
>> +<&tegra_car TEGR
On 13.2.2019 23.13, Ivan Mironov wrote:
Hi all,
There is a known problem on some MacBooks: internal card reader
disappears after the first suspend/resume and all subsequent attempts
to suspend laptop are failing.
This was reported[1][2] and even discussed in the mailing lists[3],
without any re
On 14-02-2019 14:29, Thierry Reding wrote:
> On Thu, Feb 14, 2019 at 10:58:13AM +0530, Nagarjuna Kristam wrote:
>>
>>
>> On 13-02-2019 18:46, Thierry Reding wrote:
>>> On Wed, Feb 13, 2019 at 01:56:24PM +0100, Thierry Reding wrote:
On Wed, Feb 13, 2019 at 04:08:15PM +0530, Nagarjuna Kristam
On 02/14/2019 03:12 PM, Heikki Krogerus wrote:
>>> +static int tps6598x_check_mode(struct tps6598x *tps)
>>> +{
>>> + char mode[5] = { };
>>> + int ret;
>>> +
>>> + ret = tps6598x_read32(tps, TPS_REG_MODE, (void *)mode);
>>
>>Casting pointers to 'void *' happens automagically, doesn't i?
On Thu, Feb 14, 2019 at 06:22:12PM +0300, Sergei Shtylyov wrote:
> On 02/14/2019 03:12 PM, Heikki Krogerus wrote:
>
> >>> +static int tps6598x_check_mode(struct tps6598x *tps)
> >>> +{
> >>> + char mode[5] = { };
> >>> + int ret;
> >>> +
> >>> + ret = tps6598x_read32(tps, TPS_REG_MODE, (void *)mod
On 14 February 2019 14:30, Greg KH wrote:
> On Thu, Feb 14, 2019 at 02:17:14PM +, Adam Thomson wrote:
> > On 12 February 2019 16:20, Guenter Roeck wrote:
> >
> > > On 2/12/19 2:54 AM, Greg KH wrote:
> > > > On Tue, Feb 12, 2019 at 06:29:39PM +0800, Kyle Tso wrote:
> > > >> On Thu, Jan 31, 2019
On 02/14/2019 06:28 PM, Heikki Krogerus wrote:
> +static int tps6598x_check_mode(struct tps6598x *tps)
> +{
> + char mode[5] = { };
> + int ret;
> +
> + ret = tps6598x_read32(tps, TPS_REG_MODE, (void *)mode);
Casting pointers to 'void *' happens automagically,
Hello Felipe,
Who is the best person for taking patches for renesas_usb3.c?
Thanks,
Fab
> From: Fabrizio Castro
> Sent: 13 December 2018 20:24
> Subject: [PATCH] usb: gadget: udc: renesas_usb3: add support for r8a774c0
>
> RZ/G2E USB 3.0 implementation is like the one found on R-Car E3,
> there
I am attempted to debug an android problem related to USB hubs.
On desktop Linux 'lsusb -vv' details the HUB description, but 'lsusb' on
Android is the simple cousin and does not know this information.
I have found the 'descriptors' file for the USB device under the '/sys'
interface, however this
On Thu, Feb 14, 2019 at 09:03:43AM -0700, Simon Wood wrote:
> I am attempted to debug an android problem related to USB hubs.
>
> On desktop Linux 'lsusb -vv' details the HUB description, but 'lsusb' on
> Android is the simple cousin and does not know this information.
That's because Android is u
Hi,
With kernel 4.20.8 as well as 5.0-rc6 I have the following problem.
I have an AT2020USBi microphone from audio-technica. This is a full speed USB
device which supports 24 bit audio at up to 96 kHz. Although the hardware is
only mono it requestes a wMaxPacketSize of 576 corresponding to 24 bi
On Thu, 2019-02-14 at 17:03 +0200, Mathias Nyman wrote:
> This card reader prevents second system suspend on latest kernels, see thread:
> https://marc.info/?l=linux-usb&m=154816680816246&w=2
>
> In that case the card reader fails to resume from usb3 U3 suspend state,
> and ends up stuck in USB3 p
On Thu, 2019-02-14 at 06:40 +0500, Ivan Mironov wrote:
> Unfortunately, everything broke again after yet another suspend/resume.
> Currently I'm suspecting that my patch maybe only helps to survive the
> short suspend, but not the long one.
>
> After this bad suspend/resume, card reader disappeare
On Thu, February 14, 2019 9:42 am, Greg KH wrote:
> That's because Android is using toybox's version of 'lsusb'. I
> recommend using the real version if you need this information.
I would if I could, I do not control the BSP for this hardware :-(
>> I have found the 'descriptors' file for the U
On Thu, 14 Feb 2019, Simon Wood wrote:
> On Thu, February 14, 2019 9:42 am, Greg KH wrote:
>
> > That's because Android is using toybox's version of 'lsusb'. I
> > recommend using the real version if you need this information.
>
> I would if I could, I do not control the BSP for this hardware :
On Thu, February 14, 2019 11:10 am, Alan Stern wrote:
>> The 'HUB descriptor' is not contained within the 'descriptors' file
>> from the '/sys' interface, although I suspect that it can be accessed
>> via _another_ file within '/sys' hopefully someone can point me at
>> it.
>
> No, there is no
Patch moves some decoding functions from driver/usb/dwc3/debug.h driver
to driver/usb/common/debug.c file. These moved functions include:
dwc3_decode_get_status
dwc3_decode_set_clear_feature
dwc3_decode_set_address
dwc3_decode_get_set_descriptor
dwc3_decode_get_configuration
This patch introduce new Cadence USBSS DRD driver to linux kernel.
The Cadence USBSS DRD Driver is a highly configurable IP Core whichi
can be instantiated as Dual-Role Device (DRD), Peripheral Only and
Host Only (XHCI)configurations.
The current driver has been validated with FPGA burned. We hav
Controller for OUT endpoints has shared on-chip buffers for all incoming
packets, including ep0out. It's FIFO buffer, so packets must be handle
by DMA in correct order. If the first packet in the buffer will not be
handled, then the following packets directed for other endpoints and
functions will
This adds the USB ID of the Hjelmslund Electronics USB485 Iso stick.
Signed-off-by: Mans Rullgard
---
drivers/usb/serial/ftdi_sio.c | 2 ++
drivers/usb/serial/ftdi_sio_ids.h | 6 ++
2 files changed, 8 insertions(+)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio
Patch moves switch responsible for decoding descriptor type
outside snprintf. It improves code readability a little.
Signed-off-by: Pawel Laszczak
---
drivers/usb/common/debug.c | 113 +++--
1 file changed, 58 insertions(+), 55 deletions(-)
diff --git a/drivers/u
Patch adds usb_decode_test_mode and usb_decode_device_feature functions,
which allow to make more readable and simplify the
usb_decode_set_clear_feature function.
Signed-off-by: Pawel Laszczak
---
drivers/usb/common/debug.c | 89 ++
1 file changed, 43 insertio
This patch aim at documenting USB related dt-bindings for the
Cadence USBSS-DRD controller.
Signed-off-by: Pawel Laszczak
---
.../devicetree/bindings/usb/cdns-usb3.txt | 30 +++
1 file changed, 30 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/cdns-us
On Thu, 14 Feb 2019, Michael [ISO-8859-1] H�ckel wrote:
> Hi,
>
> With kernel 4.20.8 as well as 5.0-rc6 I have the following problem.
> I have an AT2020USBi microphone from audio-technica. This is a full speed USB
> device which supports 24 bit audio at up to 96 kHz. Although the hardware is
>
There won't be a case that all of the super-speed ports are in used but
none of the ports can be paired with the OTG capable USB2 port.
T210/T210B01(aka T214) has 4 super-speed ports and 4 USB2 ports. A USB
3.0 connection (either host role or device role) must have one
super-speed port pair wit
> >
> > Hi Rob,
> > >On Thu, Jan 31, 2019 at 11:52:28AM +, Pawel Laszczak wrote:
> > >> This patch aim at documenting USB related dt-bindings for the
> > >> Cadence USBSS-DRD controller.
> > >>
> > >> Signed-off-by: Pawel Laszczak
> > >> ---
> > >> .../devicetree/bindings/usb/cdns-usb3.txt
From: Dan Carpenter
[ Upstream commit df28169e1538e4a8bcd8b779b043e5aa6524545c ]
The source_sink_alloc_func() function is supposed to return error
pointers on error. The function is called from usb_get_function() which
doesn't check for NULL returns so it would result in an Oops.
Of course, in
From: Zhang Run
[ Upstream commit 6eea3527e68acc22483f4763c8682f223eb90029 ]
The ax88772_bind() should return error code immediately when the PHY
was not reset properly through ax88772a_hw_reset().
Otherwise, The asix_get_phyid() will block when get the PHY
Identifier from the PHYSID1 MII regist
From: Dan Carpenter
[ Upstream commit df28169e1538e4a8bcd8b779b043e5aa6524545c ]
The source_sink_alloc_func() function is supposed to return error
pointers on error. The function is called from usb_get_function() which
doesn't check for NULL returns so it would result in an Oops.
Of course, in
From: Zeng Tao
[ Upstream commit 88b1bb1f3b88e0bf20b05d543a53a5b99bd7ceb6 ]
Currently the link_state is uninitialized and the default value is 0(U0)
before the first time we start the udc, and after we start the udc then
stop the udc, the link_state will be undefined.
We may have the following
From: Dan Carpenter
[ Upstream commit df28169e1538e4a8bcd8b779b043e5aa6524545c ]
The source_sink_alloc_func() function is supposed to return error
pointers on error. The function is called from usb_get_function() which
doesn't check for NULL returns so it would result in an Oops.
Of course, in
From: Zeng Tao
[ Upstream commit 88b1bb1f3b88e0bf20b05d543a53a5b99bd7ceb6 ]
Currently the link_state is uninitialized and the default value is 0(U0)
before the first time we start the udc, and after we start the udc then
stop the udc, the link_state will be undefined.
We may have the following
From: Zhang Run
[ Upstream commit 6eea3527e68acc22483f4763c8682f223eb90029 ]
The ax88772_bind() should return error code immediately when the PHY
was not reset properly through ax88772a_hw_reset().
Otherwise, The asix_get_phyid() will block when get the PHY
Identifier from the PHYSID1 MII regist
From: Zeng Tao
[ Upstream commit 88b1bb1f3b88e0bf20b05d543a53a5b99bd7ceb6 ]
Currently the link_state is uninitialized and the default value is 0(U0)
before the first time we start the udc, and after we start the udc then
stop the udc, the link_state will be undefined.
We may have the following
From: Dan Carpenter
[ Upstream commit df28169e1538e4a8bcd8b779b043e5aa6524545c ]
The source_sink_alloc_func() function is supposed to return error
pointers on error. The function is called from usb_get_function() which
doesn't check for NULL returns so it would result in an Oops.
Of course, in
From: Bo He
[ Upstream commit 01c10880d24291a96a4ab0da773e3c5ce4d12da8 ]
We see dwc3 endpoint stopped by unwanted irq during
suspend resume test, which is caused dwc3 ep can't be started
with error "No Resource".
Here, add synchronize_irq before suspend to sync the
pending IRQ handlers complete
From: Zhang Run
[ Upstream commit 6eea3527e68acc22483f4763c8682f223eb90029 ]
The ax88772_bind() should return error code immediately when the PHY
was not reset properly through ax88772a_hw_reset().
Otherwise, The asix_get_phyid() will block when get the PHY
Identifier from the PHYSID1 MII regist
From: Dan Carpenter
[ Upstream commit df28169e1538e4a8bcd8b779b043e5aa6524545c ]
The source_sink_alloc_func() function is supposed to return error
pointers on error. The function is called from usb_get_function() which
doesn't check for NULL returns so it would result in an Oops.
Of course, in
From: Zeng Tao
[ Upstream commit 88b1bb1f3b88e0bf20b05d543a53a5b99bd7ceb6 ]
Currently the link_state is uninitialized and the default value is 0(U0)
before the first time we start the udc, and after we start the udc then
stop the udc, the link_state will be undefined.
We may have the following
From: Bo He
[ Upstream commit 01c10880d24291a96a4ab0da773e3c5ce4d12da8 ]
We see dwc3 endpoint stopped by unwanted irq during
suspend resume test, which is caused dwc3 ep can't be started
with error "No Resource".
Here, add synchronize_irq before suspend to sync the
pending IRQ handlers complete
From: Dan Carpenter
[ Upstream commit df28169e1538e4a8bcd8b779b043e5aa6524545c ]
The source_sink_alloc_func() function is supposed to return error
pointers on error. The function is called from usb_get_function() which
doesn't check for NULL returns so it would result in an Oops.
Of course, in
From: Zeng Tao
[ Upstream commit 88b1bb1f3b88e0bf20b05d543a53a5b99bd7ceb6 ]
Currently the link_state is uninitialized and the default value is 0(U0)
before the first time we start the udc, and after we start the udc then
stop the udc, the link_state will be undefined.
We may have the following
From: Bo He
[ Upstream commit 01c10880d24291a96a4ab0da773e3c5ce4d12da8 ]
We see dwc3 endpoint stopped by unwanted irq during
suspend resume test, which is caused dwc3 ep can't be started
with error "No Resource".
Here, add synchronize_irq before suspend to sync the
pending IRQ handlers complete
From: Zhang Run
[ Upstream commit 6eea3527e68acc22483f4763c8682f223eb90029 ]
The ax88772_bind() should return error code immediately when the PHY
was not reset properly through ax88772a_hw_reset().
Otherwise, The asix_get_phyid() will block when get the PHY
Identifier from the PHYSID1 MII regist
From: Zeng Tao
[ Upstream commit 88b1bb1f3b88e0bf20b05d543a53a5b99bd7ceb6 ]
Currently the link_state is uninitialized and the default value is 0(U0)
before the first time we start the udc, and after we start the udc then
stop the udc, the link_state will be undefined.
We may have the following
From: Bo He
[ Upstream commit 01c10880d24291a96a4ab0da773e3c5ce4d12da8 ]
We see dwc3 endpoint stopped by unwanted irq during
suspend resume test, which is caused dwc3 ep can't be started
with error "No Resource".
Here, add synchronize_irq before suspend to sync the
pending IRQ handlers complete
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/usb/host/oxu210hp-hcd.c: In function 'scan_periodic':
drivers/usb/host/oxu210hp-hcd.c:2256:13: warning:
variable 'uframes' set but not used [-Wunused-but-set-variable]
drivers/usb/host/oxu210hp-hcd.c: In function 'oxu_urb_enqueue':
drivers/u
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
usb-testing
head: 09aa11cfda9d8186046bcd1adcd6498b688114f4
commit: 96a6d031ca9930938bd66d0052fc7ed2b56e3583 [63/64] usb: typec: mux: Find
the muxes by also matching against the device node
smatch warnings:
drivers/usb/typec
Hi Minas,
On 2/14/19 8:43 PM, Minas Harutyunyan wrote:
> Hi Jaehoon Chung,
>
> On 2/14/2019 2:04 PM, Jaehoon Chung wrote:
>> This patch is referred to Robert's patch
>> commit cf54772b913b ("usb: dwc2: call dwc2_is_controller_alive() under
>> spinlock")
>>
>> During running sdb with otg mode, th
On 13-02-2019 12:34, Nagarjuna Kristam wrote:
>>> EXPORT_SYMBOL_GPL(tegra_xusb_padctl_usb3_set_lfps_detect);
>>>
>>> +int tegra_xusb_padctl_set_vbus_override(struct tegra_xusb_padctl *padctl)
>>> +{
>>> + if (padctl->soc->ops->vbus_override)
>>> + return padctl->soc->ops->vbus_ove
Hi,
(no top-posting, please)
Fabrizio Castro writes:
> Hello Felipe,
>
> Who is the best person for taking patches for renesas_usb3.c?
they're already in my 'next' branch. I'll send pull request to Greg shortly
--
balbi
signature.asc
Description: PGP signature
Hi Greg,
Here's my pull request for v5.1. Changes have been sitting in next for a
while now. No shenanigans were reported.
Surprisingly, we have only 40 commits thihs time. Even less than the
previous time. Seems like I could train a deep neural network to
handle this part of my job
On Thu, Feb 14, 2019 at 10:48:15AM +0100, Stefan Wahren wrote:
> Hi Stanislaw,
>
> Am 14.02.19 um 10:25 schrieb Stanislaw Gruszka:
> > On Thu, Feb 14, 2019 at 07:49:57AM +0100, Stefan Wahren wrote:
> >> Hi Stanislaw,
> >>
> >>> Stanislaw Gruszka hat am 12. Februar 2019 um 10:30
> >>> geschrieben
69 matches
Mail list logo
