[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1a5735e8-b876-92e4-9f1e-687f5abf8708@i2se.com>
Date: Mon, 24 Feb 2020 10:21:39 +0100
From: Stefan Wahren <stefan.wahren@...e.com>
To: Lukas Wunner <lukas@...ner.de>
Cc: Marc Zyngier <maz@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
linux-kernel@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
Serge Schneider <serge@...pberrypi.org>,
Kristina Brooks <notstina@...il.com>,
Matthias Brugger <mbrugger@...e.com>,
Martin Sperl <kernel@...tin.sperl.org>,
Phil Elwell <phil@...pberrypi.org>
Subject: Re: [PATCH v2] irqchip/bcm2835: Quiesce IRQs left enabled by
bootloader
Hi Lukas,
On 23.02.20 19:24, Lukas Wunner wrote:
> On Sun, Feb 23, 2020 at 06:59:56PM +0100, Stefan Wahren wrote:
>> thanks for all the investigation. Unfortunately the patch below doesn't
>> compile, since it lacks the definiton of REG_FIQ_ENABLE.
> Ugh, I recall fixing that when compile-testing. I must have forgotten
> to invoke "git commit --amend" before "git format-patch".
>
>> Btw the name is a little bit unlucky because it defines a single flag
>> within REG_FIQ_CONTROL instead of a separate register.
> The Foundation's repo uses that name so I stuck by it to reduce the
> number of merge conflicts Phil will have to resolve. Happy to change
> though, suggestions welcome.
readability has a higher prio. How about:
#define FIQ_CONTROL_ENABLE BIT(7)
Regards
Stefan
Powered by blists - more mailing lists