From: Johan Hovold <johan@kernel.org>
To: Sebastian Reichel <sre@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>,
Yegor Yefremov <yegorslists@googlemail.com>,
linux-omap@vger.kernel.org, vkoul@kernel.org,
Bin Liu <b-liu@ti.com>, linux-usb <linux-usb@vger.kernel.org>,
Andrey Skvortsov <andrej.skvortzov@gmail.com>,
giulio.benetti@benettiengineering.com,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: musb: cppi41: broken high speed FTDI functionality when connected to musb directly
Date: Tue, 1 Oct 2019 10:03:39 +0200 [thread overview]
Message-ID: <20191001080339.GF13531@localhost> (raw)
In-Reply-To: <20190930195411.6porqtm7tlokgel3@earth.universe>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
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 same module clock from what I remember though. So
> > maybe increase the cppi41 autosuspend_timeout from 100 ms to 500 ms
> > or higher:
> >
> > # echo 500 > /sys/bus/platform/drivers/cppi41-dma-engine/47400000.dma-controller/power/autosuspend_delay_ms
> >
> > If changing the autosuspend_timeout_ms value does not help, then
> > try setting control to on there.
>
> I did not check the details, but from the cover-letter this might be
> woth looking into:
>
> https://lore.kernel.org/lkml/20190930161205.18803-1-johan@kernel.org/
No, that one should be unrelated as it would only prevent later suspends after
a driver has been unbound (and rebound).
Johan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-10-01 8:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 8:18 musb: cppi41: broken high speed FTDI functionality when connected to musb directly Yegor Yefremov
2019-09-27 12:30 ` Yegor Yefremov
2019-09-27 15:19 ` Tony Lindgren
2019-09-27 15:57 ` Tony Lindgren
2019-09-28 16:09 ` Yegor Yefremov
2019-09-30 6:59 ` Yegor Yefremov
2019-09-30 8:19 ` Yegor Yefremov
2019-09-30 14:57 ` Tony Lindgren
2019-09-30 15:23 ` Tony Lindgren
2019-09-30 19:54 ` Sebastian Reichel
2019-10-01 8:03 ` Johan Hovold [this message]
2019-10-01 9:19 ` Yegor Yefremov
2019-10-01 16:43 ` Tony Lindgren
2019-10-01 22:03 ` Tony Lindgren
2019-10-02 6:56 ` Yegor Yefremov
2019-10-02 16:52 ` Tony Lindgren
2019-10-03 8:39 ` Yegor Yefremov
2019-10-21 8:39 ` Yegor Yefremov
2019-10-22 14:56 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191001080339.GF13531@localhost \
--to=johan@kernel.org \
--cc=andrej.skvortzov@gmail.com \
--cc=b-liu@ti.com \
--cc=bigeasy@linutronix.de \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
--cc=vkoul@kernel.org \
--cc=yegorslists@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.