From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kumar Gala Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Date: Thu, 5 Mar 2015 14:23:04 -0600 Message-ID: <07D4E4D1-BF8C-4583-9505-9F321DB10406@codeaurora.org> References: <1425503602-24916-1-git-send-email-galak@codeaurora.org> <7h8ufbjkod.fsf@deeprootsystems.com> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <7h8ufbjkod.fsf@deeprootsystems.com> Sender: linux-kernel-owner@vger.kernel.org To: Kevin Hilman Cc: linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, arm@kernel.org, devicetree@vger.kernel.org, heiko@sntech.de List-Id: devicetree@vger.kernel.org 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 - k -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project