From: Wolfram Sang <wsa@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v7 3/3] i2c: aspeed: Assert NAK when slave is busy
Date: Sat, 14 May 2022 16:31:28 +0200 [thread overview]
Message-ID: <Yn+9QBoPdH8fMm/m@shikoro> (raw)
In-Reply-To: <20220422040803.2524940-4-quan@os.amperecomputing.com>
On Fri, Apr 22, 2022 at 11:08:03AM +0700, Quan Nguyen wrote:
> When processing I2C_SLAVE_WRITE_REQUESTED event, if slave returns
> -EBUSY, i2c controller should issue RxCmdLast command to assert NAK
> on the bus.
That should be I2C_SLAVE_WRITE_RECEIVED and it should be NAKed on all
errnos. Have you tested it?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/linux-aspeed/attachments/20220514/72da26af/attachment.sig>
next prev parent reply other threads:[~2022-05-14 14:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 4:08 [PATCH v7 0/3] Add SSIF BMC driver Quan Nguyen
2022-04-22 4:08 ` [PATCH v7 1/3] ipmi: ssif_bmc: " Quan Nguyen
2022-04-22 4:16 ` Quan Nguyen
2022-04-23 1:51 ` Corey Minyard
2022-05-04 6:45 ` Quan Nguyen
2022-05-04 12:06 ` [Openipmi-developer] " Corey Minyard
2022-06-01 8:23 ` Quan Nguyen
2022-06-02 0:32 ` Corey Minyard
2022-06-02 9:38 ` Quan Nguyen
2022-04-22 4:08 ` [PATCH v7 2/3] bindings: ipmi: Add binding for " Quan Nguyen
2022-04-22 4:16 ` Quan Nguyen
2022-04-22 7:21 ` Krzysztof Kozlowski
2022-04-22 7:56 ` Quan Nguyen
2022-04-25 21:39 ` Rob Herring
2022-04-22 4:08 ` [PATCH v7 3/3] i2c: aspeed: Assert NAK when slave is busy Quan Nguyen
2022-04-22 4:17 ` Quan Nguyen
2022-05-14 14:31 ` Wolfram Sang [this message]
2022-05-16 2:32 ` Quan Nguyen
2022-06-15 20:32 ` Wolfram Sang
2022-06-16 7:16 ` Quan Nguyen
2022-06-16 12:29 ` Wolfram Sang
2022-06-17 7:08 ` Quan Nguyen
2022-07-05 2:45 ` Quan Nguyen
2022-04-22 4:16 ` [PATCH v7 0/3] Add SSIF BMC driver Quan Nguyen
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=Yn+9QBoPdH8fMm/m@shikoro \
--to=wsa@kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
/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