[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20201209170948.GA2249@kunai>
Date: Wed, 9 Dec 2020 18:09:48 +0100
From: Wolfram Sang <wsa@...-dreams.de>
To: Kevin Herbert <kph@...tinasystems.com>
Cc: Biwen Li <biwen.li@....nxp.com>, leoyang.li@....com,
linux@...pel-privat.de, kernel@...gutronix.de, shawnguo@...nel.org,
s.hauer@...gutronix.de, festevam@...il.com, aisheng.dong@....com,
xiaoning.wang@....com, o.rempel@...gutronix.de,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
jiafei.pan@....com, xiaobo.xie@....com,
linux-arm-kernel@...ts.infradead.org, Biwen Li <biwen.li@....com>
Subject: Re: [v10] i2c: imx: support slave mode for imx I2C driver
On Wed, Dec 09, 2020 at 09:03:50AM -0800, Kevin Herbert wrote:
> What is the protocol for the I2C_SLAVE_STOP event? I am working on my own
> backend, and I've only tried it with this i.mx driver, and I do not receive
> I2C_SLAVE_STOP at the end of every I2C transaction. It was my expectation
> I'd receive this event at the end of every frame. In my testing, I've never
> received this event at all.
>
> Where are the I2C registers on the i.mx documented? My board is an i.mx6sx.
Hmm, from a glimpse, it looks the STOP event is only sent after a write
and not after a read? Does this match your findings?
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists