From: Tony Lindgren <tony@atomide.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Guo Zeng <Guo.Zeng@csr.com>, Barry Song <Baohua.Song@csr.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Subject: Re: [PATCH] regmap: irq: fix ack-invert
Date: Wed, 28 Feb 2018 14:04:33 -0800 [thread overview]
Message-ID: <20180228220433.GJ5448@atomide.com> (raw)
In-Reply-To: <CAJ+vNU2d-KKMHvb2bJt-b_9h7c2YM1NJS4PYYi7Y=YzT-VQJNg@mail.gmail.com>
* Tim Harvey <tharvey@gateworks.com> [180228 21:18]:
> On Tue, Feb 27, 2018 at 10:39 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * Tim Harvey <tharvey@gateworks.com> [180227 16:07]:
> >> When acking irqs we need to take into account the ack-invert case. Without
> >> this chips that require 0's to ACK interrupts will never clear the interrupt.
> >>
> >> I am working on an mfd driver that will use ack-invert and discovered
> >> this issue. The only user of ack_invert currently appears to be the
> >> motorola-cpcap driver. I'm not clear why that driver doesn't appear affected
> >> so I'm cc'ing those involved with that driver for review and testing.
> >
> > I gave this a quick try and it fails with cpcap. So yeah, you're right,
> > it seems we still have the cpcap config wrong.
> >
>
> Tony,
>
> So you would agree with my findings/patch right? I certainly don't
> want to break regmap-irq in general :)
Yes I agree that it breaks now things for me, so if it works for you
it seems we're good to go. But I don't want to ack it yet as I'm
worried that it gets applied without the cpcap changes which would
break things :)
> Adding Guo Zeng and Barry Song to the thread as they were the authors
> of the ack_invert feature (a650fdd9427f1f5236f83d2d8137bea9b452fa53)
> and I'm not clear what happened to the chip they were needing it for.
>
> > Things do work with the following patch and your patch for cpcap. So
> > they should both be applied together as a single patch.
> >
> > Care to fold in the following change and then repost your patch?
> >
> > Otherwise we might end up breaking things easily for booting or
> > bisect or stable. Or else the patch below needs to be applied first
> > to avoid breaking things.
> >
>
> So cpcap needs to write 1's to clear irq's not 0's right?
Correct. And I tried to follow what the Motorola kernel tree
was doing to configure things but got the configuration wrong
but it worked so I never had a reason to doubt it before your
patch.
> Yes, I can certainly roll in the fix for cpcap if everyone agrees
> that's the right move.
OK thanks.
> I'll wait for some feedback from Mark Brown as well.
OK
Tony
next prev parent reply other threads:[~2018-02-28 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 16:05 [PATCH] regmap: irq: fix ack-invert Tim Harvey
2018-02-27 18:39 ` Tony Lindgren
2018-02-28 21:17 ` Tim Harvey
2018-02-28 22:04 ` Tony Lindgren [this message]
2018-03-03 17:01 ` Tim Harvey
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=20180228220433.GJ5448@atomide.com \
--to=tony@atomide.com \
--cc=Baohua.Song@csr.com \
--cc=Guo.Zeng@csr.com \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
--cc=tharvey@gateworks.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.