From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E2ABFC433F5 for ; Sun, 22 May 2022 10:27:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232098AbiEVK1E (ORCPT ); Sun, 22 May 2022 06:27:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43502 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230336AbiEVK1D (ORCPT ); Sun, 22 May 2022 06:27:03 -0400 Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 62BD53819E for ; Sun, 22 May 2022 03:27:01 -0700 (PDT) Received: by mail-lf1-x12b.google.com with SMTP id y32so21053237lfa.6 for ; Sun, 22 May 2022 03:27:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=fMNwqXeV2uBe+evUoLZgmTmVyGADR/eLkrGswoXQxA4=; b=aiibXUoW6fGLAoY6m08x9kmFx17Wpj3QAahbMWPFXr7lHKX9J/dIS0qEnZTETp7pR6 BXljZldyjeA/sEDbPTZZxFqRfCKzBghbv9+jA3nEv6XiAyYart5kdSwfL5uFBQFCW+4T SYYqBsbg6Zt+sYdVpHpUgJwkGnCl2FTaM3RyUOdqqd8Rk6MYRRvGgwtkng73huayt0mz 3fL2gI41mb+624m0aYB4Tavh50F77LNgianztzQs8PT4RvbA3dsYUgdeqTagB4s3pZSz IbcZGQDhTM0R8D0rSQa16x9DxmFB1/cyNMzcZZusyBUQChqAB1DH0BtZD6QBAvRtwZZ7 CaxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=fMNwqXeV2uBe+evUoLZgmTmVyGADR/eLkrGswoXQxA4=; b=SkBd4PFSBMsOqoYHfeA7EMTHEiHYnafBaqxSsYG4Ol4cvr0wLo5UvdkcbfhncgMLpk woq8O/gJtuHkyS5qkip1h/lf6CAJKAztvIYup/EMTap6cPA1xWSlLp7MOVs4rqWupVqf hoUE2IYIasLSIg4JLgECbygdkzD40O0MxB9JHb9G9VzAC6fLChYr89PEgksb7Sz3+OhU z5Bxe12GJDvOcZtnU7uwi7ogc/vvI/qCA3ZWhzhm/hnkfJF1Zf8WhyT2i1a3v4M0bdbe fgTeQTbZa6L7UhwtVP16amC+omxpLKz2n3A98dCN1WjvrUsqYt9nKhDh7kYghkhk4D7V sOrA== X-Gm-Message-State: AOAM5307oHfzuMSFxQHhZg7/jYF7BIlgIlVBxnH0jfmO6+g44RkGStAN UZ5Lg8MvF5QVJmQuyEAZW+9W101WVOAc6jzH X-Google-Smtp-Source: ABdhPJyOR4yZnga56TAbIe1Pgby+ggk+HW859Rb54J83gtSMzvrVoXi6kzlOGEy8W5sTI3Ees33A8Q== X-Received: by 2002:a05:6512:1585:b0:445:908b:ad71 with SMTP id bp5-20020a056512158500b00445908bad71mr12439284lfb.200.1653215219755; Sun, 22 May 2022 03:26:59 -0700 (PDT) Received: from [192.168.0.17] (78-11-189-27.static.ip.netia.com.pl. [78.11.189.27]) by smtp.gmail.com with ESMTPSA id f17-20020a056512093100b0047255d21162sm1403396lft.145.2022.05.22.03.26.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 22 May 2022 03:26:59 -0700 (PDT) Message-ID: Date: Sun, 22 May 2022 12:26:57 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: Removal of qcom,board-id and qcom,msm-id Content-Language: en-US To: Dmitry Baryshkov , Stephen Boyd Cc: Andy Gross , Arnd Bergmann , Bjorn Andersson , Olof Johansson , Rob Herring , "devicetree@vger.kernel.org" , linux-arm-msm , Linux Kernel Mailing List References: <35051bec-98ea-b4c5-f734-06b3f22f3562@linaro.org> <8a90ffbc-b376-9115-fb91-0b46d98873b7@linaro.org> <40f29157-52c0-001f-6c14-fb90b351756a@linaro.org> <20220519221227.B66D3C385AA@smtp.kernel.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 20/05/2022 03:39, Dmitry Baryshkov wrote: > >> >> I vaguely recall that the properties had to be extracted during the >> boot.img creation process to create a table of contents header. But >> after some time the bootloader started scanning the DTBs directly for >> the vendor properties and thus the header was deprecated/removed. If the >> bootloader is doing the scanning then I'm not sure what is preventing >> the properties from being documented and allowed. I think the main >> rejection was that the properties were added purely to be extracted >> during post processing and placed into the table of contents header, >> i.e. they weren't actually used by the kernel or the bootloader. If they >> are now used by the bootloader it sounds OK to me if they're kept >> around. > > Yes, as far as I understand, they are used by the bootloader directly. > I entirely missed one part - Stephen's patches from 2015 were actually applied and since 2015 we expect all boards to follow convention: compatible = "qcom,[-][-]-[/][-]" The patchset was accepted, although in the thread I do not see "Applied" message. Stephen, can you or anyone else confirm that the dtbTool Qualcomm uses (and/or bootloader) are adjusted as well to these new compatibles? If yes, we can simply remove board-id and msm-id properties from new boards, because 7 years was enough to switch to these new tools... Best regards, Krzysztof