From: Wolfram Sang <wsa@the-dreams.de>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 00/12] i2c-pxa cleanups
Date: Wed, 29 Apr 2020 00:06:16 +0200 [thread overview]
Message-ID: <20200428220616.GA7698@kunai> (raw)
In-Reply-To: <20200427184658.GM25745@shell.armlinux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]
On Mon, Apr 27, 2020 at 07:46:58PM +0100, Russell King - ARM Linux admin wrote:
> Hi,
>
> This series cleans up the i2c-pxa code via the following changes:
>
> 1. replace i2c_pxa_addr_byte() with the functional equivalent
> i2c_8bit_addr_from_msg().
>
> 2. removing unnecessary headers, and rearranging those that remain
> in alphabetical order.
>
> 3. rearranging functions in the file to flow better; particularly
> placing the PIO specific functions next to the PIO algorithm
> structure, so all the PIO mode related code is together. This
> eliminates the forward declaration of i2c_pxa_handler().
>
> 4. group the register bitfield definitions, which were split over two
> separate locations in the file, into a single location, and add
> some definitions for the IBMR register.
>
> 5. always set the 'fm' and 'hs' members for each hardware type; the
> storage for these members is always allocated, we don't need to
> bloat the code (neither runtime, nor in the source) for this.
>
> 6. move definitions private to i2c-pxa out of the platform data
> header; platforms have no business knowing these details.
>
> 7. group all driver-based IDs match (platform and OF) to one common
> location rather than at either end of the file.
>
> 8. fix i2c_pxa_scream_blue_murder()'s log output to be printed on a
> single line as it was intended, rather than being printed one
> entry per line - which makes it difficult to read particularly
> when it has been enabled and you're getting lots of them. Also
> fix decode_bits() output in the same way.
>
> 9. fix i2c_pxa_wait_bus_not_busy() boundary condition, so that a
> coincidental success and timeout results in the function being
> successful rather than failing. (This has never been seen in
> practice, but was spotted while reviewing the code.)
>
> All in all, these changes should have (and have had so far) no
> observable impact on the driver; therefore, I do not see any reason
> to backport any of these changes to stable trees.
>
> This series has been rebased on the linux-i2c for-next branch.
Applied all to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-28 22:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 18:46 [PATCH v2 00/12] i2c-pxa cleanups Russell King - ARM Linux admin
2020-04-27 18:48 ` [PATCH v2 01/12] i2c: pxa: use official address byte helper Russell King
2020-04-27 18:48 ` [PATCH v2 02/12] i2c: pxa: remove unneeded includes Russell King
2020-04-27 18:48 ` [PATCH v2 03/12] i2c: pxa: re-arrange includes to be in alphabetical order Russell King
2020-04-27 18:48 ` [PATCH v2 04/12] i2c: pxa: re-arrange functions to flow better Russell King
2020-04-27 18:48 ` [PATCH v2 05/12] i2c: pxa: re-arrange register field definitions Russell King
2020-04-27 18:49 ` [PATCH v2 06/12] i2c: pxa: add and use definitions for IBMR register Russell King
2020-04-27 18:49 ` [PATCH v2 07/12] i2c: pxa: always set fm and hs members for each type Russell King
2020-04-27 18:49 ` [PATCH v2 08/12] i2c: pxa: move private definitions to i2c-pxa.c Russell King
2020-04-27 18:49 ` [PATCH v2 09/12] i2c: pxa: move DT IDs along side platform IDs Russell King
2020-04-27 18:49 ` [PATCH v2 10/12] i2c: pxa: fix i2c_pxa_scream_blue_murder() debug output Russell King
2020-04-27 18:49 ` [PATCH v2 11/12] i2c: pxa: clean up decode_bits() Russell King
2020-04-27 18:49 ` [PATCH v2 12/12] i2c: pxa: fix i2c_pxa_wait_bus_not_busy() boundary condition Russell King
2020-04-28 22:06 ` Wolfram Sang [this message]
2020-05-05 12:02 ` [PATCH v2 00/12] i2c-pxa cleanups Russell King - ARM Linux admin
2020-05-05 13:00 ` 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=20200428220616.GA7698@kunai \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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