From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757696AbbCETmQ (ORCPT ); Thu, 5 Mar 2015 14:42:16 -0500 Received: from mail-pa0-f53.google.com ([209.85.220.53]:41465 "EHLO mail-pa0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752756AbbCETmN (ORCPT ); Thu, 5 Mar 2015 14:42:13 -0500 From: Kevin Hilman To: Kumar Gala 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 Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id References: <1425503602-24916-1-git-send-email-galak@codeaurora.org> Date: Thu, 05 Mar 2015 11:42:10 -0800 In-Reply-To: <1425503602-24916-1-git-send-email-galak@codeaurora.org> (Kumar Gala's message of "Wed, 4 Mar 2015 15:13:20 -0600") Message-ID: <7h8ufbjkod.fsf@deeprootsystems.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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