From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753074AbbCJRON (ORCPT ); Tue, 10 Mar 2015 13:14:13 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:43260 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751589AbbCJROK convert rfc822-to-8bit (ORCPT ); Tue, 10 Mar 2015 13:14:10 -0400 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id From: Kumar Gala In-Reply-To: <89746055.qtEO3GZJmR@wuerfel> Date: Tue, 10 Mar 2015 12:13:46 -0500 Cc: Olof Johansson , Kevin Hilman , linux-arm-msm , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "arm@kernel.org" , "devicetree@vger.kernel.org" , =?windows-1252?Q?Heiko_St=FCbner?= Content-Transfer-Encoding: 8BIT Message-Id: References: <1425503602-24916-1-git-send-email-galak@codeaurora.org> <89746055.qtEO3GZJmR@wuerfel> To: Arnd Bergmann X-Mailer: Apple Mail (2.1878.6) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mar 9, 2015, at 7:11 AM, Arnd Bergmann wrote: > On Friday 06 March 2015 14:37:52 Kumar Gala wrote: >> On Mar 6, 2015, at 1:15 PM, Olof Johansson wrote: >> >>> On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala wrote: >>>> >>>> On Mar 5, 2015, at 7:59 PM, Olof Johansson wrote: >>>> >>>>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala wrote: >>>>>> >>>>>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman wrote: >>>>>> >>>>>>> Kumar Gala writes: >>>>>>> >>>>>>>> The top level qcom,msm-id and qcom,board-id are utilized by bootloaders >>>>>>>> on Qualcomm MSM platforms to determine which device tree should be >>>>>>>> utilized and passed to the kernel. >>>>>>>> >>>>>>>> Cc: >>>>>>>> Signed-off-by: Kumar Gala >>>>>>> >>>>>>> Is this the special magic that allows qcom bootloaders to take a kernel >>>>>>> plus multiple DTBs and figure out which DTB to pass? >>>>>>> >>>>>>> Kevin >>>>>> >>>>>> yes >>>>> >>>>> That's a bummer. >>>>> >>>>> Luckily, the solution for upstream is still quite simple: Provide only >>>>> one devicetree, and it'll be used, right? >>>> >>>> We can provide only one, we still need the IDs in the DT. >>> >>> How are the DTS provided? Concatenated with the kernel, or in a >>> wrapped data format? Or in a separate partition from the kernel? >> >> Its a wrapped data format that is than concatenated with the kernel if I remember correctly. > > Then you should be able to create a tool that can write this concatenated > format and insert these properties from a table that matches the boot > loader, right? > > Arnd Are you suggesting the tool insert the properties in the DT? I’m not sure I understand what the point of doing that would be. - k -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project