From: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: [PATCH 00/14] Various updates to the Nomadik I2C controller v2
Date: Fri, 13 May 2011 12:28:48 +0200 [thread overview]
Message-ID: <1305282528-20499-1-git-send-email-linus.walleij@linaro.org> (raw)
This is an interation of the previous patch set that hopefully
adress Ben's comments: we took some runtime PM hooks out and
added a refactoring on the tail.
Actually the last patch fixing the platform config can be fed into the
I2C tree as well, if subsys maintainers are comfortable with it. I
won't be changing much stuff in the ux500 in this merge window due to
kernel consolidations taking place.
Jonas Aberg (1):
i2c/i2c-nomadik: add regulator support
Linus Walleij (3):
i2c/i2c-nomadik: fix speed enumerator
i2c/i2c-nomadik: break out single messsage transmission
mach-ux500: set proper I2C platform data from MOP500s
Rabin Vincent (1):
i2c/i2c-nomadik: use pm_runtime API
Virupax Sadashivpetimath (8):
i2c/i2c-nomadik: make i2c timeout specific per i2c bus
i2c/i2c-nomadik: corrrect returned error numbers
i2c/i2c-nomadik: correct adapter timeout initialization
i2c/i2c-nomadik: print abort cause only on abort tag
i2c/i2c-nomadik: add code to retry on timeout failure
i2c/i2c-nomadik: change the TX and RX threshold
i2c/i2c-nomadik: remove the unnecessary delay
i2c/i2c-nomadik: reset the hw after status check
srinidhi kasagar (1):
i2c/i2c-nomadik: remove the redundant error message
arch/arm/mach-ux500/board-mop500.c | 14 +-
arch/arm/plat-nomadik/include/plat/i2c.h | 8 +-
drivers/i2c/busses/i2c-nomadik.c | 276 ++++++++++++++++++++----------
3 files changed, 197 insertions(+), 101 deletions(-)
--
1.7.5.1
reply other threads:[~2011-05-13 10:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1305282528-20499-1-git-send-email-linus.walleij@linaro.org \
--to=linus.walleij-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).