Received: by 10.223.185.116 with SMTP id b49csp29230wrg; Thu, 8 Mar 2018 12:17:20 -0800 (PST) X-Google-Smtp-Source: AG47ELvfA2vbzU4bCWwQC5Aukl1f67tK8MS+yF+evXlrKjLzBPgmxdO/rugk/eDstRLoj7HYqz/v X-Received: by 10.99.42.83 with SMTP id q80mr22070005pgq.115.1520540240401; Thu, 08 Mar 2018 12:17:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520540240; cv=none; d=google.com; s=arc-20160816; b=ul8vhge60utXNRh4ffwcTgbkHZNETSqw/tnp++x1KdK80DS6ke1kO/E/KneJ+S2oMs tmG2fmbd6M2Y4GVQg43OHyqJ6GGzeHFqXuJasPyqDUyZI5Mr3IKsizo4rV3g1O25SC6W 1JDRaDtbgwuQaf3AYHhmO+0rDX4Q6bg223JgmRfyosNrWc9qcHgSNwhxA+cKNRJX7wR0 tdRh5j3B+yHTAofFxdSaGEazT7bTNLQrAt1EOomzOd9UBcfFhUbC5IlASRNU9VpDDajt dfGeS0xT4K46whXWErMVMTCVMmd53IL2zLIaVlajKl6u1GgsKv1yLGzMUrijlATDAugL gvQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:user-agent :references:in-reply-to:subject:cc:to:from :arc-authentication-results; bh=/wV+fucJyKWXvd6z10KsmS3/rGDBbcjiS4jSgLVeNnc=; b=XSYr08TcgYRXw0E0hlX4hpAvreS97w6gnoqc3LPxDDtZPShJsRCRXh7GmhQ+6fDVqM 8E7msdryVjx5Kgb5ZMRNskR8+UMfmixyj8T+p5DU5sJmH7KoVQjtrHPaUKtD5tIwIwVs 9D4a5t4ytjh/s3+NaUB4i5NCzMyNxOf3fNMKksXimbBS/OgATSpmmHRZHidSZyZlhdBQ vx4QrcdfX2cYbM6FGamWNHPpZRmah+0zFK1q25CIYO8xVuJ5BYsjAmeiQvk7jpI/NVWO sI1MwfWciipWIdHOXQoQeJY61UDOXBpX9LFbgxg3Yh1R2QU4BkD3iGf0g1EiyUNZWsSg qUHA== ARC-Authentication-Results: i=1; mx.google.com; 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 80si14846546pfn.73.2018.03.08.12.17.06; Thu, 08 Mar 2018 12:17:20 -0800 (PST) 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; 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 S1751151AbeCHUPu (ORCPT + 99 others); Thu, 8 Mar 2018 15:15:50 -0500 Received: from anholt.net ([50.246.234.109]:54524 "EHLO anholt.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751102AbeCHUPs (ORCPT ); Thu, 8 Mar 2018 15:15:48 -0500 Received: from localhost (localhost [127.0.0.1]) by anholt.net (Postfix) with ESMTP id CBE7610A1355; Thu, 8 Mar 2018 12:15:47 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at anholt.net Received: from anholt.net ([127.0.0.1]) by localhost (kingsolver.anholt.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id JkOsmwMP5mcW; Thu, 8 Mar 2018 12:15:46 -0800 (PST) Received: from eliezer.anholt.net (localhost [127.0.0.1]) by anholt.net (Postfix) with ESMTP id 7DEE910A0F9E; Thu, 8 Mar 2018 12:15:46 -0800 (PST) Received: by eliezer.anholt.net (Postfix, from userid 1000) id F0B892FE2D33; Thu, 8 Mar 2018 12:15:45 -0800 (PST) From: Eric Anholt To: Rob Herring Cc: Florian Fainelli , Mark Rutland , devicetree@vger.kernel.org, Greg Kroah-Hartman , Phil Elwell , "moderated list\:BROADCOM BCM2835 ARM ARCHITECTURE" , "moderated list\:ARM\/FREESCALE IMX \/ MXC ARM ARCHITECTURE" , "linux-kernel\@vger.kernel.org" , Stefan Wahren , bcm-kernel-feedback-list@broadcom.com Subject: Re: [PATCH v2 3/6] dt-bindings: soc: Add a binding for the Broadcom VCHIQ services. In-Reply-To: References: <20180307185716.17449-1-eric@anholt.net> <20180307185716.17449-3-eric@anholt.net> User-Agent: Notmuch/0.22.2+1~gb0bcfaa (http://notmuchmail.org) Emacs/25.2.2 (x86_64-pc-linux-gnu) Date: Thu, 08 Mar 2018 12:15:45 -0800 Message-ID: <87lgf2fhn2.fsf@anholt.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-=-= Content-Type: text/plain Rob Herring writes: > On Wed, Mar 7, 2018 at 12:57 PM, Eric Anholt wrote: >> The VCHIQ communication channel can be provided by BCM283x and Capri >> SoCs, to communicate with the VPU-side OS services. >> >> Signed-off-by: Eric Anholt >> --- >> >> v2: dropped firmware property, added cache-line-size. >> >> .../bindings/soc/bcm/brcm,bcm2835-vchiq.txt | 28 ++++++++++++++++++++++ >> 1 file changed, 28 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt >> >> diff --git a/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt >> new file mode 100644 >> index 000000000000..cdef4abc5e47 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt >> @@ -0,0 +1,28 @@ >> +Broadcom VCHIQ firmware services >> + >> +Required properties: >> + >> +- compatible: Should be "brcm,bcm2835-vchiq" >> +- reg: Physical base address and length of the doorbell register pair >> +- interrupts: The interrupt number >> + See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt >> + >> +Optional properties: >> + >> +- cache-line-size: >> + Size of L2 cache lines. The VPU firmware detects >> + this property and overrides it with the actual L2 >> + cache line size it's using when loading the >> + device-tree. Determines the required alignment of >> + offsets/sizes of VCHIQ pagelists. If missing, the >> + firmware assumes an older kernel using 32-byte >> + alignment. > > How is this a VCHIQ property? This is a standard property for cache > nodes, but this is not a cache node. Because the existing firmware code is choosing a value based on the property's presence in this node. This is the DT ABI for the firmware that's been shipping for a long time (at least since the 4.9 era). > Is it really a problem to just use a fixed maximum alignment? That > seems to be good enough for all the rest of the kernel. If we can't have this DT property, then it looks like we need the upstream kernel to just use 32, since that's what the firmware will assume in its absence. Maybe the firmware maintainers can give us a new arg to the mailbox call for setup where we could pass in the value to use (or flag for them to pass their preferred value back to us) so we can avoid DT. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE/JuuFDWp9/ZkuCBXtdYpNtH8nugFAlqhmfEACgkQtdYpNtH8 nujgDg//WUpAZuKEvrf/LC3Q/PJvpwU9xsPLOcgNFi8MTG81AFoG+BDc9TXVccZY tpUe8WQufeLJqj8DI5DNPt355vOSvr6lCdU5H4RWv6mhA82uAO1TfULpO6DcV1Pi 8R2IEBqgQPIFdIOBvbggSHr5gvzAOT57ICwRDu802B9lY2Eor4prvpdjINYjMJS0 a1MQiQM/jtBguU68GQ3OL9EbMar8hhTX+IEUudJ9v8UAw7OQH8RdK1rC2TbY2sOs 6kEOOrXxJsfRU5czrBKEksgKj3U4+CjZnpx172rtIBbXmT1Q+V51j92RLteNwNZ5 mF1v2he0DggCgsco9VMwiS5szs5edsWWs+9GoV7qFWfBBcmFDJNZsi2HYrJTyeLA VnTmByFC37jf/561Q6rnYcG6CXe4tJxgsz/cVqiIGif6ah+E0dI9PFFKdBE25k++ CBrQvrM0Qrh6XPHcgEMonUFichkys3eTb0hmUmtSOe8JwDCyqccoSnQpR2XAhEzw zFCF2c8N8lymoh2EOdzV/T4w/hTgBLFuwqiBInWJl4XAm/YT2++XGpZJ+Dpv8jov BaL7fII7pSWcRPWuhHWjPLtagHUQl/vlsH8FXnDT9mJy/tNxidBxefwWEGdZR963 eLERHSxsxyk6pdcOYIsqVRIW9zd2PUdZ8L7FPPunylqY/bpYiLw= =7AfP -----END PGP SIGNATURE----- --=-=-=--