From: Jochen Friedrich <jochen@scram.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Kumar Gala <galak@kernel.crashing.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
"Kernel, Linux" <linux-kernel@vger.kernel.org>,
Scott Wood <scottwood@freescale.com>,
Linux I2C <i2c@lm-sensors.org>
Subject: Re: [i2c] [PATCH6/7] i2c: adds support for i2c bus on Freescale CPM1/CPM2 controllers
Date: Tue, 06 May 2008 17:19:39 +0200 [thread overview]
Message-ID: <4820770B.1010002@scram.de> (raw)
In-Reply-To: <20080506135113.GA4265@pengutronix.de>
Hi Wolfram,
>> + /* Begin transmission */
>> + setbits8(&i2c_reg->i2com, 0x80);
> Hardcoded value. (I also wonder if 0x81 might be more suitable, as it
> keeps the "be-a-master"-bit set. Still, both values work with my setup.)
>> +#ifdef I2C_CHIP_ERRATA
>> + /*
>> + * Chip errata, clear enable. This is not needed on rev D4 CPUs.
>> + * Disabling I2C too early may cause too short stop condition
>> + */
>> + udelay(4);
>> + clrbits8(&i2c_reg->i2mod, 1);
> I was unable to find the corresponding errata document, still I wonder
> if it is a 0 which should have been written? The text says "clear" and
> according to the reference manual, this means the bit should be 0.
setbits8() and clrbits8() use a bitmask as second argument.
setbits8(&i2c_reg->i2com, 0x80) will set bit 7 on the i2com register but
leave bit 0 untouched. Likewise, clrbits8(&i2c_reg->i2mod, 1) will clear bit 0.
Thanks,
Jochen
WARNING: multiple messages have this Message-ID (diff)
From: Jochen Friedrich <jochen@scram.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Linux I2C <i2c@lm-sensors.org>,
"Kernel, Linux" <linux-kernel@vger.kernel.org>
Subject: Re: [i2c] [PATCH6/7] i2c: adds support for i2c bus on Freescale CPM1/CPM2 controllers
Date: Tue, 06 May 2008 17:19:39 +0200 [thread overview]
Message-ID: <4820770B.1010002@scram.de> (raw)
In-Reply-To: <20080506135113.GA4265@pengutronix.de>
Hi Wolfram,
>> + /* Begin transmission */
>> + setbits8(&i2c_reg->i2com, 0x80);
> Hardcoded value. (I also wonder if 0x81 might be more suitable, as it
> keeps the "be-a-master"-bit set. Still, both values work with my setup.)
>> +#ifdef I2C_CHIP_ERRATA
>> + /*
>> + * Chip errata, clear enable. This is not needed on rev D4 CPUs.
>> + * Disabling I2C too early may cause too short stop condition
>> + */
>> + udelay(4);
>> + clrbits8(&i2c_reg->i2mod, 1);
> I was unable to find the corresponding errata document, still I wonder
> if it is a 0 which should have been written? The text says "clear" and
> according to the reference manual, this means the bit should be 0.
setbits8() and clrbits8() use a bitmask as second argument.
setbits8(&i2c_reg->i2com, 0x80) will set bit 7 on the i2com register but
leave bit 0 untouched. Likewise, clrbits8(&i2c_reg->i2mod, 1) will clear bit 0.
Thanks,
Jochen
next prev parent reply other threads:[~2008-05-06 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 14:11 [PATCH6/7] i2c: adds support for i2c bus on Freescale CPM1/CPM2 controllers Jochen Friedrich
2008-04-11 14:11 ` Jochen Friedrich
2008-05-06 13:51 ` [i2c] " Wolfram Sang
2008-05-06 13:51 ` Wolfram Sang
2008-05-06 13:51 ` Wolfram Sang
2008-05-06 15:19 ` Jochen Friedrich [this message]
2008-05-06 15:19 ` Jochen Friedrich
2008-05-06 15:40 ` Wolfram Sang
2008-05-06 15:40 ` 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=4820770B.1010002@scram.de \
--to=jochen@scram.de \
--cc=galak@kernel.crashing.org \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=w.sang@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.