Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp470932ybl; Fri, 30 Aug 2019 02:33:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqzHLr/JtVe4pLWcVocNp566FisetHNWlp/GLq7JIBmqtNZS6rJ+PbCgWzlNbDt2Gv3xFRze X-Received: by 2002:a65:534c:: with SMTP id w12mr12272668pgr.51.1567157621882; Fri, 30 Aug 2019 02:33:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567157621; cv=none; d=google.com; s=arc-20160816; b=o8jSY5mB8sc8GG5Mu3D4sBHeCGKUekwLmEEllWQcq9YgnB4zR6JaQBFAiK3VRRJM6D OIeREZcZViLx/MMbKrFK1dsinqM+PAmJIHoS62glftBuwoLQUKoAj5uQcS+VodVmN2Ei L71MkNWJaCDB3TvjOAm2qV5IrMy4HPr2HVoizWccJO1ZzOhKdytd40bdB/kSfUyQgMT8 AxnjTd1u4vs/uh5CCm0NCftG7CZTL/WUCY0lLvzkaRjqkNC4UyJRqIPnSvP+8gvuRlYm Z17HchtdZ97VbyL59Lb53oSwqSmWUZDOkAavTrf5Q+xHyc+yYmlKjmmc0yttzKsMm/DP p7PQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=xXG66rTA6JtP9inqiBGoStiLMdcNO0kPgeVk0ErCLhc=; b=pm/Cz2UreFwPR22E358hkCFwaYwUPICHliPY9Kx1Pc63GE9k4c55Vqjr70UIJwOQ7F 5U+W1namILhP48emAZ6uRkDMVwmd80yMDklcpj2sx81JadLzT5ov64/yBAbfUpk2ak8n 9CD99olE2k2b7l6uUPkrBDiUTxzw97Zsx0Gqf+UJOmaVSSycLPkXkM1Vg0k74TvJEqFV 7zfPuRkUbQXItZVsYmy2YUwZkmVUKlps1yk+v4I9Iom6w7Tj8xgxl13V50eOPsZ/ALh7 uLxxD2aJGqCp1oGUAdQxY42g1u6IEDs5eXZhj4Rew/f5O7kXWR0PPoWFXJbyoXwkD/xZ qsPw== 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 f7si5624345pfq.93.2019.08.30.02.33.25; Fri, 30 Aug 2019 02:33:41 -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; 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 S1727991AbfH3Jc3 (ORCPT + 99 others); Fri, 30 Aug 2019 05:32:29 -0400 Received: from foss.arm.com ([217.140.110.172]:57128 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727236AbfH3Jc3 (ORCPT ); Fri, 30 Aug 2019 05:32:29 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5ADE6344; Fri, 30 Aug 2019 02:32:28 -0700 (PDT) Received: from bogus (e107155-lin.cambridge.arm.com [10.1.196.42]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E0C913F718; Fri, 30 Aug 2019 02:32:26 -0700 (PDT) Date: Fri, 30 Aug 2019 10:32:24 +0100 From: Sudeep Holla To: Jassi Brar Cc: Peng Fan , "robh+dt@kernel.org" , "mark.rutland@arm.com" , "andre.przywara@arm.com" , "f.fainelli@gmail.com" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , dl-linux-imx , Sudeep Holla Subject: Re: [PATCH v5 1/2] dt-bindings: mailbox: add binding doc for the ARM SMC/HVC mailbox Message-ID: <20190830093224.GB31297@bogus> References: <1567004515-3567-1-git-send-email-peng.fan@nxp.com> <1567004515-3567-2-git-send-email-peng.fan@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 30, 2019 at 02:52:40AM -0500, Jassi Brar wrote: > On Fri, Aug 30, 2019 at 2:37 AM Peng Fan wrote: [...] > > > > If I get your point correctly, > > On UP, both could not be active. On SMP, tx/rx could be both active, anyway > > this depends on secure firmware and Linux firmware design. > > > > Do you have any suggestions about arm,func-ids here? > > > I was thinking if this is just an instruction, why can't each channel > be represented as a controller, i.e, have exactly one func-id per > controller node. Define as many controllers as you need channels ? > I might have missed to follow this, but what's the advantage of doing so ? Which can't single controller instance deal with all the channels ? -- Regards, Sudeep