public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivo Manca <pinkel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Hans de Goede <j.w.r.degoede-fbo2DhPpy/Q@public.gmane.org>,
	i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH][RESEND] i2c-i801: Add basic interrupt support
Date: Wed, 20 Aug 2008 06:53:48 +0200	[thread overview]
Message-ID: <48ABA35C.50404@gmail.com> (raw)
In-Reply-To: <20080816203347.0af81c5b-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

Hey Jean,

Jean Delvare wrote:
>>> OK, I see what's going on. On this laptop, IRQ 9 is used by many
>>> things, not just SMBus. So the interrupt handler keeps being called even
>>> without SMBus activity or with polled-based SMBus activity. That's what
>>> happens during SMBus block transactions: the interrupt handler is
>>> called but not for us. However the interrupt handler thinks it is
>>> called by us and clears the status register value. This causes the
>>> polled-based loop to wait forever: by the time it looks for the status
>>> register value, it has been cleared.
>>>
>>> So we need to change the code in either of three ways:
>>> * Drop support for byte-by-byte block transactions.
>>> * Inhibit the interrupt handler during polled-based block transactions.
>>> * Convert the byteb-by-byte block transaction code to use interrupts
>>>   instead of polling.
>>> The latter would be cleaner, but that's also more work.
>>>       
I tried monday to add interrupt support to the byte-by-byte block 
transactions, but it's not working yet. Keeps messing up (and eventually 
crashing) my I2C bus.

>> Erm, is this testing with or without your merging of the status flags defines? 
>> Maybe that is causing this?
>>     
>
> This is indeed with my merging of the status flag defines. But the
> problem would happen regardless: the interrupt handler resets all the
> status flags if any flag of I801_HST_STS_MASK_ALL, not just
> I801_HST_STS_MASK_NORM, is set.
>
> You might argue that the interrupt handler could be modified to only
> reset the flags it knows about, i.e. I801_HST_STS_MASK_NORM. This is
> probably correct, but even then, it doesn't feel safe to have an
> interrupt handler triggered while poll-based code operated on the same
> register values
True, it shouldn't happen. However, always only resetting flags it knows 
about seems to make sense in every case, or not?

Not sure when i'll have some more time to look into it though...

Ivo

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

  parent reply	other threads:[~2008-08-20  4:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 20:05 [PATCH][RESEND] i2c-i801: Add basic interrupt support Ivo Manca
     [not found] ` <48A33E77.7060502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-08-16 13:58   ` Jean Delvare
     [not found]     ` <20080816155856.2e0bcf4c-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-16 16:22       ` Ivo Manca
     [not found]         ` <48A6FECC.8020801-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-08-16 16:50           ` Jean Delvare
     [not found]             ` <20080816185013.30fcf4ee-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-16 17:41               ` Jean Delvare
     [not found]                 ` <20080816194147.7c0a11dc-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-16 18:01                   ` Hans de Goede
     [not found]                     ` <48A715FE.80802-fbo2DhPpy/Q@public.gmane.org>
2008-08-16 18:33                       ` Jean Delvare
     [not found]                         ` <20080816203347.0af81c5b-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-20  4:53                           ` Ivo Manca [this message]
     [not found]                             ` <48ABA35C.50404-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-08-23  8:11                               ` 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=48ABA35C.50404@gmail.com \
    --to=pinkel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=j.w.r.degoede-fbo2DhPpy/Q@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@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