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 87649C74A5B for ; Wed, 29 Mar 2023 03:41:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229522AbjC2Dlw (ORCPT ); Tue, 28 Mar 2023 23:41:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34966 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229544AbjC2Dlv (ORCPT ); Tue, 28 Mar 2023 23:41:51 -0400 Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DA9452728 for ; Tue, 28 Mar 2023 20:41:49 -0700 (PDT) Received: by mail-pj1-x102d.google.com with SMTP id qe8-20020a17090b4f8800b0023f07253a2cso14791894pjb.3 for ; Tue, 28 Mar 2023 20:41:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1680061309; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=zWa7wOxAFG7tdLlil0NzPbk6K8fs9R4JDMItxPB89Zk=; b=FLF2hx/aelGWFy3MQVxuI78e6bOjKUK0lDvmENJJpmng1+jiJwkepTsA6xcZ7bgyJL DmUnAcpXeCosXu57J8rd/T5bW2vQu2R18QhdAcLfCAYqBZYTe7ZOpng9pfU6q3pZLZWy bZ0xYsmqIJh9d+pDd+SvQtG1AcdGk5PjZL7mr06iuDiGUN2YyXXOWbosx+9jl89gm15+ tAhoQzr7B/nPPEHzzERhQigxMSOza9THTNsE4XgiryPRfsIjMZtlHOGDNlCN8/gDXP2k tUVI0zXENIL+47cZxozxrhKUktrd2ctQyctmqqGPMag5wvF1b81ZzC62uflLkKA237Jl jhFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680061309; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=zWa7wOxAFG7tdLlil0NzPbk6K8fs9R4JDMItxPB89Zk=; b=idzbrs6zhbDNl+zqDusA/8GvpqYd222vrawWDbi8EuorjdxN8xBfWc8U3jgMQxnKfz IvVE6cVDfF7H1jUJQLFjH5eNxVIL7ERFHKOYWL4Xms7ZSYFntD2R2jwP2x9aSVvw7k1r MGmqgf2LoZp09U4YpzLWM3oh8RLV0sSogUhs7v826MEwmukri8z+URfjJeX6wFJlkIzY VxkIlIZmV3Km9eQG8GQPTLfdIR5J3PTX5g7vxho4WFE66DXdwAMHNdPP5HZLfYSJRgMp ooAC5DtQWW9ZAxSYPbhoW1fb6N2ityLG8dc9XBtZYrvReHoAfQbMMmAjKv0wRdgbqOqe RevQ== X-Gm-Message-State: AAQBX9fMNLCX0shr8z8HUGL4kl0uzXHbAAvv5lamFSP8tP+QTO5gOhlY tKn8WvBQBkhqJUtulBz9rYwE3g== X-Google-Smtp-Source: AKy350Z9qGLrPtkmUBr4ckTpyxUSYvNDmeQ5iMJn6z0y5G7PURan5PkPuuuHsPMHlcFFJYajoaXeSw== X-Received: by 2002:a17:90b:4c0c:b0:233:d12f:f43a with SMTP id na12-20020a17090b4c0c00b00233d12ff43amr17346852pjb.1.1680061309170; Tue, 28 Mar 2023 20:41:49 -0700 (PDT) Received: from dragon (80.251.214.228.16clouds.com. [80.251.214.228]) by smtp.gmail.com with ESMTPSA id fh5-20020a17090b034500b0023b5566f744sm311482pjb.39.2023.03.28.20.41.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Mar 2023 20:41:48 -0700 (PDT) Date: Wed, 29 Mar 2023 11:41:41 +0800 From: Shawn Guo To: Konrad Dybcio Cc: Andy Gross , Bjorn Andersson , Thomas Gleixner , Marc Zyngier , Rob Herring , Krzysztof Kozlowski , Marijn Suijten , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH 1/2] dt-bindings: interrupt-controller: mpm: Allow passing reg through phandle Message-ID: <20230329034141.GB3554086@dragon> References: <20230328-topic-msgram_mpm-v1-0-1b788a5f5a33@linaro.org> <20230328-topic-msgram_mpm-v1-1-1b788a5f5a33@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230328-topic-msgram_mpm-v1-1-1b788a5f5a33@linaro.org> Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Tue, Mar 28, 2023 at 12:02:52PM +0200, Konrad Dybcio wrote: > Due to the wild nature of the Qualcomm RPM Message RAM, we can't really > use 'reg' to point to the MPM's slice of Message RAM without cutting into > an already-defined RPM MSG RAM node used for GLINK and SMEM. > > Document passing the register space as a slice of SRAM through the > qcom,rpm-msg-ram property. This also makes 'reg' no longer required. > > Signed-off-by: Konrad Dybcio > --- > .../devicetree/bindings/interrupt-controller/qcom,mpm.yaml | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/interrupt-controller/qcom,mpm.yaml b/Documentation/devicetree/bindings/interrupt-controller/qcom,mpm.yaml > index 509d20c091af..77fe5e0b378f 100644 > --- a/Documentation/devicetree/bindings/interrupt-controller/qcom,mpm.yaml > +++ b/Documentation/devicetree/bindings/interrupt-controller/qcom,mpm.yaml > @@ -30,6 +30,11 @@ properties: > description: > Specifies the base address and size of vMPM registers in RPM MSG RAM. > > + qcom,rpm-msg-ram: > + $ref: /schemas/types.yaml#/definitions/phandle > + description: > + Phandle to the APSS MPM slice of the RPM Message RAM > + > interrupts: > maxItems: 1 > description: > @@ -64,7 +69,6 @@ properties: > > required: > - compatible > - - reg It's not my call, but I wonder if we need to maintain the 'reg' ABI at all, as there is no DTS landed so far. In either case, I suggest we update the example to adopt the new way. Shawn > - interrupts > - mboxes > - interrupt-controller > > -- > 2.40.0 >