Hi,
Tejas Joglekar writes:
> From: Thinh Nguyen
>
> This commit adds a new debugging option CONFIG_USB_DWC3_DEBUG_REG_PRINT
> to enable printing of register names to tracepoints for
> register read/write.
>
> Sample trace:
> --
> 283.675504: dwc3_writel: DEPCMDPAR0 addr c9000ba1
On Wed, 2018-11-28 at 14:26 +0800, Hsin-Yi Wang wrote:
> Hi Chunfeng,
> On mt8183, We found `ip sleep failed!!!` with powerd_dbus_suspend.
Did you enable usb device mode in BROM or LK stage? e.g. download image
by fastboot / flashtool
> Referenced from xhci, it also power down device ip at
> xhci
Hi Chunfeng,
On mt8183, We found `ip sleep failed!!!` with powerd_dbus_suspend.
Referenced from xhci, it power down device ip at
xhci_mtk_ssusb_config(). Also if dr_mode is PERIPHERAL and OTG, they
both power down device ip at ssusb_gadget_init().
On Wed, Nov 28, 2018 at 2:22 PM Chunfeng Yun wrot
From: Thinh Nguyen
This commit adds a new debugging option CONFIG_USB_DWC3_DEBUG_REG_PRINT
to enable printing of register names to tracepoints for
register read/write.
Sample trace:
--
283.675504: dwc3_writel: DEPCMDPAR0 addr c9000ba1c838 value
283.675505: dwc3_write
Hi Hsin-Yi,
On Wed, 2018-11-28 at 14:04 +0800, Hsin-Yi, Wang wrote:
> Originally, when dr_mode is USB_DR_MODE_HOST, it didn't power down device ip,
> so host ip sleep will fail at ssusb_host_disable.
>
> Power down device ip at ssusb_host_setup.
>
> Signed-off-by: Hsin-Yi, Wang
> ---
> drivers
Originally, when dr_mode is USB_DR_MODE_HOST, it didn't power down device ip,
so host ip sleep will fail at ssusb_host_disable.
Power down device ip at ssusb_host_setup.
Signed-off-by: Hsin-Yi, Wang
---
drivers/usb/mtu3/mtu3_host.c | 8
1 file changed, 8 insertions(+)
diff --git a/dri
From: Igor Russkikh
Date: Mon, 26 Nov 2018 09:32:56 +
> This patchset introduces support for new multigig ethernet to USB dongle,
> developed jointly by Aquantia (Phy) and ASIX (USB MAC).
Series applied, thanks.
From: Bernd Eckstein <3erndeckst...@gmail.com>
Date: Fri, 23 Nov 2018 13:51:26 +0100
> The bug is not easily reproducable, as it may occur very infrequently
> (we had machines with 20minutes heavy downloading before it occurred)
> However, on a virual machine (VMWare on Windows 10 host) it occurre
> Le 27/11/2018 à 16:19, mario.limoncie...@dell.com a écrit :
> >> Some news from today.
> >>
> >> I realized that I was not always restarting the computer when changing
> >> the Mac pass-through setting in the BIOS.
> >>
> >> Sometimes I was just hibernating, and this could be the origin of some
>
The implementation for setting the over current polarity has always been
the over-current-active-high property. The problem with this is there
is no way to enable over current active low polarity since the default
state of the register bit that controls the over current polarity is a 0
which means
Add SPI bus controller driver for FTDI MPSSE mode. This driver
is supposed to be used together with the FT232H interface driver
for FPGA configuration in drivers/usb/misc/ft232h-intf.c which
adds an mpsse spi platform device describing USB SPI bus with
attached SPI slave devices.
Signed-off-by: An
Add USB interface driver for ARRI FPGA configuration devices based on
FTDI FT232H chip. Depending on USB PID the driver registers different
platform devices describing an FPGA configuration interface.
One FPGA configuration interface type is the usual SPI bus with
additional control and status GPI
Add FPGA manager driver for loading ARRI Altera FPGAs via fast
passive parallel (FPP) interface using FTDI FT232H chip.
Signed-off-by: Anatolij Gustschin
---
.../ABI/testing/sysfs-driver-ftdi-fifo-fpp| 7 +
drivers/fpga/Kconfig | 7 +
drivers/fpga/Makefile
This series adds drivers and FPGA manager support required
for FT232H based ARRI FPGA configuration adapters.
Patch 1/3 adds FT232H interface driver (for ARRI USB PIDs)
implementing commonly used FTDI USB transfer operations and
ACBUS/MPSSE GPIO controllers. Depending on USB PIDs it creates
platfo
Signed-off-by: "David R. Piegdon"
systemd allows use of predictable netdev names. these currently do
not work for netdevs connected to USB platform busses, as the id
of the platform bus is not necessarily consistent across kernel
versions. this patch allows setting a suggested bus id for platform
Hi,
on our embedded systems we rely on systemd's persistent netdev names.
Those currently do not work for USB netdevs that are connected to a
platform USB bus.
In https://github.com/systemd/systemd/pull/7273 a systemd patch was
suggested that would allow exactly this, but it was (rightfully) said
Signed-off-by: "David R. Piegdon"
systemd allows use of predictable netdev names. these currently do
not work for netdevs connected to USB platform busses, as the id
of the platform bus is not necessarily consistent across kernel
versions. this patch allows setting a suggested bus id for platform
Le 27/11/2018 à 16:19, mario.limoncie...@dell.com a écrit :
Some news from today.
I realized that I was not always restarting the computer when changing
the Mac pass-through setting in the BIOS.
Sometimes I was just hibernating, and this could be the origin of some
failures.
OK. Great.
Th
On Thu, Nov 22, 2018 at 04:00:17PM +0800, JackyChou wrote:
>
> From: JackyChou
Thanks for the update. This patch appears to have been corrupted (tabs
replaced with spaces) so it cannot be applied. Try sending the patch to
yourself first and make sure you can apply it with git am (and/or run
chec
> Some news from today.
>
> I realized that I was not always restarting the computer when changing
> the Mac pass-through setting in the BIOS.
>
> Sometimes I was just hibernating, and this could be the origin of some
> failures.
OK. Great.
>
> The second usbc dongle works again so there was
On 27.11.18 10:30, PETER CHEN wrote:
> NXP (Freecale) imx HSIC design has some special requirements, add
> some flags at host code to handle them.
>
> Signed-off-by: Peter Chen
Tested on i.MX6S with Microchip LAN9730 USB HSIC Ethernet Controller.
Reviewed-by: Frieder Schrempf
Tested-by: Friede
On 27.11.18 10:30, PETER CHEN wrote:
> To support imx HSIC, there are some special requirement:
> - The HSIC pad is 1.2v, it may need to supply from external
> - The data/strobe pin needs to be pulled down first, and after
>host mode is initialized, the strobe pin needs to be pulled up
> - Duri
On 27.11.18 10:30, PETER CHEN wrote:
> The chipidea controller has some special requirements during
> suspend/resume, override common ehci->hub_control to implement
> it.
>
> Signed-off-by: Peter Chen
Tested on i.MX6S with Microchip LAN9730 USB HSIC Ethernet Controller.
I have some minor format
Pawel,
On 27/11/18 13:29, Pawel Laszczak wrote:
> Hi Roger
>
Patch adds supports for detecting Host/Device mode.
+
+static int cdns3_otg_get_id(struct cdns3 *cdns)
+{
+ int id;
+
+ id = readl(&cdns->otg_regs->sts) & OTGSTS_ID_VALUE;
+ dev_dbg(cdns->dev,
On 27.11.2018 09:44, Kai Heng Feng wrote:
On Nov 24, 2018, at 00:24, Singh, Sandeep wrote:
From: Sandeep Singh
Occasionally AMD SNPS 3.0 xHC does not respond to
CSS when set, also it does not flag anything on SRE and HCE
to point the internal xHC errors on USBSTS register. This stalls
the
On 19/11/18 10:30 pm, Hao Wei Tee wrote:
On 25/10/18 11:37 am, Hao Wei Tee wrote:
I got another RTL8153-powered adapter and, guess what, I can't seem to reproduce
this anymore. Not sure if it is something that changed in 4.19 or something to
do
with the adapters themselves (I don't have the old
Hi Roger
>>> Patch adds supports for detecting Host/Device mode.
>>> +
>>> +static int cdns3_otg_get_id(struct cdns3 *cdns)
>>> +{
>>> + int id;
>>> +
>>> + id = readl(&cdns->otg_regs->sts) & OTGSTS_ID_VALUE;
>>> + dev_dbg(cdns->dev, "OTG ID: %d", id);
>>> + return id;
>>> +}
>>> +
>>> +in
Hi Peter,
On Tue, Nov 27, 2018 at 7:31 AM PETER CHEN wrote:
>
> For USB HSIC, the data and strobe pin needs to be pulled down
> at default, we consider it as "idle" state. When the USB host
> is ready to be used, the strobe pin needs to be pulled up,
> we consider it as "active" state.
>
> Signed
Le 26/11/2018 à 21:27, mario.limoncie...@dell.com a écrit :
It would be most useful if you can share the kernel's output when you have
dynamic
debugging enabled as Bjorn said for these other devices so we can see why that's
happening.
Some news from today.
I realized that I was not always r
Hi,
Takashi Matsuzawa writes:
> Sorry for excess message:
>
>>7) Where additional EPs appear?
>
> I tried, and they appear in /dev/myffs1 mountpoint alongside with ep0,
> and they are there only while I keep opening ep0.
that's correct. As soon as ep0 is closed, we assume application is
quitti
Sorry for excess message:
>7) Where additional EPs appear?
I tried, and they appear in /dev/myffs1 mountpoint alongside with ep0, and they
are there only while I keep opening ep0.
From: linux-usb-ow...@vger.kernel.org on
behalf of Takashi Matsuzawa
Se
NXP (Freecale) imx HSIC design has some special requirements, add
some flags at host code to handle them.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/host.c | 17 +
include/linux/usb/chipidea.h | 3 +++
2 files changed, 20 insertions(+)
diff --git a/drivers/usb/chipidea
To support imx HSIC, there are some special requirement:
- The HSIC pad is 1.2v, it may need to supply from external
- The data/strobe pin needs to be pulled down first, and after
host mode is initialized, the strobe pin needs to be pulled up
- During the USB suspend/resume, special setting is ne
For USB HSIC, the data and strobe pin needs to be pulled down
at default, we consider it as "idle" state. When the USB host
is ready to be used, the strobe pin needs to be pulled up,
we consider it as "active" state.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb
Most of NXP (Freescale) i.mx USB part has HSIC support, in this series,
we add support for them, it should cover all imx6 and imx7d SoC.
@Schrempf, since some code logic have changed, please help to re-test
v3, thanks.
Changes for v3:
- Delete the internal API ci_ehci_override_wakeup_flag, and ju
The chipidea controller has some special requirements during
suspend/resume, override common ehci->hub_control to implement
it.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/host.c | 76 +
1 file changed, 76 insertions(+)
diff --git a/drivers/usb
Hi,
Todor Tomov writes:
> After I apply this patch on 4.14 (or receive it with 4.14.70) I see a
> regression with
> the Qualcomm QUSB2 phy driver. I'm testing on a Dragonboard 820c.
> In boot log I get:
>
> [4.525502] phy phy-7412000.phy.6: QUSB2PHY pll lock failed:
Hello.
I further debugged, and may I an a couple of questions to my list.
5) In the following steps, must I keep ep0 open until I successfully write
controller name to UDC file?
>iii) Set descriptors, etc.
>
>Write necessary info into /dev/myffs1/ep0
>(So that ffs thinks descriptors are ready.)
38 matches
Mail list logo
