From: Wolfram Sang <wsa@the-dreams.de>
To: Sifan Naeem <sifan.naeem@imgtec.com>
Cc: James Hogan <james.hogan@imgtec.com>,
linux-i2c@vger.kernel.org,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Ionela Voinescu <Ionela.Voinescu@imgtec.com>
Subject: Re: [PATCH v3 0/7] i2c: img-scb: fixes to support i2c on pistachio
Date: Sat, 10 Oct 2015 08:43:19 +0100 [thread overview]
Message-ID: <20151010074318.GC1619@katana> (raw)
In-Reply-To: <1441896607-16310-1-git-send-email-sifan.naeem@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
On Thu, Sep 10, 2015 at 03:50:00PM +0100, Sifan Naeem wrote:
> The following patches are required to fix the existing driver to
> support i2c on pistachio.
>
> Tested on Pistachio bub using an Adafruit I2C Non-Volatile FRAM Breakout
> (256Kbit / 32KByte) eeprom.
>
> Used i2c buildroot tools to test the eeprom and the other i2c blocks.
> Also used dd commands to copy data to and then to dump data from the
> eeprom. i2ctransfer was used to test repeated starts and verified
> using a scope.
>
> Odeally these fixes should go in to Stable kernel (v3.19+).
>
> Changes from v2:
> 5/7: Remove start bit detected not required, use line_status instead of i2c->line_status
> 7/7: use %u instead if %d for unsigned
>
> Sifan Naeem (7):
> i2c: img-scb: enable fencing for all versions of the ip
> i2c: img-scb: do dummy writes before fifo access
> i2c: img-scb: use DIV_ROUND_UP to round divisor values
> i2c: img-scb: fix LOW and HIGH period values for the SCL clock
> i2c: img-scb: use line_status instead of i2c->line_status
> i2c: img-scb: Clear line and interrupt status before starting a
> transfer
> i2c: img-scb: verify support for requested bit rate
>
> drivers/i2c/busses/i2c-img-scb.c | 73 ++++++++++++++++++++++----------------
> 1 file changed, 43 insertions(+), 30 deletions(-)
Series applied to for-next. Thanks to both James for the review!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-10-10 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 14:50 [PATCH v3 0/7] i2c: img-scb: fixes to support i2c on pistachio Sifan Naeem
[not found] ` <1441896607-16310-1-git-send-email-sifan.naeem-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2015-09-10 14:50 ` [PATCH v3 1/7] i2c: img-scb: enable fencing for all versions of the ip Sifan Naeem
2015-09-10 14:50 ` [PATCH v3 2/7] i2c: img-scb: do dummy writes before fifo access Sifan Naeem
2015-09-10 14:50 ` [PATCH v3 3/7] i2c: img-scb: use DIV_ROUND_UP to round divisor values Sifan Naeem
2015-09-10 14:50 ` [PATCH v3 4/7] i2c: img-scb: fix LOW and HIGH period values for the SCL clock Sifan Naeem
2015-09-10 14:50 ` [PATCH v3 5/7] i2c: img-scb: use line_status instead of i2c->line_status Sifan Naeem
[not found] ` <1441896607-16310-6-git-send-email-sifan.naeem-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2015-09-14 12:15 ` James Hogan
2015-09-10 14:50 ` [PATCH v3 6/7] i2c: img-scb: Clear line and interrupt status before starting a transfer Sifan Naeem
2015-09-10 14:50 ` [PATCH v3 7/7] i2c: img-scb: verify support for requested bit rate Sifan Naeem
2015-10-10 7:43 ` Wolfram Sang [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=20151010074318.GC1619@katana \
--to=wsa@the-dreams.de \
--cc=Ionela.Voinescu@imgtec.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=james.hogan@imgtec.com \
--cc=linux-i2c@vger.kernel.org \
--cc=sifan.naeem@imgtec.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 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).