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
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:
> 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
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.
> 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:
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
> -
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
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 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.
>
>
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
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
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
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
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
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
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
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
---
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.)
20 matches
Mail list logo
