From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Date: Thu, 05 Mar 2015 11:42:10 -0800 Message-ID: <7h8ufbjkod.fsf@deeprootsystems.com> References: <1425503602-24916-1-git-send-email-galak@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: 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") Sender: linux-arm-msm-owner@vger.kernel.org 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 List-Id: devicetree@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