Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp783470imm; Wed, 10 Oct 2018 04:21:39 -0700 (PDT) X-Google-Smtp-Source: ACcGV63Wt46ivGNmq1N0VAkT8UioGxSnrxDfvSqfBzdrtYd1DBZW4o8n2l2EfcHMfUJ7sn8rm0LF X-Received: by 2002:a62:32c4:: with SMTP id y187-v6mr34287168pfy.4.1539170498853; Wed, 10 Oct 2018 04:21:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539170498; cv=none; d=google.com; s=arc-20160816; b=bIJjRhj2Uqw2XyzjayzufnT0py4lQND2Ctst7A9I2uHBrid6qQWQq+ac96v+mdzfDb 20LP8mNL8KlS+UG84ZZuVCQw7WGzrgw76wHBAoU+02M9zgCT1dL89YVp8ZGi4D/BMboX E/2w+DdxUwb0ThtVIS42rP/X4hVgm+JmQSYnBen1vJxaOKRHwTeRC5FJJioJiZQ7yZaY pAV7jE/MhIYq7+W3Fx+f7bSX5GyeLhiSGyjzhHD+YLh+0Qu+5Hzg2Nerx4VBjjI+XGVJ wSCnf2Up5A10Mo1fN/GHol2Fx8DjuUxkzLXUFDJeJ1r1Oxi2U14PMKqTJk3iMvrFBH3v hMAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=0j+fajQexnlp2IqoN+7PRzjwmdbE8hNCtKkuzaSoYbA=; b=oS0ezss689m+r57BH+2u/1E95CzhEAhyPRgO7WigH04Nw1Nc19+vx07qAGqzoeomcq volCZyQ6L7QAN7XAfTz3bCMlIzPMXQrzsvPV54n3NSh33jCcnmgUaSnpeEDURxDSWEgh cGMHPimuw+1V93hppMQ9MlGOFkfJM7Ug8uuDji3gyJash+X1lodJY+9I8NCr6GkVXklq 6PbBuEgvmLUEYUTQEO3cGNcKV8yvYrq6TrjtWQ+gJ/fi6cn7RZSHmK3ixxdHEuYdkM7w rdn0gzMgJDjMh5W6NJ6burn/drEDshb8Pu9kCZ1aSBYV5DlTPUUK5rkGnlWIFn171vVf pjAw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=bEKSf6hv; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t13-v6si24592661ply.279.2018.10.10.04.21.23; Wed, 10 Oct 2018 04:21:38 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=default header.b=bEKSf6hv; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726908AbeJJSlZ (ORCPT + 99 others); Wed, 10 Oct 2018 14:41:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:45892 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726870AbeJJSlY (ORCPT ); Wed, 10 Oct 2018 14:41:24 -0400 Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 49D8F21524 for ; Wed, 10 Oct 2018 11:19:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539170383; bh=0j+fajQexnlp2IqoN+7PRzjwmdbE8hNCtKkuzaSoYbA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=bEKSf6hvZqJtMcsj0NETb8BNY3Bqw58wcRADTb0dI3vWXTPlzbOuPMPFixtW2FJ04 RUzoBCnRV0IGkvD9/vAJuqej+yHfCdLbtqQ/iRGLFwMWrjldlS38zHCY3QD9YArND1 l6j0uEt4T4bdYfqdAtyZVTXL2816QTEry0P8mryY= Received: by mail-wr1-f54.google.com with SMTP id n11-v6so5177472wru.13 for ; Wed, 10 Oct 2018 04:19:43 -0700 (PDT) X-Gm-Message-State: ABuFfoirRzmdFCD9acSqSPF4uDL8RTnQsY1JVHaf3aFp0Z2Bjzv0A3Tz SAF2JnJ7MN31rXymgqu4etF1TMGOsNj0X10FEdQ/jA== X-Received: by 2002:adf:df88:: with SMTP id z8-v6mr19035312wrl.113.1539170381621; Wed, 10 Oct 2018 04:19:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Rob Herring Date: Wed, 10 Oct 2018 06:19:30 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [Question] directory for SoC-related DT binding To: Masahiro Yamada Cc: devicetree@vger.kernel.org, linux-arm-kernel , Linux Kernel Mailing List , Frank Rowand , Mark Rutland Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 10, 2018 at 6:08 AM Masahiro Yamada wrote: > > Hi, > > > I see a bunch of vendor (or SoC) names in > Documentation/device/bindings/arm/ > > ./Documentation/devicetree/bindings/arm/altera > ./Documentation/devicetree/bindings/arm/amlogic Yeah, it's kind of a mixture of board/soc bindings mostly with some ARM architecture, ARM, Ltd. IP, and SoC system reg bindings. Eventually, I'd like to not split board bindings by arch and maybe we should move all the system/misc reg bindings out. [,,,] > I also see some vendor names in > Documentation/device/bindings/soc/ > > ./Documentation/devicetree/bindings/soc/bcm > ./Documentation/devicetree/bindings/soc/dove > ./Documentation/devicetree/bindings/soc/fsl > ./Documentation/devicetree/bindings/soc/mediatek > ./Documentation/devicetree/bindings/soc/qcom > ./Documentation/devicetree/bindings/soc/rockchip > ./Documentation/devicetree/bindings/soc/ti > ./Documentation/devicetree/bindings/soc/xilinx > ./Documentation/devicetree/bindings/soc/zte This I believe is mostly SoC system reg bindings though there's probably a few other things. > Confusingly, I see bcm, mediatek, rockchip > in both locations. > > Is there any rule to choose one than the other? Top-level SoC/board bindings in arm/ and anything else elsewhere ideally. Rob