Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3774322imj; Tue, 19 Feb 2019 09:11:46 -0800 (PST) X-Google-Smtp-Source: AHgI3IYC6sRiBSzg4nwPeOiGXBFz+IXaVZLqRV8ymedI8DQxZ/cLQ88P5BTCpJP6tl987wk+ozou X-Received: by 2002:a17:902:788d:: with SMTP id q13mr13418368pll.154.1550596306568; Tue, 19 Feb 2019 09:11:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550596306; cv=none; d=google.com; s=arc-20160816; b=SORb8K2BmTmT8wlN9iB0000wDl4goyjZka6tdNmW3vHIRC+qB/qtQ37P0OUP/FBaCc M2M5IdB05k6xBXE6dZdVfGhLnMoQ0aXp3nmfiiur3uh4pfsQ//1QbYLBCM1mXk1vP5Yc 2r99VOv1vz5exguheyLezrNGRk33jSYAaIXpx9GplVm+rmlFN/hf23a1Za//pl/fCN7R CYBWp8m8iKskc0OlHQYtP5+ILqgFpCP+zeqNvgvsbTufIakbLuQfPMt1+W5nvNAVBCTa 4qAMTOf7rXiGONo+cxj9eZ/6yYwc1JdfLNk0wrLFQWTVEyg0LHUdpV9z3fQMvl2v1z2+ J/4A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=FDzRn533OLSaEc/O2JcKJeL3vDy9k0Uxici5JT0jemc=; b=iwX36PrTStiCSTpStQAlOMlPRN5hM1sWLyP6eS0p6fNLQVoMgG5EsMZKEh8XErjfR+ EJbCJMV3Irtj+lZ8KxRn2XJuZcBBnpzw8ENbDfFMx6pe/ctDHq4ht5mh0tg1DqBEBwhc VpAHmxrR9bRCXbVSRAUP73lX2cByYlb0WCe4bJGMq/ONUYWt9asWe5HTQfi9MWGVbQCY QlEqldiQMz0cuMnuXV6eap6J8zA9Ebk50/N4akx2PSSxwtuR+lKccRR1M7/OBKM+Hu4e 2JePKa6dMAFP6uGfzPMVHwuauKrzr4VdcBp8mGIWeANSOIzVoXqmcECkEb0cu6qPmQ9P V48A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l68si18201391plb.90.2019.02.19.09.11.31; Tue, 19 Feb 2019 09:11:46 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728899AbfBSRLI (ORCPT + 99 others); Tue, 19 Feb 2019 12:11:08 -0500 Received: from muru.com ([72.249.23.125]:39674 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726811AbfBSRLI (ORCPT ); Tue, 19 Feb 2019 12:11:08 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id B315E80FB; Tue, 19 Feb 2019 17:11:17 +0000 (UTC) Date: Tue, 19 Feb 2019 09:11:04 -0800 From: Tony Lindgren To: Lokesh Vutla Cc: marc.zyngier@arm.com, Nishanth Menon , Santosh Shilimkar , Rob Herring , tglx@linutronix.de, jason@lakedaemon.net, Linux ARM Mailing List , linux-kernel@vger.kernel.org, Device Tree Mailing List , Sekhar Nori , Tero Kristo , Peter Ujfalusi Subject: Re: [PATCH v5 05/10] dt-bindings: irqchip: Introduce TISCI Interrupt router bindings Message-ID: <20190219171104.GM15711@atomide.com> References: <20190214154100.GB5720@atomide.com> <20190214174612.GF5720@atomide.com> <171e8597-2156-747d-d024-7b4bfc6f9186@ti.com> <20190215161629.GK5720@atomide.com> <2369739e-3bc8-257a-99e0-db2951c6777d@ti.com> <20190218143245.GC15711@atomide.com> <84b3ec21-9ce9-b9a8-80a9-75001db43a90@ti.com> <20190219153537.GJ15711@atomide.com> <6aa37276-0833-fdf5-575b-c3ca14f776a6@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6aa37276-0833-fdf5-575b-c3ca14f776a6@ti.com> User-Agent: Mutt/1.11.2 (2019-01-07) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Lokesh Vutla [190219 16:19]: > yes. How different is this from any of the above mentioned drivers using > firmware specific ids. Like sci pm domain[1] driver utilizes the same > device id for enabling any device in the system. Similarly clock > driver[2] uses the same device ids and clock ids specified by firmware. > There are more which similarly represents firmware ids from DT. > > [1] Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt > [2] Documentation/devicetree/bindings/clock/ti,sci-clk.txt That's horrible. We really must not use any firmware invented numbers in the device as they do not describe hardware. Regards, Tony