From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752850Ab0IJSVj (ORCPT ); Fri, 10 Sep 2010 14:21:39 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:37631 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751719Ab0IJSVi (ORCPT ); Fri, 10 Sep 2010 14:21:38 -0400 Date: Fri, 10 Sep 2010 12:21:35 -0600 From: Grant Likely To: Ingo Molnar Cc: Andres Salomon , devicetree-discuss@lists.ozlabs.org, x86@kernel.org, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, Mitch Bradley , linux-kernel@vger.kernel.org, Stephen Neuendorffer Subject: Re: [PATCH 2/2] x86: of: define irq functions to allow drivers/of/* to build on x86 Message-ID: <20100910182135.GG11284@angua.secretlab.ca> References: <20100910060151.6613e9c3@debxo> <20100910172538.GC11284@angua.secretlab.ca> <20100910181458.GA7243@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100910181458.GA7243@elte.hu> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 10, 2010 at 08:14:58PM +0200, Ingo Molnar wrote: > > * Grant Likely wrote: > > > On Fri, Sep 10, 2010 at 06:01:51AM -0700, Andres Salomon wrote: > > > > > > - Define a stub irq_create_of_mapping for x86 as a stop-gap solution until > > > drivers/of/irq is further along. > > > - Define irq_dispose_mapping for x86 to appease of_i2c.c > > > > > > Signed-off-by: Andres Salomon > > > > Applied to my test-devicetree branch. I'll need an ack from the x86 > > maintainers before I put it into my -next branch. > > The purpose of the patch is not clear to me. What does it do and why? It allows CONFIG_OF to be enabled on x86 without a build failure. > The changelog says it's a stopgap measure - what exactly is the long > term plan and how long will it take? It is a stop gap because it performs a trivial direct map of an IRQ number in the device tree data structure to a Linux irq number. This works for a single IRQ controller, but falls apart when cascaded controller are described in the device tree. The long term plan is to have the drivers/of/ code handling the mapping intelligently like powerpc currently does. g.