From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org
Subject: Re: droid 4: no sound in the morning
Date: Tue, 10 Jul 2018 15:53:26 +0200 [thread overview]
Message-ID: <20180710135325.GA23878@amd> (raw)
In-Reply-To: <20180710105910.GA4442@amd>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Tue 2018-07-10 12:59:10, Pavel Machek wrote:
> Hi!
>
> I attempted to use droid 4 as an alarm clock, but got no sound in the
> morning.
>
> Log said:
>
> [78798.682830] omap-mcbsp 40124000.mcbsp: CLKS: could not
> clk_set_parent() to prcm_fck
> [78803.561767] omap-mcbsp 40126000.mcbsp: CLKS: could not
> clk_set_parent() to prcm_fck
>
> Could it be related? Everything ok after reboot, v4.18-rc4.
>
> Does anyone else see that? Any ideas?
Ok, so I see that
[ 1775.896270] Charging, 4350000 uV, 532000 uA
[ 1778.700286] omap-mcbsp 40124000.mcbsp: CLKS: could not
clk_set_parent() to prcm_fck
[ 1778.898468] Charging, 4350000 uV, 532000 uA
...even when audio still works. So possibly not related.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: droid 4: no sound in the morning
Date: Tue, 10 Jul 2018 15:53:26 +0200 [thread overview]
Message-ID: <20180710135325.GA23878@amd> (raw)
In-Reply-To: <20180710105910.GA4442@amd>
On Tue 2018-07-10 12:59:10, Pavel Machek wrote:
> Hi!
>
> I attempted to use droid 4 as an alarm clock, but got no sound in the
> morning.
>
> Log said:
>
> [78798.682830] omap-mcbsp 40124000.mcbsp: CLKS: could not
> clk_set_parent() to prcm_fck
> [78803.561767] omap-mcbsp 40126000.mcbsp: CLKS: could not
> clk_set_parent() to prcm_fck
>
> Could it be related? Everything ok after reboot, v4.18-rc4.
>
> Does anyone else see that? Any ideas?
Ok, so I see that
[ 1775.896270] Charging, 4350000 uV, 532000 uA
[ 1778.700286] omap-mcbsp 40124000.mcbsp: CLKS: could not
clk_set_parent() to prcm_fck
[ 1778.898468] Charging, 4350000 uV, 532000 uA
...even when audio still works. So possibly not related.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180710/2d0cea09/attachment.sig>
next prev parent reply other threads:[~2018-07-10 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 10:59 droid 4: no sound in the morning Pavel Machek
2018-07-10 10:59 ` Pavel Machek
2018-07-10 13:53 ` Pavel Machek [this message]
2018-07-10 13:53 ` Pavel Machek
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=20180710135325.GA23878@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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.