From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934653AbcATQYb (ORCPT ); Wed, 20 Jan 2016 11:24:31 -0500 Received: from mail1.bemta12.messagelabs.com ([216.82.251.7]:30435 "EHLO mail1.bemta12.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934015AbcATQY2 (ORCPT ); Wed, 20 Jan 2016 11:24:28 -0500 X-Env-Sender: Marc_Gonzalez@sigmadesigns.com X-Msg-Ref: server-7.tower-163.messagelabs.com!1453307056!22718347!1 X-Originating-IP: [195.215.56.170] X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Subject: Re: [RFC PATCH v3] irqchip: Add support for Tango interrupt controller To: Mans Rullgard , Marc Zyngier CC: Thomas Gleixner , Jason Cooper , LKML , Linux ARM , Sebastian Frias , Arnd Bergmann References: <569CE0F2.1060507@sigmadesigns.com> <569D0B80.1010908@sigmadesigns.com> <569D165E.4060004@sigmadesigns.com> <569FAFF5.4090909@arm.com> From: Marc Gonzalez Message-ID: <569FB4AE.8000506@sigmadesigns.com> Date: Wed, 20 Jan 2016 17:24:14 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [172.27.0.114] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/01/2016 17:10, Måns Rullgård wrote: > Marc Zyngier wrote: > >>> + if (of_property_read_u32(node, "reg", &ctl)) >>> + panic("%s: failed to get reg base", node->name); >>> + >>> + chip = kzalloc(sizeof(*chip), GFP_KERNEL); >>> + chip->ctl = ctl; >>> + chip->base = base; > > As I said before, this assumes the outer DT node uses a ranges > property. Normally reg properties work the same whether they specify an > offset within an outer "ranges" or have a full address directly. It > would be easy enough to make this work with either, so I don't see any > reason not to. IIRC, I was told very early in the review process that the ranges prop was mandatory. Lemme look for it... It was Arnd: http://thread.gmane.org/gmane.linux.ports.arm.kernel/444131/focus=444207 > You are missing a ranges property that describes what address > space these addresses are in. > > 'ranges;' would be wrong here, as the interrupt controller is > not a bus. If you have no ranges property, the bus is interpreted > as having its own address space with no relation to the parent bus > (e.g. an I2C bus uses addresses that are not memory mapped). > > Just list the addresses that are actually decoded by child > devices here. Did I misunderstand? Regards.