From: Samuel Ortiz <sameo@openedhand.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: Support active high IRQs on WM835x
Date: Fri, 6 Feb 2009 14:54:32 +0100 [thread overview]
Message-ID: <20090206135431.GA3341@sortiz.org> (raw)
In-Reply-To: <20090202135650.838a3ddd.akpm@linux-foundation.org>
Hi Andrew,
On Mon, Feb 02, 2009 at 01:56:50PM -0800, Andrew Morton wrote:
> On Mon, 26 Jan 2009 19:23:18 +0000
> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>
> > Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > ---
> > drivers/mfd/wm8350-core.c | 16 +++++++++++++++-
> > include/linux/mfd/wm8350/core.h | 2 ++
> > 2 files changed, 17 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/mfd/wm8350-core.c b/drivers/mfd/wm8350-core.c
> > index e5e82c7..908284c 100644
> > --- a/drivers/mfd/wm8350-core.c
> > +++ b/drivers/mfd/wm8350-core.c
> > @@ -1423,7 +1423,21 @@ int wm8350_device_init(struct wm8350 *wm8350, int irq,
> > mutex_init(&wm8350->irq_mutex);
> > INIT_WORK(&wm8350->irq_work, wm8350_irq_worker);
> > if (irq) {
> > - ret = request_irq(irq, wm8350_irq, 0,
> > + int flags = 0;
> > +
> > + if (pdata && pdata->irq_high) {
> > + flags |= IRQF_TRIGGER_HIGH;
> > +
> > + wm8350_set_bits(wm8350, WM8350_SYSTEM_CONTROL_1,
> > + WM8350_IRQ_POL);
> > + } else {
> > + flags |= IRQF_TRIGGER_LOW;
> > +
> > + wm8350_clear_bits(wm8350, WM8350_SYSTEM_CONTROL_1,
> > + WM8350_IRQ_POL);
> > + }
> > +
> > + ret = request_irq(irq, wm8350_irq, flags,
> > "wm8350", wm8350);
> > if (ret != 0) {
> > dev_err(wm8350->dev, "Failed to request IRQ: %d\n",
>
> This conflicts a bit with your earlier
> mfd-initialise-wm8350-interrupts-earlier.patch.
>
> I had marked mfd-initialise-wm8350-interrupts-earlier.patch as
> needed-in-2.6.29 so I reworked this patch to fit.
>
> afacit we haven't heard from Sam in a couple of weeks. If he's having
> a bit of downtime I guess I'll merge
Sorry for the latency. Our mailserver had some issues, and I was quite busy
fixing wireless drivers myself :/
I'm back on track now. Mark, I havent got those 2 mfd patches. Did you send
them to me for merging ? If that's so, could you please resend them ?
Cheers,
Samuel.
> mfd-initialise-wm8350-interrupts-earlier.patch
> mfd-mark-wm835x-usb_slv_500ma-bit-as-accessible.patch
> mfd-pcf50633-terminate-i2c_device_id-list.patch
>
> myself. But I'll leave that a week or two yet.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2009-02-06 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 19:23 [PATCH 1/2] mfd: Support active high IRQs on WM835x Mark Brown
2009-01-26 19:23 ` [PATCH 2/2] mfd: Ensure all WM8350 IRQs are masked at startup Mark Brown
2009-02-02 21:56 ` [PATCH 1/2] mfd: Support active high IRQs on WM835x Andrew Morton
2009-02-06 13:54 ` Samuel Ortiz [this message]
2009-02-06 14:27 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 18:12 [PATCH 0/2] WM8350 updates Mark Brown
2009-02-05 18:13 ` [PATCH 1/2] mfd: Support active high IRQs on WM835x Mark Brown
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=20090206135431.GA3341@sortiz.org \
--to=sameo@openedhand.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.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 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.