From: Wolfram Sang <wsa@the-dreams.de>
To: Kevin Herbert <kph@platinasystems.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
Biwen Li <biwen.li@nxp.com>, Leo Li <leoyang.li@nxp.com>,
linux@rempel-privat.de, kernel@pengutronix.de,
shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com,
Aisheng Dong <aisheng.dong@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiafei Pan <jiafei.pan@nxp.com>, Xiaobo Xie <xiaobo.xie@nxp.com>,
linux-arm-kernel@lists.infradead.org,
Biwen Li <biwen.li@oss.nxp.com>
Subject: Re: [PATCH] i2c-imx.c: Synthesize end of transaction events without idle interrupts
Date: Thu, 28 Jan 2021 10:20:48 +0100 [thread overview]
Message-ID: <20210128092048.GK963@ninjato> (raw)
In-Reply-To: <CABP=6zY0xV3dLE5t7qad6TauQsaLmQtYi73BS9XBHwZ2FrgM8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Thu, Jan 14, 2021 at 05:27:11PM -0800, Kevin Herbert wrote:
> The loop sends either one or two events to the slave driver. If the
> state is I2C_SLAVE_READ_REQUESTED, we synthesize the
> I2C_SLAVE_READ_PROCESSED event, and then our state becomes
> I2C_SLAVE_READ_PROCESSED. In all other states, we transition to
> I2C_SLAVE_STOP and exit the loop.
>
> It is not a busy loop at all. It is calling the callback handler (that
> already expects to be in IRQ context) one or two times, and then it
> exits the loop.
Oleksij, does this answer your question?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-28 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 19:48 [PATCH] i2c-imx.c: Synthesize end of transaction events without idle interrupts Kevin Paul Herbert
2021-01-08 8:05 ` Oleksij Rempel
2021-01-15 1:27 ` Kevin Herbert
2021-01-28 9:20 ` Wolfram Sang [this message]
2021-02-01 22:13 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2020-12-18 17:53 Kevin Herbert
2020-12-19 14:47 ` Fabio Estevam
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=20210128092048.GK963@ninjato \
--to=wsa@the-dreams.de \
--cc=aisheng.dong@nxp.com \
--cc=biwen.li@nxp.com \
--cc=biwen.li@oss.nxp.com \
--cc=festevam@gmail.com \
--cc=jiafei.pan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kph@platinasystems.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=xiaobo.xie@nxp.com \
--cc=xiaoning.wang@nxp.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;
as well as URLs for NNTP newsgroup(s).