From: Wolfram Sang <wsa@kernel.org>
To: Quan Nguyen <quan@os.amperecomputing.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
Thang Nguyen <thang@os.amperecomputing.com>
Subject: Re: [PATCH] docs: i2c: slave-interface: return errno when handle I2C_SLAVE_WRITE_REQUESTED
Date: Wed, 28 Sep 2022 21:41:29 +0200 [thread overview]
Message-ID: <YzSjaVQUm/B4Jtwf@shikoro> (raw)
In-Reply-To: <20220915035440.2862532-1-quan@os.amperecomputing.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
On Thu, Sep 15, 2022 at 10:54:40AM +0700, Quan Nguyen wrote:
> In case backend is not ready, ie: fail to wakeup or initialization, on
> the returning of the I2C_SLAVE_WRITE_REQUESTED event, bus driver should
> aware the backend status and might auto sending NACK on the next
> incoming bytes for I2C master to retry.
>
> Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
> Links:https://lore.kernel.org/linux-arm-kernel/556fa9e1-c54b-8370-4de7-c2d3ec7d6906@os.amperecomputing.com/
Sorry for the delay. I made some wording more precise and applied it to
for-next. So, we can use it right for next merge window, if needed.
Thank you for suggesting this and for your patience!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-28 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 3:54 [PATCH] docs: i2c: slave-interface: return errno when handle I2C_SLAVE_WRITE_REQUESTED Quan Nguyen
2022-09-28 19:41 ` Wolfram Sang [this message]
2022-09-29 8:07 ` 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=YzSjaVQUm/B4Jtwf@shikoro \
--to=wsa@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=thang@os.amperecomputing.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