From: Wolfram Sang <wsa@the-dreams.de>
To: Kevin Paul Herbert <kph@platinasystems.com>
Cc: biwen.li@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@oss.nxp.com
Subject: Re: [PATCH] i2c-imx.c: Synthesize end of transaction events without idle interrupts
Date: Mon, 1 Feb 2021 23:13:51 +0100 [thread overview]
Message-ID: <20210201221351.GG24315@kunai> (raw)
In-Reply-To: <20201222194850.2274527-1-kph@platinasystems.com>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
On Tue, Dec 22, 2020 at 11:48:50AM -0800, Kevin Paul Herbert wrote:
> Only the Layerscape SoCs have interrupts on bus idle, which facilitate
> sending events which complete slave bus transactions.
>
> Add support for synthesizing missing events. If we see a master request,
> or a newly addressed slave request, if the last event sent to the backend
> was I2C_SLAVE_READ_REQUESTED, send the backend a I2C_SLAVE_READ_PROCESSED
> followed by I2C_SLAVE_STOP. For all other events, send an I2C_SLAVE_STOP.
>
> Signed-off-by: Kevin Paul Herbert <kph@platinasystems.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-01 22:14 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
2021-02-01 22:13 ` Wolfram Sang [this message]
-- 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=20210201221351.GG24315@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 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).