Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753683AbbDXD2Y (ORCPT ); Thu, 23 Apr 2015 23:28:24 -0400 Received: from mail-lb0-f180.google.com ([209.85.217.180]:32769 "EHLO mail-lb0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751597AbbDXD2V (ORCPT ); Thu, 23 Apr 2015 23:28:21 -0400 MIME-Version: 1.0 In-Reply-To: <55394F98.3060600@codeaurora.org> References: <1428795178-24312-1-git-send-email-bjorn.andersson@sonymobile.com> <55394F98.3060600@codeaurora.org> Date: Thu, 23 Apr 2015 20:28:19 -0700 Message-ID: Subject: Re: [PATCH v2 1/2] soc: qcom: Add device tree binding for SMEM From: Bjorn Andersson To: Jeffrey Hugo Cc: Bjorn Andersson , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Andry Gross , "devicetree@vger.kernel.org" , linux-arm-msm , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1015 Lines: 26 On Thu, Apr 23, 2015 at 1:01 PM, Jeffrey Hugo wrote: > On 4/11/2015 5:32 PM, Bjorn Andersson wrote: >> >> Add device tree binding documentation for the Qualcom Shared Memory >> manager. >> [..] > > For my information, is there any intention to support the relocatable > smem_region by looking it up at init time? It does not seem like it would > be possible to support that with this binding. > I haven't been able to grasp the purpose of making the smem addresses completely dynamic. As far as I can see there might be use cases where certain devices needs to move the smem region from the default area. But even so, it's not dynamically choosen so it's in essence static - so we can just encode it in the individual dts files. Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/