Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3819743imj; Tue, 19 Feb 2019 09:58:30 -0800 (PST) X-Google-Smtp-Source: AHgI3IaEnt3b3wJsNdeSoCIRq0VD+DqZflZBTuWVsX8GF+YVwXvAtj2jufiyDHdmDOoOzVsfAROY X-Received: by 2002:a63:d158:: with SMTP id c24mr7116785pgj.34.1550599110842; Tue, 19 Feb 2019 09:58:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550599110; cv=none; d=google.com; s=arc-20160816; b=Clc+knkuHwroHnsSwurD1tBPvBo8x0fUyU9vUJtOKgb2JtcOOZLz9Ae+x9em73y+zu NoBGVoKbrUOEY+Rjc4+IuXq5t92AP/s5xxAJK9tCk3LmRZpzDU/+JilBRphwbg/vZzxS 0ARIdOx22RwrMIPGNcPVG853qdnKvV8bFrTV75j2rkEfXwIiCcR2oxGRy1XeddpuKpOt chuBjF/E9anR3xYEXlo5TBPwcx3fW48UiIltAGU8VkoOFqkQwE1DFoMOnZ2xjXwbXMUQ Np02xyRfYiIt8EQ0bcuYEqIGJQhzVTM+b9V9pAeJ5ieJgqcqc+MBOq6SL6FQgtiFYLYX 3ekA== 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=Lfjs9+ZzztQEsIaMuoieiCGP8mWE9bTaboFRaRAv7Gg=; b=zfPS/JUBCxpveHmKqSkCE0uvcpDJ0AC9f+Hjt3hARXPORVCwWGbyS7S+76FU9sS75b Zqh6ezlAWg8hAwV+SXoIfCb0uVaZOhGV19zyUBAyHDhzm2iZRhHFdKpPpHbwW3fPAF7C WnZQV2PCtNYDvMz1qNh02B4PFYNZSPvHU2H1IPHlPGY/iQ7XHOpej9YthOyeShTML8Rj XknMK1q8f9c2YQCFILX2jvX2Y8+z0NAwau8dAavrftIiuMaFyby+aqeD6UsAH0HA3Yba Tz3WULZw4PVr9ahuvRupvo74J4kb8KQVT8GzVgmcGIw8LLZX+SZA5P2kzdsqY+nV8GWU /JxQ== 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 y14si15140937plr.78.2019.02.19.09.58.04; Tue, 19 Feb 2019 09:58:30 -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 S1726794AbfBSR44 (ORCPT + 99 others); Tue, 19 Feb 2019 12:56:56 -0500 Received: from muru.com ([72.249.23.125]:39692 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726425AbfBSR44 (ORCPT ); Tue, 19 Feb 2019 12:56:56 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 2526580B6; Tue, 19 Feb 2019 17:57:05 +0000 (UTC) Date: Tue, 19 Feb 2019 09:56:51 -0800 From: Tony Lindgren To: Lokesh Vutla Cc: Nishanth Menon , Device Tree Mailing List , jason@lakedaemon.net, Peter Ujfalusi , marc.zyngier@arm.com, Sekhar Nori , linux-kernel@vger.kernel.org, Tero Kristo , Rob Herring , Santosh Shilimkar , tglx@linutronix.de, Linux ARM Mailing List Subject: Re: [PATCH v5 05/10] dt-bindings: irqchip: Introduce TISCI Interrupt router bindings Message-ID: <20190219175651.GN15711@atomide.com> References: <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> <20190219171104.GM15711@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190219171104.GM15711@atomide.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 * Tony Lindgren [190219 17:11]: > * 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. No firmware invented numbers in the device tree I mean naturally. Drivers do whatever they need to do to deal with the firmware. Regards, Tony