Hi Tony,
On Thu, Oct 3, 2019 at 10:39 AM Yegor Yefremov
wrote:
>
> Hi Tony,
>
> On Wed, Oct 2, 2019 at 6:52 PM Tony Lindgren wrote:
> >
> > * Yegor Yefremov [191002 06:57]:
> > > On Wed, Oct 2, 2019 at 12:03 AM Tony Lindgren wrote:
> > > > The o
Hi Tony,
On Wed, Oct 2, 2019 at 6:52 PM Tony Lindgren wrote:
>
> * Yegor Yefremov [191002 06:57]:
> > On Wed, Oct 2, 2019 at 12:03 AM Tony Lindgren wrote:
> > > The other way to fix this would be to just wake up cpp41 in
> > > cppi41_dma_prep_slave_sg()
On Wed, Oct 2, 2019 at 12:03 AM Tony Lindgren wrote:
>
> Hi,
>
> * Tony Lindgren [191001 16:52]:
> > * Yegor Yefremov [191001 09:20]:
> > > I've tried to increase the autosuspend_delay_ms and to set control to
> > > "on" but nothing
On Tue, Oct 1, 2019 at 10:03 AM Johan Hovold wrote:
>
> On Mon, Sep 30, 2019 at 09:54:11PM +0200, Sebastian Reichel wrote:
> > Hi,
> >
> > On Mon, Sep 30, 2019 at 08:23:30AM -0700, Tony Lindgren wrote:
>
> > > Actually playing with the cppi41 timeout might be more suitable here,
> > > they use the
On Mon, Sep 30, 2019 at 8:59 AM Yegor Yefremov
wrote:
>
> On Sat, Sep 28, 2019 at 6:09 PM Yegor Yefremov
> wrote:
> >
> > On Fri, Sep 27, 2019 at 5:57 PM Tony Lindgren wrote:
> > >
> > > * Tony Lindgren [190927 15:20]:
> > > > * Yegor Yefremov
On Sat, Sep 28, 2019 at 6:09 PM Yegor Yefremov
wrote:
>
> On Fri, Sep 27, 2019 at 5:57 PM Tony Lindgren wrote:
> >
> > * Tony Lindgren [190927 15:20]:
> > > * Yegor Yefremov [190927 12:31]:
> > > > On Fri, Sep 27, 2019 at 10:18 AM Yegor Yefremov
&g
On Fri, Sep 27, 2019 at 5:57 PM Tony Lindgren wrote:
>
> * Tony Lindgren [190927 15:20]:
> > * Yegor Yefremov [190927 12:31]:
> > > On Fri, Sep 27, 2019 at 10:18 AM Yegor Yefremov
> > > wrote:
> > > >
> > > > I was porting my system from
On Fri, Sep 27, 2019 at 10:18 AM Yegor Yefremov
wrote:
>
> I was porting my system from 3.18/4.2 to 5.3. During this process I
> noticed that FT4232 that is attached directly to musb is not working
> correctly when opened for the first time: tx is working but nothing
> can be r
I was porting my system from 3.18/4.2 to 5.3. During this process I
noticed that FT4232 that is attached directly to musb is not working
correctly when opened for the first time: tx is working but nothing
can be received. On the second opening everything is working fine.
When the same chip is conne
On Mon, Sep 23, 2019 at 7:45 PM Tony Lindgren wrote:
>
> * Yegor Yefremov [190821 01:24]:
> > I'm moving our systems to the recent kernel and have encountered an
> > older musb issue [1] that occurs with some 3G/4G modems. In this case
> > it is SIMCom 7600G-H. Aft
On Wed, Sep 18, 2019 at 1:45 PM Greg KH wrote:
>
> On Wed, Sep 18, 2019 at 01:22:42PM +0200, Yegor Yefremov wrote:
> > On Wed, Sep 18, 2019 at 1:08 PM Greg KH wrote:
> > >
> > > On Wed, Sep 18, 2019 at 11:14:15AM +0200, yegorsli...@googlemail.com
> > &
On Wed, Sep 18, 2019 at 1:08 PM Greg KH wrote:
>
> On Wed, Sep 18, 2019 at 11:14:15AM +0200, yegorsli...@googlemail.com wrote:
> > From: Yegor Yefremov
> >
> > Add additional port statistics like received and transmitted bytes
> > the way /proc/tty/driver/serial doe
I'm moving our systems to the recent kernel and have encountered an
older musb issue [1] that occurs with some 3G/4G modems. In this case
it is SIMCom 7600G-H. After this dump occurs the modem is still
working though.
[ 45.585644] [ cut here ]
[ 45.590785] WARNING: CPU
Fixes wrong spelled "pinctrl-bindings.txt" and "qcom-dwc3-usb-phy.txt"
file names as also wrong specified "mt8173-mtu3.txt" file name.
Signed-off-by: Yegor Yefremov
---
Changes:
v1 -> v2: add changelog text (Greg Kroah-Hartman)
Documentation/devicetree
Signed-off-by: Yegor Yefremov
---
Documentation/devicetree/bindings/usb/dwc3-st.txt | 4 ++--
Documentation/devicetree/bindings/usb/ehci-st.txt | 2 +-
Documentation/devicetree/bindings/usb/mt8173-mtu3.txt | 2 +-
Documentation/devicetree/bindings/usb/mt8173-xhci.txt | 4
On Tue, May 3, 2016 at 4:35 PM, Bin Liu wrote:
> Hi,
>
> On Tue, May 03, 2016 at 04:25:58PM +0200, Yegor Yefremov wrote:
>> On Tue, May 3, 2016 at 3:48 PM, Bin Liu wrote:
>> > Hi,
>> >
>> > On Tue, May 03, 2016 at 12:03:52PM +0200, Yegor Yefremov wrote:
On Tue, May 3, 2016 at 3:48 PM, Bin Liu wrote:
> Hi,
>
> On Tue, May 03, 2016 at 12:03:52PM +0200, Yegor Yefremov wrote:
>> On Thu, Apr 28, 2016 at 4:37 PM, Bin Liu wrote:
>> > Hi,
>> >
>> > On Thu, Apr 28, 2016 at 09:51:37AM +0300, Maxim Uvarov wr
t;>
>> if (USB_ENDPOINT_XFER_ISOC != qh->type) {
>>
>
> Thanks for testing it.
Have tested your patch and now both FT4232 and Huawei don't freeze on removal.
Bin, Max thanks for fixing this issue.
Tested-by: Yegor Yefremov
>> That I think a key
>> > > On Thu, Mar 31, 2016 at 07:29:21AM +0200, Yegor Yefremov wrote:
>> > > > Hello Greg,
>> > > >
>> > > > 3.18.x is missing this patch [1] in order to perform a successful
>> > > > build. The reason: following patch [2] in 3.1
Hello Greg,
3.18.x is missing this patch [1] in order to perform a successful
build. The reason: following patch [2] in 3.18.x uses a macro name
introduced in the missing patch [1].
Could you queue it for 3.18.30?
[1] http://marc.info/?l=git-commits-head&m=142403040503570&w=2
[2]
https://git.ke
On Fri, Dec 11, 2015 at 2:46 PM, Bjørn Mork wrote:
> Yegor Yefremov writes:
>
>> Let me know, if you need any additional info or if I should make specific
>> tests.
>
> First of all: Does it work with qmi_wwan? There is already a device
> entry there. You'll
Hi Bjørn,
On Fri, Dec 11, 2015 at 1:50 PM, Bjørn Mork wrote:
> Johan Hovold writes:
>
>> Dan and Björn,
>>
>> On Thu, Dec 10, 2015 at 04:42:52PM +0100, yegorsli...@googlemail.com wrote:
>>> From: Yegor Yefremov
>>>
>>> Signed-off-by: Yegor Yef
On Mon, Oct 12, 2015 at 11:34 AM, Yegor Yefremov
wrote:
> We have a problem, when using more than 12 FTDI ports. Kernels tried:
> 3.18.1, 4.2.3 and 4.3-rc5. SoC am335x 600MHz
>
> Below the USB topology:
>
> # lsusb -t
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=musb-hd
We have a problem, when using more than 12 FTDI ports. Kernels tried:
3.18.1, 4.2.3 and 4.3-rc5. SoC am335x 600MHz
Below the USB topology:
# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M
|__ Por
Hi Johan,
On Mon, Aug 17, 2015 at 5:29 PM, Johan Hovold wrote:
> On Tue, Aug 11, 2015 at 12:31:47PM +0200, Yegor Yefremov wrote:
>> On Tue, Aug 11, 2015 at 11:58 AM, Bjørn Mork wrote:
>> > [replaced 'netdev' with 'linux-usb' as this concerns a USB ser
[adding musb maintainer Felipe Balbi to this discussion]
On Tue, Aug 11, 2015 at 2:25 PM, Oliver Neukum wrote:
> On Tue, 2015-08-11 at 13:48 +0200, Bjørn Mork wrote:
>> I wonder if this is related to different platforms using different
>> errors for this event? As you can see, I get ESHUTDOWN wh
On Tue, Aug 11, 2015 at 11:58 AM, Bjørn Mork wrote:
> [replaced 'netdev' with 'linux-usb' as this concerns a USB serial driver only]
>
> Yegor Yefremov writes:
>
>> I have following problem. When removing USB dongle 07d1:3e01 or
>> SierraWireless MC
lipe Balbi wrote:
>>>> Hi,
>>>>
>>>> On Tue, Feb 24, 2015 at 11:39:11AM +0100, Maxime Ripard wrote:
>>>>> On Thu, Feb 05, 2015 at 02:21:42PM +0100, Maxime Ripard wrote:
>>>>>> Hi,
>>>>>>
>>>
On 21.01.2015 19:53, Bin Liu wrote:
> Hi,
>
> On Wed, Jan 21, 2015 at 10:06 AM, Maxime Ripard
> wrote:
>> Hi Felipe,
>>
>> I'm currently working on a custom AM335x-based board, that has a OTG
>> connector wired to one of the musb controlers, and Linux 3.17
>>
>> This OTG connector seems to behave
On Sat, Nov 29, 2014 at 4:35 PM, Felipe Balbi wrote:
> Hi,
>
> On Fri, Nov 28, 2014 at 11:35:53AM +0100, Yegor Yefremov wrote:
>> On Wed, Nov 19, 2014 at 6:53 PM, Tony Lindgren wrote:
>> > * Enric Balletbo Serra [141119 03:14]:
>> >> 2014
On Wed, Nov 19, 2014 at 6:53 PM, Tony Lindgren wrote:
> * Enric Balletbo Serra [141119 03:14]:
>> 2014-11-18 16:42 GMT+01:00 Tony Lindgren :
>>
>> Checked again, and no luck. It's very weird because from the OTG point
>> of view, OTG is exactly the same between Beagleboard-XM and IGEPv2.
>>
>> Ca
On Wed, Aug 27, 2014 at 10:42 AM, wrote:
> From: Yegor Yefremov
>
> Using $(PWD) breaks builds when make was invoked from outside
> of the kernel tree.
Some details: I've experienced this issue with Buildroot. I don't
know, if this will happen with OpenEmbedded, but it is
On Wed, Jul 2, 2014 at 3:28 PM, Yegor Yefremov
wrote:
> On Tue, Jul 1, 2014 at 5:37 PM, Ezequiel García
> wrote:
>> On 1 July 2014 12:07, Yegor Yefremov wrote:
>> [..]
>>>
>>> What can be done with these error messages:
>>>
>>> of_get
On Tue, Jul 1, 2014 at 5:43 PM, Bin Liu wrote:
> On Tue, Jul 1, 2014 at 10:37 AM, Ezequiel García
> wrote:
>> On 1 July 2014 12:07, Yegor Yefremov wrote:
>> [..]
>>>
>>> What can be done with these error messages:
>>>
>>> of_get_named_gpi
On Tue, Jul 1, 2014 at 5:37 PM, Ezequiel García
wrote:
> On 1 July 2014 12:07, Yegor Yefremov wrote:
> [..]
>>
>> What can be done with these error messages:
>>
>> of_get_named_gpiod_flags: can't parse gpios property of node
>> '/ocp/usb@4740/u
On Tue, Jul 1, 2014 at 3:03 PM, Yegor Yefremov
wrote:
> I have following system:
>
> USB0: host mode (USB hub is soldered internally)
> USB1: OTG mode with OTG connector
>
> My DTS: http://pastebin.com/KB3iTehQ
>
> If I enable DMA in the kernel, I get USB0 working, i.e. U
I have following system:
USB0: host mode (USB hub is soldered internally)
USB1: OTG mode with OTG connector
My DTS: http://pastebin.com/KB3iTehQ
If I enable DMA in the kernel, I get USB0 working, i.e. USB hub is
detected and USB devices, that are connected to this hub are also
detected and worki
On Tue, May 28, 2013 at 7:36 PM, Felipe Balbi wrote:
> On Tue, May 28, 2013 at 09:21:01AM +0200, yegorsli...@googlemail.com wrote:
>> From: Yegor Yefremov
>>
>> 'ick' was changed to 'hsotgusb_ick'
>> 'fck' was changed to 'hsotgusb
On Wed, May 29, 2013 at 11:36 AM, Jan Lübbe wrote:
> On Tue, 2013-05-28 at 20:36 +0300, Felipe Balbi wrote:
>> On Tue, May 28, 2013 at 09:21:01AM +0200, yegorsli...@googlemail.com wrote:
>> > From: Yegor Yefremov
>> >
>> > 'ick' was chang
On Wed, Apr 3, 2013 at 12:16 PM, Yegor Yefremov
wrote:
> On Wed, Apr 3, 2013 at 9:12 AM, Yegor Yefremov
> wrote:
>> On Tue, Apr 2, 2013 at 4:36 PM, Alan Stern wrote:
>>> On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>>>
>>>> On Tue, Apr 2, 2013 at 4:14 PM,
On Wed, Apr 3, 2013 at 9:12 AM, Yegor Yefremov
wrote:
> On Tue, Apr 2, 2013 at 4:36 PM, Alan Stern wrote:
>> On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>>
>>> On Tue, Apr 2, 2013 at 4:14 PM, Alan Stern
>>> wrote:
>>> > On Tue, 2 Apr 2013, Yegor Yefr
On Tue, Apr 2, 2013 at 4:36 PM, Alan Stern wrote:
> On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>
>> On Tue, Apr 2, 2013 at 4:14 PM, Alan Stern wrote:
>> > On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>> >
>> >> I'm making a burn-in test (see serialtest
On Tue, Apr 2, 2013 at 4:14 PM, Alan Stern wrote:
> On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>
>> I'm making a burn-in test (see serialtest.py
>> http://pastebin.com/pz47gaar) for our devices, that have built-in FTDI
>> chips. If FT2232C is attached directly to th
I'm making a burn-in test (see serialtest.py
http://pastebin.com/pz47gaar) for our devices, that have built-in FTDI
chips. If FT2232C is attached directly to the USB host controller
port, the tests run properly. If I connect the chip to a USB-hub some
of the tests show timeout errors (read() routin
44 matches
Mail list logo
