From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753140AbdKTVpY (ORCPT ); Mon, 20 Nov 2017 16:45:24 -0500 Received: from mail-pf0-f176.google.com ([209.85.192.176]:33975 "EHLO mail-pf0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753082AbdKTVpW (ORCPT ); Mon, 20 Nov 2017 16:45:22 -0500 X-Google-Smtp-Source: AGs4zMYJS3vt5LIzK5vJ1Xch488gXi+NF3B+gAVRq6Rld/EMLztJKMNlSLOIfvSQGjD/nPcfRHBkmQ== Date: Mon, 20 Nov 2017 15:45:20 -0600 From: Rob Herring To: Palmer Dabbelt Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, patches@groups.riscv.org, linux-kernel@vger.kernel.org, nathan=20Neusch=C3=A4fer?= Subject: Re: [PATCH] dt-bindings: Add a RISC-V SBI firmware node Message-ID: <20171120214520.dcaqvyncojwefmgt@rob-hp-laptop> References: <20171120195000.2070-1-palmer@sifive.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171120195000.2070-1-palmer@sifive.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 20, 2017 at 11:50:00AM -0800, Palmer Dabbelt wrote: > The RISC-V privileged ISA mandates the presence of an SBI, but there's > no reason not to put it in the device tree. This would allow us to > possibly remove the SBI later. If it is mandatory, then it should not be in DT. DT is not a driver instantiation mechanism. If your ISA can vary, I'd recommend you make that discoverable. DT is for what we failed to make discoverable. Rob