From: Wolfram Sang <wsa@the-dreams.de>
To: Kevin Herbert <kph@platinasystems.com>
Cc: Biwen Li <biwen.li@oss.nxp.com>,
leoyang.li@nxp.com, linux@rempel-privat.de,
kernel@pengutronix.de, shawnguo@kernel.org,
s.hauer@pengutronix.de, festevam@gmail.com, aisheng.dong@nxp.com,
xiaoning.wang@nxp.com, o.rempel@pengutronix.de,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
jiafei.pan@nxp.com, xiaobo.xie@nxp.com,
linux-arm-kernel@lists.infradead.org, Biwen Li <biwen.li@nxp.com>
Subject: Re: [v10] i2c: imx: support slave mode for imx I2C driver
Date: Wed, 9 Dec 2020 18:09:48 +0100 [thread overview]
Message-ID: <20201209170948.GA2249@kunai> (raw)
In-Reply-To: <CABP=6zZcmsFUVwUaAH7f2-RqFHz71GLDnSfLreUo5GA3Y58HYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Kevin Herbert <kph@platinasystems.com>
Cc: aisheng.dong@nxp.com, Biwen Li <biwen.li@nxp.com>,
festevam@gmail.com, s.hauer@pengutronix.de,
linux-kernel@vger.kernel.org, Biwen Li <biwen.li@oss.nxp.com>,
linux@rempel-privat.de, o.rempel@pengutronix.de,
xiaoning.wang@nxp.com, linux-i2c@vger.kernel.org,
kernel@pengutronix.de, jiafei.pan@nxp.com, leoyang.li@nxp.com,
shawnguo@kernel.org, xiaobo.xie@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [v10] i2c: imx: support slave mode for imx I2C driver
Date: Wed, 9 Dec 2020 18:09:48 +0100 [thread overview]
Message-ID: <20201209170948.GA2249@kunai> (raw)
In-Reply-To: <CABP=6zZcmsFUVwUaAH7f2-RqFHz71GLDnSfLreUo5GA3Y58HYA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 621 bytes --]
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?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-09 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 11:32 [v10] i2c: imx: support slave mode for imx I2C driver Biwen Li
2020-11-11 11:32 ` Biwen Li
2020-11-13 13:59 ` Oleksij Rempel
2020-11-13 13:59 ` Oleksij Rempel
2020-11-30 5:26 ` Biwen Li (OSS)
2020-11-30 5:26 ` Biwen Li (OSS)
2020-12-02 15:10 ` Wolfram Sang
2020-12-02 15:10 ` Wolfram Sang
[not found] ` <CABP=6zZcmsFUVwUaAH7f2-RqFHz71GLDnSfLreUo5GA3Y58HYA@mail.gmail.com>
2020-12-09 17:09 ` Wolfram Sang [this message]
2020-12-09 17:09 ` Wolfram Sang
[not found] ` <CABP=6zbKxu7ruGRi59k8+JbX5UB9jfP=C76-Pd4Q39Mc0yOTrA@mail.gmail.com>
[not found] ` <DB6PR0401MB2438F3FF50B601295BBE7F378FCB0@DB6PR0401MB2438.eurprd04.prod.outlook.com>
2020-12-11 17:57 ` [EXT] " Kevin Herbert
2020-12-11 17:57 ` Kevin Herbert
2020-12-12 7:11 ` Oleksij Rempel
2020-12-12 7:11 ` Oleksij Rempel
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=20201209170948.GA2249@kunai \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.