Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1867579imm; Sun, 15 Jul 2018 19:52:11 -0700 (PDT) X-Google-Smtp-Source: AAOMgpe6amgdsyFp7Im+BVMmqaiF0FheAadccQYEi+DN7E4L0GSXAIV8L7vlHHrnOVubH7IBQPW7 X-Received: by 2002:a63:144b:: with SMTP id 11-v6mr14305095pgu.219.1531709531622; Sun, 15 Jul 2018 19:52:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531709531; cv=none; d=google.com; s=arc-20160816; b=G9DfWHY0ZkvyhY7ZYA4IQr+9fg8+3FJ5G/TglRxo7u6prTPNlQRcD2FLVvF47+cba0 ae7E5UW0NX82XbW6aQOw7NLP5akEBABwXCP/7vehtnkSLgGl6DQb18PBFzbINt6mgu2A Ak9KsTMQgM2J9+l5YeCHu2a0kMT+Wrn3OQb6FcyOCjwP2IbqICSpEhjvEKbW2q8UZN5M zKfFEX6ZFePCnYhMJk3CzyvNG0vvhx/6iVhJG7Y5GhMvgsSSdXQXrwSJhFsreIfpQcvU 2RDNQXb6lRZIU+JgBsoJNXM3jSzzd8BWZ9pyTDJY33apgNunEPxJEjScHEebReMaU7mQ aYSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:date:subject:in-reply-to :content-transfer-encoding:mime-version:cc:to:from:message-id :dkim-signature:dkim-signature:arc-authentication-results; bh=Zzl7/sHSNh+IyPQWupkGHIFiP4/yfQZ+hKPwMIwSg88=; b=sFfD24n7vI4NW9O7QpQg2ajZc8HMnqkTCHsAm1vUYpB+ZIv88bIn/xCpXSqtSoUB9b 96nAAiRM0ast6rJiSKYUQdlwylv3mQffYOANmS5GR6UyjU8Wit7eCOBxjNnejTFImULf JX881MirmYxpvEF1enKR0hL8851yWOQV0q+jHqFS1i0x7rzZgTAsEv58DCA97eTayO3s 74IEeR+BtWVmkLVltdmAAexV1csHkT05hOmSPH9Deq9kegC1ohLjTA+gm1efE8Y+TYT4 9IYG+t2vshw400fDrcumrbgTlGNRyPvr5epqRhkp53gMysvyLB24zJFop6d5jPwG7FFU BV5g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm3 header.b=ixvRTK7h; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=ckyVHmX0; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y63-v6si28721113pgb.5.2018.07.15.19.51.46; Sun, 15 Jul 2018 19:52:11 -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=@aj.id.au header.s=fm3 header.b=ixvRTK7h; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=ckyVHmX0; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727522AbeGPDQE (ORCPT + 99 others); Sun, 15 Jul 2018 23:16:04 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:49311 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727374AbeGPDQE (ORCPT ); Sun, 15 Jul 2018 23:16:04 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 132F721B82; Sun, 15 Jul 2018 22:50:54 -0400 (EDT) Received: from web5 ([10.202.2.215]) by compute4.internal (MEProxy); Sun, 15 Jul 2018 22:50:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=Zzl7/sHSNh+IyPQWupkGHIFiP4/yf QZ+hKPwMIwSg88=; b=ixvRTK7hFWNCX7jVankQK53KlBrEZnr287ulbWGM1D6ZZ YxMF4Jk5eAKNJMSycMbwTue3rkA5R6Ujyz+oOva+APfWDqdcxGVuuKejiWEL8M8z WTInibBGM+RrJWa5ndKFyL8B4lz3jhtlwrVS1Fb47vdpwj0nitn0NjJc2teWZmn2 D1vgWULf+njJw8HZwu4rGVPhn4jOjE6DE2DgNnqO2emIRafQBXEnz0hbBYvHp8GX TnZ8E3H7apixX1Aryd7Lxsp8OY/+RXvzEFu0AEFHZZs0IN8/hDxTeIxolZnJ2XjF UDpsTaDvQya/BMyp5DLPnZzpySF+10URhElBjzSLA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Zzl7/s HSNh+IyPQWupkGHIFiP4/yfQZ+hKPwMIwSg88=; b=ckyVHmX03SmfMlOVkWqmh1 +Tq5AQKi3H+2jlzV+Ebk8rgN+TcFqu0wQDFJo8BusC298LRgPmiFV2SmzJL51DBL cw/kidPbk9yig6uN4+Lw30iMmJwFjeU4gqwGtpWFVAjF/wj/z7qv843Vfy/xztOa gcBV25GpO2pzq7HkqVD59BpLkqrLo5d3dv0jXnWzHQPTQnb/bOTctj22dJQgqH8A dhhBe+m0l8JzZayIqgyQqfSvhin7c3wTuaRNaAeXkiMaJRODhjNT6aXZo+HEFbWI WBNOy3vsFedMPefNV6I9lTk82Zhl+IpFlpvn4E4uTJYAOyWS+CMMvZ5dzuPb3IEg == X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id F016B9E0F5; Sun, 15 Jul 2018 22:50:52 -0400 (EDT) Message-Id: <1531709452.1037890.1441737864.7E216D02@webmail.messagingengine.com> From: Andrew Jeffery To: Rob Herring , Tomer Maimon Cc: mark.rutland@arm.com, arnd@arnd.de, gregkh@linuxfoundation.org, avifishman70@gmail.com, yuenn@google.com, brendanhiggins@google.com, venture@google.com, joel@jms.id.au, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org, openbmc@lists.ozlabs.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-957169fa In-Reply-To: <20180711202107.GA29980@rob-hp-laptop> Subject: Re: [PATCH v1 1/2] dt-binding: bmc: Add NPCM7xx LPC BPC documentation Date: Mon, 16 Jul 2018 12:20:52 +0930 References: <20180704091427.409971-1-tmaimon77@gmail.com> <20180704091427.409971-2-tmaimon77@gmail.com> <20180711202107.GA29980@rob-hp-laptop> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Jul 2018, at 05:51, Rob Herring wrote: > On Wed, Jul 04, 2018 at 12:14:26PM +0300, Tomer Maimon wrote: > > Added device tree binding documentation for Nuvoton BMC > > NPCM7xx BIOS Post Code (BPC). > > The NPCM7xx BPC monitoring two configurable I/O addresses > > written by the host on Low Pin Count (LPC) bus. > > > > Signed-off-by: Tomer Maimon > > --- > > .../devicetree/bindings/bmc/npcm7xx-lpc-bpc.txt | 26 ++++++++++++++++++++++ > > 1 file changed, 26 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/bmc/npcm7xx-lpc-bpc.txt > > > > diff --git a/Documentation/devicetree/bindings/bmc/npcm7xx-lpc-bpc.txt b/Documentation/devicetree/bindings/bmc/npcm7xx-lpc-bpc.txt > > new file mode 100644 > > index 000000000000..0832c9cbea32 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/bmc/npcm7xx-lpc-bpc.txt > > @@ -0,0 +1,26 @@ > > +Nuvoton NPCM7xx LPC BPC interface > > + > > +Nuvoton BMC NPCM7xx BIOS Post Code (BPC) monitoring two > > +configurable I/O addresses written by the host on the > > +Low Pin Count (LPC) bus, the capure data stored in 128-word FIFO. > > s/capure/capture/ > > Otherwise, > > Reviewed-by: Rob Herring So uncovering a bit of a dirty secret here, we should probably consider this in the context of the ASPEED snoop function. A driver snuck into the misc tree without an associated bindings document: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/misc/aspeed-lpc-snoop.c (it wasn't me, I'm happy to discuss my proposed bindings, please don't shoot the messenger :)) The devicetree node looks something like: lpc_snoop: lpc-snoop@0 { compatible = "aspeed,ast2500-lpc-snoop"; reg = <0x0 0x80>; interrupts = <8>; status = "disabled"; }; and also has a required "snoop-ports" property with at least one and up to two cells that describe the channels to snoop. Channel values are either 0 or 1. It's feasible that the double-word capture could also be supported as both supported channels have their data captured in different fields of the same register. Do we go with what's already in the tree in supporting 'snoop-ports' or keep 'monitor-ports' as proposed by Tomer? Andrew > > > > + > > +NPCM7xx BPC supports capture double words, when using capture > > +double word only I/O address 1 is monitored. > > + > > +Required properties for lpc_bpc node > > +- compatible : "nuvoton,npcm750-lpc-bpc" for Poleg NPCM7XX. > > +- reg : specifies physical base address and size of the registers. > > +- interrupts : contain the LPC BPC with flags for falling edge. > > +- monitor-ports : contain monitor I/O addresses, at least one monitor I/O > > + address required > > + > > +Optional property for lpc_bpc node > > +- bpc-en-dwcapture : enable capture double words support. > > + > > +Example: > > + lpc_bpc: lpc-bpc@f0007040 { > > + compatible = "nuvoton,npcm7xx-lpc-bpc"; > > + reg = <0xf0007040 0x14>; > > + monitor-ports = <0x80>; > > + interrupts = ; > > + }; > > -- > > 2.14.1 > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html