From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: linux-i2c@vger.kernel.org
Subject: [PATCH 0/4] Further i2c-pxa cleanups
Date: Wed, 6 May 2020 10:28:32 +0100 [thread overview]
Message-ID: <20200506092831.GN1551@shell.armlinux.org.uk> (raw)
Hi,
This small series contains some further cleanups to i2c-pxa:
Patch 1 gets rid of the duplication between i2c_pxa_pio_xfer() and
i2c_pxa_xfer(), which are mostly identical.
Patch 2 avoids the "exhausted retries" spamming the kernel log when
running i2cdetect - this occurs when a slave does not respond. We
keep the existing behaviour for all other retries.
Patch 3 changes the kernel messages printed when timeouts happen so
they are unique - thus allowing identification of which one triggered.
Patch 4 removes an unnecessary show_state() while waiting for the
bus to become free.
drivers/i2c/busses/i2c-pxa.c | 56 +++++++++++++++++++++-----------------------
1 file changed, 27 insertions(+), 29 deletions(-)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
next reply other threads:[~2020-05-06 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 9:28 Russell King - ARM Linux admin [this message]
2020-05-06 9:29 ` [PATCH 1/4] i2c: pxa: consolidate i2c_pxa_*xfer() implementations Russell King
2020-05-11 19:59 ` Wolfram Sang
2020-05-11 20:20 ` Russell King - ARM Linux admin
2020-05-06 9:29 ` [PATCH 2/4] i2c: pxa: avoid complaints with non-responsive slaves Russell King
2020-05-06 9:29 ` [PATCH 3/4] i2c: pxa: ensure timeout messages are unique Russell King
2020-05-06 9:29 ` [PATCH 4/4] i2c: pxa: remove some unnecessary debug Russell King
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=20200506092831.GN1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-i2c@vger.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).