From: Wolfram Sang <w.sang@pengutronix.de>
To: Sander van Ginkel <sander@van-ginkel.eu>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
shawn.guo@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH] add hardware I2C support for ARM IMX23
Date: Wed, 28 Nov 2012 18:09:07 +0100 [thread overview]
Message-ID: <20121128170907.GC4659@pengutronix.de> (raw)
In-Reply-To: <50B63F81.4050008@van-ginkel.eu>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Hi,
(adding the i2c list)
On Wed, Nov 28, 2012 at 05:44:49PM +0100, Sander van Ginkel wrote:
> tested with:
> CONFIG_I2C_MXS=m
> CONFIG_I2C_MXS=y
>
> in combination with CONFIG_GPIO_MXS enabled and disabled
>
> used kernels: 3.6 and 3.7.0-rc6
>
> My I2C slave is a PCF8575 i/o expander with some LEDs at the output.
> These are controlled through sysfs.
Thanks, this is useful info.
> Just tested with "i2cdetc -y -r 0" that crashes with "BUG: soft
> lockup - CPU#0 stuck for 22s!"
> according to the docs (IMX23RM.pdf) the interrupts for I2C are 26
> and 27 that why I assigned these two in the dts.
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/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next parent reply other threads:[~2012-11-28 17:09 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 ` Wolfram Sang [this message]
2012-11-28 17:34 ` [PATCH] add hardware I2C support for ARM IMX23 sander van ginkel
[not found] ` <20121128170907.GC4659-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-11-30 16:32 ` sander van ginkel
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=20121128170907.GC4659@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sander@van-ginkel.eu \
--cc=shawn.guo@linaro.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).