From: "sander van ginkel" <sander-fTxOWN6e5APJxEgaCYcSJA@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] add hardware I2C support for ARM IMX23
Date: Fri, 30 Nov 2012 17:32:24 +0100 [thread overview]
Message-ID: <20121130173224.10203ha9fee3y36g@62.129.139.42> (raw)
In-Reply-To: <20121128170907.GC4659-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
> You might want to try my for-next branch or wait for 3.8-rc1, maybe
the
> DMA termination patch helps? Also enabling I2C debug messages is
> probably worth it.
>
> Regards,
>
> Wolfram
>
> --
> Pengutronix e.K. | Wolfram Sang
|
> Industrial Linux Solutions |
http://www.pengutronix.de/ |
>
I've tested your git tree, with the same config as I used for the
3.7.0-rc6 release (IMX i2c build in)
It's not a 100% fix
If I do "i2cdetect -y -r 0" with 3.7.0-rc6, i2cdetect gets confused
and the kernel keeps dumping "mxs-i2c 80058000.i2c: Failed to get PIO
reg. write descriptor."
If I do the same with your git release I get the same result, but only
when i2cdetect is running. When it's finished or I terminate, the
kprint will also disappear.
So there is some improvement but not 100% yet.
prev parent reply other threads:[~2012-11-30 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121128152403.45224dvyaufb1j7n@62.129.139.42>
[not found] ` <20121128150851.GA4659@pengutronix.de>
[not found] ` <20121128171039.14705ltphptrp5kv@62.129.139.42>
[not found] ` <20121128162452.GB4659@pengutronix.de>
[not found] ` <50B63F81.4050008@van-ginkel.eu>
2012-11-28 17:09 ` [PATCH] add hardware I2C support for ARM IMX23 Wolfram Sang
2012-11-28 17:34 ` sander van ginkel
[not found] ` <20121128170907.GC4659-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-11-30 16:32 ` sander van ginkel [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=20121130173224.10203ha9fee3y36g@62.129.139.42 \
--to=sander-ftxown6e5apjxegacycsja@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@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).