From: Wolfram Sang <wsa@the-dreams.de>
To: James Maki <jamescmaki@revolayer.com>
Cc: "Éric Piel" <eric.piel@tremplin-utc.net>, linux-i2c@vger.kernel.org
Subject: Re: lis3lv02d i2c access on shutdown
Date: Mon, 6 Mar 2017 17:54:54 +0100 [thread overview]
Message-ID: <20170306165454.GA2086@katana> (raw)
In-Reply-To: <41bff51c-9a4c-3e28-a9ed-eea916f87e9d@revolayer.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On Mon, Mar 06, 2017 at 09:10:52AM -0600, James Maki wrote:
> I think it is the same issue. How would i2c_transfer_noirq work? In my case
> another task was in the middle of a transaction when it was "stopped". This
> means not only do you need i2c_transfer_noirq, but also need to flush the
> bus before calling kernel_shutdown_prepare().
I don't know yet. I have a rough idea, but not even a design. The above
issue is important to know when starting to design the interface,
though. So, thanks for letting us know.
That all being said, if somebody is faster than me in doing this
interface, I am all for it :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-03-06 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <647cd755-3554-0719-6811-c64ffae0fc1e@revolayer.com>
2017-03-04 21:35 ` lis3lv02d i2c access on shutdown Éric Piel
2017-03-04 22:32 ` Wolfram Sang
2017-03-06 15:10 ` James Maki
2017-03-06 16:54 ` Wolfram Sang [this message]
2017-02-18 18:02 James Maki
2017-02-20 18:41 ` James Maki
-- strict thread matches above, loose matches on Subject: below --
2017-02-18 17:43 James Maki
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=20170306165454.GA2086@katana \
--to=wsa@the-dreams.de \
--cc=eric.piel@tremplin-utc.net \
--cc=jamescmaki@revolayer.com \
--cc=linux-i2c@vger.kernel.org \
/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).