From: Thomas Gleixner <tglx@linutronix.de>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Jason Cooper <jason@lakedaemon.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] irqchip/mmp: only touch the PJ4 & FIQ bits on enable/disable
Date: Tue, 15 Jan 2019 11:22:36 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1901151121071.1865@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20181220215547.4813-1-lkundrak@v3.sk>
On Thu, 20 Dec 2018, Lubomir Rintel wrote:
> On an OLPC XO 1.75 machine, the "security processor" handles the GPIO 71
> and 72 interrupts. Don't reset the "route to SP" bit (4).
>
> I'm just assuming the bit 4 is the "route to SP" bit -- it fixes the
> SP-based keyboard for me and <mach-mmp/regs-icu.h> defines
> ICU_INT_ROUTE_SP_IRQ to be 1 << 4. When asked for a data sheet, Marvell
> was not helpful.
>
> Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
> Acked-by: Pavel Machek <pavel@ucw.cz>
>
> ---
> I'm not removing the defines from regs-icu.h at the moment.
> Of the MPP2 defines there, only MMP2_ICU_INT4_MASK ends up actually
> being used, in one place. That said, the header servers mostly as
> a documentation, because the documentation for the platform is lacking.
>
> Changes since v3:
> - Use #defined instead of integer literals
>
> Changes since v2:
> - Correct subsystem maintainers on Cc (irqchip)
>
> Changes since v1:
> - Adjusted wording & ack from Pavel
> ---
> drivers/irqchip/irq-mmp.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-mmp.c b/drivers/irqchip/irq-mmp.c
> index 25f32e1d7764..65fa5a1d8310 100644
> --- a/drivers/irqchip/irq-mmp.c
> +++ b/drivers/irqchip/irq-mmp.c
> @@ -34,6 +34,10 @@
> #define SEL_INT_PENDING (1 << 6)
> #define SEL_INT_NUM_MASK 0x3f
>
> +#define MMP2_ICU_INT_ROUTE_SP_IRQ (1 << 4)
Where is this used?
> +#define MMP2_ICU_INT_ROUTE_PJ4_IRQ (1 << 5)
> +#define MMP2_ICU_INT_ROUTE_PJ4_FIQ (1 << 6)
> +
> struct icu_chip_data {
> int nr_irqs;
> unsigned int virq_base;
> @@ -190,7 +194,8 @@ static const struct mmp_intc_conf mmp_conf = {
> static const struct mmp_intc_conf mmp2_conf = {
> .conf_enable = 0x20,
> .conf_disable = 0x0,
> - .conf_mask = 0x7f,
> + .conf_mask = MMP2_ICU_INT_ROUTE_PJ4_IRQ |
> + MMP2_ICU_INT_ROUTE_PJ4_FIQ,
So the mask changes from 0x7f to 0x60, but the changelog does not mention
any of this. It only talks about bit 4 ....
Thanks,
tglx
next prev parent reply other threads:[~2019-01-15 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 21:55 Lubomir Rintel
2019-01-10 19:56 ` Lubomir Rintel
2019-01-15 10:22 ` Thomas Gleixner [this message]
2019-01-16 8:54 ` Lubomir Rintel
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=alpine.DEB.2.21.1901151121071.1865@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=marc.zyngier@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®