From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Christoph Baumann <cb-/RsSufbtIHM@public.gmane.org>,
Fabio Estevam <r49496-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Torsten Fleischer
<to-fleischer-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Subject: Re: [PATCH 2/3] i2c: mxs: Rework the PIO mode operation
Date: Thu, 18 Jul 2013 02:51:41 +0200 [thread overview]
Message-ID: <201307180251.41366.marex@denx.de> (raw)
In-Reply-To: <1374108530-7608-2-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
Dear Marek Vasut,
> Analyze and rework the PIO mode operation. The PIO mode operation
> was unreliable on MX28, by analyzing the bus with LA, the checks
> for when data were available or were to be sent were wrong.
>
> The PIO WRITE has to be completely reworked as it multiple problems.
> The MX23 datasheet helped here, see comments in the code for details.
> The problems boil down to:
> - RUN bit in CTRL0 must be set after DATA register was written
> - The PIO transfer must be 4 bytes long tops, otherwise use
> clock stretching.
> Both of these fixes are implemented.
>
> The PIO READ operation can only be done for up to four bytes as
> we are unable to read out the data from the DATA register fast
> enough.
>
> This patch also tries to document the investigation within the
> code.
>
> Signed-off-by: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
> Cc: Alexandre Belloni <alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
> Cc: Christoph Baumann <cb-/RsSufbtIHM@public.gmane.org>
> Cc: Fabio Estevam <r49496-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> Cc: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> Cc: Torsten Fleischer <to-fleischer-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org>
> Cc: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Please discard that previous submission, looks like I'm still not at home on my
new laptop and some of the email addresses got corrupted. This one shall be OK.
I appologize for the double-post.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-07-18 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 0:48 [PATCH 1/3] i2c: mxs: distinguish i.MX23 and i.MX28 based I2C controller Marek Vasut
[not found] ` <1374108530-7608-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2013-07-18 0:48 ` [PATCH 2/3] i2c: mxs: Rework the PIO mode operation Marek Vasut
[not found] ` <1374108530-7608-2-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2013-07-18 0:51 ` Marek Vasut [this message]
2013-07-18 0:48 ` [PATCH 3/3] i2c: mxs: Fix PIO mode on i.MX23 Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2013-07-18 0:46 [PATCH 1/3] i2c: mxs: distinguish i.MX23 and i.MX28 based I2C controller Marek Vasut
[not found] ` <1374108401-7439-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2013-07-18 0:46 ` [PATCH 2/3] i2c: mxs: Rework the PIO mode operation Marek Vasut
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=201307180251.41366.marex@denx.de \
--to=marex-ynqeqjnshbs@public.gmane.org \
--cc=alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=cb-/RsSufbtIHM@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=r49496-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=to-fleischer-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@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).