[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYjg3aVavgsS1Ccq5QEh1MFXafBn3zkF_hTTtm+rmt+og@mail.gmail.com>
Date: Fri, 28 Nov 2014 09:06:59 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Doug Anderson <dianders@...omium.org>
Cc: Heiko Stuebner <heiko@...ech.de>,
Sonny Rao <sonnyrao@...omium.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Chris Zhong <zyw@...k-chips.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/2] pinctrl: rockchip: Fix enable/disable/mask/unmask
On Wed, Nov 19, 2014 at 11:51 PM, Doug Anderson <dianders@...omium.org> wrote:
> The Rockchip pinctrl driver was only implementing the "mask" and
> "unmask" operations though the hardware actually has two distinct
> things: enable/disable and mask/unmask. It was implementing the
> "mask" operations as a hardware enable/disable and always leaving all
> interrupts unmasked.
>
> I believe that the old system had some downsides, specifically:
> - (Untested) if an interrupt went off while interrupts were "masked"
> it would be lost. Now it will be kept track of.
> - If someone wanted to change an interrupt back into a GPIO (is such a
> thing sensible?) by calling irq_disable() it wouldn't actually take
> effect. That's because Linux does some extra optimizations when
> there's no true "disable" function: it does a lazy mask.
>
> Let's actually implement enable/disable/mask/unmask properly.
>
> Signed-off-by: Doug Anderson <dianders@...omium.org>
> Reviewed-by: Dmitry Torokhov <dmitry.torokhov@...il.com>
> Reviewed-by: Heiko Stuebner <heiko@...ech.de>
> ---
> Changes in v2:
> - Spread out code (heiko)
Patch applied.
Yours,
Linus Walleij
--
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