From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: "dbasehore ." <dbasehore@chromium.org>, Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, Guenter Roeck <groeck@chromium.org>,
Linux-pm mailing list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] i2c: enable async suspend/resume on i2c devices
Date: Sun, 29 Mar 2020 12:24:05 +0200 [thread overview]
Message-ID: <e69c39e6d86fb4e9fe560a20485158e7aa7d80cf.camel@collabora.com> (raw)
In-Reply-To: <CAGAzgsqJznZi83ijxCgQg463Q4AnwiNX-a0Q9+Og9MW5OJ4Vew@mail.gmail.com>
On Fri, 2020-03-27 at 13:26 -0700, dbasehore . wrote:
>
> Enabling async is a confirmation that all dependencies to other
> devices are properly tracked, whether through the parent/child
> relationship or otherwise.
Thanks for the info, Derek.
Wouldn't it be risky then to enable async for all i2c client devices
indiscriminately? Or is it safe to assume that all i2c devices will be
idependent from each other?
Cheers,
Ricardo
next prev parent reply other threads:[~2020-03-29 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 15:19 [PATCH] i2c: enable async suspend/resume on i2c devices Ricardo Cañuelo
2020-03-27 15:43 ` Wolfram Sang
2020-03-27 20:26 ` dbasehore .
2020-03-29 10:24 ` Ricardo Cañuelo [this message]
2020-03-29 12:49 ` Ezequiel Garcia
2020-04-08 5:06 ` dbasehore .
-- strict thread matches above, loose matches on Subject: below --
2018-07-26 22:55 Derek Basehore
2018-07-27 10:44 ` Andy Shevchenko
2018-07-27 12:07 ` Hans de Goede
2018-07-27 16:17 ` dbasehore .
2018-08-14 17:52 ` Andy Shevchenko
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=e69c39e6d86fb4e9fe560a20485158e7aa7d80cf.camel@collabora.com \
--to=ricardo.canuelo@collabora.com \
--cc=dbasehore@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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).