All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: Tony Lindgren <tony@atomide.com>, Vignesh R <vigneshr@ti.com>,
	"Andreas Kemnade" <andreas@kemnade.info>,
	Kevin Hilman <khilman@baylibre.com>,
	"Roger Quadros" <rogerq@kernel.org>,
	Andi Shyti <andi.shyti@kernel.org>
Cc: <linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [uL RFC PATCH v3 0/8] OMAP I2C driver cleanups
Date: Wed, 30 Sep 2026 17:37:12 -0500	[thread overview]
Message-ID: <8cc00d08-b13f-491a-a986-a2030820c577@ti.com> (raw)
In-Reply-To: <20260930223503.616776-1-afd@ti.com>

On 9/30/26 5:34 PM, Andrew Davis wrote:
> Hello all,
> 
> Some hopefully simple cleanups and updates found while using this driver
> as reference when porting the same over to Zephyr. No functional changes.
> 
> Thanks,
> Andrew
> 

Just noticed this was sent with the wrong tag, not an RFC, let me
know if this needs resent with just [PATCH v3] or if your tooling
can handle it the same.

Andrew

> Changes for v3:
>   - Fix OMAP_I2C_STAT_REG value in [1/8] (Sashiko)
>   - Add Acked-by tag
> 
> Changes for v2:
>   - Seems bitfield.h is not indirectly included for all archs, include
>     it explicitly in patch [8/8]
>   - Add Reviewed-by tags
> 
> Andrew Davis (8):
>    i2c: omap: Drop bit shift for I2C register addresses
>    i2c: omap: Remove unused is_rdr and is_xdr variables
>    i2c: omap: Use devm_pm_runtime_enable() helper
>    i2c: omap: Combine event flags register definitions
>    i2c: omap: Use bool for flag values
>    i2c: omap: Make reset bit name match register name
>    i2c: omap: Switch to using BIT and GENMASK
>    i2c: omap: Add OMAP_I2C_BUF_{TX,RX}TRSH definitions
> 
>   arch/arm/mach-omap1/i2c.c              |   4 -
>   drivers/i2c/busses/i2c-omap.c          | 255 +++++++++++--------------
>   include/linux/platform_data/i2c-omap.h |   5 -
>   3 files changed, 113 insertions(+), 151 deletions(-)
> 


      parent reply	other threads:[~2026-09-30 22:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 22:34 [uL RFC PATCH v3 0/8] OMAP I2C driver cleanups Andrew Davis
2026-09-30 22:34 ` [uL RFC PATCH v3 1/8] i2c: omap: Drop bit shift for I2C register addresses Andrew Davis
2026-09-30 22:34 ` [uL RFC PATCH v3 2/8] i2c: omap: Remove unused is_rdr and is_xdr variables Andrew Davis
2026-09-30 22:34 ` [uL RFC PATCH v3 3/8] i2c: omap: Use devm_pm_runtime_enable() helper Andrew Davis
2026-09-30 22:34 ` [uL RFC PATCH v3 4/8] i2c: omap: Combine event flags register definitions Andrew Davis
2026-09-30 22:35 ` [uL RFC PATCH v3 5/8] i2c: omap: Use bool for flag values Andrew Davis
2026-09-30 22:35 ` [uL RFC PATCH v3 6/8] i2c: omap: Make reset bit name match register name Andrew Davis
2026-09-30 22:35 ` [uL RFC PATCH v3 7/8] i2c: omap: Switch to using BIT and GENMASK Andrew Davis
2026-09-30 22:35 ` [uL RFC PATCH v3 8/8] i2c: omap: Add OMAP_I2C_BUF_{TX,RX}TRSH definitions Andrew Davis
2026-09-30 22:37 ` Andrew Davis [this message]

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=8cc00d08-b13f-491a-a986-a2030820c577@ti.com \
    --to=afd@ti.com \
    --cc=andi.shyti@kernel.org \
    --cc=andreas@kemnade.info \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.com \
    --cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.