From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751879AbcGTGkk (ORCPT ); Wed, 20 Jul 2016 02:40:40 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:57940 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751130AbcGTGkh (ORCPT ); Wed, 20 Jul 2016 02:40:37 -0400 Date: Wed, 20 Jul 2016 08:38:22 +0200 (CEST) From: Thomas Gleixner To: Andy Gross cc: =?ISO-8859-15?Q?S=F6ren_Brinkmann?= , Jason Cooper , Marc Zyngier , linux-arm-kernel@lists.infradead.org, Michal Simek , linux-kernel@vger.kernel.org Subject: Re: SOC-specific action for irq_set_wake In-Reply-To: <20160719224713.GA13533@hector.attlocal.net> Message-ID: References: <20160719181804.GX3847@xsjsorenbubuntu> <20160719224713.GA13533@hector.attlocal.net> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 19 Jul 2016, Andy Gross wrote: > So not too long ago there were irq extensions that you could add in to an > irq controller that would allow for intercepting the set wake calls. This > went away and was replaced by the hierarchical irq design. For a very good reason. The 'extensions' were a horrible hack and an unmaintainable mess. This problem is not that hard to solve w/o these hacks. Thanks, tglx