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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DBAEFC43334 for ; Thu, 14 Jul 2022 12:34:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239294AbiGNMeA (ORCPT ); Thu, 14 Jul 2022 08:34:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52256 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239315AbiGNMd6 (ORCPT ); Thu, 14 Jul 2022 08:33:58 -0400 Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4F8F2101CA for ; Thu, 14 Jul 2022 05:33:56 -0700 (PDT) Received: by mail-lf1-x12e.google.com with SMTP id a9so2529181lfk.11 for ; Thu, 14 Jul 2022 05:33:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=znBmTmWbrra/OYjTkxnIPxribEEA4AB0oOiGcRO1fM4=; b=am2BWu1YVCHhUdeG+SgRP5hOGK4IVx1sW+EN3dHRC5r9mK69YjS+uxvRAc+hmP2jR8 GjraOZ6I4dIffe61z32cemcVORC0jEs9EiDERpA8gMhNNhV+byMO8sX9Fdii2iRcesbM ZtZc53neKhKK/UkXPL3Wz0lSee0uL33e9a4O2bCZPNQCOQPzviu9ces26f1418c9p0H6 N9xuboR+q1nQf52SFwdxBpaFe8oxDYnd9qF0IRaBCLjeo3SW83aFgVUPJ0VLi6Rz+6ds QCChPKu2a+OZWdfSNxz0buNSSrmvX54Cdk/6UapcwXbdDTAdAgIHc1xK+w4JSl3Fh8PL KRGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=znBmTmWbrra/OYjTkxnIPxribEEA4AB0oOiGcRO1fM4=; b=cFoa5c+WYSwv4mEqgI0oYnSK9xih0YBKfdf8svRAf2Y7zDwILmVPBt8zWgscdCNFSB fnlo6M/GK6Xaf5IRAyOuOsy77JVTHm+qscHK0dy5PtCfPsmFo1heExctHRiAvSTE1Dm1 aY4MRJ0RRoGJ3oxDK/qIxXjfnvwQTAAk53VfJruU5Vxbs+Q0AjopCNK1WCpBXETMU9gj qO250tEse7giKHHVCaraeU9JIglbjq6M74g0wffxPXlHXeRdfD81zodx5IZDBJj9Does gY1mtpxMS4abwat+JsqhjjjcI0R1JMmki4iL72KUMSNj0kEclVO8WS69dzdv/kZDOTQM 9LYA== X-Gm-Message-State: AJIora9UWj0Xk+uvYcSxNqihdwcq3zswGQNE4mIEFiqPEB3hgqfzdNa0 NSHDHE/GWxqEvJVeeiMLruYwsA== X-Google-Smtp-Source: AGRyM1v3jmzJ7ayv07Ch9djYz/ySqe3koVDpxqaTr3phOrx5yXav0xsji5TaHJDbSL8JsyIGcdO0dw== X-Received: by 2002:ac2:5509:0:b0:489:e7f9:75b9 with SMTP id j9-20020ac25509000000b00489e7f975b9mr4855400lfk.507.1657802034487; Thu, 14 Jul 2022 05:33:54 -0700 (PDT) Received: from [10.0.0.8] (fwa5da9-171.bb.online.no. [88.93.169.171]) by smtp.gmail.com with ESMTPSA id q27-20020a05651232bb00b00489de5012d4sm335536lfe.301.2022.07.14.05.33.52 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 14 Jul 2022 05:33:53 -0700 (PDT) Message-ID: Date: Thu, 14 Jul 2022 14:33:51 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH 1/2] dt-bindings: mailbox : marvell,mbox: Add bindings Content-Language: en-US To: Wojciech Bartczak , linux-kernel@vger.kernel.org Cc: wbartczak@gmail.com, Piyush Malgujar , Sunil Goutham , Jassi Brar , Rob Herring , Krzysztof Kozlowski , devicetree@vger.kernel.org References: <20220714121215.22931-1-wbartczak@marvell.com> <20220714121215.22931-2-wbartczak@marvell.com> From: Krzysztof Kozlowski In-Reply-To: <20220714121215.22931-2-wbartczak@marvell.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 14/07/2022 14:12, Wojciech Bartczak wrote: > This patch adds device tree binding for Marvell Message Handling Unit > (MHU) controller. > > Signed-off-by: Wojciech Bartczak > --- > .../mailbox/marvell,mbox-mailbox.yaml | 112 ++++++++++++++++++ > 1 file changed, 112 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mailbox/marvell,mbox-mailbox.yaml > > diff --git a/Documentation/devicetree/bindings/mailbox/marvell,mbox-mailbox.yaml b/Documentation/devicetree/bindings/mailbox/marvell,mbox-mailbox.yaml > new file mode 100644 > index 0000000000000000000000000000000000000000..d9a6e14dcb12da6c3a9db2dfafc075ccefa8711c > --- /dev/null > +++ b/Documentation/devicetree/bindings/mailbox/marvell,mbox-mailbox.yaml > @@ -0,0 +1,112 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/mailbox/marvell,mbox-mailbox.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Marvell Message Handling Unit > + > +maintainers: > + - Wojciech Bartczak > + - Piyush Malgujar > + > +description: > + The Marvell's Message Handling Unit is a mailbox controller > + with a single channel used to communicate with System Control Processor. > + Driver supports series of cn9x and cn10x SoC. Driver is not related to bindings, remove implementation details. > + Sole purpose of the link is to exchange SCMI related data with SCP. > + The link has hardwired configuration, it uses simple notification scheme > + over shared memory block to push data back and forth. > + Interrupts used by mailbox may be configured in two ways, > + as SPI interrupts, then driver uses platform device forntend. > + Other way is to use PCI bus frontend with LPI interrupts. > + > +properties: > + compatible: > + items: No "items", you have just one here, but see comment below. > + - const: marvell,mbox Need SoC or model specific compatible. Generic fallbacks are accepted if always prepended with specific compatible. Are you sure that all, absolutely all, including ones made in 20 years, of Marvell mboxes will be 100% compatible with "marvell,mbox"? > + > + reg: > + maxItems: 1 > + > + interrupts: > + items: > + - description: interrupt type > + const: 0 > + - description: interrupt number > + - description: interrupt trigger type > + const: 1 This looks wrong. You just specified here three interrupts, which are fixed... It does not make really sense. > + > + '#mbox-cells': > + description: Index of the channel Skip description, obvious. > + const: 1 > + > + shmem: > + description: > + List of phandle pointing to the shared memory area between SCP and AP. > + The area is used to exchange additional information not covered by SCMI. > + maxItems: 1 > + > +required: > + - compatible > + - reg > + - '#mbox-cells' > + - shmem > + > +additionalProperties: false > + > +examples: > + - | > + soc@0 { > + reg = <0 0>; > + #address-cells = <2>; Messed up indentation. While fixing it, convert to 4 space for DTS example, as recommended. > + #size-cells = <2>; > + > + sram@36,0 { > + compatible = "cpc-shmem"; > + reg = <0x86d0 0xdd400 0 0x200>; > + #address-cells = <2>; > + #size-cells = <1>; > + ranges = <0 0x0 0x86d0 0xdd400 0x200>; > + > + scp_to_cpu0: scp-shmame@0 { > + compatible = "cpc-shmem"; > + reg = <0x0 0x0 0x200>; > + }; > + }; Isn't smem a generic property and generic use case? If so, then drop this part, unless it brings anything specific to your mailbox example. > + > + mailbox0: mailbox@28,0 { > + #mbox-cells = <1>; First compatible, then reg then the rest of properties. > + compatible = "marvell,mbox"; > + reg = <0xe000 0 0 0>; > + shmem = <&scp_to_cpu0>; > + }; > + }; > + - | > + soc@1 { > + reg = <1 0>; > + #address-cells = <2>; > + #size-cells = <2>; > + > + sram@36,0 { > + compatible = "cpc-shmem"; > + reg = <0x86d0 0xdd400 0 0x200>; > + #address-cells = <2>; > + #size-cells = <1>; > + ranges = <0 0x0 0x86d0 0xdd400 0x200>; > + > + scp_to_cpu1: scp-shmame@1 { > + compatible = "cpc-shmem"; > + reg = <0x0 0x0 0x200>; > + }; > + }; > + > + mailbox1: mailbox@82c000000000 { > + #mbox-cells = <1>; > + compatible = "marvell,mbox"; > + reg = <0x82c0 0x00000000 0x0 0x100000>; > + interrupt-parent = <&gic0>; > + interrupts = <0 59 1>; These look like GIC and interrupt flags, so definitely not three interrupts. Use proper defines. > + shmem = <&scp_to_cpu1>; This is the same example as before, drop it or merge with previous. > + }; > + }; Best regards, Krzysztof