All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary King <GKing@nvidia.com>
To: Mike Rapoport <mike@compulab.co.il>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mfd: tps6586x: add basic interrupt support
Date: Mon, 13 Sep 2010 18:24:38 -0700	[thread overview]
Message-ID: <4C8ECED6.9030209@nvidia.com> (raw)
In-Reply-To: <4C8C88DD.5070406@compulab.co.il>



On 09/12/2010 01:01 AM, Mike Rapoport wrote:
>
> Hi Gary,
>
> Gary King wrote:
> > Hi Samuel, Mike,
> >
> > This patch incorporates Mike Rapoport's feedback on my initial patch
> > to add interrupt support to the tps6586x driver.
>
> Overall looks good to me, two nitpicking comments though.
>
> > Changes since v1:
> >
> > * Move the interrupt enum ordering to match the ACK register values
> >
> > * Treat the INT_ACK registers as a single 32b unsigned int.
> >
> > * Name and define all the interrupts on the device
> >
> > * If reading the ACK registers in the interrupt thread fails, IRQ_NONE
> >   is returned, rather than disabling the IRQ handler. This fixes
> >   interrupts following suspend.
> >
> > * The cascaded IRQ is passed through the i2c_client's .irq field, rather
> >   than through platform data.
> >
> > --
> > From bf2f95da6f192e091d9ac0b30c186050aa5fd4e5 Mon Sep 17 00:00:00 2001
> > From: Gary King <gking@nvidia.com>
> > Date: Mon, 30 Aug 2010 16:16:55 -0700
> > Subject: mfd: tps6586x: add basic interrupt support
> >
> > add support for enabling and disabling tps6586x subdevice interrupts,
> > and add support for the RTC interrupts
>
> I think the "add support for the RTC interrupts" is not relevant anymore
>

Oops, I meant to delete that.

> > Signed-off-by: Gary King <gking@nvidia.com>
> > ---
> >  drivers/mfd/tps6586x.c       |  202 
> ++++++++++++++++++++++++++++++++++++++++++
> >  include/linux/mfd/tps6586x.h |   31 +++++++
> >  2 files changed, 233 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/mfd/tps6586x.c b/drivers/mfd/tps6586x.c
> > index 4cde31e..626081c 100644
> > --- a/drivers/mfd/tps6586x.c
> > +++ b/drivers/mfd/tps6586x.c
> > @@ -15,6 +15,8 @@
> >   * published by the Free Software Foundation.
> >   */
> >
> > +#include <linux/interrupt.h>
> > +#include <linux/irq.h>
> >  #include <linux/kernel.h>
> >  #include <linux/module.h>
> >  #include <linux/mutex.h>
>
> [ snip ]
>
> >  struct tps6586x_subdev_info {
> >       int             id;
> >       const char      *name;
> > @@ -29,6 +59,7 @@ struct tps6586x_platform_data {
> >       struct tps6586x_subdev_info *subdevs;
> >
> >       int gpio_base;
> > +     int irq_base;
>
> not needed anymore
>

This is still used; it is passed as the irq_base parameter to 
tps6586x_irq_init.

I will send out a v3 that fixes the commit message.

- Gary

      reply	other threads:[~2010-09-14  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 20:15 [PATCH v2] mfd: tps6586x: add basic interrupt support Gary King
2010-09-12  8:01 ` Mike Rapoport
2010-09-14  1:24   ` Gary King [this message]

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=4C8ECED6.9030209@nvidia.com \
    --to=gking@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@compulab.co.il \
    --cc=sameo@linux.intel.com \
    /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.