From: Wolfram Sang <wsa@the-dreams.de>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Shardar Shariff Md <smohammed@nvidia.com>,
linux-tegra@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] i2c: tegra: Remove suspend-resume
Date: Tue, 29 May 2018 20:06:59 +0200 [thread overview]
Message-ID: <20180529180659.f5s56nstykztvykr@ninjato> (raw)
In-Reply-To: <5949e650-8ab5-b4bb-196d-5a0705383141@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
> > Our I2C driver is based on the interrupt. So we have converted the
> > suspend/resume to suspend_noirq and reseume_noirq so that we will not allow the
> > transfer when system interrupt disabled in downstream.
> > SET_NOIRQ_SYSTEM_SLEEP_PM_OPS(tegra_i2c_suspend, tegra_i2c_resume)
> >
> > In shutdown path, where interrupt disabled and still need i2c, we use the
> > bit-bang method via GPIO for i2c transfer.
> In the current upstream kernel suspend/resume can't be simply moved to the
> 'noirq' stage because resume invokes tegra_i2c_init() which uses runtime PM and
> that doesn't work with the IRQ's being disabled. But things do not work even
> with the tegra_i2c_init() changed to work with the disabled IRQ's, like I wrote
> above the I2C transfer fails (due to timeout) and a "fix" for that failure was
> to remove reset_control_assert/deassert from the tegra_i2c_init(). So I'd go for
> a complete suspend/resume removal for now as it is causes problem.
Laxman, are you convinced or do you have still objections?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-29 18:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 21:13 [PATCH v1] i2c: tegra: Remove suspend-resume Dmitry Osipenko
2018-05-14 11:59 ` Thierry Reding
2018-05-14 12:18 ` Wolfram Sang
2018-05-14 13:03 ` Dmitry Osipenko
2018-05-14 12:21 ` Laxman Dewangan
2018-05-14 12:47 ` Thierry Reding
2018-05-14 12:51 ` Dmitry Osipenko
2018-05-29 18:06 ` Wolfram Sang [this message]
2018-05-30 10:59 ` Laxman Dewangan
2018-05-30 20:18 ` Wolfram Sang
2018-05-30 20:25 ` Wolfram Sang
2018-05-30 22:17 ` Dmitry Osipenko
2018-10-17 13:59 ` Jon Hunter
2018-10-17 14:30 ` Dmitry Osipenko
2018-10-17 19:41 ` Jon Hunter
2018-10-17 20:49 ` Dmitry Osipenko
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=20180529180659.f5s56nstykztvykr@ninjato \
--to=wsa@the-dreams.de \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=smohammed@nvidia.com \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox