linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: ben-linux@fluff.org
Cc: Tony Lindgren <tony@atomide.com>,
	w.sang@pengutronix.de,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	linux-i2c@vger.kernel.org,
	Linux ARM Kernel Mailing List
	<linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Felipe Balbi <balbi@ti.com>
Subject: [PATCH 00/17] Big OMAP I2C Cleanup
Date: Thu, 14 Jun 2012 13:20:33 +0300	[thread overview]
Message-ID: <1339669250-9183-1-git-send-email-balbi@ti.com> (raw)

Hi guys,

I have dropped a few patches from the series and also
tested every single patch on my pandaboard. I2C messages
are still working fine with panda after each patch.

There's still lots of work to be done on the i2c-omap.c
driver but it's now easier to read, IMO.

Felipe Balbi (17):
  i2c: omap: simplify num_bytes handling
  i2c: omap: decrease indentation level on data handling
  i2c: omap: add blank lines
  i2c: omap: simplify omap_i2c_ack_stat()
  i2c: omap: split out [XR]DR and [XR]RDY
  i2c: omap: improve 1p153 errata handling
  i2c: omap: re-factor receive/transmit data loop
  i2c: omap: switch over to do {} while loop
  i2c: omap: ack IRQ in parts
  i2c: omap: get rid of the "complete" label
  i2c: omap: switch to devm_* API
  i2c: omap: switch to platform_get_irq()
  i2c: omap: bus: add a receiver flag
  i2c: omap: simplify errata check
  i2c: omap: always return IRQ_HANDLED
  i2c: omap: simplify IRQ exit path
  i2c: omap: resize fifos before each message

 drivers/i2c/busses/i2c-omap.c |  388 +++++++++++++++++++++++------------------
 1 file changed, 222 insertions(+), 166 deletions(-)

-- 
1.7.10.4


             reply	other threads:[~2012-06-14 10:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 10:20 Felipe Balbi [this message]
2012-06-14 10:20 ` [PATCH 01/17] i2c: omap: simplify num_bytes handling Felipe Balbi
     [not found]   ` <1339669250-9183-2-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-06-14 10:33     ` Shilimkar, Santosh
2012-06-14 10:20 ` [PATCH 02/17] i2c: omap: decrease indentation level on data handling Felipe Balbi
     [not found]   ` <1339669250-9183-3-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-06-14 10:41     ` Shilimkar, Santosh
2012-06-14 10:40       ` Felipe Balbi
2012-06-14 10:20 ` [PATCH 03/17] i2c: omap: add blank lines Felipe Balbi
     [not found]   ` <1339669250-9183-4-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-06-14 10:43     ` Shilimkar, Santosh
2012-06-14 10:20 ` [PATCH 05/17] i2c: omap: split out [XR]DR and [XR]RDY Felipe Balbi
2012-06-14 10:20 ` [PATCH 07/17] i2c: omap: re-factor receive/transmit data loop Felipe Balbi
2012-06-14 10:20 ` [PATCH 09/17] i2c: omap: ack IRQ in parts Felipe Balbi
2012-06-14 11:11   ` Shilimkar, Santosh
2012-06-14 11:46     ` Felipe Balbi
2012-06-14 11:20   ` Russell King - ARM Linux
     [not found]     ` <20120614112017.GC31187-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-06-14 11:47       ` Felipe Balbi
2012-06-14 10:20 ` [PATCH 10/17] i2c: omap: get rid of the "complete" label Felipe Balbi
2012-06-14 10:20 ` [PATCH 11/17] i2c: omap: switch to devm_* API Felipe Balbi
2012-06-14 10:20 ` [PATCH 12/17] i2c: omap: switch to platform_get_irq() Felipe Balbi
2012-06-14 10:20 ` [PATCH 14/17] i2c: omap: simplify errata check Felipe Balbi
2012-06-14 10:20 ` [PATCH 15/17] i2c: omap: always return IRQ_HANDLED Felipe Balbi
     [not found]   ` <1339669250-9183-16-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-06-14 11:18     ` Shilimkar, Santosh
2012-06-14 11:23       ` Russell King - ARM Linux
     [not found]         ` <20120614112323.GD31187-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-06-14 11:25           ` Shilimkar, Santosh
     [not found] ` <1339669250-9183-1-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-06-14 10:20   ` [PATCH 04/17] i2c: omap: simplify omap_i2c_ack_stat() Felipe Balbi
     [not found]     ` <1339669250-9183-5-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-06-14 10:45       ` Shilimkar, Santosh
2012-06-14 11:13     ` Russell King - ARM Linux
2012-06-14 11:45       ` Felipe Balbi
2012-06-14 10:20   ` [PATCH 06/17] i2c: omap: improve 1p153 errata handling Felipe Balbi
2012-06-14 11:01     ` Shilimkar, Santosh
2012-06-14 11:17     ` Russell King - ARM Linux
     [not found]       ` <20120614111746.GB31187-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-06-14 11:48         ` Felipe Balbi
2012-06-14 10:20   ` [PATCH 08/17] i2c: omap: switch over to do {} while loop Felipe Balbi
     [not found]     ` <1339669250-9183-9-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-06-14 11:03       ` Shilimkar, Santosh
2012-06-14 11:05         ` Felipe Balbi
2012-06-14 10:20   ` [PATCH 13/17] i2c: omap: bus: add a receiver flag Felipe Balbi
2012-06-14 10:20   ` [PATCH 16/17] i2c: omap: simplify IRQ exit path Felipe Balbi
2012-06-14 11:23   ` [PATCH 00/17] Big OMAP I2C Cleanup Shilimkar, Santosh
2012-06-14 10:20 ` [PATCH 17/17] i2c: omap: resize fifos before each message Felipe Balbi

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=1339669250-9183-1-git-send-email-balbi@ti.com \
    --to=balbi@ti.com \
    --cc=ben-linux@fluff.org \
    --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=tony@atomide.com \
    --cc=w.sang@pengutronix.de \
    /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).