public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Jochen Friedrich <jochen-NIgtFMG+Po8@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH] Bugfixes for i2c-cpm.c
Date: Fri, 27 Jun 2008 10:40:27 +0200	[thread overview]
Message-ID: <20080627084027.GA3931@pengutronix.de> (raw)
In-Reply-To: <4864A342.4020900-NIgtFMG+Po8@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 666 bytes --]

Hi Jochen,

On Fri, Jun 27, 2008 at 10:22:26AM +0200, Jochen Friedrich wrote:

> What kind of problems have this been? In normal operation there shouldn't be
> any I2CER_TXE interrupts being generated.
I had problems when writing to an EEPROM, reading worked, though.

I didn't really investigate why this happened. I just saw that the old
version used a hardcoded 0x13 to set interrupts and the replacement
using defined constants resulted in 0x7. Changing constants to achieve
0x13 solved my problems.

All the best,

   Wolfram

-- 
  Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-06-27  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20  8:41 [PATCH] Bugfixes for i2c-cpm.c Wolfram Sang
     [not found] ` <20080620084155.GA17701-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-06-23 12:44   ` Wolfram Sang
     [not found]     ` <20080623124425.GE3926-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-06-23 13:59       ` Jean Delvare
     [not found]         ` <20080623155909.525f5095-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-23 15:07           ` Wolfram Sang
2008-06-27  8:15           ` Jochen Friedrich
2008-06-24 14:15   ` Laurent Pinchart
     [not found]     ` <200806241615.08826.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
2008-06-27  8:22       ` Jochen Friedrich
     [not found]         ` <4864A342.4020900-NIgtFMG+Po8@public.gmane.org>
2008-06-27  8:40           ` Wolfram Sang [this message]
2008-07-01 13:26           ` Laurent Pinchart
     [not found]             ` <200807011526.14514.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
2008-07-02 11:40               ` Laurent Pinchart
  -- strict thread matches above, loose matches on Subject: below --
2008-06-19 13:09 Wolfram Sang
     [not found] ` <20080619130922.GF3860-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-06-27 16:22   ` Jochen Friedrich
     [not found]     ` <486513C5.7040105-NIgtFMG+Po8@public.gmane.org>
2008-06-27 16:58       ` Wolfram Sang
     [not found]         ` <20080627165808.GE3931-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-06-27 17:06           ` Jochen Friedrich
     [not found]             ` <48651E1E.7060002-NIgtFMG+Po8@public.gmane.org>
2008-06-28  7:03               ` Jean Delvare

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=20080627084027.GA3931@pengutronix.de \
    --to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=jochen-NIgtFMG+Po8@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