[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170110234638.nm2xveibo4bpyiup@piout.net>
Date: Wed, 11 Jan 2017 00:46:39 +0100
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: Martin Kaiser <martin@...ser.cx>
Cc: Lucas Stach <l.stach@...gutronix.de>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <kernel@...gutronix.de>,
Juergen Borleis <jbe@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
rtc-linux@...glegroups.com, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH 1/3 v4] rtc: imxdi: use the security violation interrupt
On 03/01/2017 at 19:49:50 +0100, Martin Kaiser wrote :
> The DryIce chipset has a dedicated security violation interrupt that is
> triggered for security violations (if configured to do so). According
> to the publicly available imx258 reference manual, irq 56 is used for
> this interrupt.
>
> If an irq number is provided for the security violation interrupt,
> install the same handler that we're already using for the "normal"
> interrupt.
>
> imxdi->irq is used only in the probe function, make it a local variable.
>
> Signed-off-by: Martin Kaiser <martin@...ser.cx>
> ---
> v4:
> - separate patches for imx25.dtsi and documentation of the new dt binding
>
> v3:
> - add the device tree changes to this patch series
> - install the same interrupt handler for normal and sec irq, rename
> the handler function accordingly
> - make imxdi->irq and imxdi->sec_irq local variables in the probe
> function
>
> v2:
> - make sec_irq optional to avoid breaking the Device Tree ABI
> - removed the Device Tree bindings, I'll prepare a separate patch for them
>
>
> drivers/rtc/rtc-imxdi.c | 28 ++++++++++++++++++++--------
> 1 file changed, 20 insertions(+), 8 deletions(-)
>
Applied after fixing the multiline comment, thanks.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
Powered by blists - more mailing lists