From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CB5CCC28EBD for ; Sun, 9 Jun 2019 05:50:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8F3FB208E4 for ; Sun, 9 Jun 2019 05:50:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="j/5W+Sr8" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726770AbfFIFuU (ORCPT ); Sun, 9 Jun 2019 01:50:20 -0400 Received: from mail-pf1-f196.google.com ([209.85.210.196]:37324 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725787AbfFIFuU (ORCPT ); Sun, 9 Jun 2019 01:50:20 -0400 Received: by mail-pf1-f196.google.com with SMTP id 19so2587893pfa.4 for ; Sat, 08 Jun 2019 22:50:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=g5g0galx8RyvOsGO1iYuup0nP37+YQK2f5/z3KYX1Es=; b=j/5W+Sr8ZHhSAf244dwdVTBvj2tr7+iZOWOKMMfzhIdFRqi7/u2TWYwP2epGcXpNlW I/pwIxHeXTA7MG4TUk0ufCyZSyIIQCyjiYyrHyWYIDcTZHo1r+jsI0EBt7hr3FN0zF6I 9aQi/LIdQB7E6GlEfpTnYulqzgptG5UTsd45QMT4YAbNIlHdVNnESvsPdRQyDQdtMXPS jPux964RM50+CXs/BZwcQ7pdwuI3t2VFovovnu6vLXDKg5CDrROdsbaULSS6ohRCdHuV S0Iv21sLf6xxu5Yv8dwERodWihPDBsIc7gff7PUgGOY1ooe1vEiFAqb/Yrg666boUpoB aieA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=g5g0galx8RyvOsGO1iYuup0nP37+YQK2f5/z3KYX1Es=; b=OHKIcNmrEIQF+pYOstuCtZt2USVmKEPjRck4sDZXoOnravxWIc5EhhDmS0brrZbxQi eUdFyGWqIfQlrO6pT1OKcc2qKywmTRLIvgAdWmM1x+lW8ihLdK6WcN1ClmrMHnhvb+q9 9yKloM7HmS8RUQ7aDRK3khAdsl0tume/ZeBBWWYnKFxnNVOrAXhycmNTJzVN1siXFAq9 UO2rQ5xLNQ1XM6mfSJ+zhkFjOMahWuzIc1rWVfAbFS/NWUAzR9Ce9T9OGLgMr5PWopyP CTL2BkGfqy33ApQI0jNTu3jhF3LAr1Eko1Hm9TKmIJDxDYYK7ngc3Dpx+F6/kpZlMjKi oROg== X-Gm-Message-State: APjAAAVm2LqU8my/fcA7+RNaewAstIv0z0vD6P5rVCoXBzPiikaiMSgx U5rYJlQNAcnh2SjKjppe/dCY3Q== X-Google-Smtp-Source: APXvYqxz5Y4VKifbCFKug9kpochpBP/0jxW+Ow0eYUlsETgxmERQpqyTgihHK+7isHFvK+mEGd1Mhw== X-Received: by 2002:a62:15c3:: with SMTP id 186mr3310072pfv.141.1560059419499; Sat, 08 Jun 2019 22:50:19 -0700 (PDT) Received: from localhost ([202.131.137.2]) by smtp.gmail.com with ESMTPSA id y13sm8257212pfb.143.2019.06.08.22.50.18 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Sat, 08 Jun 2019 22:50:18 -0700 (PDT) Date: Sat, 8 Jun 2019 22:50:14 -0700 (PDT) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Palmer Dabbelt cc: lollivier@baylibre.com, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, paul@pwsan.com, aou@eecs.berkeley.edu Subject: Re: [PATCH v3 1/5] arch: riscv: add support for building DTB files from DT source data In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 8 Jun 2019, Palmer Dabbelt wrote: > On Thu, 06 Jun 2019 22:12:05 PDT (-0700), Paul Walmsley wrote: > > On Tue, 4 Jun 2019, Loys Ollivier wrote: > > > > > Always build it ? > > > Any particular reason to drop ARCH_SIFIVE ? > > > > Palmer had some reservations about it, so I dropped it for now. But then > > as I was thinking about it, I remembered that I also had some reservations > > about it, years ago: that everyone should use CONFIG_SOC_* for this, > > rather than CONFIG_ARCH. CONFIG_ARCH_* seems better reserved for > > CPU architectures. > > The SOC stuff will, of course, be vendor specific. In this idealized world > SiFive's SOC support has nothing to do with RISC-V, but of course all of > SiFive's SOCs are RISC-V based so the separation is a bit of pedantry. That > said, in this case I think getting the name right does make it slightly easier > to espouse this "one kernel can run on all RISC-V systems" philosophy. > Balancing the SiFive and RISC-V stuff can be a bit tricky, which is why I am > sometimes a bit pedantic about these sorts of things. Once there are SoC variants that have different CPU cores, but with the remaining chip integration the same, I think it would make sense to move the CONFIG_SOC_ stuff out from ARM, RISC-V, etc., into something that's not CPU architecture-specific. But for the time being, that seems premature. Might as well have it be driven by an actual use-case. - Paul From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4A83EC28EBD for ; Sun, 9 Jun 2019 05:50:28 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1F7FF208C0 for ; Sun, 9 Jun 2019 05:50:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="sprpa5Eo"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="j/5W+Sr8" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1F7FF208C0 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sifive.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:Message-ID: In-Reply-To:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=wUEB48+G02MOKwzjHjw9E0IOQ1BN+CPyGxM7f7EwUrU=; b=sprpa5EoHl5bIV FhI+Lh6GB0ks3/Zekulbc05eEhbDqczo7qigUyyb1b2OBtUZWWUDH8XLueQxEqcZgyfNb7TfOBcHj NYJqtqi0etUVkcDGWcDCVbB/hW6nTYBSE45OkwJ+oIpCTPAbdi1xqwg+UeG9P+YNommD7JVg/RcUo B9xhgYsqNEjsqX4NAOFLx4bz6AogT7iDcrmAAfcVYgmE/aTQa/ySWelOjmQBooF+IWRSJ6YVQRBHx 47GaWrTC4RM/R8fp+VmoNJ1uddpUkAP1A5KvxGWgAcGcnVudBB9ZuXtY5uujeVhDXIiNHbxvFucJ6 PQe/xBeAHoaXYI8UF5Uw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hZqim-0004Bv-Qu; Sun, 09 Jun 2019 05:50:24 +0000 Received: from mail-pg1-x543.google.com ([2607:f8b0:4864:20::543]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hZqij-0004B9-Da for linux-riscv@lists.infradead.org; Sun, 09 Jun 2019 05:50:22 +0000 Received: by mail-pg1-x543.google.com with SMTP id l19so681602pgh.9 for ; Sat, 08 Jun 2019 22:50:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=g5g0galx8RyvOsGO1iYuup0nP37+YQK2f5/z3KYX1Es=; b=j/5W+Sr8ZHhSAf244dwdVTBvj2tr7+iZOWOKMMfzhIdFRqi7/u2TWYwP2epGcXpNlW I/pwIxHeXTA7MG4TUk0ufCyZSyIIQCyjiYyrHyWYIDcTZHo1r+jsI0EBt7hr3FN0zF6I 9aQi/LIdQB7E6GlEfpTnYulqzgptG5UTsd45QMT4YAbNIlHdVNnESvsPdRQyDQdtMXPS jPux964RM50+CXs/BZwcQ7pdwuI3t2VFovovnu6vLXDKg5CDrROdsbaULSS6ohRCdHuV S0Iv21sLf6xxu5Yv8dwERodWihPDBsIc7gff7PUgGOY1ooe1vEiFAqb/Yrg666boUpoB aieA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=g5g0galx8RyvOsGO1iYuup0nP37+YQK2f5/z3KYX1Es=; b=JxgSwBnfSHZ+1OPx8D/JlbqIK4CQ96Afr0eh6U0v6S2n/rEUCRl+fd9i6Iina05In/ /9fD39nwsMytpWCj7CUOBsrj7pSe9aNo8b+9jRIWTZPRncUU0UOhyGtlTF4P+m+lRY0p Vx2qRvnHoGge0KEFiA2hIvMQUPK1PEHpRXww9n+pAdPKuPJb8sPxrEAR+zlruKbnWLMc ndLDTjPkU5nr0PlFAimG6jRwfOtTbquJd44ErJS9Td4nKlPoQhWusS4JZJePg4465+LZ g9ElW9DSlwT+1UrJO/oDR9KMHb0eA1RVdrc8ag4UY8OFAOxScx0MctpP4gRY+bQpVPbK kN0g== X-Gm-Message-State: APjAAAW3XEPGrdbe7wrjLiFF2Qlpb2kGG0GW4tlOzwRPg/Mt7mCeh0k9 VaJHETZH0Spyn+1NRsMo9HBSFA== X-Google-Smtp-Source: APXvYqxz5Y4VKifbCFKug9kpochpBP/0jxW+Ow0eYUlsETgxmERQpqyTgihHK+7isHFvK+mEGd1Mhw== X-Received: by 2002:a62:15c3:: with SMTP id 186mr3310072pfv.141.1560059419499; Sat, 08 Jun 2019 22:50:19 -0700 (PDT) Received: from localhost ([202.131.137.2]) by smtp.gmail.com with ESMTPSA id y13sm8257212pfb.143.2019.06.08.22.50.18 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Sat, 08 Jun 2019 22:50:18 -0700 (PDT) Date: Sat, 8 Jun 2019 22:50:14 -0700 (PDT) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Palmer Dabbelt Subject: Re: [PATCH v3 1/5] arch: riscv: add support for building DTB files from DT source data In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190608_225021_521445_6E245D3A X-CRM114-Status: GOOD ( 14.01 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-riscv@lists.infradead.org, lollivier@baylibre.com, paul@pwsan.com, linux-kernel@vger.kernel.org, aou@eecs.berkeley.edu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org On Sat, 8 Jun 2019, Palmer Dabbelt wrote: > On Thu, 06 Jun 2019 22:12:05 PDT (-0700), Paul Walmsley wrote: > > On Tue, 4 Jun 2019, Loys Ollivier wrote: > > > > > Always build it ? > > > Any particular reason to drop ARCH_SIFIVE ? > > > > Palmer had some reservations about it, so I dropped it for now. But then > > as I was thinking about it, I remembered that I also had some reservations > > about it, years ago: that everyone should use CONFIG_SOC_* for this, > > rather than CONFIG_ARCH. CONFIG_ARCH_* seems better reserved for > > CPU architectures. > > The SOC stuff will, of course, be vendor specific. In this idealized world > SiFive's SOC support has nothing to do with RISC-V, but of course all of > SiFive's SOCs are RISC-V based so the separation is a bit of pedantry. That > said, in this case I think getting the name right does make it slightly easier > to espouse this "one kernel can run on all RISC-V systems" philosophy. > Balancing the SiFive and RISC-V stuff can be a bit tricky, which is why I am > sometimes a bit pedantic about these sorts of things. Once there are SoC variants that have different CPU cores, but with the remaining chip integration the same, I think it would make sense to move the CONFIG_SOC_ stuff out from ARM, RISC-V, etc., into something that's not CPU architecture-specific. But for the time being, that seems premature. Might as well have it be driven by an actual use-case. - Paul _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv