From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Matwey V. Kornilov" <matwey@sai.msu.ru>
Cc: Bin Liu <b-liu@ti.com>,
hdegoede@redhat.com, linux-media@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: pwc over musb: 100% frame drop (lost) on high resolution stream
Date: Mon, 1 Aug 2016 09:50:07 -0700 [thread overview]
Message-ID: <20160801165007.GL4605@ubuntu> (raw)
In-Reply-To: <CAJs94EbpTzpzDeubBGOaqPavwBHzgKhb9E0MN0_v_irWRRwJDQ@mail.gmail.com>
On 31-07-16, 23:31, Matwey V. Kornilov wrote:
> Hello,
>
> I've also just found that the same commit breaks cpufreq on BeagleBone Black :)
>
> So, probably without HCD_BH flag musb works correctly only at 1Ghz CPU
> frequency, which is unlisted and being set to 720Mhz by cpufreq driver
> (as it did whet there was cpufreq driver).
>
> 2016-07-29 21:01 GMT+03:00 Matwey V. Kornilov <matwey@sai.msu.ru>:
> > Hello,
> >
> > I've found that the following commit fixes the issue:
> >
> > commit 7694ca6e1d6f01122f05039b81f70f64b1ec4063
> > Author: Viresh Kumar <viresh.kumar@linaro.org>
> > Date: Fri Apr 22 16:58:42 2016 +0530
> >
> > cpufreq: omap: Use generic platdev driver
> >
> > The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform
> > device now, reuse that and remove similar code from platform code.
Sorry for this commit and the man hours wasted to get to this :(
I am trying to figure out why things break though, as this patch shouldn't have
had any functional impacts. So, some of the assumptions I had are surely
incorrect..
The defconfig linked in the original thread [1] has this:
CONFIG_CPUFREQ_DT=m
So, the cpufreq-dt module needs to get inserted to make it work.
Can someone provide the output of:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
with and without this patch ?
It looks like we wanted to select "omap-cpufreq" for beaglebone and selected
"cpufreq-dt" by mistake.
[Note]: I am not subscribed to USB lists and so please include me for any emails
you want my response on.
--
viresh
[1] http://www.spinics.net/lists/linux-usb/msg143956.html
--
viresh
next prev parent reply other threads:[~2016-08-01 16:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 20:21 pwc over musb: 100% frame drop (lost) on high resolution stream matwey
2016-07-19 20:56 ` Bin Liu
2016-07-19 21:25 ` Matwey V. Kornilov
2016-07-19 21:34 ` Bin Liu
2016-07-20 6:09 ` Matwey V. Kornilov
2016-07-20 8:21 ` Matwey V. Kornilov
2016-07-20 14:13 ` Bin Liu
2016-07-20 14:44 ` Matwey V. Kornilov
2016-07-20 15:06 ` Bin Liu
2016-07-20 18:56 ` Matwey V. Kornilov
2016-07-23 19:24 ` Matwey V. Kornilov
2016-07-27 17:34 ` Matwey V. Kornilov
2016-07-28 16:16 ` Matwey V. Kornilov
2016-07-29 18:01 ` Matwey V. Kornilov
2016-07-31 20:31 ` Matwey V. Kornilov
2016-08-01 16:50 ` Viresh Kumar [this message]
2016-08-01 17:01 ` Matwey V. Kornilov
2016-08-01 17:06 ` Viresh Kumar
2016-08-01 18:11 ` Matwey V. Kornilov
2016-08-01 18:16 ` Matwey V. Kornilov
2016-08-04 16:57 ` Matwey V. Kornilov
2016-08-04 19:08 ` Matwey V. Kornilov
2016-08-04 19:58 ` Matwey V. Kornilov
2016-08-04 20:08 ` Matwey V. Kornilov
2016-08-18 13:31 ` Matwey V. Kornilov
2016-08-20 18:09 ` Matwey V. Kornilov
2016-08-21 14:02 ` Matwey V. Kornilov
2016-08-21 16:07 ` Matwey V. Kornilov
2016-08-21 22:00 ` Alan Stern
2016-08-22 8:32 ` Matwey V. Kornilov
2016-08-24 18:17 ` Matwey V. Kornilov
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=20160801165007.GL4605@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=b-liu@ti.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matwey@sai.msu.ru \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox