Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp913589imm; Wed, 8 Aug 2018 07:48:57 -0700 (PDT) X-Google-Smtp-Source: AA+uWPx6Sh+T14F4tVlVuQtGPxGh+OWwDUKRft7tUxwiQjM10I6pcvqg5QGSAQK6sDqxVCclYJeu X-Received: by 2002:a62:586:: with SMTP id 128-v6mr3334209pff.80.1533739737935; Wed, 08 Aug 2018 07:48:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533739737; cv=none; d=google.com; s=arc-20160816; b=jBsWWnqTVmPIC4hFELVl/be/laNqaQDu+wgMUkhG7VK0c56Pa5Fq4CVxQzBu8I0cuL 4o9NvWYZseTEoycVM+GkjomuaLemt7jyE3/zJTofDJbDMAX1cM+ds85B/QTGjcZVXIW6 RtfAp5smhKS3ZwrcmxGwBohrChsJYq4ltI7P3/7kgZ9xkRtw0V4SLNjZvjv0PbGubLNM cdi84ILdlLj87s//sPLIVImhO9zCQ+o0+wvjEmaxs7Xoe74ikhBH9HVpcsM0GCPbvwKc 6sLtUiBUHdorZGnUh/vqkacudLjw8NDjJte0mIphDhuobWrjQVaSOnMQcYPFYrRm6NrS pJqg== 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 :arc-authentication-results; bh=0bfP6MswGZiiwY6wbYXSBOljSwj+cFGd3Ui4/hZvWWg=; b=H5tJp2cFDuo8K7zKHf2FQeOxgUlOrtPaA1NfmWC62kpWi0RU5xE8cUDbOBfxh8JWrc QM5V/R8f1HdQiYmyNRNn3h868aL/41LZLU/YCJkIxfPH/xNwXboJ1KGyg9OvCCthQVK5 0t1ZGqK2FQrSp2DQ+NGiZyrCly3xYL9vZ5IifUdRUP/o7aPCr+iaW/hJju4YWWDiebRb RSJVQY6GbzOpAbnObUCkFz+NNK0iDD5XgsbKtnqGG8E3N+7gAhWRo0ZxEn03o4OyH44R 8yTxL2BZJ7OJRh5gMwZqa4H3h0g6QH+w8pNny3KtWqjAX2t8r4m8FtaitY+57JgH5x1l 8cMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=lY+CUrhv; 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 a190-v6si5187995pfb.144.2018.08.08.07.48.43; Wed, 08 Aug 2018 07:48:57 -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=lY+CUrhv; 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 S1727821AbeHHREz (ORCPT + 99 others); Wed, 8 Aug 2018 13:04:55 -0400 Received: from mail.kernel.org ([198.145.29.99]:43064 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727713AbeHHREw (ORCPT ); Wed, 8 Aug 2018 13:04:52 -0400 Received: from mail-qt0-f173.google.com (mail-qt0-f173.google.com [209.85.216.173]) (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 5BD2E21718; Wed, 8 Aug 2018 14:44:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1533739493; bh=kpU+MJt+DW8vUI+D8bsiqJJjkiQhWxEU1ek7i+ZbqUw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=lY+CUrhvZ8inaOS6+EGCMyFJ8jFSnScIBOf+KSW5dToxrY19hqPMk4fjicF4rp0e/ 6OUPC/cqjYRAZ42opbNDzBT8pJ54UYgbhU/8b46QEVpYYESI44plQrZOvQ798FbFXE TwBqxoRLZbf9IdPA+/qk0O03+fztHz2d0O+Ey9Bo= Received: by mail-qt0-f173.google.com with SMTP id d4-v6so2628066qtn.13; Wed, 08 Aug 2018 07:44:53 -0700 (PDT) X-Gm-Message-State: AOUpUlFh5pA9GGX8+Qw8e2VhqdC6KNrgCIe43CFmdBxewqMBoc1Cvh6i 84PsWd+JeAvHH3m6A7n6QQQALmQAnirIWvbGhg== X-Received: by 2002:ac8:71c9:: with SMTP id i9-v6mr2899056qtp.22.1533739492588; Wed, 08 Aug 2018 07:44:52 -0700 (PDT) MIME-Version: 1.0 References: <20180802115008.4031-1-hch@lst.de> <20180802115008.4031-2-hch@lst.de> In-Reply-To: <20180802115008.4031-2-hch@lst.de> From: Rob Herring Date: Wed, 8 Aug 2018 08:44:41 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 01/11] dt-bindings: Correct RISC-V's timebase-frequency To: Christoph Hellwig Cc: Thomas Gleixner , Palmer Dabbelt , Jason Cooper , Marc Zyngier , Mark Rutland , Anup Patel , atish.patra@wdc.com, devicetree@vger.kernel.org, Albert Ou , "linux-kernel@vger.kernel.org" , linux-riscv@lists.infradead.org, Stafford Horne 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 Thu, Aug 2, 2018 at 5:50 AM Christoph Hellwig wrote: > > From: Palmer Dabbelt > > Someone must have read the device tree specification incorrectly, > because we were putting timebase-frequency in the wrong place. This > corrects the issue, moving it from > > / { > cpus { > timebase-frequency = X; > } > } > > to > > / { > cpus { > cpu@0 { > timebase-frequency = X; > } > } > } > > This is great, because the timer's frequency should really be a per-cpu > quantity on RISC-V systems since there's a timer per CPU. This should > lead to some cleanups in our timer driver. > > Signed-off-by: Palmer Dabbelt > Signed-off-by: Christoph Hellwig > --- > Documentation/devicetree/bindings/riscv/cpus.txt | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) Reviewed-by: Rob Herring