[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A874F61F95741C4A9BA573A70FE3998FD9B7@DQHE02.ent.ti.com>
Date: Thu, 19 Jul 2012 09:05:30 +0000
From: "Kim, Milo" <Milo.Kim@...com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC: "sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Girdwood, Liam" <lrg@...com>,
Anton Vorontsov <cbouatmailru@...il.com>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"a.zummo@...ertech.it" <a.zummo@...ertech.it>,
Andrew Morton <akpm@...ux-foundation.org>,
Richard Purdie <rpurdie@...ys.net>,
Bryan Wu <bryan.wu@...onical.com>
Subject: RE: [PATCH 1/6] mfd: add lp8788 mfd driver
> > +struct lp8788_irq_data {
> > + struct lp8788 *lp;
> > + struct irq_domain *irqdm;
> > + struct mutex irq_lock;
> > + struct delayed_work work;
> > + struct workqueue_struct *thread;
> > + int enabled[LP8788_INT_MAX];
> > + int irq;
> > + int irq_base;
> > +};
>
> Can you use regmap-irq? If not can we fix things so that's possible?
Mark,
Currently, there is some limitation on regmap-irq with LP8788.
In LP8788, interrupt is enabled when the IRQ bit is set to 1.
This concept is opposite to interrupt-mask register.
So experimental patch has been sent.
Could you please review it ?
Patch title: [PATCH 2/2] regmap-irq: support different type of irq register
Thank you.
Best Regards,
Milo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists