linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Kurtz <djkurtz-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2] i2c-i801: Enable interrupts for all post-ICH5 chips
Date: Thu, 13 Dec 2012 09:53:10 +0800	[thread overview]
Message-ID: <CAGS+omCzK2mj6EsCQo1q4MRFHghMzWNfHZmn3DjZuPLfDkoZXg@mail.gmail.com> (raw)
In-Reply-To: <20121106203803.6af84fc8-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>

Hi Jean,

On Wed, Nov 7, 2012 at 3:38 AM, Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> wrote:
> I did not receive a single bug report after interrupt support was
> added for a limited number of chips. So I'd say the code is good and
> should be enabled for all supported chips, that is: ICH5 and later.
>
> Signed-off-by: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
> Cc: Daniel Kurtz <djkurtz-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> ---
> I was able to test on Patsburg IDF channels and although I couldn't
> test all transaction types, interrupts seem to work the same as on the
> main SMBus channel so let's enable interrupts there too.


I can confirm that the IRQ works on PantherPoint at least, if enabled
(by this patch, for example).  However, I don't know anything about
IDF, so I can't help there.
Here's an R-B, if you need it:

Reviewed-by: Daniel Kurtz <djkurtz-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>

Are you targeting this for 3.8?

>
>  drivers/i2c/busses/i2c-i801.c |   11 +----------
>  1 file changed, 1 insertion(+), 10 deletions(-)
>
> --- linux-3.7-rc4.orig/drivers/i2c/busses/i2c-i801.c    2012-11-05 16:55:23.271739149 +0100
> +++ linux-3.7-rc4/drivers/i2c/busses/i2c-i801.c 2012-11-06 19:26:04.073280924 +0100
> @@ -1109,6 +1109,7 @@ static int __devinit i801_probe(struct p
>                 /* fall through */
>         default:
>                 priv->features |= FEATURE_I2C_BLOCK_READ;
> +               priv->features |= FEATURE_IRQ;
>                 /* fall through */
>         case PCI_DEVICE_ID_INTEL_82801DB_3:
>                 priv->features |= FEATURE_SMBUS_PEC;
> @@ -1121,16 +1122,6 @@ static int __devinit i801_probe(struct p
>                 break;
>         }
>
> -       /* IRQ processing tested on CougarPoint PCH, ICH5, ICH7-M and ICH10 */
> -       if (dev->device == PCI_DEVICE_ID_INTEL_COUGARPOINT_SMBUS ||
> -           dev->device == PCI_DEVICE_ID_INTEL_82801EB_3 ||
> -           dev->device == PCI_DEVICE_ID_INTEL_ICH7_17 ||
> -           dev->device == PCI_DEVICE_ID_INTEL_ICH8_5 ||
> -           dev->device == PCI_DEVICE_ID_INTEL_ICH9_6 ||
> -           dev->device == PCI_DEVICE_ID_INTEL_ICH10_4 ||
> -           dev->device == PCI_DEVICE_ID_INTEL_ICH10_5)
> -               priv->features |= FEATURE_IRQ;
> -
>         /* Disable features on user request */
>         for (i = 0; i < ARRAY_SIZE(i801_feature_names); i++) {
>                 if (priv->features & disable_features & (1 << i))
>
> --
> Jean Delvare

  parent reply	other threads:[~2012-12-13  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 11:03 [PATCH] i2c-i801: Enable interrupts for all post-ICH5 chips Jean Delvare
     [not found] ` <20121031120336.3229e1a2-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-11-06 19:38   ` [PATCH v2] " Jean Delvare
     [not found]     ` <20121106203803.6af84fc8-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-12-13  1:53       ` Daniel Kurtz [this message]
     [not found]         ` <CAGS+omCzK2mj6EsCQo1q4MRFHghMzWNfHZmn3DjZuPLfDkoZXg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-15 13:41           ` 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=CAGS+omCzK2mj6EsCQo1q4MRFHghMzWNfHZmn3DjZuPLfDkoZXg@mail.gmail.com \
    --to=djkurtz-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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).