[<prev] [next>] [day] [month] [year] [list]
Message-ID: <57308B3D.3020502@roeck-us.net>
Date: Mon, 9 May 2016 06:06:05 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Álvaro Fernández Rojas <noltari@...il.com>,
Simon Arlott <simon@...e.lp0.eu>,
Thomas Gleixner <tglx@...utronix.de>
Cc: Ralf Baechle <ralf@...ux-mips.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
Florian Fainelli <f.fainelli@...il.com>,
Kumar Gala <galak@...eaurora.org>,
Kevin Cernekee <cernekee@...il.com>,
MIPS Mailing List <linux-mips@...ux-mips.org>,
Wim Van Sebroeck <wim@...ana.be>,
Miguel Gaio <miguel.gaio@...xo.com>,
Marc Zyngier <marc.zyngier@....com>,
Jonas Gorski <jogo@...nwrt.org>,
Pawel Moll <pawel.moll@....com>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
Maxime Bizon <mbizon@...ebox.fr>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
linux-watchdog@...r.kernel.org, Jason Cooper <jason@...edaemon.net>
Subject: Re: [PATCH (v5) 3/11] MIPS: bmips: Add bcm6345-l2-timer interrupt
controller
On 05/09/2016 05:01 AM, Álvaro Fernández Rojas wrote:
> Hello Guenter,
>
> Are there any other issues preventing this patches from being merged?
>
My major problem/concern is the interrupt handling and the repeated
restart of the hardware timer with continuously reduced timeouts.
This appears fragile, and it doesn't really make sense from a system
level point of view. Unfortunately, I don't have a data sheet for
the chip, nor the means or the time to test it myself. So we are pretty
much in limbo, unless someone from Broadcom confirms that, yes, this is
the one and expected means to program this watchdog.
Guenter
> Regards,
> Álvaro.
> _____________________________
> From: Guenter Roeck <linux@...ck-us.net <mailto:linux@...ck-us.net>>
> Sent: martes, diciembre 1, 2015 1:23 a. m.
> Subject: Re: [PATCH (v5) 3/11] MIPS: bmips: Add bcm6345-l2-timer interrupt controller
> To: Simon Arlott <simon@...e.lp0.eu <mailto:simon@...e.lp0.eu>>, Thomas Gleixner <tglx@...utronix.de <mailto:tglx@...utronix.de>>
> Cc: Ralf Baechle <ralf@...ux-mips.org <mailto:ralf@...ux-mips.org>>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org <mailto:linux-kernel@...r.kernel.org>>, Mark Rutland <mark.rutland@....com <mailto:mark.rutland@....com>>, Florian Fainelli <f.fainelli@...il.com <mailto:f.fainelli@...il.com>>, Ian Campbell <ijc+devicetree@...lion.org.uk <mailto:ijc+devicetree@...lion.org.uk>>, Kevin Cernekee <cernekee@...il.com <mailto:cernekee@...il.com>>, MIPS Mailing List <linux-mips@...ux-mips.org <mailto:linux-mips@...ux-mips.org>>, Kumar Gala <galak@...eaurora.org <mailto:galak@...eaurora.org>>, Miguel Gaio <miguel.gaio@...xo.com <mailto:miguel.gaio@...xo.com>>, Jonas Gorski <jogo@...nwrt.org <mailto:jogo@...nwrt.org>>, Marc Zyngier <marc.zyngier@....com <mailto:marc.zyngier@....com>>, Pawel Moll <pawel.moll@....com <mailto:pawel.moll@....com>>, Rob Herring <robh+dt@...nel.org <mailto:robh+dt@...nel.org>>, <devicetree@...r.kernel.org <mailto:devicetree@...r.kernel.org>>, Maxime
> Bizon <mbizon@...ebox.fr <mailto:mbizon@...ebox.fr>>, Wim Van Sebroeck <wim@...ana.be <mailto:wim@...ana.be>>, <linux-watchdog@...r.kernel.org <mailto:linux-watchdog@...r.kernel.org>>, Jason Cooper <jason@...edaemon.net <mailto:jason@...edaemon.net>>
>
>
> On 11/28/2015 04:26 AM, Simon Arlott wrote:
> > Add the BCM6345/BCM6318 timer as an interrupt controller so that it can be
> > used by the watchdog to warn that its timer will expire soon.
> >
> > Support for clocksource/clockevents is not implemented as the timer
> > interrupt is not per CPU (except on the BCM6318) and the MIPS clock is
> > better. This could be added later if required without changing the device
> > tree binding.
> >
> > Signed-off-by: Simon Arlott <simon@...e.lp0.eu <mailto:simon@...e.lp0.eu>>
>
> Hi Simon,
>
> can you please re-send the entire series, with all Acked-by:/Reviewed-by:
> tags as appropriate ?
>
> Thanks,
> Guenter
>
>
>
>
Powered by blists - more mailing lists