From: "Jayachandran C" <jayachandranc-oSioyQM9ZPnuBjGU1YDckgC/G2K4zDHf@public.gmane.org>
To: w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org,
richard.rojfors-gfIc91nka+FZroRs9YW3xA@public.gmane.org
Cc: Jayachandran C
<jayachandranc-oSioyQM9ZPnuBjGU1YDckgC/G2K4zDHf@public.gmane.org>
Subject: [PATCH RESEND 0/4] I2C Ocores updates
Date: Tue, 10 Jul 2012 11:40:54 +0530 [thread overview]
Message-ID: <1341900658-7698-1-git-send-email-jayachandranc@netlogicmicro.com> (raw)
[Sending this out again - the changes are straight-forward and I
do not see any reason for not merging them. Comments welcome]
While trying to add reg-io-width property to i2c-ocores, we noticed
a few things that needs to fixed up in i2c-ocores device tree code.
The changes are to:
* use the standard 'reg-shift' property instead of 'regstep'
* fix the fallout of the about change in drivers/mfd/timberdale.c
* move bindings documentation to under Documentation/,
* fix up formatting, and add \n to a few dev_* messages,
* and finally to add reg-io-width optional property.
Regards,
JC.
Ganesan Ramalingam (2):
i2c: i2c-ocores: Use reg-shift property
i2c: i2c-ocores: support for 16bit and 32bit IO
Jayachandran C (2):
i2c: i2c-ocores - DT bindings and minor fixes.
V4L/DVB: mfd: use reg_shift instead of regstep
.../devicetree/bindings/i2c/i2c-ocores.txt | 33 +++++++
drivers/i2c/busses/i2c-ocores.c | 96 +++++++++-----------
drivers/mfd/timberdale.c | 2 +-
include/linux/i2c-ocores.h | 7 +-
4 files changed, 83 insertions(+), 55 deletions(-)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-ocores.txt
--
1.7.9.5
next reply other threads:[~2012-07-10 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 6:10 Jayachandran C [this message]
[not found] ` <1341900658-7698-1-git-send-email-jayachandranc-oSioyQM9ZPnuBjGU1YDckgC/G2K4zDHf@public.gmane.org>
2012-07-10 6:10 ` [PATCH 1/4] i2c: i2c-ocores - DT bindings and minor fixes Jayachandran C
2012-07-10 6:10 ` [PATCH 2/4] i2c: i2c-ocores: Use reg-shift property Jayachandran C
[not found] ` <1341900658-7698-3-git-send-email-jayachandranc-oSioyQM9ZPnuBjGU1YDckgC/G2K4zDHf@public.gmane.org>
2012-07-12 13:31 ` Wolfram Sang
[not found] ` <20120712133157.GI2194-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-07-12 14:02 ` Jayachandran C.
2012-07-10 6:10 ` [PATCH 3/4] V4L/DVB: mfd: use reg_shift instead of regstep Jayachandran C
[not found] ` <1341900658-7698-4-git-send-email-jayachandranc-oSioyQM9ZPnuBjGU1YDckgC/G2K4zDHf@public.gmane.org>
2012-07-11 21:09 ` Richard Röjfors
2012-07-12 13:34 ` Wolfram Sang
2012-07-10 6:10 ` [PATCH 4/4] i2c: i2c-ocores: support for 16bit and 32bit IO Jayachandran C
[not found] ` <1341900658-7698-5-git-send-email-jayachandranc-oSioyQM9ZPnuBjGU1YDckgC/G2K4zDHf@public.gmane.org>
2012-07-12 13:35 ` 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=1341900658-7698-1-git-send-email-jayachandranc@netlogicmicro.com \
--to=jayachandranc-osioyqm9zpnubjgu1ydckgc/g2k4zdhf@public.gmane.org \
--cc=jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=richard.rojfors-gfIc91nka+FZroRs9YW3xA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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).