From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="v9/gjCb5"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="7KgWsTdQ" Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3D65C1712; Fri, 8 Dec 2023 06:33:16 -0800 (PST) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1702045994; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1ifPekkHiXm+lcwtuf5lbbYNKF0qvQaOPaFCAVY6Z3g=; b=v9/gjCb5yzOa/MONNnVonsIQDXSguuXkH6dOQXz1HZQnwcireIC9FcfuhQAiVx1BzFbNwk tJv2phQFVrHSaw7Dkzi1yU2JEL4P7E7Y63i5IYfTOXyJX5a1SmwYz7Ludayt6yCTremiSi 8+13LSJoMNwgznljoHKKeHY1tsyAJ4fX5m0TSpP64E3lYouhrVMhG67yBo5ghxr29pCOD8 7ExhXhQ8KfNxPKNGnLjI2zlhPmJqXLeApI0Cl7WPxSS1JkVFZv7vw/RW9Lwb+hJ6EWXdkA ZGpcr7zV8VqaaTZL+p549o4Ed8khn9o4NnXZm168z7pvEVy4dvu916MGnUoMfA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1702045994; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1ifPekkHiXm+lcwtuf5lbbYNKF0qvQaOPaFCAVY6Z3g=; b=7KgWsTdQrZJiDvbEvccaBFpNsVcf/LlEosW+NC3hpa9G7kMBm+bf9ksp/OmQSoU6EpCoU+ W+nlmI1tJxHN8lDQ== To: Konrad Dybcio , Andy Gross , Bjorn Andersson , Marc Zyngier , Rob Herring , Krzysztof Kozlowski , Shawn Guo , Conor Dooley Cc: Marijn Suijten , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Konrad Dybcio , Krzysztof Kozlowski , Bryan O'Donoghue Subject: Re: [PATCH v7 0/2] Resolve MPM register space situation In-Reply-To: <20230328-topic-msgram_mpm-v7-0-6ee2bfeaac2c@linaro.org> References: <20230328-topic-msgram_mpm-v7-0-6ee2bfeaac2c@linaro.org> Date: Fri, 08 Dec 2023 15:33:13 +0100 Message-ID: <87il58sr12.ffs@tglx> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Konrad! On Mon, Nov 27 2023 at 16:52, Konrad Dybcio wrote: This list of version changes is useful, but seriously not on top of the cover letter. It makes me scroll down 60 lines to find the real meat. > Depends on resolution of https://github.com/devicetree-org/dt-schema/issues/104 Is this resolved? I can't figure out from this non-format whether this belongs to V1 or to the actual cover letter... > The MPM (and some other things, irrelevant to this patchset) resides > (as far as the ARM cores are concerned, anyway) in a MMIO-mapped region > that's a portion of the RPM (low-power management core)'s RAM, known > as the RPM Message RAM. Representing this relation in the Device Tree > creates some challenges, as one would either have to treat a memory > region as a bus, map nodes in a way such that their reg-s would be > overlapping, or supply the nodes with a slice of that region. > > This series implements the third option, by adding a qcom,rpm-msg-ram > property, which has been used for some drivers poking into this region > before. Bindings ABI compatibility is preserved through keeping the > "normal" (a.k.a read the reg property and map that region) way of > passing the register space. > > Signed-off-by: Konrad Dybcio Signed-off-by on the cover letter is completely meaningless. Thanks, tglx