From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: "Wolfram Sang" <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@osg.samsung.com>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>,
linux-pm@vger.kernel.org,
"Alan Stern" <stern@rowland.harvard.edu>,
"Enric Balletbo i Serra" <eballetbo@gmail.com>,
"Agustí Fontquerni" <af@iseebcn.com>
Subject: Re: tvp5150 regression after commit 9f924169c035
Date: Fri, 15 Apr 2016 10:08:04 -0700 [thread overview]
Message-ID: <20160415170804.GW5973@atomide.com> (raw)
In-Reply-To: <57111B76.8020106@osg.samsung.com>
* Javier Martinez Canillas <javier@osg.samsung.com> [160415 09:50]:
> On 04/15/2016 10:58 AM, Tony Lindgren wrote:
> > If you block PM runtime for I2C, then it blocks deeper idle states
> > for the whole device. Note that you can disable off mode during idle
>
> Thanks again for this clarification.
>
> > and suspend with:
> >
> > # echo 0 > /sys/kernel/debug/pm_debug/enable_off_mode
> >
>
> I see thought that enable_off_mode is 0 by default when booting the board:
>
> # cat /sys/kernel/debug/pm_debug/enable_off_mode
> 0
OK so you're not hitting off mode then.
> So if I understood your explanation correctly, that means that the glitch
> should not happen for the GPIO pins since the machine doesn't enter into
> deeper idle states that could cause the glitch from erratum 1.158?
Correct. But you could still have a dependency to some other
device driver that stays active if I2C keeps the whole system
from hitting retention mode during idle.
Regards,
Tony
next prev parent reply other threads:[~2016-04-15 17:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56B204CB.60602@osg.samsung.com>
2016-02-08 10:54 ` tvp5150 regression after commit 9f924169c035 Wolfram Sang
2016-02-12 22:09 ` Javier Martinez Canillas
2016-02-12 22:13 ` Tony Lindgren
2016-02-12 22:28 ` Javier Martinez Canillas
2016-02-12 22:40 ` Tony Lindgren
2016-02-12 23:08 ` Javier Martinez Canillas
2016-02-12 23:46 ` Tony Lindgren
2016-02-13 2:47 ` Javier Martinez Canillas
2016-04-12 22:32 ` Wolfram Sang
2016-04-13 22:39 ` Javier Martinez Canillas
2016-04-14 11:12 ` Wolfram Sang
2016-04-14 13:41 ` Javier Martinez Canillas
2016-04-14 14:19 ` Wolfram Sang
2016-04-14 14:27 ` Javier Martinez Canillas
2016-04-14 15:12 ` Tony Lindgren
2016-04-14 23:59 ` Javier Martinez Canillas
2016-04-15 14:58 ` Tony Lindgren
2016-04-15 16:48 ` Javier Martinez Canillas
2016-04-15 17:08 ` Tony Lindgren [this message]
2016-02-12 22:22 ` Wolfram Sang
2016-02-12 22:26 ` Javier Martinez Canillas
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=20160415170804.GW5973@atomide.com \
--to=tony@atomide.com \
--cc=af@iseebcn.com \
--cc=eballetbo@gmail.com \
--cc=javier@osg.samsung.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=stern@rowland.harvard.edu \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).