linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Jokiniemi <kalle.jokiniemi@jollamobile.com>
To: Shubhrajyoti Datta <omaplinuxkernel@gmail.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	linux-i2c@vger.kernel.org, Wolfram Sang <w.sang@pengutronix.de>,
	linux-omap@vger.kernel.org,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Shubhrajyoti Datta <shubhrajyoti@ti.com>,
	Huzefa Kankroliwala <huzefank@ti.com>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH] i2c: omap: fix spurious IRQs: disable/enable IRQ at INTC when idle
Date: Mon, 15 Oct 2012 09:25:37 +0300	[thread overview]
Message-ID: <1350282337.17145.45.camel@kj-X230> (raw)
In-Reply-To: <CAM=Q2csm0Eh9F6d1wKhEfOOtG+aY+Fh8D-dKPC0RMbKupVQHYQ@mail.gmail.com>

Hi,

la, 2012-10-13 kello 01:00 +0530, Shubhrajyoti Datta kirjoitti:
> On Sat, Oct 13, 2012 at 12:10 AM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
> > From: Kevin Hilman <khilman@ti.com>
> >
> > Currently, runtime PM is used to keep the device enabled only during
> > active transfers and for a configurable runtime PM autosuspend timout
> > after an xfer.
> >
> > In addition to idling the device, driver's ->runtime_suspend() method
> > currently disables device interrupts when idle.  However, on some SoCs
> > (notably OMAP4+), the I2C hardware may shared with other coprocessors.
> > This means that the MPU will still recieve interrupts if a coprocessor
> > is using the I2C device.  To avoid this, also disable interrupts at
> > the MPU INTC when idling the device in ->runtime_suspend() (and
> > re-enable them in ->runtime_resume().)  This part based on an original
> > patch from Shubhrajyoti Datta.  NOTE: for proper sharing the I2C with
> > a coprocessor, this driver still needs hwspinlock support added.
> >
> > This change is also meant to address an issue reported by Kalle
> > Jokiniemi where I2C bus interrupt may be enabled before an I2C device
> > interrupt handler (e.g. just after noirq resume phase) causing an

It is actually in middle of resume_noirq.

> > interrupt flood on the I2C bus interrupt before the device interrupt
> > is enabled (e.g. interrupts coming from devices on I2C connected PMIC
> > before the PMIC chained hanlder is enabled.)  This problem is addresed
> > by ensuring that the I2C bus interrupt left disabled until an I2C xfer
> > is requested.
> 
> Looks good to me.
> Will wait for Kalle though.

Does not work for me :(

As I said, the issue occurs for me when I enter static suspend (echo mem
> /sys/power/autosleep or /sys/power/state). I don't think doing this
just in runtime pm will fix my issue. Or do those handlers get run in
the normal suspend path as well?

- Kalle

> 
> >
> > Cc: Kalle Jokiniemi <kalle.jokiniemi@jollamobile.com>
> > Cc: Grygorii Strashko <grygorii.strashko@ti.com>
> > Cc: Shubhrajyoti Datta <shubhrajyoti@ti.com>,
> > Cc: Huzefa Kankroliwala <huzefank@ti.com>
> > Cc: Nishanth Menon <nm@ti.com>
> > Signed-off-by: Kevin Hilman <khilman@ti.com>
> > ---
> >  drivers/i2c/busses/i2c-omap.c |    3 +++
> >  1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
> > index db31eae..e6413e8 100644
> > --- a/drivers/i2c/busses/i2c-omap.c
> > +++ b/drivers/i2c/busses/i2c-omap.c
> > @@ -1255,6 +1255,7 @@ static int omap_i2c_runtime_suspend(struct device *dev)
> >                 /* Flush posted write */
> >                 omap_i2c_read_reg(_dev, OMAP_I2C_STAT_REG);
> >         }
> > +       disable_irq(_dev->irq);
> >
> >         return 0;
> >  }
> > @@ -1275,6 +1276,8 @@ static int omap_i2c_runtime_resume(struct device *dev)
> >                 omap_i2c_write_reg(_dev, OMAP_I2C_CON_REG, OMAP_I2C_CON_EN);
> >         }
> >
> > +       enable_irq(_dev->irq);
> > +
> >         /*
> >          * Don't write to this register if the IE state is 0 as it can
> >          * cause deadlock.
> > --
> > 1.7.9.2
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2012-10-15  6:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 18:40 [PATCH] i2c: omap: fix spurious IRQs: disable/enable IRQ at INTC when idle Kevin Hilman
     [not found] ` <1350067225-24589-1-git-send-email-khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2012-10-12 19:30   ` Shubhrajyoti Datta
2012-10-15  6:25     ` Kalle Jokiniemi [this message]
2012-10-15 17:31       ` Kevin Hilman
     [not found]         ` <87zk3ntzfe.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2012-10-16  1:02           ` Tony Lindgren
     [not found]             ` <20121016010223.GL15569-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2012-10-16  8:47               ` Kalle Jokiniemi
2012-11-01 22:49                 ` Wolfram Sang
     [not found]                   ` <20121101224921.GE22956-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-11-02  6:17                     ` Kalle Jokiniemi

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=1350282337.17145.45.camel@kj-X230 \
    --to=kalle.jokiniemi@jollamobile.com \
    --cc=grygorii.strashko@ti.com \
    --cc=huzefank@ti.com \
    --cc=kalle.jokiniemi@jolla.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=omaplinuxkernel@gmail.com \
    --cc=shubhrajyoti@ti.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 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).