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=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, 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 C4DF4C31E57 for ; Mon, 17 Jun 2019 08:56:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 91B8D2084A for ; Mon, 17 Jun 2019 08:56:55 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="lAOFLfNp" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727786AbfFQI4y (ORCPT ); Mon, 17 Jun 2019 04:56:54 -0400 Received: from mail-ed1-f67.google.com ([209.85.208.67]:40035 "EHLO mail-ed1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725763AbfFQI4x (ORCPT ); Mon, 17 Jun 2019 04:56:53 -0400 Received: by mail-ed1-f67.google.com with SMTP id k8so15025045eds.7 for ; Mon, 17 Jun 2019 01:56:52 -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=nYP7nwkWft+3uUp9e25ZuOw9THhDw1ggRk0lkiQT8jk=; b=lAOFLfNpOvUuTJG1ReESb/ZnQ/2/zpkokfGcQ2pm7U3B/ryQAyyBLNSwP+NaSwRoqS U9lIIWVsfLkHWjYKJNX9okgatDFpPrHcqGu5rwGnoQigsqMslV09MLZojcrsVT7jgDyX nrXyhqJ9ZHGZRUS7ihpHWC4mZHqlD9wRoW57gXBHyhQhSYKH6mkGgHi9aXZFwCbmvxKs JVPkRYWJ6lr3YwDp2RVZWtnfBrbdFjWztay7Az2zA/5ZG15yTbT8JyJVWMbNm0djowcr so84g4+chJssDRGKjlNSz5ubvVvDAAEsGAN4CXgcqf8mslLPgg9lphass99teg01v2X9 nGXA== 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=nYP7nwkWft+3uUp9e25ZuOw9THhDw1ggRk0lkiQT8jk=; b=X9KLvDsiY9JP84WBregupGDYvpl5ms30wljxzaIH67zAhwnGbZTztykKMjWL+ZyCyi JAyfWHKTXNXPxGiJVYPEKKBxri4YMn5180fbsxpeXIeBTdJ8YbLMPQhZSmfoKRDMISd1 A9brglVKAPeB5Z7k8gPtBP469JGFneF/5Lr4s4a1trNq3toHvcbE60EVOv1BQSPkkao5 c62RFQj62Ot7t0CKjBZ2DyibIkJfQ1hGnatRIBZ+1J1XfOREG0diWSe1nGXAjutkFGR9 J/CHyScrBLRsqlGUJMEYzLNqdh7JuuQqMMgEqrxIT2uvEwdPZqj1UeAxH34vNyyOD+IV rkPQ== X-Gm-Message-State: APjAAAVVXg+0kBYrNj2sQkaXUCCzBM1MFwjMNHcg8LFu3bs2l2o+VpwL vhvq2N996UEtyF/Nx25QIGFvSg== X-Google-Smtp-Source: APXvYqwylTBcYALz6DItF8lNeiu/bxiKZNfUEzJ2MwvfkvNg59Cyc/65bONS/5J26iZtM3yzFUyF6w== X-Received: by 2002:a17:906:1181:: with SMTP id n1mr63614604eja.177.1560761812064; Mon, 17 Jun 2019 01:56:52 -0700 (PDT) Received: from localhost ([81.92.102.43]) by smtp.gmail.com with ESMTPSA id a3sm3394908edr.48.2019.06.17.01.56.51 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 17 Jun 2019 01:56:51 -0700 (PDT) Date: Mon, 17 Jun 2019 01:56:50 -0700 (PDT) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Yash Shah cc: davem@davemloft.net, devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, robh+dt@kernel.org, mark.rutland@arm.com, nicolas.ferre@microchip.com, palmer@sifive.com, aou@eecs.berkeley.edu, ynezz@true.cz, sachin.ghadi@sifive.com Subject: Re: [PATCH v2 1/2] macb: bindings doc: add sifive fu540-c000 binding In-Reply-To: <1560745167-9866-2-git-send-email-yash.shah@sifive.com> Message-ID: References: <1560745167-9866-1-git-send-email-yash.shah@sifive.com> <1560745167-9866-2-git-send-email-yash.shah@sifive.com> 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 Mon, 17 Jun 2019, Yash Shah wrote: > Add the compatibility string documentation for SiFive FU540-C0000 > interface. > On the FU540, this driver also needs to read and write registers in a > management IP block that monitors or drives boundary signals for the > GEMGXL IP block that are not directly mapped to GEMGXL registers. > Therefore, add additional range to "reg" property for SiFive GEMGXL > management IP registers. > > Signed-off-by: Yash Shah Reviewed-by: Paul Walmsley - Paul