[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210128092048.GK963@ninjato>
Date: Thu, 28 Jan 2021 10:20:48 +0100
From: Wolfram Sang <wsa@...-dreams.de>
To: Kevin Herbert <kph@...tinasystems.com>
Cc: Oleksij Rempel <o.rempel@...gutronix.de>,
Biwen Li <biwen.li@....com>, Leo Li <leoyang.li@....com>,
linux@...pel-privat.de, kernel@...gutronix.de, shawnguo@...nel.org,
s.hauer@...gutronix.de, festevam@...il.com,
Aisheng Dong <aisheng.dong@....com>,
Clark Wang <xiaoning.wang@....com>, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, Jiafei Pan <jiafei.pan@....com>,
Xiaobo Xie <xiaobo.xie@....com>,
linux-arm-kernel@...ts.infradead.org,
Biwen Li <biwen.li@....nxp.com>
Subject: Re: [PATCH] i2c-imx.c: Synthesize end of transaction events without
idle interrupts
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?
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists