From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S964844AbcATRG4 (ORCPT <rfc822;w@1wt.eu>);
	Wed, 20 Jan 2016 12:06:56 -0500
Received: from unicorn.mansr.com ([81.2.72.234]:49982 "EHLO unicorn.mansr.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752348AbcATRGx convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 20 Jan 2016 12:06:53 -0500
From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= <mans@mansr.com>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Mark Rutland <mark.rutland@arm.com>, Marc Zyngier <marc.zyngier@arm.com>,
        Sebastian Frias <sf84@laposte.net>,
        Jason Cooper <jason@lakedaemon.net>, Arnd Bergmann <arnd@arndb.de>,
        LKML <linux-kernel@vger.kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH v3] irqchip: Add support for Tango interrupt controller
References: <569CE0F2.1060507@sigmadesigns.com>
	<569D0B80.1010908@sigmadesigns.com>
	<569D165E.4060004@sigmadesigns.com> <569FAFF5.4090909@arm.com>
	<yw1xr3hcqlix.fsf@unicorn.mansr.com>
	<569FB4AE.8000506@sigmadesigns.com>
	<20160120170219.GC28169@leverpostej> <569FBE76.10609@sigmadesigns.com>
Date: Wed, 20 Jan 2016 17:06:52 +0000
In-Reply-To: <569FBE76.10609@sigmadesigns.com> (Marc Gonzalez's message of
	"Wed, 20 Jan 2016 18:05:58 +0100")
Message-ID: <yw1x60yoqixf.fsf@unicorn.mansr.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Marc Gonzalez <marc_gonzalez@sigmadesigns.com> writes:

> On 20/01/2016 18:02, Mark Rutland wrote:
>
>> When you put together the binding document, please point out that the
>> ranges property is necessary.
>
> I don't quite understand.
>
> Can I write the node without a ranges property, and the driver would
> still function correctly?

Not the one you posted.

-- 
Måns Rullgård