From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:38613) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h1vBR-00027c-CM for qemu-devel@nongnu.org; Thu, 07 Mar 2019 10:43:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h1vBQ-0003vP-M2 for qemu-devel@nongnu.org; Thu, 07 Mar 2019 10:43:45 -0500 Received: from mail-ot1-x342.google.com ([2607:f8b0:4864:20::342]:37881) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h1vBQ-0003uU-Be for qemu-devel@nongnu.org; Thu, 07 Mar 2019 10:43:44 -0500 Received: by mail-ot1-x342.google.com with SMTP id b3so14486496otp.4 for ; Thu, 07 Mar 2019 07:43:44 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Peter Maydell Date: Thu, 7 Mar 2019 15:43:31 +0000 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] [PATCH] Added periodic IRQ support for bcm2836_control local timer List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: bzt Cc: Andrew Baumann , =?UTF-8?Q?Philippe_Mathieu=2DDaud=C3=A9?= , qemu-arm , QEMU Developers On Thu, 7 Mar 2019 at 15:27, bzt wrote: > Yes, could be. The QA7 spec is not really detailed, and calling both > timers simply ARM timers can be misleading. But it's not relevant > anyway from the IRQ's point of view. My latest patch checks both bits > to be set to generate the IRQ, so it does not really matter. As I've > said, this patch adds only the periodic IRQ, and not a full timer > emulation. > > Do you want any modifications on the patch? If so, what exactly? Let > me know and I'll update it. I assume by "latest patch" you mean a planned v3 that you haven't sent yet? I think it's probably best to go with my interpretation of the specs, if you think it makes sense: * running and stopping the timer is controlled by the "timer enable" bit (and doesn't care about the "interrupt enable" bit) * the timer timing out always sets the "interrupt flag" bit * we set the destination core IRQ/FIQ if the "interrupt flag" and "interrupt enable" bits are both set (we don't care about whether the "timer enable" bit is set for this) That should be only very minor changes from what you have now. thanks -- PMM