From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Andreas Färber" <afaerber@suse.de>,
"Wolfram Sang" <wsa@kernel.org>, "Peter Rosin" <peda@axentia.se>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-actions@lists.infradead.org
Subject: [PATCH 0/3] Improve Actions Semi Owl I2C driver
Date: Fri, 9 Oct 2020 00:44:38 +0300 [thread overview]
Message-ID: <cover.1602190168.git.cristian.ciocaltea@gmail.com> (raw)
This patchset brings a few improvements to the Actions Semiconductor
Owl I2C driver driver:
- Fixes an issue reported by Mani related to the error handling
- Adds support for atomic transfers
- Enables asynchronous probing, per Mani's suggestion
Please note the first two patches incorporate the review received for
the following patch (which became obsolete now):
https://lore.kernel.org/lkml/b6c56858854805b0f03e29b7dde40b20796d5c93.1599561278.git.cristian.ciocaltea@gmail.com/
Kind regards,
Cristi
Cristian Ciocaltea (3):
i2c: owl: Clear NACK and BUS error bits
i2c: owl: Add support for atomic transfers
i2c: owl: Enable asynchronous probing
drivers/i2c/busses/i2c-owl.c | 83 +++++++++++++++++++++++++++---------
1 file changed, 63 insertions(+), 20 deletions(-)
--
2.28.0
next reply other threads:[~2020-10-08 21:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 21:44 Cristian Ciocaltea [this message]
2020-10-08 21:44 ` [PATCH 1/3] i2c: owl: Clear NACK and BUS error bits Cristian Ciocaltea
2020-10-10 11:16 ` Wolfram Sang
2020-10-11 14:09 ` Manivannan Sadhasivam
2020-10-12 9:05 ` Cristian Ciocaltea
2020-10-08 21:44 ` [PATCH 2/3] i2c: owl: Add support for atomic transfers Cristian Ciocaltea
2020-10-11 14:09 ` Manivannan Sadhasivam
2020-10-12 9:07 ` Cristian Ciocaltea
2020-11-03 20:57 ` Wolfram Sang
2020-10-08 21:44 ` [PATCH 3/3] i2c: owl: Enable asynchronous probing Cristian Ciocaltea
2020-10-11 14:06 ` Manivannan Sadhasivam
2020-10-12 9:08 ` Cristian Ciocaltea
2020-11-03 20:57 ` Wolfram Sang
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=cover.1602190168.git.cristian.ciocaltea@gmail.com \
--to=cristian.ciocaltea@gmail.com \
--cc=afaerber@suse.de \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=peda@axentia.se \
--cc=wsa@kernel.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;
as well as URLs for NNTP newsgroup(s).