From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753236AbcAVQp3 (ORCPT ); Fri, 22 Jan 2016 11:45:29 -0500 Received: from mail1.bemta12.messagelabs.com ([216.82.251.1]:18949 "EHLO mail1.bemta12.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750940AbcAVQp1 (ORCPT ); Fri, 22 Jan 2016 11:45:27 -0500 X-Env-Sender: Marc_Gonzalez@sigmadesigns.com X-Msg-Ref: server-2.tower-163.messagelabs.com!1453481125!23345967!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 CC: Marc Zyngier , Thomas Gleixner , Jason Cooper , LKML , Linux ARM , Sebastian Frias References: <569CE0F2.1060507@sigmadesigns.com> <569D0B80.1010908@sigmadesigns.com> <569D165E.4060004@sigmadesigns.com> <569FAFF5.4090909@arm.com> <569FB471.8000909@arm.com> <569FB7A9.9080309@sigmadesigns.com> <569FB91D.9030704@sigmadesigns.com> <56A2518F.6060808@sigmadesigns.com> <56A25ACF.5040205@sigmadesigns.com> From: Marc Gonzalez Message-ID: <56A25CA3.9000001@sigmadesigns.com> Date: Fri, 22 Jan 2016 17:45:23 +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 22/01/2016 17:39, Måns Rullgård wrote: > Marc Gonzalez writes: > >> On 22/01/2016 17:35, Måns Rullgård wrote: >> >>> Marc Gonzalez writes: >>> >>>> With your latest patch, can I drop the ranges property? >>> >>> Why would you want to do that? >> >> I thought that was the whole point of the v4 improvement? > > The point was to make it work right *if* someone were to do that even > though having it there better reflects what the hardware actually looks > like. That's the part I'm struggling to understand. Who other than you or me would write a device tree from scratch for this interrupt controller?