On Wednesday, September 14, 2016 9:49:30 AM CEST Peter Chen wrote:
> According to (badf6d47f8a9 "usb: common: rework CONFIG_USB_COMMON logic")
> we should select USB_COMMON at Kconfig when usb common stuffs are needed,
> but some of Kconfig enties have not followed it, update them.
>
> Cc: Arnd Be
On Tue, Sep 13, 2016 at 10:58:26PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-09-13 20:32:00)
> > On Tue, Sep 13, 2016 at 06:42:46PM -0700, Stephen Boyd wrote:
> > > On the db410c 96boards platform we have a TC7USB40MU[1] on the
> > > board to mux the D+/D- lines from the SoC between a m
On Wed, Sep 14, 2016 at 09:35:10AM +0200, Arnd Bergmann wrote:
> On Wednesday, September 14, 2016 9:49:30 AM CEST Peter Chen wrote:
> > According to (badf6d47f8a9 "usb: common: rework CONFIG_USB_COMMON logic")
> > we should select USB_COMMON at Kconfig when usb common stuffs are needed,
> > but som
Am Dienstag, den 13.09.2016, 17:59 -0700 schrieb Kevin Hilman:
> Martin Blumenstingl writes:
>
> > On Tue, Sep 13, 2016 at 5:28 PM, Philipp Zabel
> > wrote:
>
> [...]
>
> >>> I added Philipp and Hans to this thread - maybe they can comment on this.
> >>> To sum it up, our problem is:
> >>> -
Am Dienstag, den 13.09.2016, 17:59 -0700 schrieb Kevin Hilman:
> Martin Blumenstingl writes:
>
> > On Tue, Sep 13, 2016 at 5:28 PM, Philipp Zabel
> > wrote:
>
> [...]
>
> >>> I added Philipp and Hans to this thread - maybe they can comment on this.
> >>> To sum it up, our problem is:
> >>> -
Am Dienstag, den 13.09.2016, 20:38 +0200 schrieb Martin Blumenstingl:
> Hi Philipp,
>
> On Tue, Sep 13, 2016 at 5:28 PM, Philipp Zabel wrote:
> > Hi Martin,
> >
> > Am Freitag, den 09.09.2016, 22:36 +0200 schrieb Martin Blumenstingl:
> >> On Fri, Sep 9, 2016 at 5:33 PM, Kevin Hilman wrote:
> >>
Quoting Stephen Boyd (2016-09-13 18:42:46)
> On the db410c 96boards platform we have a TC7USB40MU[1] on the
> board to mux the D+/D- lines from the SoC between a micro usb
> "device" port and a USB hub for "host" roles. Upon a role switch,
> we need to change this mux to forward the D+/D- lines to
On Tue, Sep 13, 2016 at 11:29:12PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-09-13 19:11:33)
> > On Tue, Sep 13, 2016 at 01:41:44PM -0700, Stephen Boyd wrote:
> > > Quoting Peter Chen (2016-09-13 00:03:58)
> > > > On Wed, Sep 07, 2016 at 02:35:19PM -0700, Stephen Boyd wrote:
> > > > > T
On Tue, Sep 13, 2016 at 08:05:32PM +0200, Fabien Lahoudere wrote:
> Hi Peter,
>
> >>
> >>This is our device tree imx-ppd.dts:
> >
> >I may know the reason why you meet hang at current flow, you are using
> >generic phy driver, and the PHY clock is enabled at phy_init which is
> >called later than
On Tue, Sep 13, 2016 at 10:00:28AM +0200, NeilBrown wrote:
> On Mon, Sep 12 2016, Mark Brown wrote:
> > That's not actually 100% clear to me - for what the wm831x is doing it
> > probably *does* want the higher limit. This is a system inflow limit
> > (as it should be for this), at least the char
Hi Greg,
Here's my pull request for v4.9 merge window. Patches have been tested
with plataforms I have around (where applicable) and have also been
soaking in linux-next for a while.
Let me know if you want anything to be changed.
The following changes since commit fa8410b355251fd30341662a40ac6
Add tree entry for USB Serial.
Signed-off-by: Johan Hovold
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6781a3febd59..c7131a91013a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12267,6 +12267,7 @@ F: drivers/net/usb/rtl8150.c
USB SERI
may be i can help to test something else? I am ready and have enough free time
2016-09-12 20:44 GMT+03:00 c400 :
> [182047.000570] xhci_hcd :02:00.0: remove, state 4
> [182047.000577] usb usb4: USB disconnect, device number 1
> [182047.023980] xhci_hcd :02:00.0: Host not halted after 16000
On Wed, 2016-09-14 at 15:22 +0300, c400 wrote:
> may be i can help to test something else? I am ready and have enough free time
You may need to mount debugfs at /sys/kernel/debug
HTH
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the bo
On Tue, Sep 13, 2016 at 10:22:43AM -0700, Tony Lindgren wrote:
> We can occasionally get -EINPROGRESS for pm_runtime_get. In that case
> we can just continue as we're queueing transfers anyways when
> pm_runtime_active is not set.
Applied, thanks
--
~Vinod
--
To unsubscribe from this list: send
We have had two new PHY drivers call of_usb_get_dr_mode_by_phy()
recently without having a dependency on CONFIG_USB_COMMON, resulting
in a link error:
ERROR: "of_usb_get_dr_mode_by_phy" [drivers/phy/phy-meson-usb2.ko] undefined!
I fixed up the first one (sun4i) by adding the dependency, but
if we
On 08.09.2016 17:38, Alan Stern wrote:
On Thu, 8 Sep 2016, Mathias Nyman wrote:
ehci-hcd includes checks in several places for ehci->rh_state ==
RH_STATE_RUNNING. The removal pathway sets ehci->rh_state to
RH_STATE_HALTED. As a result, the driver avoids waiting for things
that will never happ
On Wed, Sep 14 2016, Mark Brown wrote:
> [ Unknown signature status ]
> On Tue, Sep 13, 2016 at 10:00:28AM +0200, NeilBrown wrote:
>> On Mon, Sep 12 2016, Mark Brown wrote:
>
>> > That's not actually 100% clear to me - for what the wm831x is doing it
>> > probably *does* want the higher limit. Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Ulf and Alan,
On Fri, 2016-09-09 at 19:34 +0530, Ritesh Raj Sarraf wrote:
> For #2, I'm building the 4.8-rc5 kernel with the following change. This build
> does not include the previous change you had suggested (related to
> POWER_CYCLE)
>
>
On Wed, Sep 14, 2016 at 04:11:58PM +0200, NeilBrown wrote:
> On Wed, Sep 14 2016, Mark Brown wrote:
> > Yes, the idea is that the charger will back off charging and stop
> > entirely if the rest of the system is consuming too much power to allow
> > it to continue effectively. The same thing happ
On Wed, 14 Sep 2016, Ritesh Raj Sarraf wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hello Ulf and Alan,
>
> On Fri, 2016-09-09 at 19:34 +0530, Ritesh Raj Sarraf wrote:
> > For #2, I'm building the 4.8-rc5 kernel with the following change. This
> > build
> > does not include th
Please use Reply-To-All so that your message gets sent to the mailing
list as well as to me.
On Tue, 13 Sep 2016, Arun Thiruvanantha wrote:
> Thanks Alan for your Help
>
> I have tried dyndbg="module ehci_hcd =p" in boot command line param, But
> No effect.
>
> Also enabled USB_DEBUG flag but
On Wed, Sep 07, 2016 at 01:47:22PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Robin Murphy writes:
> > On 07/09/16 10:55, Peter Chen wrote:
> > [...]
> >>> Regarding the DMA configuration that you mention in ci_hdrc_add_device(),
> >>> I think we should replace
> >>>
> >>> pdev->dev.dma_mas
On Wed, Sep 14 2016, Mark Brown wrote:
> TI do a lot of the more software managed chargers (which I suspect are
> the main thing Felipe will have looked at) if that's what you're
> referring to here? The device is implementing pretty much the algorithm
> you're describing in that e-mail so I'm a
On Wed, 14 Sep 2016, Arun Thiruvanantha wrote:
> Hi Alan ,
> We are using linux kernel 2.6.32 version
That's a very old kernel release. A lot of bugs have been fixed since
it came out.
Can you try using a more recent version, like 4.7? It will make
debugging a lot easier.
Alan Stern
--
To
On Wed, Sep 14, 2016 at 07:50:00PM +0200, NeilBrown wrote:
> On Wed, Sep 14 2016, Mark Brown wrote:
> Ah my mistake, sorry.
> When earlier you said:
> > It's a
> > current limiter intended to sit in line with the USB power lines
Martin Blumenstingl writes:
> From: Jerome Brunet
>
> Enable both gxbb USB controller and add a 5V regulator for the OTG port
> VBUS
>
> Signed-off-by: Jerome Brunet
nit: subject should have "ARM64: dts:" prefix.
> ---
> arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi | 29
> ++
Commit a83e17d0f73b ("usb: musb: Improve PM runtime and phy handling
for 2430 glue layer") moved PHY enable/disable calls to happen from
omap2430_musb_enable/disable(). That broke enumeration for several
devices as PM runtime in the PHY will never enable it.
The root cause of the problem is unpair
On 9/14/2016 9:11 AM, Kevin Hilman wrote:
> Hi John,
>
> Martin Blumenstingl writes:
>
>> From: Jerome Brunet
>>
>> Add compatible strings for amlogic Meson8b and GXBB SoCs with the
>> corresponding configuration parameters.
>>
>> Signed-off-by: Jerome Brunet
>> Signed-off-by: Martin Blumensti
On Wed, Sep 14, 2016 at 11:12 AM, John Youn wrote:
> On 9/14/2016 9:11 AM, Kevin Hilman wrote:
>> Hi John,
>>
>> Martin Blumenstingl writes:
>>
>>> From: Jerome Brunet
>>>
>>> Add compatible strings for amlogic Meson8b and GXBB SoCs with the
>>> corresponding configuration parameters.
>>>
>>> Si
On 9/14/2016 11:17 AM, Kevin Hilman wrote:
> On Wed, Sep 14, 2016 at 11:12 AM, John Youn wrote:
>> On 9/14/2016 9:11 AM, Kevin Hilman wrote:
>>> Hi John,
>>>
>>> Martin Blumenstingl writes:
>>>
From: Jerome Brunet
Add compatible strings for amlogic Meson8b and GXBB SoCs with the
>
On Wed, Sep 14, 2016 at 11:26 AM, John Youn wrote:
> On 9/14/2016 11:17 AM, Kevin Hilman wrote:
>> On Wed, Sep 14, 2016 at 11:12 AM, John Youn wrote:
>>> On 9/14/2016 9:11 AM, Kevin Hilman wrote:
Hi John,
Martin Blumenstingl writes:
> From: Jerome Brunet
>
> Add
On Wed, Sep 14, 2016 at 03:00:49PM +0300, Felipe Balbi wrote:
>
> Hi Greg,
>
> Here's my pull request for v4.9 merge window. Patches have been tested
> with plataforms I have around (where applicable) and have also been
> soaking in linux-next for a while.
>
> Let me know if you want anything to
2016-09-14 15:43 GMT+03:00 Oliver Neukum :
> On Wed, 2016-09-14 at 15:22 +0300, c400 wrote:
>> may be i can help to test something else? I am ready and have enough free
>> time
>
> You may need to mount debugfs at /sys/kernel/debug
>
> HTH
> Oliver
>
>
mount -t debugfs none
On Wed, 14 Sep 2016, c400 wrote:
> 2016-09-14 15:43 GMT+03:00 Oliver Neukum :
> > On Wed, 2016-09-14 at 15:22 +0300, c400 wrote:
> >> may be i can help to test something else? I am ready and have enough free
> >> time
Did you try Mathias's suggestion of forcing DMA to use 32 bits?
After unloadin
On Wed, Sep 14, 2016 at 10:37 AM, Philipp Zabel wrote:
> Am Dienstag, den 13.09.2016, 17:59 -0700 schrieb Kevin Hilman:
>> Martin Blumenstingl writes:
>>
>> > On Tue, Sep 13, 2016 at 5:28 PM, Philipp Zabel
>> > wrote:
>>
>> [...]
>>
>> >>> I added Philipp and Hans to this thread - maybe they ca
On Wed, 14 Sep 2016, c400 wrote:
> yep! enabling You need to enable CONFIG_DYNAMIC_DEBUG. did the trick!
> here is my new dmesg output:
Did you use the 32-bit DMA quirks option for xhci_hcd?
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a mess
On Wed, Sep 14, 2016 at 10:37 AM, Philipp Zabel wrote:
> Am Dienstag, den 13.09.2016, 20:38 +0200 schrieb Martin Blumenstingl:
>> Hi Philipp,
>>
>> On Tue, Sep 13, 2016 at 5:28 PM, Philipp Zabel
>> wrote:
>> > Hi Martin,
>> >
>> > Am Freitag, den 09.09.2016, 22:36 +0200 schrieb Martin Blumenstin
On Sun, Sep 11, 2016 at 3:41 PM, Martin Blumenstingl
wrote:
> This is a new driver for the USB PHY found in Meson8b and GXBB SoCs.
>
> Signed-off-by: Martin Blumenstingl
> Signed-off-by: Jerome Brunet
> Tested-by: Kevin Hilman
> ---
> drivers/phy/Kconfig | 11 ++
> drivers/phy/Makefi
On 8/31/2016 1:37 PM, John Youn wrote:
> On 8/31/2016 12:47 PM, Felipe Balbi wrote:
>>
>> Hi John,
>>
>> John Youn writes:
>>> On 8/31/2016 2:38 AM, Felipe Balbi wrote:
If we don't know what are the actual U1/U2 exit
latencies from the UDC, we're better off using
maximum latencies a
On Wednesday, September 14, 2016 5:31:36 PM CEST Lorenzo Pieralisi wrote:
> On Wed, Sep 07, 2016 at 01:47:22PM +0300, Felipe Balbi wrote:
> >
> > Hi,
> >
> > Robin Murphy writes:
> > > On 07/09/16 10:55, Peter Chen wrote:
> > > [...]
> > >>> Regarding the DMA configuration that you mention in
>
XHCI_NO_64BIT_SUPPORT
can't find such flag in my kernel config. May be you can help me to
find it in menuconfig tree?
2016-09-14 23:25 GMT+03:00 c400 :
> yep! enabling You need to enable CONFIG_DYNAMIC_DEBUG. did the trick!
> here is my new dmesg output:
>
>
> 2016-09-14 22:39 GMT+03:00 c400 :
>>
On Wednesday, September 14, 2016 3:51:01 PM CEST Arnd Bergmann wrote:
> We have had two new PHY drivers call of_usb_get_dr_mode_by_phy()
> recently without having a dependency on CONFIG_USB_COMMON, resulting
> in a link error:
>
> ERROR: "of_usb_get_dr_mode_by_phy" [drivers/phy/phy-meson-usb2.ko]
On Wed, Sep 14, 2016 at 10:42:50AM -0700, Stephen Boyd wrote:
> > >
> > > Hmm.. maybe the confusion is in which registers we should be able to
> > > access? Are we talking about the ULPI viewport MMIO register space or
> > > the ULPI registers that we access through the viewport? I have a
> > > hw
On Thu, Sep 15, 2016 at 12:03:48AM +0100, Aidan Thornton wrote:
> On 24 Jun 2016 16:10, "Greg KH" wrote:
> >
> > On Fri, Jun 24, 2016 at 01:42:24PM +0800, WCH Tech Group wrote:
> > > There are several reasons why we decided to revoke the old one after
> > > communicating with the author of
>
Hi,
John Youn writes:
>>> John Youn writes:
On 8/31/2016 2:38 AM, Felipe Balbi wrote:
> If we don't know what are the actual U1/U2 exit
> latencies from the UDC, we're better off using
> maximum latencies as default. This should avoid
> any problems with too frequent U1/U2
46 matches
Mail list logo
