From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753999AbbIHXTG (ORCPT ); Tue, 8 Sep 2015 19:19:06 -0400 Received: from seldrel01.sonyericsson.com ([37.139.156.2]:19999 "EHLO seldrel01.sonyericsson.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752310AbbIHXTD (ORCPT ); Tue, 8 Sep 2015 19:19:03 -0400 Date: Tue, 8 Sep 2015 16:18:58 -0700 From: Bjorn Andersson To: Stephen Boyd CC: Andy Gross , "linux-kernel@vger.kernel.org" , "linux-arm-msm@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH] soc: qcom: smem: Move RPM message ram out of smem DT node Message-ID: <20150908231858.GB13472@usrtlx11787.corpusers.net> References: <1441750812-13041-1-git-send-email-sboyd@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <1441750812-13041-1-git-send-email-sboyd@codeaurora.org> User-Agent: Mutt/1.5.22 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 08 Sep 15:20 PDT 2015, Stephen Boyd wrote: > SMEM is a software construct built on top of a DDR carveout and > sometimes a device memory called RPM message ram. Having the RPM > message ram in the smem DT node's reg property leads to the smem > node being located in different places depending on if the > message ram is being used or not. Let's add a qcom specific > property, qcom,rpm-msg-ram, and point to the device memory from > the SMEM node via a phandle. This allows us to always have the > SMEM node at the root of the DT regardless of whether it's using > the message ram or not. > Based on the codeaurora limit of 99 aux-mem regions I figured this had to be more generic. But I think this makes sense and we can easily extend it with other specific regions (if we ever find any of those other 98 supported aux-mems). Can you update the dt binding document as well? Regards, Bjorn